XPSP2 setup crashes at end of preload with stop error, as if there is no i/o to any drive

check if the partition is set to active, use fdisk to check it.

I loaned it to a Mac developer who needed to install MSVisual on a pc--it wouldn't install on the functioning hd and xp...he then tried to do a clean install with the xp that came with VisualStudio and the BSOD problem started...he eventually had to buy a barebones pc and could do the clean install with my original hd.

The exact error is the bsod and 0x7b with no driver or other indicator specified.

I will d/l a Win98 startup floppy and reformat a hd.

My bios sees both a pata and sata drive, but dos recognizes neither, regardless of bios boot order.  All my hds are ntfs-formatted; wouldn't they still be "seen" by dos?  Do I need to reformat to fat in another machine?

try fdisk (from a bootable win98 floppy) and check if it sees the drives :

www.bootdisk.com

...and DOS does not recognise NTFS format

If you are trying to install on the SATA drive, you will need the SATA drivers on a floppy disc for use when you see the "Press F6 to install third party drivers" promtp early in the installation.  

FWIW . . I discopnnect all drives other than the one I am installing on, then connect after the installation is finished.  Seems to cause less issues and avoids the risk of damaging a drive

fdisk sees a small ntfs partition, which is set active

format sees no drive

I pulled the sata off the system

format will not work, but what does fdisk see - please post something clear, we have no crystal ball over here

fdisk saw a dos partition; I removed all partitions from hd, fdisk went through the analyize
 
still couldn't see drive with format

then I rebooted the w98 dos floppy

format could see the hd; I reformatted the partition and rebooted with WXP

the WXP install still freezes with the same bsod 0X7b after it loads all the pre-stuff and before it writes
anything to the hd

ok - a Q : how long did memtest run? (at least 3 full passes)

did you test the disk(s) using one of these ?   http://www.disk-utility.com/hard-disk-low-level-format.html
another thing to try is another XP cd, or malking a copy of it, and use that
You can also try connectong 1 disk and cd to the same IDE cable, and test while it connects to the IDE 0 connector, or to the IDE 1. You can have a bad disk controller.

The disk-utility.com link isn't working at the moment...

This mobo, Intel D925, has only one ide channel; the other channel is the floppy channel with a smaller ribbon config.  The cdrom is sata and reads disks ok.

I get the same bsod with my new licensed xpProSP2, my old xp-sp zero, and a bootleg aio with xpprosp2.  Unfortunately I tossed my W98 a while back not thinking that at least it could be used for making boot disks...I still have my W2k but doubt if the results would differ...

I guess there is no simple way to check an on-board disc controller without a functioning Windows install.  I'm going to buy a bare-bones box at Frys and will continue to try the disk-utility link and probably buy another mobo to reuse the box, memory and cpu;  and entertain any other suggestions...

Thanks

addendum:

reminder that the bsod is the same with a sata drive attached and no ide drive attached.

download the ubcd cd then, it contains all those tests, and more :
http://ubcd.sourceforge.net/download.html      

read thru these:
http://support.microsoft.com/?kbid=316401
http://aumha.org/win5/kbestop.php#0x7b

I did all the ubcd mem and cpu tests with flying colors; there is apparently no diagnostic on the disk to check out i/o, which I think this is...

None of about 8 ide nor sata drives I have will accept a win install, though all appear correctly in the bios; the 0x7b stop always occurs at the end of the install write to memory (sysprep?).

the aumha page is the best info yet on stop errors, but the 0x7b entry applies to a pre-existing install:
=====
When you start Windows XP Setup after you copy an image to a new target computer, you may receive the following error message:
STOP 0x0000007B
INACCESSABLE_BOOT_DEVICE
 Back to the top

CAUSE
This problem can occur if the Sysprep.inf file (the Sysprep answer file) that was used on the master computer (before the image was created) was missing the [SysprepMassStorage] section.
=====

I am shopping for a new D925 mobo; a hundred dollars or so, plus some labor, is more appealing right now than wringing our hands trying to figure this out...

Thanks for all the suggestions !

actually there are many links in that one pertaining to different issues on 7b errors (corrupt registry, virus, sysprep image, f6 to load scsi or sata drvrs, new mobo with different ide chipset , usb boot devices, bios firmware upgrade with different scsi drvrs)
http://support.microsoft.com/?kbid=316401&sd=RMVP     new mobo with different ide chipset
http://support.microsoft.com/?kbid=314859&sd=RMVP     bios firmware upgrade with different scsi drvrs

good luck on that new mobo

http://www.experts-exchange.com/help.jsp#hi51

I have been through all the references and none seem to suggest a way to check the i/o portion of the mobo.  As I have said, any of several xp install disks halts at the point where I think hd access is required, using any of several sata and pata drives.  There has been no recent bios or other driver or chipset changes prior to this failure; the bios setup functions normally--recognizes any hd I install.

The D925 mobo is only available as leftover stock at around $120 so I will proceed to replace the mobo as an effort to salvage memory and cpu.

sounds good,
one more quick thing can you hit, i think, f5 or f7 to try getting to the acpi/hal settings then either turn off acpi or use the standard hal?

During the bios bootup? Or during the windows preinstall loadup?

during windows preload near where it says hit f6 i believe

force HAL hardware abstraction layer upgrade xp (F6 F5 F7)
http://support.microsoft.com/kb/299340/EN-US/

hey nick, the above link clarifies setting the default HAL for you.

Thank you; I am going on vacation tomorrow.  When I get back I will get the workstation cabled up one more time and check it out before buying a new mobo.

hey nick, hope you had a good vacation.  any luck with setup hal?

ok, checked out the hal options several times and same old same old bsod...

well, i would make sure i can access the drives; download a copy of the knoppix cd, and boot from it.
If the drives are accessable, your hardware is fine; if not it's bad.
www.knoppix.org

if the bios see the drive, but you can't access them & drive diagnostics report bad, then i'm thinking you may want to go ahead & grab another mobo as you first assumed.

thanks for all your assistance.

hello nick, to get a refund see here about closing -> http://www.experts-exchange.com/help.jsp#hs5

hey, just call me "one more last chance"...this weekend I will find a monitor, put back the graf card I cannibalized, and do the Knnoppix tip you suggested...

I applied Knoppix and could see a Windows install and file structure on a sample hd.

Bios also recognizes the drive.

Re-running the Windows install, it fails with a "asc3350p.sys corrupted" error.

try forcing a standard Hal layer (press F7 or F5 key during install, when asked to press F6 key)
http://support.microsoft.com/kb/299340

The 2 choices I get are 386 and other; 368 leads to the usual bsod, other says "file txtsetup.oem" could not be found...

Maybe I can clean format a had with Knoppix...and try this stuff again; does the fact that the hd is visible in Knoppix indicate that the mobo may not be defective?

if knoppix does not have problems, your hard is probably OK.
you can clean your disk with DBAN :  http://dban.sourceforge.net/      

I reformatted the hd with DBAN and get the same 07b stop, with or without the HAL process.

Attempting a W2K install results in the same stop message with the additional "inaccessible boot device" comment.

did you try connecting the disk to the other channnel ? or other sata connectors?
also, is the disk accessible from a boot disk ?  www.bootdisk.com

I have used several hds, both sata and pata.  Both formatted and unformatted (DBAN).

They are visible in the bios, in Knnopix, in DBAN, etc.

News Flash:

I set the bios to factory default with exception of boot order and WXP offered to install on a sata drive (no bsod); I am now installing on pata drive successfully...

I don't have any idea what bios property was borked all this time, and in 20 years never had to reset a bios to factory.

any status updates?

Yes, in my news flash above was the unexpected solution (reset bios to factory except for boot order), and I really appreciate all the suggestions from you and your 'staff'...

ok didn't see that it was resolved, just that you were installing

see here about closing->http://www.experts-exchange.com/help.jsp#hs5
http://www.experts-exchange.com/help.jsp#hi70   for refund

Moderator:

As a paying subscriber to EE, I never understood or cared about the point system...please resolve:

After all the help from the experts above, the stumbled-upon answer was to reset the bios to factory and apply the desired boot order.

This "answer" could help others at wit's end to resolve tough issues.

From the post just above yours . . . I answered my question myself. What do I do?

http://www.experts-exchange.com/help.jsp#hi70

nick, you have to make a request to the moderators to close this

Requesting a refund-> http://www.experts-exchange.com/help.jsp#hi70

do so here:    http://www.experts-exchange.com/Community_Support/askQuestion.jsp

actually he should be given a refund as he solved it himself, see his post on 10/11 & both myself & simpswr posted comments on how he should request a refund.

http://www.experts-exchange.com/Hardware/Desktops/Q_21928902.html#17710297

Agree . .

By resetting the BIOS, he changed the Setup of the IDE and SATA controllers. Many mainboards can be set to use different settings, so sata emulates IDE or uses legacy SATA mode or even some raid modes. If it isn't setup to use IDE mode you need to provide drivers through f6 like simps' said earlier (I don't think the asker tried these drivers by reading the thread, or he used the wrong ones, which happens rather often), and nobus' answer with knoppix showed the hardware was working and that got the asker to try again.