#Chaos won't exit!!!
2 messages in this thread
We don't know why you are running into the message that says Metashel can't
be unloaded, not last TSR. However, from time to time we hear folks with
that problem.
We have tried NDOS here and can only duplicate the Errorlevel issue
(apparently, up to 99 errorlevels in NDOS).
I suspect that if you were to boot clean, with the exception of the NDOS
(no files, buffers, mouse, etc.) that the problem will go away. Then try
adding your device drivers and TSRs back experimently until the problem
reoccurs.
Good luck, let us know!
Nik
Nik,
I believe that I have found the offending culprit. As part of my
autoexec.bat file, I am using the NDOS "set" command to read an ASCII file
and then set the environment variables listed within. One of the variables,
NDSHELL, was set to a different directory than COMSPEC. NDSHELL determines
where a secondary shell is to be loaded from.
These are the old 2 lines:
comspec=c:\ndos.com ndshell=/l:c:\norton /u
And these are the new 2 lines:
comspec=c:\ndos.com ndshell=l:c:\ /u
All seems to be well now. Metashel is releasing itself from memory when it
is supposed to. I would tend to think that NDOS, as a secondary shell, was
the tsr that the error message refers to. Metashel, apparently didn't
recognize the fact that the secondary shell had been terminated.
A lesson learned for all, I'm sure. Thanks for all of yours and Bob's help.
md