Anyone remember this old-school bug?

[RJARRRPCGP]

This link shows the same symptom as the dreaded Via KT133-GeForce 2 MX bug:

http://wintoflash.com/forum/viewtopic.php?f=10&t=36189

Back in 2002, I had to pop my Voodoo 3 back in to get past this!

[mockingbird]

Re: Anyone remember this old-school bug?

I would slipstrem every possible driverpack and see if it gets past that screen.

[RJARRRPCGP]

Re: Anyone remember this old-school bug?

This wasn't ATA driver related nor video driver related.

This part can't even use the drivers anyways, lol.
(It's still so early in the installation)

[RJARRRPCGP]

Re: Anyone remember this old-school bug?

And I had that issue before I got my first DDR board.

This is a bad bug that prevents the partitioner from starting, even when still in DOS-like mode when a GeForce 2 MX is installed on a Via KT133 board.

I doubt you're ever gonna see this on Radeon and >2001 boards.

This is an issue with the video card BIOS and/or motherboard chipset.

[mockingbird]

Re: Anyone remember this old-school bug?

This wasn't ATA driver related nor video driver related.

This part can't even use the drivers anyways, lol.
(It's still so early in the installation)

Incorrect.

This stage is after all the TXT mode drivers are loaded...

And when I say DriverPacks, there is not just ATA driver packs, there's chipset, vga, etc... So my reasoning is that if all the text mode drivers are loaded, maybe it will get past this incompatibility. They have their own utility to slipstream everything. It's pretty easy to do.

[Uranium-235]

Re: Anyone remember this old-school bug?

driverpacks can be hit-and-miss with some chipsets, especially intel AHCI ones (newer ICH 7/8 in particular). Newer revisions match compatible ID's and it loads one that is CLOSE, but not correct. Gets past the blue screen install, but fails on the setting up phase. I've had that happen to me at least 3 times. I go to intels site and slipstream the latest iastor driver with nlite and that usually works

this guys problem might be USB related (this is a mini, it might not have a built in CD drive), or a bad CD or HD

usually if XP dosen't have the chipset ATA driver it will ether bluescreen (0x000007a I believe) or say it can't find the hard drive)

[cheapie]

Re: Anyone remember this old-school bug?

usually if XP dosen't have the chipset ATA driver it will ether bluescreen (0x000007a I believe) or say it can't find the hard drive)

I think it's 0x000007B (INACCESSIBLE_BOOT_DEVICE).

[RJARRRPCGP]

Re: Anyone remember this old-school bug?

Incorrect.

This stage is after all the TXT mode drivers are loaded...

And when I say DriverPacks, there is not just ATA driver packs, there's chipset, vga, etc...

Text mode VGA driver that you're taking about does not apply to anything before the GUI. (The first reboot)

Incorrect. This stage just uses BIOS-mode graphics. The only additional stuff needed is for the ATA support.

Integrating VGA drivers is not required.

GUI is NOT until this stage completes!

[RJARRRPCGP]

Re: Anyone remember this old-school bug?

I think it's 0x000007B (INACCESSIBLE_BOOT_DEVICE).

Correct.

[mockingbird]

Re: Anyone remember this old-school bug?

Ok but if it has something to do with an inaccessible boot device, maybe force loading the IDE driver via F6 (Which is indeed loaded during this stage) would help.

[RJARRRPCGP]

Re: Anyone remember this old-school bug?

Ok but if it has something to do with an inaccessible boot device, maybe force loading the IDE driver via F6 (Which is indeed loaded during this stage) would help.

That was with PATA ATA 100.

[Uranium-235]

Re: Anyone remember this old-school bug?

I might also make a note here that F6 would be impossible in this guys case cause its a freaking HP mini. No floppy. There is a bug in XP's setup when it comes to F6 loading ata drivers. It will take the ATA driver, start installing windows, but at the end of the blue screen setup, it will say it can't find the driver file. I've never been able to get past this, so nlite has been my only solution

[mockingbird]

Re: Anyone remember this old-school bug?

USB floppy.

[y_not]

Re: Anyone remember this old-school bug?

XP is madder than a hatter when it comes to loading AHCI/RAID on-board drivers. Less so with add-in cards to a degree.

I have fought this soooo much over the years. Even WITH a floppy and WITH the proper driver for the SB ACHI/RAID controller, STIIILLLL failing with a BSOD!! Serious Russian roulette /w driver versions when that happens. Try this version, try that, UGH!!!
I always win though, cause that's the name of the game & why, at least speaking for myself, I do it.

I wouldn't even dream of installing XP from a UFD, it's just too far past its "in-built support" to really be problem free. I have seen bad CD's cause this, bad burns, bad optical drives, etc...
The same would hold true for a UFD. Because, where did you get the files? CD, right? BAM!! If the source is bad, doesn't matter if the UFD is good or not.

Sometimes toggling legacy USB support will fix this. Or.... you could disable AHCI/RAID in the BIOS, setting the ICHx SB SATA controller (PCH if you're rockin' a Nehalem+ cpu arch.) to native or IDE mode, depending on how the board maker coded the BIOS. Some boards; native = a mode that XP requires a Mass Storage Controller driver for, others not. So for the former, you'd have to choose legacy/IDE mode. It's silly!!

But who said we actually had standards, huh??
Smack 'em for me. M'kay??

Well anyway, this should install just fine. If it doesn't it's your UFD disk or the file source as stated above. Fix it, then your install will go just fine.
Failing that, it's time to check the notebook's HDD, assuming it has a mechanical one. Use Hiren's boot cd and check the SMART data /w HDD Sentinel. If it doesn't show any problems, then run Spinrite 6 on it @ L5.
MAKE SURE HDD IS IN LEGACY MODE FOR THIS!!! Kick back and wait, it'll be a while. Like a day, or less if you're lucky.

Once you get the OS loaded /w the SATA controller in legacy mode, you can switch it to AHCI/RAID mode using the following method.
I have never tried it, but I have meant to do so, I just haven't yet. May not ever now, considering XP's a "dead duck" in my book.

http://www.geek-republic.com/software/raidfix/
You'll find a link to an alternate method there as well. Doing it manually that is. Regedit FTW!!!
*I have another method if this manual one doesn't work, but it's a bit hardcore. But not daunting and really not that hard, just a little more time consuming and tedious than I'd like. But I have done it (manually) and it works.

I would recommend, after you use the above tool, updating the AHCI/RAID driver to the latest Intel version. Look under their downloads for "Intel® Rapid Storage Technology (RAID) driver". It's listed under "software" of all things. LOL
It is partly software, but mostly driver. So whatever.
*Note, this only goes down to ICH7 series. Which is pretty stinkin' old, and should cover even chipsets down to the 845 series. But if you have ICH5R or ICH6R/M, you best be looking for an older driver. That's a whole nother bag of worms though, with what's supported and what's not. It's all supported in XP, just a matter of what driver and what modes and such.

I just checked and Intel has pulled their classic trick of putting up old old drivers in lieu of new ones. Search for "v11.7.0.1013", filename is "iata_enu.exe". Or else pick a really new desktop board and get it that way. Silly Intel!!!

As for TXT mode setup, that is correct, there's TXT mode>reboots>GUI mode>installs drivers>Reboot to OS.
What is incorrect is that it is not "DOS" mode. DOS was ditched when MS left the Win9x kernels, ME was the last one. Even it brought in more of what XP uses that it borrowed from Win2k, the NT kernels.
What in fact is a "command shell" is indeed simply the NT kernel command line. Just like BSD has one (terminal) in OSX, and Linux has one also (terminal/xterm), Windows has it too and likely always will.

Assuming you aren't using the infernal OPK tools. GRRR hate those.
But in all seriousness, SCRAP XP!!!
It's an 11.5yr old operating system, it's so riddled with security holes, not to mention slow. Why bother. If you don't have the bones to pay MS for an upgrade, just go /w Ubuntu. If it's a lower end machine, which it sounds like it may be just a netbook. Then use Lubuntu, mean and lean /w the LXCE shell. It's kinda ugly, but it's slim & trim and fast as can be.
This netbook had super rocky support in Linux at launch, later improved a few years down the road. It should be pretty solid as of now, I see people running Ubuntu on it. Not sure on the 3D front though.

PS. I have included a lot of information pertaining to the subject that isn't necessarily just for this netbook. Simply for informational sake.
But the principles and functions are the same.
You will also have to disable the Intel Flash Cache Module if it's installed. Only Vista+ can use this.
Also, I'm not entirely sure if the above listed driver, or the patch utility for that matter, supports your Atom Silverthorne's Poulsbo SCH chip or not. I can't find much on the matter. It supposedly has AHCI support, but I don't know it's only native Vista+ MS generic AHCI driver or what.
The info is out there on that, somewhere, I'm just done looking for it for the night. If you can't find it, let me know. Maybe you can persuade me to go suss it out.

[Uranium-235]

Re: Anyone remember this old-school bug?

USB floppy.

what did I just say? oh I didn't specify did I

yes, even though there is a USB Floppy driver loaded during the blue screen xp setup, it will take a raid/ahci floppy, but at the very end of the blue screen install process, it won't be able to find the raid files and finish setup. Regular floppy drives, yes, USB, I have tried many times and have NEVER gotten it to work

there is many different intel AHCI revisions. This is where sometimes the driverpacks has issues

http://en.wikipedia.org/wiki/I/O_Controller_Hub

[RJARRRPCGP]

Re: Anyone remember this old-school bug?

I forgot to say that the Windows 2000 text mode installer don't have this bug.

Never a problem installing Windows 2000.

[severach]

Re: Anyone remember this old-school bug?

XP migrating to RAID? UR doing it wrong.

Install a JMicron or Marvell SATA card (not VIA, not Silicon Image, not Initio). Once driver is installed, move boot drive to the JMicron card. Boot and install drivers with each of the BIOS SATA options set: legacy, IDE, AHCI, RAID. Put boot drive back on other controller and boot any way you want.

I've read all the instructions for enabling RAID in XP and they are way too complicated. This is dirt simple.

What do we get for ten dollars?

[Uranium-235]

Re: Anyone remember this old-school bug?

^^hah i've done that before, but with a promise ATA-100 card. I don't have a sata card

of course, you can't do this on a LAPTOP, which is where the OP was referring to

also if the persons board died and you want to switch to another one, better have close enough chipset

[RJARRRPCGP]

Re: Anyone remember this old-school bug?

Folks getting OT. This was way before SATA even existed LOL.

[y_not]

Re: Anyone remember this old-school bug?

Folks getting OT. This was way before SATA even existed LOL.

If you're referring to the netbook in question, it is very much so SATA. A dippy little Intel Atom CPU /w it's proprietary chipset, but nonetheless it's SATA.

But if it's the VIA KT133 you're referring to, well, it had so many bugs I can't even count them. I pitied anyone using any VIA chipset.... EVER!!
They were just ticking time bombs.
VIA chipsets were the worst thing ever invented in the computer industry.
Coming in second would be an SiS chipset and PC Chips boards + clones.

And for sure, SATA was far, far off into the PC world's future. Well, in computer time that is.

Was there a point to this thread? LOL
I thought we were actually trying to figure out how to fix that netbook XP bare metal install problem. Not necessarily for the OP of that thread, as I'm sure he/she is long gone now.
BTW, seeing as you're a member over there, heard any noises as to whether that OP ever got it resolved?