One of our clients has a Win95 workstation which is encountering frequent Suspend
Errors. Site has NT Service/NPP running.
We have tested the same procedures run on different workstations and with
different users and the same error message is displayed irrespective.
The error is thus:-
"An error has occurred during the Suspend operation. Status() is undefined
code "-4". "ok""
When the user hits enter this next message is displayed.
"Write Error. The operating system file C:\arevps\temp\R586917.sus does not
exist. "ok""
We have set the abovementioned path for each user to sort temp files on
their c drive. Numerous repeats of exact same tasks are performed by the
same users each day. This error comes up several times a day but not every
time that the same procedure is run.
We would appreciate some feedback on this because it is causing disruption to the client's system.
Thanks in anticipation.
Regards,
Kevin at KPW
I am having the same problem with one workstation
only on Arev 2.12, also with NT1.1 and NPP1.4.
However, I seem to have the same problem with a
local test installation. Several workstations
which appear to be identical configurations are
having no problems.
I'll let you know if I get a fix. Please do likewise.
Regards,
John,
Thanks for your response.
Seems to me that this error condition is closely
related to NT Service and NPP rather than
being Arev Specific.
We have run the exact same procedures on exact same workstations with exact same staff for almost 2 years now under novell/nlm config with absolutely no error condition wharsoever.
Now that this client is in NT environment this error has surfaced.
Regards,
Kevin at KPW
Could be. I have disabled NTService for the time
being and that has stabilized the ability to log
on more that 1 or 2 users. I tested your theory
with a local version of Arev which I disabled all
network support, but I still got the suspend error.
This problems seems isolated to a single workstation.
MINE! Good luck.
Something you're running during the SUSPEND process is probably interfering with memory. This would then cause this error. You can change the 1st line of the error message ( in SYSMESSAGES ) to an N to stop this from displaying.