[jaclaz]

surfetje
the "HAL" error has NOTHING to do with NTDETECT.COM.

This may only resolve 0x0000007b error.

However to create your own modified NTDETECT.COM, if you cannot simply replicate the instructions from ilko in post #4 above:

Quote

You may try the modified ntdetect.com as mentioned here. Copy and paste all in Tiny Hexer (freeware), select HEX TEXT, save as ntdetect.com and put it in USB stick root, filesize must become 47,596 bytes.

READ the linked to posts on 911CD:
http://www.911cd.net/forums//index.php?sho...=19235&st=2
http://www.911cd.net/forums//index.php?sho...3784&st=334
AND the posts there referenced.

jaclaz

[surfertje]

It works! i have copied the data and paste it in winhex in a new file and saved it as ntdetect.com as ASCI HEX. Now i can run setup, that is, it starts setup..

[biggis]

ilko_t, on Feb 16 2008, 05:03 PM, said:

em5xx, on Feb 16 2008, 05:05 PM, said:

em5xx, on Feb 17 2008, 12:52 AM, said:

I am having the same problem. Replacing the modified ntdetect.com does not solve the problem for me.

I got it to work after I change the sata mode in bios from AHCI to compatibility. Any idea why

Honestly it puzzles me a lot. This error basically means, that your boot device is no longer accessible. Since during Text mode the boot device is your USB disk/stick, what drivers you have for your disk controller should NOT matter, it simply wouldn't find your hard disk.
The modified ntdetect.com resolves problems with some buggy BIOSes, when USB bus is reset and USB peripherals re-enumerated. Many Dells have this problem. And it makes sense to get BSOD 7B in that case.

But why your (missing?) disk controller driver causes same I can only guess- first would be driver conflicts.
What is your disk controller/motherboard?
Do you have any third-party mass storage drivers integrated in your source?
Are you using original MS windows disk as source, even if you Nlited it?

As Wimb mentioned, most of this problems are resolved by using BTS mass storage drivers pack, for me it's a must.

I also got the BSOD 7B on my Acer Aspire One (D250-0Br) with a SATA disk. Changing NOTHING else but, in the BIOS, from AHCI to IDE did the trick (curently formatting the HDD but it looks promising so far).

My problems started when using PQ magic to resize the C: ... got a question from PQM about correcting some errors.. after that I decided to skip the resizing part (got cold feets so to say) and instead go for a recovery of the disk (using eRecovery from Acer). It didn't work and it was impossible to close the program (it booted constantly directly to eRecovery).
Fdisk (from DOS7.1 on USB) could remove the partition and re create it, but WinXPproSP2 installation never worked untill I changed the BIOS as described.
So thanks for pointing that out. An easy solution to a problem I have bused my head against the whole weekend.
Thanks
[EDIT: formated: OK! .. restarted: got the "HAL.dll" error. Solved this problem by <F12> (Boot order menu) and sellecting the USB stick (now the HDD is detected and bootable so to avoid going that route I had to do this!).
1s restart booting from USB got me to the choice of sellecting "part 2 of the installation process (GUI)" but got the HAL.dll error again (I might have chosed wrong, so..) 2nd restart from USB, CAREFULLY selecting "part 2..." the installation continued fine.]

This post has been edited by biggis: 14 September 2009 - 02:14 PM

[mel2000]

Sorry to dredge up an older thread but I'm new to the XP USB boot 0x0000007b BSOD, and my problems have gone from bad to worse. I've built my BartPE multi-software USB stick and all the apps on it work fine except the XP Recovery Console.

I got the 0x0000007b BSOD when the XP Recovery setup got to the Loading Windows screen. A poster at the msfn.org/board offered a modified NTDETECT.COM file to fix it, but after I substituted it I got a "file iaStor.sys could not be found" error and had to abort the rest of the console setup before the Loading Windows screen had a chance to display. BTW, the IASTOR.SYS file is located in my I386/SYSTEM32/DRIVERS folder of the BartPE ISO. I'd appreciate if someone could point me to a more definitive solution to these XP setup issues. Thanks.

[jaclaz]

mel2000
sorry, but I don't get it.

What has BartPE to do with SETUP from USB?
And what has Recovery Console to do with it?

Which of the various apps/methods are you using?

On which hardware?

jaclaz

[mel2000]

jaclaz, on 06 April 2010 - 01:47 AM, said:

What has BartPE to do with SETUP from USB?
And what has Recovery Console to do with it?
Which of the various apps/methods are you using?
On which hardware?

I created my BartPE ISO file using UBCD4Win 3.5 along with my WinXPproSP3 CD on the Vista Home Premium system on my Acer Aspire 5520 laptop. BartPE offers a multitude of rescue apps selectable from its boot menu. One of those apps offered is "Windows XP Recovery Console."

I used MultiBootISOs.exe (from the tutorial at http://www.pendrivel...-multiboot-usb/ ) to create a bootable USB, then added BartPE.iso and other ISOs to the Grub menu.lst configuration file which was created by MultiBootISOs.exe. All the apps within BartPE launch and work fine from the USB stick, and so do the apps I added outside of BartPE. Even the Windows Recovery Console boots OK before it bluescreens when it gets to the "Loading Windows" screen during its setup. That's the problem I'm trying to resolve. If that's not enough background I'll be happy to answer any other questions you have in regards to this issue.

This post has been edited by mel2000: 06 April 2010 - 06:01 PM

[cdob]

mel2000, on 06 April 2010 - 05:56 PM, said:

I created my BartPE ISO file using UBCD4Win 3.5

That's a UBCD4Win question and there is a UBCD4Win forum.
Recovery console use either \cmdc\ or \cmdcons\ directory.
Behaviour reminds to edited OEM windows source files.
http://ubcd4win.com/...047
If this fails still, ask at UBCD4Win forum.

[jaclaz]

@cdob
Thanks for the pointer, hilander999's quote is great :

Quote

YOUR MISSION, Should you choose to accept it...
Is to replace ONE FILE.

jaclaz

[ilko_t]

Umm, as I am reading it, mel2000 is attempting to load UBCD4Win as ISO, which supposedly would not work just like that:

Quote

...I used MultiBootISOs.exe (from the tutorial at http://www.pendrivel...-multiboot-usb/ ) to create a bootable USB, then added BartPE.iso and other ISOs to the Grub menu.lst configuration file...

mel2000, read the pinned topics here:
http://www.boot-land...hp?showforum=66

[reachvijeesh]

ilko_t, on 15 February 2008 - 06:56 PM, said:

You may try the modified ntdetect.com as mentioned here. Copy and paste all in Tiny Hexer (freeware), select HEX TEXT, save as ntdetect.com and put it in USB stick root, filesize must become 47,596 bytes. I don't know other ways to give you this file without breaking forum and MS rules.

hi

i am getting Bad_Pool_header stop: 0x00000019 error, when try to install win xp from usb, exactly it shows at "setup is starting windows " screen

pls help

Regards

Vijeesh

This post has been edited by ilko_t: 20 April 2010 - 11:03 PM
Reason for edit: Fixed quote

[ilko_t]

You have been replied in the thread you started. Why are you double posting?

http://www.msfn.org/...en-t143453.html

[sapient]

ok so ive been trying to find an answer to my problem\problems with no avail so maybe someone here can help.

im trying to do the same thing but instead of a 7b bsod im getting 6f Session3_initialization_failed.
tried everything the ntdetect the switching to ata instead of ahci. the 6f keeps popping up.

besides one time where it didnt get that far but i think that was a problem with one of my xp images i made. and that was a could not find ramdisk.sys.

btw the 6f happens during setup when it says setup is starting windows after it loads all the drivers. drivers are not a problem i am using either a xp disc i made with the massstorage and a bunch of others or someone elses with the sata drivers on it.

i cant use my dvd cuz its broken. the reason im doing this to begin with is my previous HDD fried and im installing on a new one i just bought. the only thing i can think of is the new HDD is DOA. im sure this wont matter but in case it helps anyone figure out my problem but the new HDD is SATA 3.0 and the old one is 1.5.
i cant upgrade the bios to the newest version until i buy a new battery lol. (irritating laptops) but i didnt have a problem b4. the HDD that fried is not recognized in bios but the new one is.

system specs:
dell
core2 duo 1.8 t7100
2gb ram
trying to install xp sp3 with a ton of drivers

help pls im sick of using my old single core comp

im going to make a new install source because im not sure if the manual install was right on either cuz the disc i made was so long ago. will reply when im done.

ok well i didnt make a new disc cuz im annoyed and my neck hurts atm BUT im almost positive its the manual install and upgrade removal problem. search 0x0000006F and ull find the solution.

but my solution for now was just to dl a diff copy that is setup for usb installation and then i used wintoflash but i think either method will work AS LONG AS UR SOURCE COPY IS SLIMMED DOWN RIGHT. lol (constantly kicking myself for not checking this first and trying to install 20x)

in the end i have to say this forum rocks and helped me out more than anywhere else i looked on the web.

This post has been edited by sapient: 15 June 2010 - 09:46 PM

[userb]

I created a new account simply to tell THANKS to you and all others guys who have find that trick!!
you just saved my life !


BSOD, we gonna kill you !

This post has been edited by userb: 09 July 2011 - 08:11 PM

[laddanator]

Just wanted say thanks. The modded ntdetect.com did the trick so far.