Jump to content
Compatible Support Forums

EEMeltonIV

Members
  • Content count

    18
  • Joined

  • Last visited

    Never

Community Reputation

0 Neutral

About EEMeltonIV

  • Rank
    stranger
  1. EEMeltonIV

    NTkernel --

    My guess would be it has less to do with the OS but more to do with either buggy software or bad RAM. [This message has been edited by EEMeltonIV (edited 31 March 2000).]
  2. EEMeltonIV

    I don't mean to piss everyone off..........

    Hey, wait, isn't this the guy who said he got Win2K to run perfectly and smoothly without a hitch once he, uh, upgraded it from DOS or somesuch? Ah, yes. Moving right along . . .
  3. EEMeltonIV

    Force Commander ??

    There are several other topics on this board that discuss Force Commander, plus comments in this site's games compatibility list . . . The general gist is, so long as you aren't using a Voodoo3 graphics card, the game will run. To get it to run very well, at maximum resolution and color depth, you need a fairly high-end machine.
  4. EEMeltonIV

    Slow network browsing!

    Someone asked a nearly-identical question and a coupla possibly solutions here.
  5. EEMeltonIV

    Win2k / Voodoo3 2k / Star Wars Force Commander ?

    No idea, and you're not the first to post about problems with FoCom. Everyone I've seen who's complained, though, seems to have a Voodoo3 board, so that's probably the problem (and LucasArts had trouble supporting Voodoo boards in a previous title, Rogue Squadron). I think you'll have to wait for a patch :-(
  6. EEMeltonIV

    win2k is microsoft's gaming OS of choice

    I've been under the impression that three of the major reasons Win2K isn't recommended as a game system are 1) hardware support isn't as great as Win9x (though it's gettin' there) 2) not-so-great DOS/legacy support, and there are still some great games that use the old technology (but not a whole bunch) and 3) Win2K is more of a resource hog. Well, with the X-Box, 1) it's one set o' hardware, so no real troubles dealing with compatibility. One X-Box is basically the same as any other 2) games designed from the ground-up for the Win2K kernel and 3) basically the same as response one: they know the hardware's there to support it. So, Win2K's uber-stable kernel makes sense. (And, BTW, I use Win2K as my gaming OS of choice :-))
  7. EEMeltonIV

    Windows 2000 FIX, IS THIS TRUE

    Quote: you guys believe me, Dude, no one believed you -- that's why everyone's been laughing at you.
  8. EEMeltonIV

    Windows 2000 FIX, IS THIS TRUE

    Yeah, what RobGoo said.
  9. EEMeltonIV

    Force Commander

    Again, I blame the Voodoo board. This wouldn't be the first time a LucasArts title had trouble with the Voodoo2 or Voodoo3. Rogue Squadron required a patch to work with those boards -- and, actually, the problems with both games sound identical. I guess the plus side of this is, LucasArts'll patch FoCom, too -- hopefully soon, for those of you who are having trouble.
  10. EEMeltonIV

    Force Commander

    I've heard of some similar crash problems with FoCom from other folks using Voodoo3 boards. [This message has been edited by EEMeltonIV (edited 22 March 2000).]
  11. EEMeltonIV

    Music Match 5

    Version 5.00.0142 is running on my Win2K build 2195 right now. No problems whatsoever. I upgraded Win98SE with MusicMatch 4.x with Win2K and had the same(?) error crop up after the upgrade. That's when I nuked the old version of MM and installed 5.0. I wanna say there's an upgraded version of 5.0 on the MusicMatch site that specifically addresses Win2K problems, but I might be confusing it with any number of other sites I've visited to upgrade my various programs. Might be worth checking out, anyway. If there's nothing on the site, I suggest uninstalling your copy of MM, downloading the most-recent version, and reinstalling. Not much help and doesn't actually address the problem/error message, I know -- but it might just get the program running.
  12. EEMeltonIV

    Force Commander?

    Ah, thank goodness. I reread a very nice summary posted over at http://www.theforce.net/games/ The guy got the FC beta to run just fine on a Windows 2000 machine. Hooah!
  13. EEMeltonIV

    Force Commander?

    The main NT Compatible page has a posting saying Force Commander doesn't work under Win2K. Ignoring for a moment the fact that the fella was likely either using a Beta or pirated copy (game just went gold this week), which thus makes any tests questionable at best, and the problem seemed to be video only, has anyone else here had a more-positive experience with FC on Win2K? I guess I'm looking for a little positive reassurance here, hehe. [This message has been edited by EEMeltonIV (edited 09 March 2000).]
  14. EEMeltonIV

    Gaming at 700MHz

    Yeah, it installed without a hitch and plays great.
  15. EEMeltonIV

    Gaming at 700MHz

    Thanks, all, for your input. Computer arrived Monday and I finally got Win2K setup and enough stuff moved over to have time to fire up a few games. Both XWA (which I heard runs incredibly slow on Win2K) ran like a charm, and I've been busting up those dirty Feds in the new Klingon Academy demo. As before, all your insight was appreciated. Cheerio!
×