Currently, I am running TWGS on Windows 2000 Pro Fresh install with the following changes to the OS:
- VNC Server installed
- In My Computer Properties, under Advanced, in Performance Options, I changed it to be optimized for background services.
- Completely up to date via Windows Update

The following hardware specs:
CPU: Celeron 433
RAM: 128MB
HD: 10GB Western Digital
Network Card: 3Com Etherlink XL 10/100 PCI

So, I installed and setup TWGS beta, works great, then I install it as a service (as instructed previously). So, now I'm going to do a bigbang, works fast for the first 5 mins while I stumble around the options (just looking around, getting a feeling for the options). Then all of a sudden, it takes a few seconds to respond to everything I type. I have the BigBang stop responding once (after waiting for 5 minutes, I close the window, this is before the actual generation happens), restart it, manage to get though it (painfully). Then go into TEdit, ugg... same thing, freezes up after I change an option. Then I logout to go play the game on my other comp (no need to be logged in unless I have to). and when I load up the game, I can actually watch it as it draws charactors on the screen, not what happens when I log into other places...

Then I go, hey, I never finished TEditing, and I log into the server (from the console), and after I log in (though the windows user) the server crashes.

Any Clues?

Alright, it's gotten faster (no clue why, this driving me nuts) but every two times I log in as administrator, the game crashes. Tis quite annoying.

Repost From TWGS Sysop / Gameop Forum:

TWGS/VNC Issues w/ WinNT/Win2k/WinXP

Problem: Under some WindowsNT/Win2k/WinXP setups running TWGS and the Bell Labs VNC Server for remote access, users may encounter problems with the TWGS Shell Console crashing with General Protection Fault error messages. The GPF crash occurs only when the Shell is running (TEDIT, Spy Window, Big Bang), and only if the remote pointer is moved over the remote window's taskbar.

Danger: The crash does not (appear to) affect the operation of the server, only the Command Console However, there is always a risk of data corruption when exiting (via close or crash) from a Shell window unexpectedly.

Solution: Enable the Full Screen Polling option in the VNC setup. This problem appears to resolve itself when the Full Screen Polling option is enabled.

Cause: Unknown. Because the problem can be resolved by changing the settings for the VNC server, it's likely that this is not an issue caused by TWGS/TWv3.

Lisa M. Cutler
aka Rave
EIS Product Support

Edited by - Rave on August 21 2002 12:57:59 AM