ECC

The general consensus is that my spelling is terrible.... but also... the two best monitors in existance right now are the Mitsubishi 2020u and the Sony F500 I spent a month researching it and every review gave mad props to these monitors and the mitsubishi usually won, although most of the time they said its too close to call, but gave the mitsu got the nod cause it costs 300 bux less. Thats a very good thing =] I personally use the mitsu 2020.. its 22" of pure loving.. and 1600x1200 is something to be seen. If you want links to reviews i can dig 'em up again.... but i do remember gamespot.com has a review of each monitor. Best price i found was 973 at onvia.com (free shipping even). Best price for the Sony F500 was like 1300 or so though =[ Don't be fooled by specs though.... they're rarely a representation of how good a monitor looks.... the best companies underrate because they have confidence in their stuff. Its true in the audiophile market and its true here too. -Brad

I freeze.... right after the dialog box with all the pre-startup setup stuff... and before I even get a menu... all I see is a stoney background and its a total lock. Has anyone else experienced this problem... previous version of q3a run real well. I also can not get Mech Warrior 3 runnin'... which is reported to work in w2k... I run rc1 with the asus detonator drivers (TNT2U) and a mx300 soundcard hmm, Ecc

I can't even get this program to run long enuf to show up in task manager. Has anyone had luck with this demo? -Ecc

I'm running RC1 (build 2072) and I used those d/l'able drivers. My MX300 works well.. but not perfectly. mp3's are doing a bit of popping... its slight but annoying... maybe a speaker problem... will investigate =] Not sure why my install worked and igor's din't... =[ -ECC [This message has been edited by ECC (edited August 15, 1999).]

I run RC1 as well... and I can't install the diamond MX300 drivers. Blue Screen when I try to click the Aureal "Ok" button after the files get done copying I'm d/l'ing the a3d reference drivers right now, don't forsee that working either, but we'll see. =] It looks as though RC1 is just NT4 driver unfriendly. With the DDK released for w2k there is NO reason drivers shouldn't start appearing in "beta" form or "no support from us" form. But alas... even after w2k's release we'll still be waiting for drivers. I feel like I should write my congresswoman... but that probably wouldn't do any good.... would it? =] Using his 5yr sb16 mcd for sound, ECC *shudder*