Customize FAILED! Help

Try looking for help here if you are having problems with the Ultimate Boot CD.

Moderators: Icecube, StopSpazzing

Locked
Message
Author
n0nuf
Posts: 9
Joined: Sun Jun 12, 2005 8:56 pm

Customize FAILED! Help

#1 Post by n0nuf » Sun Jun 12, 2005 9:16 pm

Hello. I have followed the directions on the customizing of UBCD. I have unpacked ISO to C:\UBCD. I have used Winimage to create the 1.44MB and 2.88 images of DOS boot disks. I have placed these images in: C:\UBCD\images. I have edited C:\UBCD\boot\menus\custom.scn with the following:

#
# User-defined Tools
#
custom_menu:
set textColor = color[white on black]
clear
set textColor = color[yellow on blue]
print " ULTIMATE BOOT CD VER 3.3 "
print " http://www.ultimatebootcd.com/ "
print " "
set textColor = color[white on red]
print " [User-defined Tools] "
set textColor = color[white on cyan]
print " "
set textColor = color[grey on cyan]
print " Please read the [Customizing Ultimate Boot CD] in ubcd/index.html first to "
print " understand how to create and add your own boot images to this CD. "
print " "
print " The menu file for this screen is found in boot/menus/custom.scn. Use any "
print " standard text editor to modify the file to add your own boot images. Make sure "
print " you modify the [Actions] section below to add your own key mappings to launch "
print " the user-defined boot images. "
set textColor = color[white on cyan]
print " "
set textColor = color[yellow on cyan]
print " User-defined Section "
set textColor = color[white on cyan]
print " [F1] PowerQuest Drive Image 2K 2.88MB "
print " [F2] PQDI2K (other) "
print " [F3] Dos 6.22 "
print " [F4] Win 98 Rescue "
print " "
print " "
print " "
print " "
print " "
set textColor = color[white on blue]
print " Please select an item (ESC returns to main menu) "
set textColor = color[white on black]
#
# Actions
#
getkey
clear
if ($lastKey == key[f1]); then diskemu /images/pqdi2k288.imz
if ($lastKey == key[f2]); then diskemu /images/pqdi2k.imz
if ($lastKey == key[f3]); then diskemu /images/dos622.imz
if ($lastKey == key[f4]); then diskemu /images/win98.imz
if ($lastKey == key[esc]); then script main.scn
goto custom_menu


I have tried diskemu AND memdisk when writing this script. UBCD burns, and boots correctly. But, when I go into [F5] to the user area, and attempt to boot ANY of my images (with either diskemu or memdisk) I get dumped to command prompt with:

Error: File not found.
[Command: diskemu (or memdisk if used)] [Line: 46.2] [File: custom.scn]

I have the cdrtools with mkisofs and all that in a directory with the PATH= set to include them. This is the cmd line from WinXP that I use to make the ISO:

mkisofs -N -J -r -o \ubcd.iso -b boot/loader.bin -no-emul-boot -boot-load-size 4 .

Anyone have any ideas/help?

Thanks in advance.

Scott - n0nuf

n0nuf
Posts: 9
Joined: Sun Jun 12, 2005 8:56 pm

Menu does not work...

#2 Post by n0nuf » Mon Jun 13, 2005 10:01 am

Well, I find that the menu SCR does not work. BUT, if I use F10 and drop directly to command prompt from UBCD, that I can manually boot an image using memdisk [image].

Anyone know if there's a bug in the menu? Can anyone see a problem with my script above?

Thank you,
n0nuf

bldrdash
Posts: 101
Joined: Thu Feb 24, 2005 10:04 am

Customize FAILED! Help

#3 Post by bldrdash » Mon Jun 13, 2005 10:03 am

Diskemu does not support compressed images. Uncompress
the images and use .img for your image names.

n0nuf
Posts: 9
Joined: Sun Jun 12, 2005 8:56 pm

No Compression

#4 Post by n0nuf » Mon Jun 13, 2005 11:50 am

None of the images I'm using are compressed. They are created with WinImage6.

n0nuf

bldrdash
Posts: 101
Joined: Thu Feb 24, 2005 10:04 am

Customize FAILED! Help

#5 Post by bldrdash » Mon Jun 13, 2005 12:01 pm

Save it as an .IMA file and change your custom.scn
appropriately. In WinImage, .IMZ is a zlib compressed
image, which none of the boot loaders support.

n0nuf
Posts: 9
Joined: Sun Jun 12, 2005 8:56 pm

Really?

#6 Post by n0nuf » Mon Jun 13, 2005 12:14 pm

Really? Well, didn't know that. Still, it must be something with the menu system. Because, like I said above, I can drop to command and "memdisk pqdi2k28.imz" and it works. Ok, I'll give this a shot.

Thanks for the info.

n0nuf

bldrdash
Posts: 101
Joined: Thu Feb 24, 2005 10:04 am

Customize FAILED! Help

#7 Post by bldrdash » Mon Jun 13, 2005 12:22 pm

> Really? Well, didn't know that. Still, it must be something
> with the menu system. Because, like I said above, I can drop
> to command and "memdisk pqdi2k28.imz" and it works. Ok,
> I'll give this a shot.

OK, then I must be wrong about .IMZ being zlib or memdisk only
supporting gzip format. In any event, the custom.scn file
you posted uses diskemu, not memdisk. If your images work
with memdisk, then simply change your custom.scn file to use
it instead. Example:
if ($lastKey == key[f1]); then memdisk /images/pqdi2k288.imz

n0nuf
Posts: 9
Joined: Sun Jun 12, 2005 8:56 pm

well...

#8 Post by n0nuf » Mon Jun 13, 2005 6:58 pm

Well, you're not wrong. If you read a little closer, I've stated that I have tried BOTH memdisk and diskemu. You were right about the IMZ being compressed. I checked in the TYPE dialog while saving. I changed all images to IMA. Still, I can boot them from the command prompt, but not from the menu system using either method.

n0nuf

Victor Chew
Posts: 1363
Joined: Mon Feb 21, 2005 10:59 pm
Contact:

#9 Post by Victor Chew » Mon Jun 13, 2005 10:09 pm

Just want to confirm.. at the console prompt, did you type:

Code: Select all

memdisk /images/xxx.imz
or:

Code: Select all

memdisk xxx.imz
It is a long shot, but I am just wondering whether it is a path problem i.e. your user images are not placed in /images.

I suspect it should not be something too complicated, since the CDShell scripting engine is quite robust and does not choke on something like this.

bldrdash
Posts: 101
Joined: Thu Feb 24, 2005 10:04 am

Customize FAILED! Help

#10 Post by bldrdash » Tue Jun 14, 2005 6:43 am

My apologies for not reading your original post more
carefully. I still don't understand why the .IMZ images
worked at all since, unless I've missed something in the
changelogs of CDShell, that format isn't supported.

Assuming your back to using .IMA files, please post the
exact line you're typing in at the command line that
works as Victor suggested.

Another thing to try is to re-create your custom.scn
file. Make it simple:

####
custom_menu:
clear
print " [F1] PowerQuest Drive Image 2K 2.88MB "
print " [F2] PQDI2K (other) "
print " [F3] Dos 6.22 "
print " [F4] Win 98 Rescue "
getkey 500 script main.scn
if ($lastKey == key[f1]); then memdisk /images/pqdi2k288.ima
if ($lastKey == key[f2]); then memdisk /images/pqdi2k.ima
if ($lastKey == key[f3]); then memdisk /images/dos622.ima
if ($lastKey == key[f4]); then memdisk /images/win98.ima
if ($lastKey == key[esc]); then script main.scn
goto custom_menu
####

If, by accident you've got hidden control characters in your
menu file, it might be causing problems with CDShell.

n0nuf
Posts: 9
Joined: Sun Jun 12, 2005 8:56 pm

Line...

#11 Post by n0nuf » Tue Jun 14, 2005 10:49 am

From the command prompt I just type...


memdisk /images/pqdi2k28.ima (worked with .imz before I changed it)

and that kicks it off. ok?

Another question... When my image is booted... I DO NOT have access to my local hard drives as I do when I just boot a floppy disk. Is there a reason for this? This same disk booted in a 3.5" floppy drive will allow access to my hard drives.

Thanks again for the help..

n0nuf

n0nuf
Posts: 9
Joined: Sun Jun 12, 2005 8:56 pm

#12 Post by n0nuf » Tue Jun 14, 2005 10:53 am

Victor Chew wrote:Just want to confirm.. at the console prompt, did you type:

Code: Select all

memdisk /images/xxx.imz
or:

Code: Select all

memdisk xxx.imz
It is a long shot, but I am just wondering whether it is a path problem i.e. your user images are not placed in /images.

I suspect it should not be something too complicated, since the CDShell scripting engine is quite robust and does not choke on something like this.

My images ARE in /images . Or in the windows path (before burning the CD) c:\ubcd\images ... I have just changed my files to uncompressed IMA. Like I said in my previous post, the line I typed BEFORE using uncompressed images was:

memdisk /images/pqdi2k28.imz

now that I have changed all files and reburnt the CD the command is:

memdisk /images/pqdi2k28.ima


Ok? All I know is that I got it to work, but NOT from the menu system.

Thanks for the help.

n0nuf

n0nuf
Posts: 9
Joined: Sun Jun 12, 2005 8:56 pm

One more thing...

#13 Post by n0nuf » Tue Jun 14, 2005 10:56 am

Don't know if it matters, but I noticed while in UBCD command prompt... When doing a DIR, the files are trunc'd to 8 chars. So I renamed the pqdi2k288.ima to pqdi2k28.ima. I changed the custom.scn to reflect this also.

Just to clear up my first post, and correct the file name in this thread.

n0nuf

Administrator
Site Admin
Posts: 12
Joined: Mon Feb 21, 2005 8:30 pm

#14 Post by Administrator » Tue Jun 14, 2005 7:22 pm

Oh, that slipped my mind. The filenames for the floppy images need to be in 8.3 format, since long filenames are not supported at that stage.

After changing your image files to 8.3 format, it works now from the custom menu, doesn't it?

Victor Chew
Posts: 1363
Joined: Mon Feb 21, 2005 10:59 pm
Contact:

#15 Post by Victor Chew » Tue Jun 14, 2005 7:25 pm

BTW, if renaming to 8.3 format still doesn't work for you, make a one-image ISO, zip it up and email to me (remove everything else, dosapps, images etc.; should be below 3MB). I can try to help you find out what's wrong.

n0nuf
Posts: 9
Joined: Sun Jun 12, 2005 8:56 pm

Think...

#16 Post by n0nuf » Wed Jun 15, 2005 12:25 pm

Hey, think I have it now. Now images are uncompressed, in 8.3 filename format. The *28.img works now. :P Must have been the combination of several factors.

Thanks for all the help!

n0nuf

Locked