[THIN] Re: Win2k "badapp" tuning

  • From: Jim Kenzig <jimkenz@xxxxxxxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx
  • Date: Mon, 24 Mar 2003 10:54:28 -0500

Jeff see this document written by Rick Mack...Only some settings work under
Win2K not all of them.

(link may wrap)
Slider also has an access 97 compatibility script he wrote see:

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Gunn, Jeff
Sent: Monday, March 24, 2003 10:10 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Win2k "badapp" tuning

Hey All,

I've been digging through the archives and I'm finding conflicting info
about "bad app" tuning and Windows 2000.

I've got the classic problem of trying to run Access 97 on a Win2K server -
quad 2Ghz procs with 4GB of RAM.  2 Access users darn near max out the CPUs,
which obviously isn't good.

Now, I have used cmptman.exe before, and just about everywhere I looked I
found a warning stating that it doesn't work for Win2k, but I also found
postings (from Jim, and others) saying the thin.net version DOES work ok for
Win2k.  I downloaded it, and after tweaking the settings for a while, I'm
not seeing much improvement.

So...what's the definitive word?  Are all of the relevant registry tweaks
effectively ignored by Win2k?  Does that make the utility useless?  Either
way, can anyone suggest a way to get Access97 tamed a bit, so we could get
maybe 15 or 20 people on the box?

        Much appreciated,
This Week's Sponsor - RTO Software / TScale
TScale increases terminal server capacity. 
Get 30-40% more users per server to save $$$ and time. 
Add users now! - not more servers. If you're using Citrix, 
you must learn about TScale!  Free 30-day eval:

For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:

Other related posts: