jcurbo

Yes, I have it and it's quite nice. Supposedly many bugs have been fixed. There is even a nice ad-removing procedure for it at http://www.govital.net/~soz/icqpc.htm. Also, ICQ has been a 'time limited free beta' for as long as I can remember using it (1998 or so)

See the other thread for an easier description. SP2 has a Compatibility tab in Shortcut Properties that simplifies things greatly. Anyway I don't want to repeat myself so just read there.

See the thread named "C&C Red Alert", which was on the front page of this forum when I saw your post. Details are within.

That is as far as I got. What that means is that there is a function call in Windows 95 that isn't there anymore in Windows 2000, and the program can't find it. I don't know any way to get around it. This is similar to the problem with Red Alert, and Westwood patched RA to fix it.

Yeah, me too. I remembered hearing somewhere that "an NT-compabtible (haha) executable is included with Aftermath" (that might have even been on the compat list here) so I installed RA using the shortcut method, and then installed Counterstrike and Aftermath. Works like a charm. Now if only they'd patch C&C 95.. it has the same problem as Red Alert

I would definately say you are running at ATA100, after looking over what you told me in the earlier post. I got part of what I said wrong though, I probably caused you some undue grief I was typing it from memory though. The post-BIOS screen says "LBA,ATA100,40022 MB" and not "UDMA5" like I said before. That's my bad Also, keep in mind that even ATA66 drives can't really fill up 66 MB/sec continous data rate. Burst, yes, maybe. ATA100 scores tend to be about like the ones everyone else have said on this thread. Oh, and random access scores always suck. It takes a long time for the read/write head to move back and forth across the platters. The real speed on a hard drive comes from sequential access, because then the heads don't have to move and you're using the 7200 RPM of the drive to move from sector to sector.

I've got them, they work great.. About the version numbering system, I thought it was weird too to go from 12.x to 14.x, until I looked at the version number on the driver in Device Manager.. it's really 1.4.2.0, so in reality we just went up a minor version.. 1.2 to 1.4. No biggie.

I used the compatiblity tab that gets installed with SP2. Create a shortcut on your desktop to <your cd drive>:\setup.exe, e.g. e:\setup.exe Go to the Compatibility tab (it will be the last tab in the Shortcut dialog, after you've installed SP2) and put it into either Win95 or Win98 mode. Click OK, and run the shortcut. RA should install normally. Then upgrade to Counterstrike and/or Aftermath.

You'll need The Aftermath. It patches RA to be compatible with NT/2000. (that's the second expansion pack for RA, if you didn't already know.. Counterstrike, the Aftermath)

I have the exact same hard drive (Western Digital WD400BB-00AUA1) and it runs flawlessly for me at ATA100. First off, here's my system: 900 Mhz Thunderbird MSI K7T Turbo (which uses the VIA 686b southbridge) GeForce 2 MX400 SBLive aforementioned hard drive Creative 12x DVD-ROM generic 56x CD-ROM Creative 6432 CD-RW Windows 2000 Professional Debian GNU/Linux And another data point, previously I had a K7T Pro (686a) and a Promise Ultra100 20267 IDE Controller, which the hard drive also ran flawlessly on. I know that you have checked a lot of things trying to get this to work, but I'd like to throw a checklist at you again, since you haven't solved your problem yet, and hopefully we can find your problem. 1. Make sure you are using an ATA66 80-wire IDE cable. One of the connectors will be blue, and the ribbon itself will have smaller wires in it. 2. When your computer boots, what does it say on the second BIOS screen? The one that has everything listed in a table and gets scrolled off the screen by Windows loading is the one I am referencing. Mine lists my drive like so: Primary Master: LBA,ATA100,UDMA5 3. Check your BIOS settings. The ones in particular that matter are in Integrated Peripherals and are: Primary Master PIO Primary Master UDMA These should both be set to AUTO. 4. Make sure you have the latest BIOS for your motherboard. 5. Check your Windows drivers. You will probably want the latest VIA 4in1 drivers, 4.32. In Win2k, under Device Manager, VIA Bus Master IDE Controller, the version number for viaide.sys is 5.0.2195.5110. Offhand I think that's not the newest version, but there has been 686b ATA100 support for the past 4 or 5 driver revisions, so as long as you are up to date, you will be ok. The procedure under WinME is similar. 6. Make sure you have Service Pack 2 installed, on Win2k. There were issues with ATA100 that were fixed in SP1, IIRC. Plus, there are literally hundreds of things that SP1+2 fix. It's just a good idea in general. 7. Check your settings in Device Manager. Under Primary IDE Channel->Advanced Settings, it should be set to DMA Mode If Available, and will register as Ultra DMA Mode on Win2k. (I noticed XP actually lists the mode number.. much nicer!) That should just about cover everything related to ATA100. I don't have Sandra installed at the moment, but in HWINFO's benchmarks, I get 74.50 read burst rate and 16.81 random access mode, which are the best scores I have had yet. (They have gotten better as newer VIA IDE drivers have been released) I would also like to point out that ATA100 does not necessarily equal 100 MB/sec. This is a theoretical maximum, and usually get bottlenecked by other parts of your system, especially your PCI bus. Also, I noticed some posters said that you had to run a program from Western Digital to enable ATA100 mode on the hard drive. I never ran such a program and my drive has worked at ATA100 from the first time I plugged it in. I have never even put the WD disk in my floppy drive! I think I will check it out though, just to see what it says. But I didn't have to do a thing to get it to work... Anyway, I hope this post helps you out. I'll be checking this thread, but feel free to mail me at the address in my profile if you have any other questions about the drive. But it'd probably be best to keep the discussion here. James

Are you using 3dfx's beta drivers? I also have a Banshee and am using them. From what I remember, the beta drivers do not support Direct3D yet, just Glide and OpenGL. I'd have to check the driver readme to be sure though. ------------------

I have a Voodoo Banshee and I have had no problems (short of 3dfx's lackluster driver release schedule). I have an OEM board, straight from 3dfx and am using the lastest 3dfx reference beta drivers from their page. I play Half-Life often and have had no problems whatsover, I run in 800x600 using the 3dfx mini-driver provided by Valve, WickedGL, and the MiniGL from 3dfx (which is newer than the one with HL) (btw the MiniGL is still there, on the Banshee driver page) Make sure you are using all 3dfx driver files. Did you install any of the non-3dfx drivers that were out for a while? You might want to check that they are all overwritten, or even do a clean install of win2k (!) Also try SP1 and see if it does anything. FYI I have played Half-Life (Counter-strike), quake 3, Jedi Knight, Descent 3, Tiberian Sun, Unreal, Unreal Tourney, Mechwarrior 3, Homeworld, X-Wing Alliance, and Starfleet Command all in win2k with no problems.

I too have gotten this, on Homeworld especially. Also a few times on Halflife and Jedi Knight. Anyone? k6-2 450, fic va-503+ mobo, win2k pro, voodoo banshee 16 meg agp