Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 14 SEP 1999 02:33:44PM Warren wrote:

Earlier this year a client moved from Novell to NT. I upgraded their v1.16 to v2.03 (app is scheduled to be phased out by 4th quarter 2000) and installed NT Service v1.5. Workstations are Win95 with Y2K patches from Microsoft. Server is NT v4.0 with SP4 and Y2K patches.

They recently added an NT Workstation (v4.0 + SP4), however it take 10-15 minutes for ARev to start on the NT WS. It then runs for a few minutes then ARev shuts down by itself. I've not made an onsite inspection yet and I am still waiting for configuration info on the WS (RAM etc).

Any suggestions as to possible trouble spots and solutions are welcome. Other clients are running NT WS with no problem so I'm scratching my head on this one.


At 14 SEP 1999 05:30PM Steve Smith wrote:

This probably has to do with device contention. Are you running AREV from a pif - if so have you enabled background processing? What are the other settings?

The service pack level may be significant.

Steve


At 14 SEP 1999 07:07PM Warren wrote:

Standard ARev 'pif' - /x /m4096 640K conventional, 256K Env, 4096 EMS, no XMS, use HMA, DPMI auto, always suspend false - first thing I had them check.

Could be a printer conflict, but app should not be accessing printer at startup.

Now that you mentioned pifs it jogs my memory that another poster mentioned a left over _default.pif from Win3.1 to NT upgrade causes much grief, however the system is new (8 gig, 128MB RAM) though I'll determine how NT was installed (over Win98, or drive formatted and installed fresh or with Ghost).

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/94128bb7c22ad7e5852567ec0065f761.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1