DosFreak

Yep, SCSI performance dropped from 2K to XP. Big bug. Dunno if it's fixed in SP1. Anyone done any benchmarks? Gonna check out the thread at storagereview and see if it has.

Have you tried any of the compatibility layers at all? Right-click on the game shortcut. Go to properties Go to compatibility Pick an OS (95/98) Hit Ok Try the game through the shortcut. I do not have the game but I can give you several tips. The above is the first thing to try as the most general fix for most compatibility problems.

The corporate updates site has not been updated since March and according to Microsoft never will be. They have moved to the "Catalog" and SUS.

Hmmmm, bump.

A Red Alert patch could not mess up your system. 2K has SFP which protects 2K files. Any file overwritten would be re-overwritten by 2K so I would say that a Red Alert patch did not mess up your system but something else did.

Welll, 1. DDR is faster than SDRAM. 2. The GF4 is basically a GF2 with just a few added features. 3. You wasted your money. 4. Sorry. 5.

On older machines the mor ram the better. Upgrade to at least 128mb.. At 64mb it *should* be faster than 98 but it depends on the user.

Yes.

Catalyst 2.2 drivers http://mirror.ati.com/support/drivers/winxp/winxpradeon613106118.html Release Notes http://mirror2.ati.com/drivers/Catalyst-02.2-Web-Posting-Release-Notes.pdf Quote: Features of ATI CATALYST™ Version 02.2 OpenGL Performance Boosts: CATALYST 02.2 provides significant performance improvements in OpenGL games across the entire RADEON product line, especially at high resolutions. Up to 25% improvement in Quake III (1600x1200, Max Quality) Up to 35% improvement in Return to Castle Wolfenstein (1600x1200, High Quality) Up to 50% improvement in Serious Sam: The Second Encounter (1600x1200, Extreme Quality) ARRRRRRRRRRRRRRRRRRGGGGGGGGGGGGHHHHHHHHHHH!!!!!!!!!!!!! 50% performance increase in SS:SE? Give me a freakin break.

Upated the guide again.

The compatibility database is unchanged as far as list of API fixes. As far as APP fixes I see no diff. The main .sdb is considerably smaller which leads me to believe that MS is actually dropping support for applications from their compatibility database in 2K but this is just conjecture so far. I'm going to do a compare between SP1/2/3 and the App Compat Releases to see if MS is dropping support. Hopefully they are not. If they are then that's another thing I can add to my linux list.

Because Microsoft didn't port the fixes in the .sdb's to 2K. Why would they? This would make Windows 2000 users happy which would take Windows XP market away..... Sigh.

2. Reinstalled IE6 again and now Web View works. Stupid IE6/SP3. NEW ISSUE #3 (SORTA) 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.

SP3 includes almost all hotfixes that have been released after SP2. Suppsedly the hotfixes in SP3 have been tested more in SP3 than the earlier pre-SP3 hotfixes. The common practice for new SP's is to wait for 30 days...which seems to even more suitable to this SP since I have noticed some oddness with it.. Problem #1 1. Reinstall 2K Server fresh. 2. Installed my apps. 3. Had problem with network adapters. All 3 would not let me modify my IP settings stating that "I had to enable a protocol and enable the device). The device was enable. The protcol was there. The protocol was checked. No go and I have no internet at home so I had to reinstall. Problem #2 Got done reinstalling. Installed IE6 release Looking in SYSTEM32 or Recycle bin I get scripting errors for the web view. I have to disable web view for these folders. Dunno if this is a posted problem or not. Gonna have to check the web.

Yup, I'm trying to figure what I should do for our network. Good thing we have a firewall but it still doesn't make me feel safe. Not going to deploy SP3 for 30 days but even then...it's a tough decision.

Check the datetime stamp in the images that you created. They should match the datetime stamp in SP3 if they updated correctly. For me I get the same datetime stamp as in the original bootdisks.

rgodart, Could you use the Slipstream thread in the Tips & Config forums? This will free up the Feedback forum for what it's for...also we are also discussing this subject in that forum.

Also to clear things up in case people get confused. If your EXTRACT.EXE does not have the -I option. Then do not use it. So to verify that you have the porper one in your path simply go to your Command line and run EXTRCT. If you do not see the -I option then you will need to download EXTRACT from the link I posted.

Yep, the procedure that I will list in the Guide for WinISO. Create an .ISO using your original 2K CD. Extract the entire CD to a subdir (Would say just extract I386 & Root files but this could be confused). Slipstream the subdir Using WinISO delete all of the files in the .ISO Using WinISO import the subdir into the original .ISO. Burn the CD. This will remove the whole boot marker files/boot sector problem altogether for those with original 2K cd's that boot properly in the first place. *Was testing last night and it seems that BDUP.CMD no longer works. Strange, because it worked a couple of months ago.... For now there are 2 ways that you can make your boot disks to get 'em working: 1. Take the TXTSETUP.SIF from the updated SP and update your floppy images with this one. (Up[censored] ALL of the files on the images is not required to perform an NT install...although it is recommended) 2. Manua update ALL of the files on the floppies yourself. This will give you a less buggy installation if you experience a problem using the original image files. This is what the BDUP.CMD was created for but I'll have to play around with it tonight to see if I can get it working.

Hmmm, gonna check this out tonight because I coulda swore it worked. Compare the files in the SP3 floppy images to the SP2 floppy images. See if there are any differences.

Just checked Microsoft Windows Update and noticed that Service Pack 3 was available for download. Looks like it's official. It's also listed here: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q260910

SP3 is officialy out: Just checked Microsoft Windows Update and noticed that Service Pack 3 was available for download. Looks like it's official. It's also listed here: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q260910

FOUND IT. DO NOT USE ANY OTHER EXTRACT BUT THIS ONE! EXTRACT From Winimage's Site: http://ourworld.compuserve.com/homepages/gvollant/extrac21.zip ftp://ftp.winimage.com/extrac21.zip Place the EXTRACT.EXE from the .zip into your SYSTEM32 or add it to your PATH. This is why BDUP.CMD was not working.

FOUND IT. DO NOT USE ANY OTHER EXTRACT BUT THIS ONE!\ EXTRACT From Winimage's Site: http://ourworld.compuserve.com/homepages/gvollant/extrac21.zip ftp://ftp.winimage.com/extrac21.zip Place the EXTRACT.EXE from the .zip into your SYSTEM32 or add it to your PATH. This is why BDUP.CMD was not working.

Nope, go the OS doesn't matter for BDUP.CMD as long as it's NT. It requires NT due to the .CMD extensio and primarily because of EXTRACT.EXE . Nope, you can't use the Extract.exe from your 2K CD....and I just noticed something. I asked if anyone had the original EXTRACT.EXE used by Zarqon @ arstechniica and someone responded that they had it and posted a link....but the posted EXTRACT.EXE doesn't seem to be the right one. Sigh. I really do not want to post the other way to make bootdisks because this script makes things ALOT easier. (Other way involves a crappy batch files that copies the files out of the I386 folder into respective # folders to match the # of the floppy disk. You then have to manually add these files to a floppy image. (This has to be done for each one PRO,SERVER,AS) Hopefully I can find the proper EXTRACT.EXE tonight. *Oh, You do not have to re-create the ISO to fix your bootdisks. Simply download WINISO and import your bootdisks directly into the .ISO. This makes it much simpler.