Using Novell Application Launcher (NAL) with Arev 2.03 (AREV Specific)
At 14 FEB 1999 09:51:37PM Bill Budge wrote:
Has anyone come across any problems using the NAL with release 2.03 of Arev on Novell 4.0 network with WIN95 pc's? I have heard that there may be memory contentions with the NAL and that Arev may tend to lock up. Is this true and how can it be overcome?
At 15 FEB 1999 03:44PM Scott Kearney wrote:
Bill,
We don't use NAL here, but any sort of memory contention between it and Arev would be unlikely, since Arev doesn't do any sort of wacky memory addressing and sticks to its own conventional and EMS memory.
Win95 should keep the two respective programs' memory separate. One possible problem I could imagine, is that NAL may spend a good deal of the computer's idle time to poll the server for network application information (path updates, etc..). If this is the case, Arev's connection to the server might time out and get booted–at which point it would probably crash. This would probably only happen when using the NLM, and if that was the case, there are various command line parameters that could be used to lengthen the amount of time allowed before a timeout. Idle-sensitivity settings in the shortcut properties could also aid in alleviating any sort of timeout-related problem.
Since I haven't used NAL, however, these are just some thoughts; I'll definitely yield to anyone with some battle-experience on this issue.
