Hi All

We have two copies of an AREV application

one copy of arev.exe is in folder S:\BUSINESS\APPLIVE

another copy of arev.exe is in folder S:\BUSINESS\APPTEST

the client is running NT and the server is running NT

S drive is some sort of "Network Access Storage" drive and it looks like a local hard drive. I can't figure out how to map a new drive letter and I don't have enough access priviledges to make a share for it.

The error out of APPLIVE is

'RTP57' Line 1, Maximum number of variables exceeded

I get this whether not I try to start the app eg

AREV appname /XM4096

and

AREV /XM4096

and

AREV LANPACK /XM4096

none of these work

but everything is just fine if I go to the APPTEST folder and run the arev.exe in there.

even worse, I did actually manage to get the APPLIVE to start up ok, and log out of it but the next time I tried (5 mins later) it failed with max var error.

The arev.exe file has the same mod date and size in both folders.

could it have something to do with the arev.ini file? Or arevc.ini file (although those looked the same to me).

This is affecting several PCs across the network and everything was fine yesterday. The client says "nothing has changed" but that doesn't make it true.

Does anyone have a clue what is going on?

Scott, LMS

I was wondering if the command lines for the respective applications were like this:

S:\BUSINESS\APPLIVE\arev.exe appname /m/x4096

and

S:\BUSINESS\Apptest\arev.exe appname /m/x4096

with

s mapped to \\servername\folder…..

Dale Walker

Hi Dale

Unfortunately S drive looks the same in Explorer as C drive. I think this has to do with the special Network Storage thing. The little disk symbol doesn't even have a little network line under it. And it doesn't seem to have a UNC name like you'd expect with an NT network drive.

And I can't even create a new folder on it.

Incidentally this whole problem seems quite intermittant. They said it's gone now. And we think it may have to do with a virus checker upgrade they did on the day. Another case of "no we never changed anything" again. The virus checking program on that site is SOPHOS and it is usually set to skip the arev data files.

Scott, LMS

Scott,

Well I guess you can put this issue on hold until it happens again. I think you may be correct if the IT people added a new virus checker. But it is strange that you cannot map the S: drive to at least a root folder. I was working for a company that ran AREV 3.12 on a NT network with the drive mappings as I indicated.

Until it happens again,

Dale

View this thread on the forum...