0x0000007B error after txtmode, before gui...i've tried everything

[Leeoniya]

everything goes fine with textmode setup. the floppy driver that i load from floppy works well, formatting goes fine, create new partition, all the files copy OK, as soon as i reboot. WinXP boot screen flashes for a fraction of a sec, then BSOD 0x0000007B.

(these raid drivers work without a hitch under a working winXP install btw.)

tried removing all my IDE drives, updated bios, used different version drivers for sii3114r raid conroller.

the only thing that has sort of worked, is cloning an IDE install, but i have to modify the boot.ini and possibly reassign drive letter before imaging. after cloning it does boot from raid, but i think it uses the MBR from the IDE. when i unplug the IDE, it freezes on wlnotify.dll. and when it is loaded the environment variables all point to the IDE drive that it was cloned from.

i dont really understand how the drivers work through all of textmode and then fail during the gui part of the setup...considering it does read the boot sector cortrectly since the winxp boot screen shows up briefly.

plz help, this is driving me nuts....tried different CDs, tried recreating the RAID array in teh 3114 bios, tried installing with replaced files from SP1 to support 16k cluster sizes that seem to work for everyone else. finally just trying to get it to go on a 4kb cluster size. (having windows do its own format during install with original SP2 cd.), tied both regular and unattended, nothing makes a diff.

i had this working before, decided to format and reinstall and doesnt want to work now.

thx,

Leon

[cancerface]

Are the driver files present after txtmode in %SystemRoot%\System32\drivers ? I had a similar problem in the past when I used the 'F6' method to supply the raid drivers from a floppy and for some reason although txtmode went fine, I would get a bsod and the system would not boot. The driver files however never made it to %SystemRoot%\System32\drivers so I booted using a BartPE CD then manually copied the .sys files and was able to boot from the array eventually.

How about integrating the SI raid driver to your install? There are many threads describing the procedure ... Try this one for example, or the unattended guide

Hope this helps ...

CF

[Leeoniya]

the drivers are actually integrated as well, among hundreds of others with nlite and Bashart's DriverPacks. once again, the precached drivers load fine and work through partitioning and formatting. but after it formats the partition and (after when it says building a list of files to be copied in txt mode) starts copying files, the first files it wants to copy are those for my 3114r controller that it has just been using, and not a single one of those driver files gets read off the cd at that point, but the rest copy just fine if those driver files are skipped.

if i use drivers from a floppy i never get the error that tells me that it cannot read the driver files off the cd. maybe u're right about them not going anywhere. strange.

i sort of found a bandaid for my situation. i installed to an IDE drive, started a second install from inside the working XP SP2...it seems that the drivers are then precached on the original IDE cause everything preloads in about 1.5 seconds in txtmode before going to the partition selection menu. then the install continues unattended as without a hitch onto the raid. it uses the MBR and loader off the IDE on restart (cause first boot order is IDE), (adds an XP Pro Setup line to the boot.ini and i just select it on restart and the GUI mode setup goes fine.) i switch the boot order at this point to boot from cd, then raid-0, go into recovery console, copy ntldr and ntdetect to the root of the RAID drive (if i dont i get NTLDR missing) at which point i get a hal.sys missing if i restart after that. but i run bootcfg /rebuild and it makes the RAID bootable.

and with that *cough* easy process i have an independent RAID boot partition.

what a mess...so much for unattended.

you may be on to something tho, thanks, i'll check....but even if it's true...why and how? even tried it with a clean sp2 on a 4kb cluster size freshly formated /mbr'd.

Leon

[Leeoniya]

not sure why it worked before, but i cant replicate....

when i initialize setup from my working IDE windows and reboot to install on my RAID drive, textmode goes fine after i select the Windows Setup that's added to the boot.ini. then on reboot to get into gui setup i get a bluescreen if i have no SP2 CD in the drive, otherwise if i have the cd inserted, but choose not to boot from it, i get a hal.dll missing?

anyone wanna take a stab? why the hell would having the cd in make it give a hall.dll missing and not having it in give a 0x0000007B BSOD?

something seems funky in the way it references different devices / drive letter assigment.

GRRRRRRRRRRRRRRRRR

Leon

[Judge_MC1]

Sounds to me like you have another HD in your PC. After TXT mode, check the hard disks, see which one has the windows setup directory on it. Had similar problems in the past which were resolved by correcting the ARC path in the boot.ini file.

This may help - http://support.microsoft.com/?id=102873

Check the order that your BIOS boots, I have been caught out by the onboard IDE controller being detected before the onboard RAID controller.

If all else fails try removing all drives except the hard disk you are installing to and the CD-ROM you are installing from.

Is the drive accessible from another OS installed on another HD, not on the same controller... rule out problems with the drive/controller.

Edited April 13, 2006 by Judge_MC1

[Leeoniya]

finally figured it out.

for some reason the driver files werent being copied to the system32\drivers dir. once i copied the si3114r5.sys to it from within my working ide xp install, the gui setup started up normally and finished the install. i guess it only loaded the raid driver in the ram to copy the install files in textmode and then decided that it wasnt too important of a file afterwards.

...figuring out why it didnt and how to fix it is the easy part. finding the problem was a b***h. glad i got it pinpointed, i was about to start self mutilation.

Leon

[Judge_MC1]

Sweeet