DosFreak

Q3 is fully compatible with Windows 2000. I'll have to look up the requirements for Alice but I believe it is fully compatible with Windows 2000. In any case Alice uses the Q3 engine and as such is compatible with Windows 2000. It'a a driver issue. Get use to it you have an ATI card.

Nope, same fps.

You said SVGA so the DOS version? Did you try to run setup in full-screen NTVDM mode?

Hmm. the SHUTDOWN problem is a registry tweak. As far as stability I can't help ya there. Pro has been the same as Server as far as stability goes in all kinds of hardware since they are pretty much the same OS...just that server has more tacken. on.

Going from 2D->3D on a 2D display. ;(

Do you mean "compressed folders" as in the inferior equivalent to Winzip? or the file-system compression used by NT (inferior equivalent is 9x's Drivespace program)

Server same as pro. With a powerful enough system leaving the extra services on will not degrade performance...unless you have 100+ users pulling stuff off your server.

1. When clicking on a link for a FAQ have the link jump to the FAQ question? 2. Provide Mod's (or anytone really) the ability to edit the FAQ. I'm guessing a seperate page would have to be provided for the FAQ for this ability.

http://g256.com/guides/Q3Bench/comments.html

In reference to above: *cough*permissions*cough*

The "Search" function is a wonderful feature. http://www.ntcompatible.com/forums/viewtopic.php?t=14115

USB does exist in "safe" mode but your BIOS must support it. Most do not. Look for "legacy" bios options in your BIOS. Yes, the ISA bus is being phased out. Although it's nice to have Serial/Parallel since that's all that's really needed in most cases to transfer data these interfaces are slowing our computers down. Also there are USB to Serial/Parallel interfaces now so there's really no reason to not upgrade. The floppy connector is also useless since IIRC some BIOS's can boot from USB.

Quote: Quote: Installing 2K SP3 on a dual-boot with XP makes XP unable to boot. This is because 2K SP3 replaces the NTLDR/NTDETECT.COM with it's own which does not recognize XP. FIX: Replace NTLDR/NTDETECT.COM with the XP versions. Stupid Microsoft. It's not SP3, this is true for any install of W2K after WXP. You will always need the newer NTLDR for dual boot to work. Install XP last and you avoid problems. Yeeess, but they bothered to provide an updated NTLDR/NTDETECT.COM in SP3 so why not update it to be XP aware? That is the point that I was making. It's thing's like these that do not happen in the *nix world. NT4 was still compatible with the 2000 NTLDR/NTDETECT.COM....but XP was not. Interesting is it not? It's a bug..

Hmmm, unsure of the .dll's that Movie maker may require. Simplest way is to copy the directory off of an XP install and copy it over to 2K. Execute it and then copy over any .dll's that the program may require. To get more indepth you'd have to check out the .inf's and try to find all of the files that go with the prog. or The Movie Maker update that just came out may be able to be extracted and run seperate without going through all of the above.

In the IT field we laugh at ourselves more so than others. I know I do. I just posted an amusing thread...I really don't see the problem.

Basically, Ansiotrop will remove the blurriness. Load up a Q3/SS level and look off in the distance at the ground. Now enable Ansiotrop. See the diff? FSAA removes the jaggies. @ 1600X1200 it'll be harder to see the diff in most games. Load up 1024X768 and enable/disable and you'll be able to tell more easily. In games such as ST:BC where lines are in your face more often it doesn't really matter what res you use because jaggies will always be there unless you use FSAA. More curvy games such as Q3/SS are hardy to notice at higher res.

Updated the guide again. Also found a link to a script on another forum that basically runs through a batch file and asks you questions. It then compiles the CD for ya. I'll see if I can find it again. Dunno if I want to post it tho since I haven't tested it out myself. I prefer the WinISO myself....

Hmmm, for me: Too much tweaking of the desktop required to get rid of annoyances. I will have to actually have to sit down with notepad and go through EVERY single thing in the OS and document all of the annoyances and then have to look for all the .reg fixes to do it. That'll take more time than I have. I've noticed that XP seem's to be slower than 2K with time....On the surface it *seems* faster and I was thinking that it was Application/Background but it isn't that either. Even with all of the desktop graphics settings set for "Best Performance" there is just too much lag/latency in the XP desktop. It's not simple graphical tweaks either. Processor usage seems to be increase and even something as simple as the CTRL-ALT-DEL when you need it the most may not ever come up if the system is "busy". This never happened in NT4/2K. RTM of 2K: Dec 1999 RTM of XP: Sep 2001 That's pretty much a year and a half of development time for XP which sums it all up for me. As insane as it sounds .NET will likely be a better desktop OS for the power user than XP is. The "increased compatibility" has no effect on me whatsoever. ALL of my games on 2K work on XP. The built-in XP sound emulation is crap compared to VDMSound and even XP's ability to play DOOM/BUILD games with SFX isn't a factor for me since I cannot play BUILD games in VESA in XP anyway. The UI since it's so unresponsive to my needs and does not benefit me in the slightest doesn't turn me on. "2K Classic" is not 2K and the UI is still slow. XP is newer than 2K. No Service Pack yet so less polish. XP also seem's buggier to me than 2K was when it first came out and the fact that XP Pro "feels" like XP Home doesn't turn me on either. The tons of "XP" programs that started coming out when XP was released just give me a sick feeling inside and I immediately ignore those. XP this...XP that ;( How about usability/efficency? I really don't care about the "experience". Hardware compatibility. It's said that XP supports more devices. Wrong. 2K currently has more driver support than XP does worldwide. I've run into this situation several times. Yes the drivers are in most cases interchangeable but when your building systems for someone or fixing someon's system it's best to use certified drivers for the OS. I have never seen the supposed performance increases that others report. I can only conclude that they not comparing the 2 OS's fairly (using different driver/hardware). In all of my testing 2K and XP are pretty much the same or so close as to not really matter. The product activation in XP is a big turn off. I use the already activated versions but that product activation really makes me . It's amazing that people actually buy the retail versions of XP. I just can't figure it. That's why I refuse to buy XP. I will be supporting their product which I do not approve of. I'll just continue to use my work copies. With all this said: XP is MS's latest and "greatest: OS. For continued usage of the latest and "greatest" Windows programs your gonna have to use XP at some point. The trick is to constantly keep track of alternative OS's and be aware of backwards compatibility of the latest Windows programs with previous OS's.

Why installer a "newer" OS when you could most likely get your games working with the old quite easily? Compatibility across the board instead of worrying about new "features" introduced by a "newer" OS. 2K is 2yrs 8months old. XP is almost a year old. Get the picture?

These constant programs showed on the frontpage are annoying. As far as I know NTCompatible is not a file-news forum. It's NTCompatible. We should leave file-news for those websites that are devoted to it..... Anyone agree?

Noticed this at www.g256.com Quote: I had an odd problem with my RAID controller (HPT372 - onboard) and sent an e-mail to Highpoint asking a question with some really detailed system info. What fixed the problem was me restoring a Ghost image from a month ago. But, HighPoint Tech Support sent me this back: We do not recommend using Norton software - much of it is listed as not compatible with RAID controllers I should send that to Norton. Do they mean older versions of Norton software..? Which Norton software..?

"Upgrade"?

If you can ping your loopack & ip then your NIC is working properly. Hmm, you say that you are getting link on the cable? This does not necessarily mean that the cable is good. Try a different crossover cable or just use the switch with straight cable.

Won't work. The .dll's that access the .sdb's are OS specific relying on dependencies not available in 2k. Bets solution for now is to use the Compat database to view the XP .SDB, write down the fixes that XP applies and then using Qfixapp apply these fixes to your games in 2K.

http://www.fastgraphics.com/forum/fastvid.html