You may want to try this in the tech forum as well. Wartrain should be able to give you a hand.

[Update]

I completely rebuilt my system over the long weekend. Haven't tried to play online yet, but we'll see how it goes. I've now got a dedicated partition just for gaming/RTW/BI, with it's own OS installed on that partition, so it should reduce the possibility of any conflicts with other games/apps.

I'm going to go ahead and move this to see if anyone can help in the tech forum.

Quote:

With 256 MB of video RAM on the 6800GT, the 64MB AGP Aperture size should be OK in most cases. The Aperture is not used until the 256 is consumed. However, RTW was built to consume quantities of video RAM that did not exist on any graphic card in the world in 2004 (using Huge size mostly). So you'll be fine on Large (e.g., 80 unit) sizes. And even in most Huge sizes... except maybe with lots of flame textures, buildings, etc.

1. Questions:
What is your exact RTW install state, right now (e.g., RTW 1.0 installed, no mods, no patches?). Did you do a multi-install?

2. Machine configuration:
- MB (with PCB revision # & BIOS version if you can) [e.g., ASUS A7N8X rev. 1.1)
- RAM (and RAM configuration in BIOS, if not default) (e.g., 2x512MB Hyperion PC3200 running at 2-2-2-5-1T)
- Power supply Maker/model & wattage rating (& rated Amps on 12v & 5v rails if known)
- Network card driver version (network chip should show up if you post a Step5).

3. RTW Preferences.txt (& the revision it is from, e.g., 1.6).

4. Output of current gaming DXDiag.

5. Output of MSInfo32; to post your System Information NFO file: SStart - Run - MSInfo32 - save - choose filename.nfo - Upload file to host - hotlink the file in your post.

Hi Wartrain, happy to see you have an interest in this challenge. I previously welcomed you to the team, and want to reiterate how happy I am you've joined the HG team whether you can help in this situation or not.

Quote:

RTW is patched to 1.5 using the (presumably correct method) 1.2, 1.3, BI install (to 1.4) and the 1.5 patch, in that order. Both games are installed in a completely vanilla way, no mods, etc.

BI was patched to 1.6 by adding the 1.6 patch after the others noted above.

Quote:

MB is Intel Corporation Model D850MV, Version AAA57887-301

BIOs version is MV85010A.15A.0035.P04.0201071437 (default for the Gateway 700XL) dated Jan. 7, 2002

Quote:

RAM configuration is 4x256MB RAMBUS PC 400, (standard manufacturers configuration)

Quote:

Power supply is 350W (upgraded at time of Video card upgrade per wattage requirements of video card vendor)

Quote:

I have two network cards: An Intel PRO/100 VE (integrated) card and a 3Com 3C905TX card. The Intel card driver has been updated, but it works no differently from the 3Com card.

Quote:

The version of this file I have (which hasn't changed much, if at all): link

Quote:

here

Quote:

hotlink the file in your post.

If there's anything else, as it may be very particular to my system/situation, feel free to email/IM me. We'll be sure to post anyting of significance here.

And yes, I've skipped a couple of very particular questions here because I did't have time to take the case off my computer, but if it's truly required, let me know and I'll be happy to do so.

Thanks in advance for your help.

[This message has been edited by Chonaman (edited 12-27-2005 @ 09:11 PM).]

Quote:

That is very useful. Your BIOS is fine, though Intel disavows this MB and banishes you to Gateway (as if Gateway made it, LOL).

You system is mostly fine.... but.

I'm assuming your fresh install has the same issues as the 1st post.

It is very complicated (and IMHO stupid), but there are certain things tied very closely between the network and sound drivers in MS OSs.

Your sound drivers say 9/13/2001 18:09:48. Yet I'm seeing some files with 2004 dates. Did you install a sound driver update, or is it stock XP drivers? I would try a new update from SB, www.soundblaster.com.
or
http://drivers.soft32.com/driver/download-Creative_Audigy_SB_Live-22633.html

The 3Com 3C905TX card is outstanding, and the most trusted card which I use in person with network issues.

Make sure you disable one network card, from within windows networking (control panel). I'd go with the 3c905tx, and disable the Intel.

For your MB, intel says this:

Quoted from Intel:

BTW, this is the sort of reason why I don't like Intel MBs. But that is their reason.

Another thing to look at the is Logitech optical mouse. You might try safe mode, with a standard plain ball mouse connected to PS2. Certain Logitech drivers, for optical mice, have given me difficulties in the past (and you guessed it, I don't use Logitech Cams or mice anymore, and hence have no troubles).

OK, so the summary is that Intel MB (especially that line, after reading about them) + Logitech + Network + Sound = potential for problems in your case. I have seen similar network issues with other games, notabley some Command & Conquer stuff and IPX + early updates of SP1.

It is quite possible for this to manifest in certain network problems, though I am not able to say for sure that X+Y=Z. Eliminate the conflicts: use the "intel method" of mobo install, use the new drivers for SB (e.g., new sound driver if not done already), test with a PS2 ball mouse and LOGITECH drivers uninstalled.

Since I know the drivers for the 3c905TX to be good, and sound to be an issue, you can also try reducing sound acceleration. Be sure to reboot after each new acceleration setting, however, or it won't take affect.

Note: To open Sounds and Audio Devices, click Start, point to Settings, click Control Panel, and then double-click Sounds and Audio Devices. In the Advanced Audio Properties dialog box, configure performance settings for sound hardware acceleration.

At the end of the day, this is a driver/OS/protocol issue, with driver conflict (and possible HW conflict, or at least someting the OS is not working out properly) the most likely. The big unknown is the intel Motherboard drivers... they and/or their registry changes can render certain network activity poorly.

Just a post script on the status of my game and machine:

Thanks to Wartrain's tips and suggestions, and a complete rebuild of my system to "Wartrain-like" specs, everything seems to be running just fine. Played a few games in yesterdays' forum party and had no disconnects, and I don't think I lagged (at least no one mentioned that I did).

*Another satisfied customer*

Now that you have a working 2nd OS, comes the most important thing:

Boot to the other OS (your original), and use WinRAR to compress these 3 directories, individually (one by one, so you actaully make 3 RAR files) using the a recovery record of about 3% (in the Advance Tab of RAR)... the recovery record will allow small defects to be corrected, and the file saved, whereas in ZIP, the file is corrupted and lost if even one bit is corrupt:

"Program Files"
"Documents and Settings"
"Windows"

Also compress any other directories (there should normally not be any) that you forced to install outside the defalut "Program Files" location. For example, I install most of my programs to a 4th directory... so I have to back that 4th directory up too.

If you ever have an issue in this OS, like crashes, virus, etc... then just boot to the other OS, and delete PF, DS, and Windows, then extract the 3 corresponding RAR backups in their place... and in a few minutes, you are exactly back to the moment of backup! No fuss. But naturally the key is taking the time to back up when things are going well .

Quote:

It would be great to recover a fully operational OS this way, considering the options. However, this option (recovery record of 3%) is inactive (grayed out) in the Advanced tab, perhaps because I have the feeware version of WinRAR? I also see this may be a command line option, but I'm guessing it too only works with the purchased version.

No. WinRAR is fully functional, not crippleware like many programs. But it is very powerful, and sometimes rather confusing in how things connect.

1. Go to GENERAL tab, & check the "Put Recover Record" box.
2. Go to ADVANCED tab, & adjust Recover Record from 1 to 10%. In my own testing, I find 1 to 3% is enough. I use 3% for the most important backups.

Should a RAR archive ever be damaged, or corrupted, you can use this recovery record to rebuild and replace the destroyed part of the archive (use TOOLS - Repair Archive). It can take a while for the repair to complete, but it does indeed work! If you used WinZip, the archive would be lost. If you used no archiver, your re-install would be corrupt and you would never know it... until the mysterious crashes & problems started occurring that is.

The only reliable way to 100% ensure OS integrity is with a strong archiver, and WinRAR creams the competition with its ability.

BTW, when you create an OS backup, you should also check 2 more boxes in the GENERAL tab... "Create solid archive" and "Test archived files". This will improve compression greatly, and ensure the file is not corrupt at creation time.

Thanks Wartrain, done successfully!