NT server - DOS/NT workstation, NT service a must ? (AREV Specific)
At 30 OCT 1998 02:04:52PM Albert Hawking wrote:
tried to read this list for hours but can't find an exact answer.
NT server - DOS and NT workstation environment, Is NT service a must ? Is there any important issues that I should be aware of?
At 30 OCT 1998 07:12PM Chris Banwarth Revelation wrote:
Albert,
We do recommend using the service due to the fact that it helps to prevent GFE's and improve performance. If you have any further questions, please contact our customer service dept. at (978)691-5757.
At 30 OCT 1998 10:13PM Andrew P McAuley wrote:
NT Service is never a must - NPP is a MUST!!
NT Service is a "gee - look at all the benefits I'd get, better performance, no GFES and all that for a small outlay" kinda solution. That is you'd be nuts not to BUT you can do without.
Kinda like driving a car in Death Valley without air-conditioning!?
Toodles
amcauley@sprezzatura.com
World Leaders in all things RevSoft
At 01 NOV 1998 03:14PM Larry Wilson - TARDIS Systems, Inc. (all things timely ) wrote:
AMcA,
I'm afraid I must disagree on the GFE problem. If you view your server stats and find errors, then the number of threads (and probably MB of memory) is too low; I have found this to be the cause of the GFEs. Apparently, when a write or lock is denied due to lack of NT resources, it doesn't tell AREV it's cacheing the action, and AREV proceeds. Once I boosted clients systems so there were no failed reads, write or locks, then the GFEs magically (in 6 months so far) reappeared; and if you adjust other parms on the server (like reducing foreground boost to 0 and doing a couple of things in REGEDT32, the system absolutely screams. (It's real scarey at first!)I don't us NPP on any system, and had have no problems in 6 months, with most system averaging 200,000 transactions/month. I'm going to publish an NT FAQ on my website this month, along with my custom RTP5 pre-compiler that can be placed on client sites so that dict source can be stripped and not injure the system. The old pre-compiler (the one I borrowed from; err, really just modified a bit) didn't account for type 'MQ' (reports) and so it would fail or produce bad results on SELECTs, but that is fixed here. It only works on 3.x system with no plans for 2.x. Also, I hope to have it modified to warn you if any screens (encrypted or not) need modification depending on how you modify the dict item (indexing also, like if you change justification from L to R, it will delete the ! item with your permission).
But, again, I digress in a rather wordy fashion, but this NPP thing seems to me just to be a way of dealing with a technical system problem with brute force.