First:

on the client side i ran arev install /x and installed from the disk

and then i ran arev lanpack and picked the new 1.5 network driver.

Second:

On the the server side i load the new nlm

Third:

I load 'lhipxtsr' at the workstation….

       and get: 'Revelation Client Watchdog TSR - Version 1.5.'

Fourth:

I load arev Projects ]]

I get this when trying to load arev at the workstation

' Processing, Please Wait….

(C) Copyright 1993, by Revelation Technologies, Inc. All rights reserved.

                  Serial Number : 402735'

P\arev30\Unable to open boot media map.

—

I get 4 dots AND NO OTHER ERROR CODES, we are dumped out of the program

I tried to run arev sysprog and it loads, but when i

try to open our application under sysprog we are again

dumped out of the program.

I am told that we are using the QuickAttach method to attach to

our data volumes.

IS THERE A WAY TO FIX THIS?

Hi Brad-

I just got back from being out of town…so to pick up from what you had responded to earlier:

I GET UNABLE TO OPEN VOC AND THEN WE ARE DUMPED OUT.

I think this is the key. Even if you were using the QuickAttach method, you would then be able to at least ATTACH the datavolumes that are associated with your application (although you wouldn't be able to get into the tables) from the SYSPROG account.

Unfortunately, troubleshooting ARev is NOT my strong suit. Here is a previous posting from Aaron Kaplan on the subject.

I don't realy remember how to do this, so try and stay with me as I ramble, OK?

Go through the ARev manuals. There is pretty good information on QuickAttach and how to set it up. I'm pretty sure all the info is stored in SYSENV. From the manuals, look through and validate the format. It's based on username or account name (depending on how it was set up) and I think it ends with *IMAGE. I'm pretty sure image is in the name anyway. Basically, what you need to do is delete the record.

Although, on second thought, follow the link Tracy posted in her responce. I'm starting to think there might be a GFE in the VOC file.

[email protected]

Sprezzatura, Inc.

Re: database broke using Revelation NLM 1.5 and 1.06 the only nlm

that works is 1.04.

I'm not sure if this helps, but this is what we get when

running 'edit systables voc' in the tcl window.

                   VOC

                   PROJECTS

                   RTP57

the manual suggests that i should get this:

                      REVBOOT

		VOC

		SYSPROG

		RTP57

View this thread on the Works forum...