Please help this error seems to be happenning very often at our client site. Arev 3.x, using NT service with NPP installed.

                  "This device does not exist on the network, reading drive? Abort, Retry, Fail? "

                  When choosing A, R or F- the screen is covered with this message

                  " ERRMSG R27 Unassigned Initialize "

                  Any ideas on this is greatly appreciated.

Can you provide some more information on this problem? Are you using a service pack on your server and what kind of OS do your client machines have? When exactly do you get this message?

You may want to check/re-map the drives from your client machines to your server.

I usually see this happen when the drive letter you use for Arev is redefined by another application.

"I usually see this happen when the drive letter you use for Arev is redefined by another application."

Victor I was not too clear on what u state here.  Please help

Perhaps clearest would be to describe a scenario.

• You start Arev using a batch file called GoArev.bat
• Within the batch file is a MAP command which maps the W: drive to your Arev directory.
• After the MAP command, Arev is loaded.
• However, since you are in Windows, you can multi-task, so you launch another application. Unfortunately, this application also maps W:. Now W: is pointing to the new location.
• Continuing in Arev, you make a request, reading a record, for example.
• The read request eventually is resolved into a request to access a file on W:. However, since W: was remapped, the request cannot be met. This generates the ERRMSG message because the message actually requested cannot be read.

Victor, Thank you for your response but I dont think that is an issue i am dealing with. The scenario is as follows:

Workstation A is win95 but has only Arev application loaded. The only function that we do through this machine is at certain time intervals shell out to dos and dial the US customs. This is the machine that has the error first which then leads to other workstations from getting the same error. The rollout file path is c:\ .One of our clients is using NLM and the other NT service. Please help

How are you shelling to DOS? When you return back, do you first CD back to the Arev directory? Depending upon the Arev version and network driver, if you do not, then you will get the message described and will not be able to proceed in Arev.

victor since my rollout file is created in the root of the local machine i do not know if it is required to cd back to the arev directory. In any case i will try that too. Thanks

Prabir

View this thread on the forum...