[Halonix]

I am trying to create a bootable CD with an unattended install of 2003 (which works fine on its own) and Windows PE. I was trying to use the Multiboot DVD tutorial as my reference. I did everything that was instructed in the tutorial but I cannot boot from the CD. I understand the PE one, I get a NTLDR missing error. But I am also unable to boot the 2003 install. I get a Code 5 error. I did everything just as instruted in the tutorial with some minor directory name changes. I edited all the bin files with Hex workshop, using only caps, and I created the ISO with cdimage. Im not sure what Im doing wrong here. Also, I edited my cdshell.ini file from the sample in the tutorial taking out only obviously non-crucial things, and changing some of the menu items. But when it boots off the CD it loads straight into a cdshell screen with some sample script buttons and stuff. I actually have to go to the command line and chain my dat files to load them. If Im doing something worng please let me know.

 multibootroot.JPG (62K)
Number of downloads: 107
 cdboot.JPG (34.55K)
Number of downloads: 99

This post has been edited by Halonix: 26 September 2005 - 05:33 PM

[LiquidSage]

The boot folders must be 4 characters...no more, no less.

If this was my cd. i would....
- Change WINPE back to I386 since it is that by default and it is easier to add to other distrosin the future. Also relieves minor naming convention problems that you could run into.
- Change WiIN2003 just to 2003 since you only have one 2003 OS in this distro.

Don't forget to edit SETUPLDR.BIN in each of the boot folders as well as the bootable dat files accordingly. Also, since mistakes are bound to be made, it wouldn't hurt to double check your OS path in txtsetup.sif

Have Fun

This post has been edited by LiquidSage: 26 September 2005 - 07:52 PM

[Halonix]

LiquidSage, on Sep 26 2005, 06:50 PM, said:

The boot folders must be 4 characters...no more, no less.

If this was my cd. i would....
- Change WINPE back to I386 since it is that by default and it is easier to add to other distrosin the future. Also relieves minor naming convention problems that you could run into.
- Change WiIN2003 just to 2003 since you only have one 2003 OS in this distro.

Don't forget to edit SETUPLDR.BIN in each of the boot folders as well as the bootable dat files accordingly. Also, since mistakes are bound to be made, it wouldn't hurt to double check your OS path in txtsetup.sif

Have Fun
<{POST_SNAPBACK}>

Good to know I will change them all back to 4 chars. I dont think it said that in the tutorial, though all of his folders were only 4 characters. Yea I edited all of the setupldr.bin files as well as the txtsetup.sif files. In fact I have heavily modified my 2003 sif file to copy a bunch of other software to the install as well. Thank you very much for the advice, I will give that a shot.

Any idea why Im geting that cdshell screen instead of my custom menu?
here is my cdshell.ini

boot:
cls
print "\n"
print "Press Enter to boot from CD... \n"
getkey 5 boot 0x80
if $lastKey == key[enter]; then goto time
# When no key found...
goto boot

# Function to display time of day
time:
set hour = $timeHour
set ampm = "am"
if $timeHour > 12; then set hour = $timeHour - 12
if $timeHour > 12; then set ampm = "pm"
set time = "$hour:$timeMinute$ampm"

# Function to display date
date:
set month = "n/a"
if $dateMonth == 1; then set month = "Jan."
if $dateMonth == 2; then set month = "Feb."
if $dateMonth == 3; then set month = "Mar."
if $dateMonth == 4; then set month = "Apr."
if $dateMonth == 5; then set month = "May."
if $dateMonth == 6; then set month = "Jun."
if $dateMonth == 7; then set month = "Jul."
if $dateMonth == 8; then set month = "Aug."
if $dateMonth == 9; then set month = "Sep."
if $dateMonth == 10; then set month = "Oct."
if $dateMonth == 11; then set month = "Nov."
if $dateMonth == 12; then set month = "Dec."
set date = "$month$dateDay,$dateYear"

# Printing the Interface
menu:
set textColor= color[grey on black]
set boldColor= color[cyan on black]
cls
print c "\n\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ<\c0B$time $date\cXX>ÄÄ \n\n"
print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n"
print "1)  Windows Server 2003 Corporate \n"
print "2)  Windows Pre-Installation Environment \n"
print "\n"
print "Q)  Quit to Command Prompt \n"
print "R)  Reboot \n"
print "ESC) Boot 1st Harddisk \n"
print c "\n"

MainKey:
getkey 20 boot 0x80
if $lastKey == key[1]; then chain /WIN2003.DAT
if $lastKey == key[1]; then chain /WINPE.DAT
if $lastKey == key[q]; then end
if $lastKey == key[r]; then reboot
if $lastKey == key[F1]; then goto Help
if $lastKey == key[esc]; then boot 0x80


end

[Screwz Luse]

uuummm.. I'm not sure but usually cdshell.ini is in the cdshell folder (usually named /BOOT/, although I have it named CDSH on my DVD and hex edited so that it points to /CDSH/ instead of /BOOT/). I don't have my cdshell.ini file in the root of my dvd.

And noticed that you have

if $lastKey == key[F1]; then goto Help

even though you have no Help section. That won't cause any problems (unless someone hits F1), but just something I thought I'd point out.

This post has been edited by Screwz Luse: 27 September 2005 - 10:37 AM

[Halonix]

Screwz Luse, on Sep 27 2005, 09:36 AM, said:

uuummm..  I'm not sure but usually cdshell.ini is in the cdshell folder (usually named /BOOT/, although I have it named CDSH on my DVD and hex edited so that it points to /CDSH/ instead of /BOOT/).  I don't have my cdshell.ini file in the root of my dvd.

And noticed that you have

if $lastKey == key[F1]; then goto Help

even though you have no Help section.  That won't cause any problems (unless someone hits F1), but just something I thought I'd point out. 
<{POST_SNAPBACK}>

I had it in the BOOT folder as well, I wasnt quite sure where to put it so I put it in both places. I got Windows PE to boot, but now I seem to be having issues getting my 2003 setup to load. I get a NTLDR is corrupt message.

[Halonix]

I did the winnt32.exe /noreboot method... but that method does not seem to copy the NTLDR file to the ~BT directory which I renamed to 3STD.

[LiquidSage]

are you using 2003 w/ sp1?

[Halonix]

LiquidSage, on Sep 28 2005, 09:36 AM, said:

are you using 2003 w/ sp1?
<{POST_SNAPBACK}>

Yes I am... I slipstreamed it into the installation first thing. Is that a problem?

[Screwz Luse]

uuummm... I believe there still is a problem with 2003. You can view the sticky about it.....