We have gradually been switching users to win 95 & win98. We are using the NLM. Task switching never caused any problems in win 3.1 . Under '95 & '98 when arev is in the background for a short time (a few seconds) and we switch back to it, it crashes in varying ways as follows:

"RTP57 line 1. B114 maximum number of variables exceeded"

 this line is repeated in an endless loop that only stops

 by using ctrl-alt-del and "end task"

1. or-

"line 1 'TCL' broke because a runtime error was encountered"

 pressing  stops and closes the program

1. or (most frequently) -

a message window appears

   W156

    Return is an unrecognized word. Please correct the word etc,etc.

    Press 'esc' to restart

   also at the top of the screen the words

    "quickdex.mfs loading error" appear in the middle of the menu      area.

   pressing  closes and ends the program

I've tried various settings in the PIF.

 "always suspend" on or off makes no difference

 "allow screen saver" on or off makes no difference

loading LHIPXTSR with or without switches (ie /s:2 /p) has no effect

running in a window or full screen makes no difference

extended memory  and HMA on or off has no effect

conventional memory protected or unprotected makes no difference

We are using AREV 2.11 in Novell4.1 environment. Our clients are WIN95, WIN98, WIN/NT WS. Everything works great in this configuration.

It is my understanding that SUSPEND WHEN MINIMIZED in PIF MUST NOT be enabled. (Screen saver have not presented a problem.) We have a dedicated indexer which could be important.

Make sure the KEEP ALIVE setting on the LHIPXTSR is set low enough and that the one on the server is set high enough. (We do not use the REVELATION user option on the NLM.) We do not have any inactivity timeout functions in the OS implemented.

Since we have a dedicated indexer, we have found that adding an index replacement process to all OTHER (non INDEXER) users of E - FLUSH was instrumental in adding stability to our installation. (TCL WINDOW) post-initialization process.]

Finally, somewhere on this site are the settings for PIF and Novell client (assuming Client32…we use a combination of CLIENT32 and INTRANETWARE 2.x) We have also found that specifying the frame type (802.2 or 802.3 on the Windows IPX Network tab was necessary for some cards… we just do it as a standard.)

Hope this helps. AREV works great in this environment. So keep after it.

View this thread on the forum...