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 07 DEC 1999 05:24:17PM Jonathan Bird wrote:

Has anyone had a problem with this configuration:

Netware client 32 version 3.1.0.0

Windows 95 version 4.0 950.C

Revalation NLM 1.5

Netware 4.0

Arev 3.12

A customer reports Arev will not start. A brief flash of stuff, no dots marching…

Input gratefully received

Jonathan.


At 08 DEC 1999 01:17AM Steve Smith wrote:

Hi JB,

First - try a copy of the system standalone (local drive) to see if you still get the flash behaviour - use no networks driver - this will eliminate Novell etc..

Sounds like a problem I had a while back on an HP PC (not using Novell) - check the memory properties on the AREV Windows shortcut - let me see -

Total Memory=Auto

Protected=ticked

Initial environment=512

Expanded=4096

Extended=None

Uses HMA=Checked

DPMI=Auto

Run AREV from a batch file.

I recall that I could sometimes get AREV to fire if I called AREV twiec in succession in the batch file. I think it had something to

do with the Expanded memory initialization. Ensure you have a default printer defined.

May be no help to you - take it FWIW,

Steve


At 08 DEC 1999 02:09PM Dan Reese wrote:

Service packs 1 and 2 (for the Novell Client 3.1) can cause these symptoms. I am not aware of a work-around, short of removing the client and re-installing the 3.1 client without the service packs.

Also, some Windows 95 machines require forcing the frame type. the 3.1 client seems to aggravate this problem.

Dan


At 14 DEC 1999 08:04AM Ian Lord wrote:

I had a similar problem on a client site recently, Running Novell 4.1x on Token ring.

We tried using Novell client 4.51 from the RevSoft site, but it would not allow arev to start. We found that it was the novel client by removing it and using the Microsoft client for Novell and then Arev would start.

In the end the latest version of the novell client had to installed to remove this problem

I would recommend trying withiut the Novell client to see if Arev wil start.

I hope this helps..


At 16 DEC 1999 05:34AM Richard Bright wrote:

Jonathan,

Just a thought, has client tried a Paramfile in Revboot vol setting

ServerOnly=False

I ask this because looks as if NLM is nocking out the Arev system. Also check driver.

Also check for effect of name space/long file names in directories.

Richard Bright

View this thread on the forum...

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