Printable View
Tried installing RC2 the other day just to see what it was like, and do some testing for my shop. It got through the first part of copying files, and then when it rebooted, showed the neat black windows XP screen, it stopped and gave me the error in the subject line. Anyone experience this error and what it means? It was a clean install on a quick formatted fat32 drive. Detailed hardware description available if you want it.
/|rokh
take out sound cards, usb devices, NIC cards, everything but the video card.
Well keep the mouse and keyboard and monitor you will need them https://forums.windrivers.com/
------------------
Stop bustin my chops!
Ill do it!
[This message has been edited by derrick (edited September 10, 2001).]
under normal circumstances I would do the whole diagnostic bit... being a technician and all... but when it comes to my computer, well i'm just too lazy :P
got me one of them stupid full tower inwin cases that weighs as much as a mack truck and it's under the desk, and it's just a pain... so i would rather give up on XP anyway. Not so sure I even wanna try XP, with how unsecure it is (the whole raw socket bit).
Speaking of raw sockets, with as far as i got in installing RC2, it's funny how M$ emphasizes to make sure your virus scanner is XP compatible. In other words, we deliberatly made this OS less secure than anything else yet, but as long as we tell you to update your virus scanner, we cover our butts and put the blame on you if anything were to happen.
Just my 2cents, I was hoping someone would have a quick answer on that error... everywhere I look on the net it refers to a registry problem. Kinda hard to have a registry problem on a fresh install isn't it? unless they have sunken to an all time low of puting a corrupt registry in with the installation.
/|rokh
http://support.microsoft.com/support...SRCH&SPR=WINXP
Not much info out there,but this might help.
Update:
Well I determined the cause to be one of two things. I had an old 1GB HDD laying around that I stuck in the removable bay and loaded it up with a newer RC of XP. I think the first one I used was actually RC1, but I did this with RC2. Now the removable HDD bay is connected to my actual motherboard, whereas my normal drives are hooked up to the hot rod 100 card. It was either the newer version of XP or not being on the hot rod card that did the trick. I guess I'll find out if I ever play with XP again.
I really liked how it looked, that was neat. I just with I had some better information on the whole raw socket thing. If the raw socket is gonna be a major security issue, I'd rather go on using Windows ME (why ME you ask? because at the time of installing it, Win2K didn't work with my NIC, so I stuck with ME. Now they have drivers for my NIC, but I was too lazy to install 2K). I've heard conflicting data about the raw socket stuff. If I could be relatively sure that it wasn't an issue, I'd probably buy the full release when it comes out.
/|rokh
I think you should stop being so lazy and actually educate yourself on this technology before you "enlighten" the rest of us on the finer points of ME vs. XP <almost laughable>Quote:
<font face="Tahoma, Arial, Helvetica, Verdana, Geneva" size="2">Originally posted by arokh:
(-snip-)
It was either the newer version of XP or not being on the hot rod card that did the trick. I guess I'll find out if I ever play with XP again.
I just with I had some better information on the whole raw socket thing.
(-snip snip-)
Now they have drivers for my NIC, but I was too lazy to install 2K). I've heard conflicting data about the raw socket stuff. If I could be relatively sure that it wasn't an issue, I'd probably buy the full release when it comes out.
/|rokh</font>
Do you have any idea what you're talking about at all? Honestly, if you don't have anything intelligent to say, keep it to yourself.
------------------
If it ain't broke, you ain't tweaking it hard enough!
[This message has been edited by rprestenback (edited September 17, 2001).]
Try updating your Motherboard BIOS and setting all pages in to to Failsafe or Bios defaults.
I've had three machines clobber up on an install that went through just fine after I did this.
have u tried pressing f6 when its booting and installing the third-party driver that should be on the ata100 cards driver disk?
i got the same(ish) error with my promise raid controller and that did the trick.
------------------
Question of the Day: If it Micro$oft didn't exist, how much easier would our lives be?