WINXPSP2_FAN Posted August 11, 2004 Posted August 11, 2004 I used to use BCDW [bOOTABLE CD WIZARD] http://bootcd.narod.ru/index_e.htm a long time ago.every thing was ok and pretty cool.suddenly when i got sp2 final i decided to slipstream windows xp sp2 cd.i did every thing ok.i got i good cd.but as you know with ONLY one boot option.so where is the problem?i wanted to make the cd multiboot with some other soft options like ghost ,acronis ,partition magic ,etc...i know what to do in this case since i have been using the BCDW 4 2 years.i linked the bootcat.ini to [setupldr.bin] as i used to do in all my previous successfull cds,but when i booted the cd,the menue appears ok.but when i choose the line containing the option of setup win xp sp2 and press [inter] ,THE COMPUTER RESTART and SO on.on virtual pc ,i got the following error:an unrecoverable processor error the virtual machine will reset nowcan any one help please.here is my configHERE IS MY BOOTCAT.INIC:\ ; Boot from drive C: ; BOOT from a hard disk.:reboot ; Reboot ; ^ Reboot computer\IMABOOT_KH\HIREN6.IMG ; HIREN BOOT CD 6.0 \IMABOOT_KH\DOS.IMA ; BOOT D O S With Smart Drive\WPRO\SETUPLDR.bin ; INSTALL WINDOWS XP SP2 [AUTOMATIC]\WPRN\SETUPLDR.bin ; INSTALL WINDOWS XP SP2 [NORMAL]\INI_FOLDER\ACRONIS.INI ; ACRONIS UTILITIES
WINXPSP2_FAN Posted August 11, 2004 Author Posted August 11, 2004 yes i replaced the 4 [i386] with [WPRO] USING ultraedit.
Jotnar Posted August 11, 2004 Posted August 11, 2004 Haven't used BCDW, just isolinux, but don't you have to load the (hexedited) cdrom bootsector instead of setupldr.bin? ie....bootsect.bin tells where setupldr.bin is located which tells where txtsetup.sif is located which in turn tells where the install files reside.Cheers
WINXPSP2_FAN Posted August 11, 2004 Author Posted August 11, 2004 yes i had done that earlier and it was ok.i made a BOOTSECT.DAT on the root of cdthen i edited its content to refer to WPRO\SETUPLDR.BINand of course i edited SETUPLDR.BIN to refer to WPRO not to i386moreover i put the [txtsetup.sif] in WPROthe txtsetup.sif refer to path=\all is ok by this method as you said.BUT my question is why the setupldr.bin of sp2 did NOT load when i linked it directlyto the BCDW,as was previously ok in case of sp1?i just try to know what is the secret behind this issue.any explanation is appreciATED.thanks for ur interest and reply.
Jotnar Posted August 15, 2004 Posted August 15, 2004 Are you sure it works using setupldr.bin in SP1? I could have sworn you couldn't go directly to that file. You can also try asking your question in the Bootable CD forum HereCheers
WINXPSP2_FAN Posted August 15, 2004 Author Posted August 15, 2004 it worked in win xp pro sp1 for sure.but in case in xpsp2 it DIDNOT work.of course i used setupldr in sp1 with windows xp sp1.and i used setupldr in sp2 in windows xpsp2.u kindly have to know that.i though made some other method which worked in SP2:[i made a BOOTSECT.DAT on the root of cdthen i edited its content to refer to WPRO\SETUPLDR.BINand of course i edited SETUPLDR.BIN to refer to WPRO not to i386moreover i put the [txtsetup.sif] in WPROthe txtsetup.sif refer to path=\all is ok by this method ]but i want to use the original method.
Metzen Posted August 16, 2004 Posted August 16, 2004 it worked in win xp pro sp1 for sure.but in case in xpsp2 it DIDNOT work.of course i used setupldr in sp1 with windows xp sp1.and i used setupldr in sp2 in windows xpsp2.u kindly have to know that.i though made some other method which worked in SP2:[i made a BOOTSECT.DAT on the root of cdthen i edited its content to refer to WPRO\SETUPLDR.BINand of course i edited SETUPLDR.BIN to refer to WPRO not to i386moreover i put the [txtsetup.sif] in WPROthe txtsetup.sif refer to path=\all is ok by this method ]but i want to use the original method.Are you using a SETUPLDR.BIN file from SP2 or from SP1?The files are different.SP2 -- 254 KB (260,272 bytes)SP1 -- 240 KB (245,920 bytes)<edit> nevermind. I should read the whole post before *I* post.
bobby100 Posted August 17, 2004 Posted August 17, 2004 Don't use Ultra Edit, it is known problem if you use with UltraEdit, use other app for hex editing.
WINXPSP2_FAN Posted August 19, 2004 Author Posted August 19, 2004 Thankx bobby100 for ur reply. But I also used WINHEX and the same faliure occured.I also would like to inform u that ULTRAEDIT was working in case of SP1 very well.I mean that the problem is not in ULTRAEDIT but it is in the BCDW LOADER.BIN.anyy comments are appreciated.
tak21 Posted September 3, 2004 Posted September 3, 2004 @WINXPSP2_FANHi, I just wanted to ask, if u got a solution for your problem so far? I wanted to use BCDW in Bart's PE with the same problems u have.
Tefole Posted September 4, 2004 Posted September 4, 2004 Dito !I have the same Problems... I hope for a solution soon....
wbrinkmann Posted September 5, 2004 Posted September 5, 2004 Hallo,ich hoste den deutschen Mirror von BCDW (www.wolfgang-brinkmann.de) und habe die Information von reanimatolog erhalten, dass erst die nächte Version von BCDW SP2 unterstützen wird. Das Erscheinungsdatum ist leider noch unbekannt.Mfg,W. Brinkmann
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now