11 replies to this topic

[domneu]

I have compiled the LiveXP project to CD and it works flawlessly on a couple of computers in my office. When I use PeToUSB.exe to put those files on my 1.9GB partition on my USB HD, the same computers boot the partition, show the XP logo (I used XP Pro SP 2) and when it seems like it should be going ot the desktop, it BSDs on me with a STOP 0x00000007 error. Does anyone have any suggestions? This only happens tith the USP HD. The CDs work fine.

Regards,

Dominic

[cjc343]

What is the full stop error?

Usually along the lines of:

STOP: 0x######## (0x########,0x########,########,0x########)
SOME_HELPFUL_MESSAGE_ABOUT_THE_ERROR

[domneu]

The error is:

STOP: 0x0000007B (0x79C8528, 0xC0000034, 0x00000000, 0x00000000)

I know what you mean by the SOME_HELPFUL_MESSAGE_ABOUT_THE_ERROR, but there is nothing there. I have seen many STOP errors in my time, but this is all this one has. I have tried this on 4 machines now all with the same results (they are Dell Optiplex systems w/ the latest BIOS updates). The CDs work fine, but not the external HD.

Thanks for your time and help.

Dominic

[cjc343]

Your stop code changed. I'm assuming it's actually the 0x0000007B one.

The most likely fix is the modified NTDETECT.COM

Instructions for creation:

http://www.msfn.org/...xt-t112630.html

[Lancelot]

domneu, try this (i am not sure but it is an easy trial):

-put RAMDISK.SYS from 2k3sp1 to livexp's ..\system32\driver folder on usbhd
-put SETUPLDR.BIN from 2k3sp1 to "livexp's root folder on usb" (minint or i386 ...)
-add ramdisk=ramdisk.sys line to [ScsiClass.Load] section in txtsetup.sif of livexp's which is in "livexp's root folder on usb" (minint or i386 ...) (Thanks to Shirin)
ScsiClass.Load section of txtsetup.sif will probably look like this.
[ScsiClass.Load]
cdrom=cdrom.sys
disk=disk.sys
ramdisk=ramdisk.sys


i hope it helps

[matte]

Probably has the same problem, but with at flash memory. Windows loading screen comes up instead of "please wait". Tried the stuff in the post before, didnt work..

[was_jaclaz]

There are only TWO known ways to avoid STOP 0x0000007b on some machines:
1) the Dietmar's modified NTDETECT.COM (as suggested by cjc343)
2) the RAMDISK booting (as suggested by Lancelot, though with a different approach from "normal" )

The modified NTDETECT.COM has proved to work in, say, 95% of cases where the STOP came out.

The RAMDISK booting has proved to work in 100% of cases, though there are limits with RAM.

It is VITAL that you use the right files, see my post on your other thread:
http://www.boot-land...opic=5224&st=70

The BootSDI .script should do this automatically, but just in case, you need a WINNT.SIF as follows:

[SetupData]BootDevice = "ramdisk(0)"BootPath = "\i386\System32\"OsLoadOptions = "/noguiboot /fastdetect /minint /rdpath=\i386\BootSDI.IMA"

or:

[SetupData]BootDevice = "ramdisk(0)"BootPath = "\i386\System32\"OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportashd /rdimageoffset=0 /rdpath=\i386\BootSDI.IMA"

Change \i386\BootSDI.IMA to the name of the generated image.

jaclaz

[domneu]

domneu, try this (i am not sure but it is an easy trial):
.....
i hope it helps

I have done both of the above with no success. I was very careful to use the correct version of both files.

[domneu]

There are only TWO known ways to avoid STOP 0x0000007b on some machines:
1) the Dietmar's modified NTDETECT.COM (as suggested by cjc343)
2) the RAMDISK booting (as suggested by Lancelot, though with a different approach from "normal" )

The modified NTDETECT.COM has proved to work in, say, 95% of cases where the STOP came out.

The RAMDISK booting has proved to work in 100% of cases, though there are limits with RAM.

It is VITAL that you use the right files, see my post on your other thread:
http://www.boot-land...opic=5224&st=70

The BootSDI .script should do this automatically, but just in case, you need a WINNT.SIF as follows:

[SetupData]BootDevice = "ramdisk(0)"BootPath = "\i386\System32\"OsLoadOptions = "/noguiboot /fastdetect /minint /rdpath=\i386\BootSDI.IMA"

or:

[SetupData]BootDevice = "ramdisk(0)"BootPath = "\i386\System32\"OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportashd /rdimageoffset=0 /rdpath=\i386\BootSDI.IMA"

Change \i386\BootSDI.IMA to the name of the generated image.

jaclaz

jaclaz, I have tried the two suggestions from lancelot and cjc343 above. I cannot seem to get past the stop error. I am a bit ignorant to theis process, but have looked on my USBHD for the WINNT.SIF file you mentioned with no luck. Should I create it with one of your examples above? If so, where at? I assume this is also all done after the image is put on the HD, and not prior to building the image.

Please excuse my ignorance, but I hope to learn how to leverage these tools and become a contributor to the forums once I get my expertise up a bit.

Dominic

[Lancelot]

domneu:
yep with the method jacklazz wrote

as you use winbuilder.exe to build bootsdi files are ready use
copy these files
basefolder\ISO\Ram\WINNT.SIF
basefolder\ISO\Ram\i386\SETUPLDR.BIN
basefolder\ISO\Ram\i386\NTDETECT.COM
to root of usbhd:

you already copied this file
basefolder\ISO\Ram\i386\Bootsdi.img
to usbhd:\i388\

also change usbhd:\WINNT.SIF (notepad) if needed

basefolder: the folder where you start winbuilder.exe

question: is the partition on usbhd, primary active????

jacklazz:
does PeToUSB.exe make the same thing with bootsect /nt52 ? or grub?

[domneu]

domneu:
yep with the method jacklazz wrote

as you use winbuilder.exe to build bootsdi files are ready use
copy these files
basefolder\ISO\Ram\WINNT.SIF
basefolder\ISO\Ram\i386\SETUPLDR.BIN
basefolder\ISO\Ram\i386\NTDETECT.COM
to root of usbhd:

you already copied this file
basefolder\ISO\Ram\i386\Bootsdi.img
to usbhd:\i388\

also change usbhd:\WINNT.SIF (notepad) if needed

basefolder: the folder where you start winbuilder.exe

question: is the partition on usbhd, primary active????

jacklazz:
does PeToUSB.exe make the same thing with bootsect /nt52 ? or grub?

I had a little difficulty with what you meant, but here is what I did without any luck. I still get the same error.

1. I copied WINNT.SIF, SETUPLDR.BIN, & NTDETECT.COM (The ones specified above) to the USBHD:\ folder
- the WINNT.SIF file has the following in it:

[SetupData]BootDevice = "ramdisk(0)"BootPath = "\i386\System32\"OsLoadOptions = "/noguiboot /fastdetect /minint /rdpath=\i386\BootSDI.IMA"

2. I could not find this file. Additionally, I think the paths of my files may be different somehow. Please see the 2 attached graphics.


3. I also did what you said in your previous post about the scsiclass section

4. The partition is primary and active.


Should I be using something different than PeToUSB.exe?

Thanks,

Dominic

Attached Thumbnails

• 
• 

[Lancelot]

domneu:
pictures help:

-you are mistaken with bootsdi (or maybe havent searched what it is yet)
-also use winbuilder under a folder without space:

**** look tutorial section
http://www.boot-land...hp?showforum=31
amulux have a wonderful "Newcomer's Tutorial" there at the TOP
there you can learn how to use bootsdi


For now:
*move "live xp" folder to D:\ and name it "winbuilder_LiveXP"
*create a folder D:\winbuilder_LiveXP\Workbench\Common\BootSDI
and put ramdisk.sys and setupldr.bin in that folder (look amulux tutorial if needed)
*when you double click winbuilder, select Finish->2 Create Image->Bootsdi

than follow things written above which will make sense now by jacklazz and me.

ps: no need to quote