Page 1 of 1
winnt32.exe /noreboot
#1
Posted 08 July 2004 - 11:05 AM
i tryed everything but the string "winnt32.exe /noreboot" doesn't work with me.
i get the same error to: CDBOOT: cannot boot from cd - Code 5
i did everything acording the manual... like 7 times now.
i tryed it with and without SP1???
still get the same problem.
please help!!!
i get the same error to: CDBOOT: cannot boot from cd - Code 5
i did everything acording the manual... like 7 times now.
i tryed it with and without SP1???
still get the same problem.
please help!!!
#2
Posted 08 July 2004 - 11:11 AM
my cd shell.ini looks like this..
i only changed: Press Enter to boot from DVD...
in to dutch.. changed it back to english din't work either.??
HELP
boot:
cls
print "\n"
print "Druk op Enter om te starten vanaf DVD... \n"
getkey 5 boot 0x80
if $lastKey == key[enter]; then goto menu
goto boot
menu:
set textColor= color[grey on black]
set boldColor= color[cyan on black]
cls
print "1) Windows XP Professional Corporate \n"
print "2) Windows XP Professional OEM \n"
print "3) Windows XP Professional Engels \n"
print "\n"
print "Q) Dit menu afsluiten \n"
print "R) Opnieuw opstarten \n"
print "ESC) Opstarten vanaf vaste schijf \n"
print c "\n"
MainKey:
getkey 20 boot 0x80
if $lastKey == key[1]; then chain \PRO2.DAT
if $lastKey == key[2]; then chain \PRO3.DAT
if $lastKey == key[3]; then chain \PRO1.DAT
if $lastKey == key[q]; then end
if $lastKey == key[r]; then reboot
if $lastKey == key[esc]; then boot 0x80
end
i only changed: Press Enter to boot from DVD...
in to dutch.. changed it back to english din't work either.??
HELP
boot:
cls
print "\n"
print "Druk op Enter om te starten vanaf DVD... \n"
getkey 5 boot 0x80
if $lastKey == key[enter]; then goto menu
goto boot
menu:
set textColor= color[grey on black]
set boldColor= color[cyan on black]
cls
print "1) Windows XP Professional Corporate \n"
print "2) Windows XP Professional OEM \n"
print "3) Windows XP Professional Engels \n"
print "\n"
print "Q) Dit menu afsluiten \n"
print "R) Opnieuw opstarten \n"
print "ESC) Opstarten vanaf vaste schijf \n"
print c "\n"
MainKey:
getkey 20 boot 0x80
if $lastKey == key[1]; then chain \PRO2.DAT
if $lastKey == key[2]; then chain \PRO3.DAT
if $lastKey == key[3]; then chain \PRO1.DAT
if $lastKey == key[q]; then end
if $lastKey == key[r]; then reboot
if $lastKey == key[esc]; then boot 0x80
end
#3
Posted 08 July 2004 - 11:17 AM
first.....
http://www.msfn.org/...showtopic=21582
second...
THe problem has NOTHING to do with CDSHELL, but rather you editing of your DAT files, and SETUPLDR.BIN
Recreate them, and be sure that the folder names are correct, and that you use CAPITOL LETTERS WHEN HEXING
http://www.msfn.org/...showtopic=21582
second...
THe problem has NOTHING to do with CDSHELL, but rather you editing of your DAT files, and SETUPLDR.BIN
Recreate them, and be sure that the folder names are correct, and that you use CAPITOL LETTERS WHEN HEXING
#4
Posted 08 July 2004 - 11:51 AM
i did that all acording to the dutch book and the english site. nothing works.
i tryed to extract a new boot sector with isobuster.
i changed the name into PRO1.DAT and tryed to hex it..
it says somthing like parameters wrong ?? i dont know what it means.
help help
i tryed to extract a new boot sector with isobuster.
i changed the name into PRO1.DAT and tryed to hex it..
it says somthing like parameters wrong ?? i dont know what it means.
help help
#5
Posted 08 July 2004 - 12:30 PM
screenshots help when I have no idea what you're talking about 
ERROR CODE 5 is typically cause by bad hexing. It matters if you use CAPITAL letters or not. Not in the file names, but when hexing. Be sure you're also hexing SETUPLDR.BIN correctly as well...
ERROR CODE 5 is typically cause by bad hexing. It matters if you use CAPITAL letters or not. Not in the file names, but when hexing. Be sure you're also hexing SETUPLDR.BIN correctly as well...
#6
Posted 08 July 2004 - 02:01 PM
i did everything acording the manual in internet, including the capitals.
i can't give any pics. at the moment but they will come, my comp. is in dutch but i have an english one to, ill try there to get an pic.
i have no idea what i do wrong, i checkt everything 3x and eveything is like the manual says..
could it maby be that my OS that i want to put on DVD is in dutch??
or that my OS verion that i'm working with is in dutch ??
i think it doesn't matter becouse i want to put an english version to and that doesn't work ether??
maby i put cd shell files wrong ??
the hexing went fine and acording manual i checked it an it is with capitals.
i can't give any pics. at the moment but they will come, my comp. is in dutch but i have an english one to, ill try there to get an pic.
i have no idea what i do wrong, i checkt everything 3x and eveything is like the manual says..
could it maby be that my OS that i want to put on DVD is in dutch??
or that my OS verion that i'm working with is in dutch ??
i think it doesn't matter becouse i want to put an english version to and that doesn't work ether??
maby i put cd shell files wrong ??
the hexing went fine and acording manual i checked it an it is with capitals.
#7
Posted 08 July 2004 - 02:29 PM
It's not CDShell....
It's something when you modified the files.....
It's something when you modified the files.....
#8
Posted 09 July 2004 - 12:03 AM
the Gosh method with /norebbot way doesn't work for server 2003 :-) any chance to get it work?
#9
Posted 09 July 2004 - 09:55 AM
the Gosh Method? Reducing Source and then adding it to Multiboot?
#10
Posted 09 July 2004 - 10:03 AM
/noreboot doesn't work here at all ???
maby thats the problem for me that i can't get it to work ??
maby thats the problem for me that i can't get it to work ??
#11
Posted 09 July 2004 - 12:44 PM
alright.....
look....
CODE ERROR5 is a problem with booting the NT shell, NOT CDSHELL or ANYTHING IN WINDOWS. It can't find certain files.
look....
CODE ERROR5 is a problem with booting the NT shell, NOT CDSHELL or ANYTHING IN WINDOWS. It can't find certain files.
#12
Posted 10 August 2004 - 03:40 PM
It is in these situations, where you don't know where the problem lies, that a good multi-boot maker comes into play. With EasyBoot, you know for sure that it works (if there was no user error
), and don't need to bother fixing it for bugs in code - you can concentrate on what you are doing instead of dealing with the boot-loader.
Get EasyBoot here.
Get EasyBoot here.
Share this topic:
Page 1 of 1



Help
Back to top









