Page 1 of 1

Corrections and suggestions for Customize page

Posted: Sat May 15, 2010 2:42 pm
by Icecube
http://www.ultimatebootcd.com/customize.html
First, extract all the files on the UBCD to a directory on your harddisk such as c:\ubcd-exracted. If you wish, you can directly extract the files from the ISO image using a tool such as WinISO, Daemon Tools or 7-Zip.
Put 7-zip first ==> freeware (useful for extracting other archives too).
Don't recommend ISO editors like WinISO, UltraISO, ... (you have to pay for it too), because modifiying an ISO with such tools won't always result in a good ISO.

I am not sure about this, so here I ask:
Do all scripts work when UBCD is extracted to a path with spaces in the name?
If not mention it explicitly.

In the "Adding floppy disk images", http://www.woundedmoon.org/win32/floppyimage.html is a dead link.

Maybe another example than Partition Magic could be used as example. Partition Magic can easily destroy partitions (because it doesn't understand new partition schemes correctly).
Adding FreeDOS-based applications

To add a DOS app to UBCD that is launched via FreeDOS, create a CAB archive of the application files. For example, if the program contains the following files:

myapp.exe
myapp.dat

Create the CAB archive by typing:

cabarc -r -p -m lzx:21 n myapp.cab *
Mention that you need to create a directory to which you add the myapp.exe and myapp.dat files.
cd to this directory.
run: cabarc -r -p -m lzx:21 n myapp.cab *
Or maybe even better, create the myapp.cab file in the directory one level up.
The format for each entry in the INI file can be found here. Section names should only contain numbers, letters and spaces.
Mention what each parameter does at this location, instead of referring to my post on the forum.
Generating customized ISO image

At the command prompt, type:

cd \ubcd-extracted\ubcd\tools\win32\ubcd2iso
ubcd2iso c:\ubcd-extracted c:\ubcd40.iso

This will create ubcd50.iso in C:\.
It should be c:\ubcd50.iso :wink:
But I think it is better to use another name for the iso in the example, so the official UBCD ISO won't get overwritten by accident:

Code: Select all

cd \ubcd-extracted\ubcd\tools\win32\ubcd2iso
ubcd2iso c:\ubcd-extracted c:\myubcd50.iso
Correct to:
For those running Linux, the equivalent tools for syslinux2grub4dos, ubcd2iso and ubcd2usb etc. are available under ./ubcd-extracted/ubcd/tools/linux.
Also add (linux section):
It might be possible that you need to make the tools executable:
$ cd ./ubcd-extracted/ubcd/tools/linux
$ chmod a+x ./*/*.sh
$ chmod a+x ./ubcd2usb/syslinux

Posted: Sun May 16, 2010 4:21 pm
by Victor Chew
Thanks for the suggestions! I have updated/corrected based on all your points.

In addition, I have added a new section on booting ISO images.

Lemme know what you think.

Posted: Mon May 17, 2010 6:25 am
by Icecube
Good job! :D
In addition, I have added a new section on booting ISO images.
Recently, I added almost all stuff that you can see on the MEMDISK wiki page ;). I hope you like it. If you have any suggestions, let me know.

Can you change:

Code: Select all

LINUX /boot/syslinux/memdisk
INITRD /ubcd/custom/win98.iso.gz
APPEND raw iso
To:

Code: Select all

LINUX /boot/syslinux/memdisk
INITRD /ubcd/custom/win98.iso.gz
APPEND iso raw
It isn't wrong of course, but I think it looks more logical when you specify 'iso' first when you want to boot an ISO image (read 'raw' isn't always needed to boot ISO's, 'iso' is).

A link to the Syslinux website would be nice too (to understand the config files):
General Syslinux stuff: http://syslinux.zytor.com/wiki/index.ph ... YSLINUX.3F
menu.c32 specific stuff: http://syslinux.zytor.com/wiki/index.ph ... t/menu.c32
Maybe a link to the Grub4DOS tutorial could be added too:
http://diddy.boot-land.net/grub4dos/Grub4dos.htm

On the download page:
Now you need to burn the ISO image to CD. This is another topic that frequently trips up newbies who are not familiar with their CD recording software, such as Nero or Easy CD Creator. Some of you end up burning the ISO file itself to the CD, or some other weird results. The easiest way to burn the ISO file to CD is to use a small specialized freeware such as BurnCDCC or Active@ ISO Burner. Where possible, experiment with CDRW discs instead of CDR discs so that you can start over if something goes wrong, instead of churning out coasters
Add a link to: http://iso.snoekonline.com/iso.htm
It shows the steps you need to take to burn correctly an ISO to a CD-R(W) with various burning applications (Freeware and Commerial).

Posted: Mon May 17, 2010 12:57 pm
by Victor Chew
It isn't wrong of course, but I think it looks more logical when you specify 'iso' first when you want to boot an ISO image (read 'raw' isn't always needed to boot ISO's, 'iso' is).
Done!
A link to the Syslinux website would be nice too (to understand the config files):
Added under an additional section called "Resources".
That link is actually available under the "Tutorials" section (with other CD burning tutorials), so I have added a link to "Tutorials" instead.

Posted: Tue Jun 01, 2010 3:54 am
by phoenix00
I found the cabarc -p parameter (saving full path into the .cab) isn't really needed. Kept wondering why the custom .cab archives I created had all the original directories!

Code: Select all

cd \myapp
cabarc -r -m lzx:21 n c:\ubcd-extracted\ubcd\custom\myapp.cab *

Posted: Thu Jun 03, 2010 1:45 pm
by Victor Chew
The "-p" parameter is required to save subdirectory names.

eg. With "-p":

Code: Select all

cabarc l test.cab
app.exe
app.dat
lng\eng.lng
lng\ger.lng
eg. Without "-p":

Code: Select all

cabarc l test.cab
app.exe
app.dat
eng.lng
ger.lng