Superdan

Yes, I agree on the issue of the whole searching issue... many of these topics become quickly confused and misleading. In the meantime, new info becomes available that warrants issuing a new topic. Esp for new members to our forum. Let's put aside our elitist attitudes and try to make this forum what it should be...a place to offer and find help for our chosen op system. Keep the good work going guys.

Gee whiz ByronT, I think this is the first time I've seen you upset... :-) Look all, good and simple. Get as much ram as you can afford. Multiply by 2.5.... be done with it. Hard drive space is cheap, so using too much aint gonna hurt so bad. BTW, I've noticed my Win2k server buzzes along using 192mb of memory pretty consistantly. My Win2k Pro uses anywhere from 55-65mb of memory. Thought i'd throw these out just to show the basic memory requirements for each. Make sure you have more RAM installed than your system is using when just idling along....

Yup, it's a no go on this one. I kept it for use with Win98, as I've been waiting for this one for awhile. Still, Hornet Korea runs in Win2k and even compared to Janes F18, is still a pretty good sim... If I knew I could attach a note to Janes and put it on the box that said "NOT WIN2K COMPATIBLE" I'd make the trip to the store today.

The Real Fix, or not...I'd like to thank this guy. I was getting consistent (every time I played) key locking in unrealT, both in Win98 and Win2k. Moved my PS2 to the serial port using the included adapter (Logitech). I've not had a lock up in over 5 hours of action. At the very least, i'd say it helps...

The Real Fix, or not...I'd like to thank this guy. I was getting consistent (every time I played) key locking in unrealT, both in Win98 and Win2k. Moved my PS2 to the serial port using the included adapter (Logitech). I've not had a lock up in over 5 hours of action. At the very least, i'd say it helps...

An interesting note... I've noticed the same thing happening in Win98 SE and UT. May be related to DirectX... i'm running 6.1, I'll try to upgrade to 7a on both Win98 and Win2k and see what happens.

Try using the 3.65 drivers. I have had problems with both the 3.66 and 3.69 drivers in other games...for Freespace I'm using my Diamond Monster2 card...

Yup, I've even installed it in Win98, and copied over the registry stuff...that has worked for many other games. Not for this one. I can't believe EA would release a game only for Win9x with W2k so close. Oh, well. Back to Hornet Korea!

I use the "HCF 56k PCI modem" and it works like a charm....

Your not gonna believe this...build 2183, Asus P3B-F, Logitech 3 button...All was fine until yesterday. My mouse works fine on the right side of the screen. But sticks (freezes for a sec) on the LEFT side...I told you, it's hard to believe...I've noticed that the hang always occurs when moving it to the left, and if I continue to slowly move it left, continues to hang. As soon as I move it to the right, it immediately releases again. Hmm. No viruses, nothing unusual running in task manager, nothing changed since yesterday... Motherboard? Corrupted mouse driver? I am running a full Thrustmaster stick set, but I've never had this prob before. I figured one of our resident guru's might shed some insight for me. Thanks in advance.

Well, while I am a MCSP, you think I would have immediate access to the latest and greatest...but the release build has not yet been posted to Microsoft's Subscirber download site yet...suck...

Yep, Yuppie. I can attest to that. I tried several drivers to get the game port working, each time wound up with increadable hosage... There are two things to know here: the game port after the Liveware install is listed as the "Creative Multimedia Interface". Come to think of it, it may have been called that too before the patch. But I digress... The name of the driver you want is "Game Port for Creative". Use the drivers that come with Win2k! Dated 5/23/98, ver 5.0.0.0. I have mine running this now, but my liveware patch got broked when I was dinking around with something else. You'll know you got it wrong if you re-boot and it takes an hour to get back to the Device Manger screen to disable it...really slows things down.

Gotta go with the P817... I'm running the P810, the previous model, and it totally rocks. No complaints, anywhere. You wont go wrong with VS...

Very good comments all, But I have a very strict ball-cleaning schedule. In fact, before I posted my comments, I made sure I was not caught with in a potentially embarrasing position of having crud on my....well, you get the idea. :-) I did the re-boot boogey several times, each time verified the same condition. Finally, stopped horking up on it's own...go figure. I think it's those nasty Ruskies, or Talibans or whom ever the bad guys are these days..... Thanks for the laughs

Hi Guys, Can anyone pass on which driver to use for the SB!Live game port? I remember seeing it here somewhere, but have yet to find it. It was working for me prior to the SBLive fix I did last week (nice to have all speaks kicking)...Thanks for the info and sorry for posting something that's been round the tree before.

Yup, seems like everytime I try a new one, after the reboot, the system slows to a crawl...it takes an hour to disable the port and try again. Bummer.

Any luck getting Flanker 2 to run? Loaded fine, plays way cool intro, then exits with no errors given. Viper 550, build 2128.

Just an update, the new Nvidia drives now loads the game. But the mouse will not work. More as I get it...