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 17 JUL 2000 04:21:32PM Michael Wasserstein wrote:

Hi-

A client of mine had a network installed in 1998. It was comprised of a dedicated fileserver running Novell Netware 3.12 and 2 workstations running windows 95 release A. All of the computers were Compaq and the network interface card protocol was ipx/spx. We were running Arev 3.12 with the NPP and it worked flawlessly. About a week ago, we added 2 more workstations. These were also Compaq computers, but were running Windows '98 2nd edition. Once these two stations were added, the Windows '98 machines in particular did not perform well. First, when one of these stations runs Arev, exits Arev and runs another Windows program like WordPerfect or ArcServe, the system locks up and pressing Ctrl-Alt-Del does nothing. The only way to power down the machine is to physically power off. This does not seem to be the case if Arev is not run. We are trying to ensure that all the updated drivers are loaded, but I was wondering if anyone could give me an idea of what I should verify in the system (ie, config.sys, desktop ic

on memory options, etc.). When Arev is running, it seems to work fine, but it seems to hold on to something when it exits. The Windows '95 workstations seem to be more stable (as they were before the addition), though they still encounter more problems than before.

Thanks.

Michael


At 17 JUL 2000 07:23PM Steve Smith wrote:

Michael - two things come to mind.

Firstly, the default Netware configuration uses a copy of command.com on the server eg. in \\SERVER\SYS\PUBLIC\MSDOS\V7.0\command.com

The Win 98 PCs may be somehow referencing this, so set all command.com's to be local.

Second, check that there is not an old command.com floating around in the AREV directory - if there is delete it. a DIR /S \COMMAND.COM will reveal any odd size files. A SUSPEND with a command.com different to the one in c:\ will cause a stack fault inside DOS and a hang some time later.

Third, if you can, try disabling EXPANDED memory and run your app and see if the problem persists.

steve@state-of-the-art.com.au


At 18 JUL 2000 12:59PM Michael Wasserstein wrote:

Thanks Steve. I'll try this.

View this thread on the forum...

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