Ok, this has been a problem since the TWGS had the ability to run as a service. The TWGS when set to run as a service just dogs my system. By that I mean I get hard drive hangups causing significant pauses where the system is totally unresponsive. The machine will not shut down unless I manually shut down the TWGS first else it throws up an End Task dialogue to kill the TWGS service. I've put it on several different machines, put it on NT 4.0 workstation, 4.0 server (what it's on now), Windows 2000 Pro and Server all with no improvements in performance. I live with it, have been for a couple of years now, but it is an annoyance. Does anybody have any ideas?

I am looking forward to the day when I can toss the Windows server altogether and just run all this kind of stuff off of my FreeBSD box...

You haven't given us your system specs, so it's hard for us to help you troubleshoot.

I was using a cyrix 533 *like a P2 or athlon 500* With a 10 gig 5400 RPM Samsung drive, and 512 SD ram.. Onboard audio and video, running XP-

I had almost 0 problems with resources, freezeing, or stalling.

I wanted a faster server, so switched to 98SE, I had major resource issues, so went back to XP. The server coming up in december has A celeron 2.0, 40 gig 7200 rpm drive, 1 gig DDR (2700 spd) With an nvidia GF4 440se.. Now.. The trial run I tested last week, had major latency and resource issues (latency was solved by disabling packet sharing, resources were free'd by using the windows graphic drivers instead of nvidia's)

I don't know what kind of issues your having yet, but I'm sure we can come up with something!

quote:Originally posted by Grazhoppa

You haven't given us your system specs, so it's hard for us to help you troubleshoot.




That's what I get for posting when I'm tired out of my mind..

Ok, it's been on everything from a dual-processor P166 system to it's current incarnation on an Athlon 500 box, each time with the same problem. Current config is Windows NT 4.0 server, 128mb RAM, with a total pagefile space of 384 divided up between NTFS volumes D: and E:; 128 on D: and 256 on E:. Foreground applications receive no performance boost. Service Pack 6a with the security update package and all current critical patches up to date. In it's current incarnation it is a domain controller with WINS and SNMP services running, though in past configurations as NT workstation and Win2k Pro it did not have these running and had the same performance problems. The disk subsystem is 4 2gig Seagate 16-bit SCSI2UW drives divided between two channels on a Mylex DAC960PG RAID controller, configured RAID level 0 for performance only, no redundancy. Video is a Number 9 Revolution IV AGP connector with 32mb SDRAM - way overkill for the box but the next step down I've got it a Matrox Millenium II AGP w/4mb (and yeah, I've tried that too). I've got no firewall running on the machine since my router is handling firewall responsibilities and I've shared the TWGS folder so that I can do weekly backups from my main machine for that computer, offloading that overhead.

If I run it in standard (non-service) mode it runs just fine. *shrug*

Some 32 bit Windows programs don't behave too well as services. I remember that Microsoft had in the NT Resource Kit, two files that allowed any EXE to be run as a service. Funny things would happen with various programs, from system hang-ups, to odd behavior, to sluggishness of the system, etc.

It also could be that you only have 128M of RAM, and it is swapping out the virutal page file. RAM is cheap, consider buying more if your motherboard can take it. NT 4.0 and Windows 2000 Server can be a memory hog when it comes to running server apps. What other server apps are you running? I had a 1Ghz Athlon with 512M of RAM, NVIDIA TNT2 AGP Card with 16M of RAM, 40 Gig EIDE Hard Drive, and Realtek Ethernet PCI card with a DSL Router running TWGS and didn't seem to have a problem. I didn't run it as a service, but I sped things up by removing Active Directory.

Yeah, I'd lose 2000 and go with lindows, or something <G>

And definitly get more ram, 256 or 512, at least..

Question: does TWGS work with WINE? Anyone tested it out?

the easiest and cheapest way to make your TWGS faster is RAM...It is cheap and effective....That is my next upgrade for my server that will happen in a couple of months
Strider

it could work with wine, but you would have to download some componants and rename them.. which? I onno.

quote:Originally posted by Orion_Blastar

Some 32 bit Windows programs don't behave too well as services. I remember that Microsoft had in the NT Resource Kit, two files that allowed any EXE to be run as a service. Funny things would happen with various programs, from system hang-ups, to odd behavior, to sluggishness of the system, etc.

It also could be that you only have 128M of RAM, and it is swapping out the virutal page file. RAM is cheap, consider buying more if your motherboard can take it. NT 4.0 and Windows 2000 Server can be a memory hog when it comes to running server apps. What other server apps are you running? I had a 1Ghz Athlon with 512M of RAM, NVIDIA TNT2 AGP Card with 16M of RAM, 40 Gig EIDE Hard Drive, and Realtek Ethernet PCI card with a DSL Router running TWGS and didn't seem to have a problem. I didn't run it as a service, but I sped things up by removing Active Directory.


Yeah, I think RAM probably is going to be the fix here. I'll see if I can scrape a few bucks together and finally upgrade it. PC133 is going for peanuts these days. Thanks everyone for your input. After taking the time out think through things, I put a few counters in the system Performance Monitor and noticed that it's hitting the page file pretty hard every time a session is opening and active. Spare parts can only get one so far, eh? I'd still like to know why it works well as an app but poorly as a service but that's just a sacrifice I'll have to live with to ensure that if I'm away and my UPS fails the system will be back up and able to accept connections as quickly as possible.

quote:Originally posted by Grazhoppa

it could work with wine, but you would have to download some componants and rename them.. which? I onno.

There have been some posts on that in the past on here. As far as I remember, people could get the TWGS to run, but couldn't make bigbang work.

Even with the Windows 98 OS installed on a FAT32 Partition option with WINE? Usually that fixes some WINE issues by having the real Windows DLLs available. Of course it defeats the purpose of having Non-Microsoft replacement DLLs in the first place.

Should be able to run Bingbang on a Windows machine, copy the data files to the Linux/WINE machine, right?

Um..

I would say yes, but it would probably cause some sort of corruption.

copying over data does cause problems. I used to do this so I never had to shut of TWGS. then the @#$% hit the fan. Ended up corrupting my TWGS and had to redo games from ground up. that was before i made .twas.

I have ran twgs on a p2 300 up to my dual p3 800s. the biggest thing i have noticed is the ram. the more the better. I currently have a gig in mine. I also do not do anything else with my twgs machine than TWGS. No AV or anything. The computer normally does not even have a monitor hooked up to it. I only do that when I need to manually get to it when a remote network connection is not possible.

Oh well there are Windows 98 emulators for Linux like VMWare that might be able to run it under a virtual machine. Costs some serious money, but runs more programs than WINE does.