Hard Light Productions Forums
Off-Topic Discussion => General Discussion => Topic started by: WMCoolmon on June 26, 2005, 08:46:36 pm
-
I recently got a 250 GB SATA for my mATX computer. Unfortunately, Windows 2000 doesn't seem to detect the SATA controller. When I tried loading the drivers onto a CD and pressing f6 at startup, I got an error involving a source code file :wtf: (ATM I'm trying to install Ubuntu Linux and get the X server working, so I don't have the exact error)
Any ideas how I might fix this? If it's at all useful, I've got my old PATA drive fully intact with Win2k installed. Googling hasn't helped.
I'd really rather avoid "upgrading" to Windows XP, or trying to use Cedega.
Stats:
Windows 2000 (SP0, bought it right when it originally came out)
2x512 DDR400 RAM
AMD64 2800+ 754-pin
MSI K8MM-ILSR Motherboard
250 GB Western Digital SATA
Gigabyte GF 6600GT
Audigy 2 NX
DVD-RW/CD-RW drive
-
Odd, is this during win2k installation? Or just in general?
My PC cannot detect the SATA (in win2k or xp) without having an IDE HDD installed.
-
During installation; there isn't really enough room in the case to have both HDDs, I guess I could hook it up temporarily if that would make win2k detect the SATA.
Edit: I'd like to just be using the SATA once I've got things set up.
-
Are you trying to load the SATA drivers from a CD or from a floppy. As i recall, CD didn't work, but floppy did, for me.
-
I didn't even get the chance. After I pressed f6 and the install had finished loading, a screen came up that said Windows install had either found unknown devices (it hadn't) or I'd pressed f6, and to press 's' to put in a disk or enter to continue with the install. I pressed 's' and it gave me the source code file the error had apparently occured in.
I actually don't have a floppy drive...just the one CD drive that the Win2k disk was in. Maybe that could be the problem? :nervous:
-
Originally posted by WMCoolmon
I actually don't have a floppy drive...just the one CD drive that the Win2k disk was in. Maybe that could be the problem? :nervous:
It's damn near impossible, if not totally impossible, to install third party drivers without a floppy drive. :(
-
Garglepleh. :sigh:
I got the exact error -
An unexpected error (0) occured at line 962 in D:\nt\private\ntos\boot\setup\oemdisk.c
Press any key to continue
Apparently it is that you need a friggin' floppy drive. Due to the nature of my case that's going to be a PITA to install...
Any ideas on how to share a home partition between Ubuntu and W2k while still keeping permissions intact (right now it defaults to the person who mounted it, which is root, so my user doesn't have permission to create the necessary gnome prefs files or anything to do anything except basic utilities operation.)
-
None for that, but for the floppy, why not just open the case, remove a floppy drive from another PC, temporarily, and plug the floppy drive into your new PC temporarily until you have windows installed, and then put the floppy back into the other machine?
-
m sata had no problems running win2k, but w2k pissed me off and i ended up installing xp instead
-
[color=66ff00]I had no end of issues with SATA and win2k/XP so I just uninstalled the card.
Drive read/write performance was terrible and often corrupted data. Bit of an all around pain in the arse.
[/color]
-
Originally posted by Raa
None for that, but for the floppy, why not just open the case, remove a floppy drive from another PC, temporarily, and plug the floppy drive into your new PC temporarily until you have windows installed, and then put the floppy back into the other machine?
Well, it's a lot easier to say that than do it. Changing *anything* is a matter of opening the case, unplugging the four cables going to the DVD drive and the hard drive, unplugging the power cable to the 6600GT and fans, taking that out, unscrewing and removing the drive bay, and then doing whatever it is you want to do.
Anyway, I'm doubtful of the floppy thing working, not to mention I don't have a floppy drive I *know* works. Plus, while trying to get the floppy drive installed, apparently I broke one end of the SATA cable and will have to get a replacement tomorrow. :blah:
How well does Cedega work these days? I could give a shot at going all-Linux; the only things keeping me on Windows are mostly game-related. I've made a conscious effort to try and shift over to OSS (Firefox/thunderbird of course, OpenOffice, AbiWord, etc.) so a lot of the 'work' programs I'm familiar with already run natively on Linux. I might even try setting up a 32-bit chroot this time. :p
-
Originally posted by WMCoolmon
How well does Cedega work these days? I could give a shot at going all-Linux; the only things keeping me on Windows are mostly game-related. I've made a conscious effort to try and shift over to OSS (Firefox/thunderbird of course, OpenOffice, AbiWord, etc.) so a lot of the 'work' programs I'm familiar with already run natively on Linux. I might even try setting up a 32-bit chroot this time. :p
[color=66ff00]Cedega is unknown to me, I tried to go all out linux a while back but a few apps wouldn't run in wine and the learning curve meant I was putting more time into learning how to do stuff than actually being productive. My motivation was much the same as yours; an attempt to embrace OSS. :nod:
Still, I keep at it albiet at a fairly slow rate. I installed freeBSD on my lappy this morning just to get a feel for what it's like. :nod:
[/color]
-
If you're game, you can rig the WinXP (and I presume 2k) install CDs with the relevant SATA drivers so you don't have to press F6 and feed it a floppy (which in a recent reformat on my box took a number of attempts due to crappy floppies/drives). You'll have to google the info though as I don't have it on hand.
-
This may be a little detailed since they're slipstreaming Service Pack 4, and other drivers apart from SATA onto the CD as well as making it into an unattended installation but you may find it useful.
Click me (http://www.pcstats.com/articleview.cfm?articleID=1703)
-
If you're going to go to the trouble of creating a whole new CD for the SATA drivers you may as well slipstream the latest service pack as well - it's one less thing you'll have to install after installing the OS.
-
I agree with that 100%.
Don't know if I'd stick the unattended install file on the CD unless I was in the same sort of situation WMC finds himself in with no floppy drive though.
-
I'd use it as an excuse to ditch the floppy drive completely myself. As I mentioned earlier, it took a dozen attempts on my last major format to get the driver disk for my SATA controller recognised by the XP setup program. Being able to stick it on the CD and not worry about it (the unattended install will even do the Windows install, including any control panels and whatnot, for you) is a god send.
I really wish MS would do this themselves though. They update those little text bites that outline the features and extol the virtues of the OS you're installing when you slipstream a service pack, it can't be any harder to add a few extra drivers - especially for something like SATA and especially when they can't get their (presumably) SATA-aware-by-default-OS out for another 12 months or so.
-
Hmm. this guide is looking good. :nod:
-
...Unfortunately it didn't work out. For whatever reason, Windows 2000 setup still didn't detect the disk, even if I went into the driver-install screen and went through the same steps as if it were on a floppy (It did not crash this time, though, which is a marginal improvement.)
So I'm on Ubuntu Linux now. Happily, the SATA drive seems to be going faster than my ATA100. Compared to 30-something before, hdparm now reports:
Timing buffered disk reads: 172 MB in 3.01 seconds = 57.15 MB/sec
Now I just need to get Cedega, ALSA, some decent MPC playing ability, DVD playing, CD writing, some sort of coding environment, and my old HD's data.
-
Hang on, after modifying TXTSETUP.SIF and creating a WINNT.SIF for the Windows part of the driver install you no longer need to press F6 at the beginning of the Windows install. Assuming the relevant files are set up correctly (it is a bit tricky, it took me a couple of goes before I got a working ISO) then Windows Setup should detect your hardware and load the driver automatically as if it were always there.
-
Yeah, I let it do that once (twice?) and it still didn't work. :blah: