3.12 on NT peer-to-peer (Networking Products)
At 06 JUL 2000 10:04:34AM Mike O'Neal wrote:
Hello all:
I have a site that is receiving messages such as:
"Error opening or reading from .INI File AREVC.INI"
"Error writing to DOS file AREVC.INI"
"B527} Your DOS path for temporary files is invalid. Please check environment setting."
"r563988.VF2 is not available for the view window"
The environment is 3 NT workstations using the NPP and bumped to 6 users. The 'server' (this is a peer-to-peer setup) runs fine, the 'remote' stations receive the error messages. The server is mapped to drive C:, the remotes are mapped to drive B:.
I have left "Rollout DOS filename" and "DOS path for temporary files" in the AREVC.INI file blank.
Any suggestions out there?
TIA,
Mike O.
At 06 JUL 2000 10:18AM Steve Smith wrote:
(a) Increase the file handles in CONFIG.NT
(b) Set "Rollout DOS filename"
© Set "DOS path for temporary files"
(d) Attach a local volume with duplicate copies of
VOC,LISTS,WINDOWS,MENUS,POPUPS,SYSMESSAGES,BP (program library)
steve@state-of-the-art.com.au
At 06 JUL 2000 01:36PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
You might also try increasing the environment size.
[/i]World leaders in all things RevSoft[/i]
At 06 JUL 2000 04:46PM Steve Botes wrote:
I have seen something similiar with win2k and what I found was that the string in the set environment variables ala set arev=xxxx.xxx was truncated to only two places past the point. I think if I remember correctly I either renamed the arevc.ini file to arevc.in or something along those lines…..
At 06 JUL 2000 05:47PM Steve Smith wrote:
Another way to effectively increase the environment under NT is to set a default environment setting.
SET DUMMY=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Then as the first line of your batch file to call AREV
SET DUMMY=
This frees up more space than would otherwise be offered. There are some problems with environment expansion under NT 4.0.
steve@state-of-the-art.com.au
At 06 JUL 2000 06:08PM Steve Botes wrote:
I had found that the problem acted differently each time using a batch file to set arev. Using Steve Smith's example of setting a dummy string in AUTOEXEC.NT and then setting it to null prior to setting AREC.INI in my batch file worked just fine…..
Thanks
At 06 JUL 2000 10:32PM Steve Smith wrote:
You are welc
At 07 JUL 2000 04:12PM Mike O'Neal wrote:
Thanks for all of your suggestions guys - problem solved! Hope I can return the favor someday…
Mike O.