STDIOERR - AREV. 3.12 (AREV Specific)
At 23 JUN 1998 02:07:25AM Jinny wrote:
I'm running on NT4.0 workstation with AREV 3.12. Recently, I startup application, following error appears.
'STDIOERR' Line 2 B10 Variable has not been assigned a vaule. Zero used.
'STDIOERR' Line 2 B10 Variable has not been assigned a vaule. Zero used.
'STDIOERR' Line 2 B10 Variable has not been assigned a vaule. Zero used.
..
..
'RPT57' Line 1 B114 Maximum number of variable exceded.
'STDIOERR' Line 2 B10 Variable has not been assigned a vaule. Zero used.
'STDIOERR' Line 2 B10 Variable has not been assigned a vaule. Zero used.
..
..
At this time, I must reboot computer. But this error not show on DOS CLIENT machine, only on NT4.0.
How should I do now?? Many thanks for your assistant.
Jinny.
At 23 JUN 1998 11:22AM Scott Revelation wrote:
Jinny,
What sort of network are these two machines (the NT 4.0 and the DOS one) on? Novell? Nt? Other? Are you using the Revelation NLM or Nt Service?
Also, make sure that the DOS session you are running Arev in is providing enough expanded memory (EMS) and that you are using the /x /m#### (replace the #'s with how many KB of EMS to use, e.g. 4096) parameters when starting Arev.
e.g. AREV JINNYAPP /x /m4096
-Scott Revelation
At 24 JUN 1998 03:05AM Steve wrote:
Hi Scott,
I got the same problem. I am using NT4.0 client, running AREV 3.12 in Novell server.
I've tried your suggestion, /x/m4096. But still doesn't work. I am frustrating cause only my PC can't run properly. Other PC can still running that AREV. Why why why . . . . .
Many thanks,
Steve
At 24 JUN 1998 03:05AM Steve wrote:
Hi Scott,
I got the same problem. I am using NT4.0 client, running AREV 3.12 in Novell server.
I've tried your suggestion, /x/m4096. But still doesn't work. I am frustrating cause only my PC can't run properly. Other PC can still running that AREV. Why why why . . . . .
Many thanks,
Steve
At 26 JUN 1998 05:19AM Jinny wrote:
Scott,
I am using Revelation NLM and NT 4.0. We have not using NT service. Do you have any suggestion or solution??? Many thanks for your help.
Jinny.
At 17 MAY 1999 12:27PM L Jones wrote:
Did anyone find a solution to this problem? I am also getting this error in a Novell enviroment.