Jarrod,
Ok, here is the procedure, but like a fool, I did not write down what software version of NAM I was working on when I established this. Hopefully it will not make a difference.
This procedure is necessary when we have a Co-resident NAM (VM and Prelude/Cinphony) that has experienced the corruption problem repeatedly and are forced to fix the problem with 2 NAMs, or an additional CallPilot.
Since the existing NAM has ACD on it we make it the ACD only .
So the procedure requires we turn off VM on the cores NAM.
Assuming we have cleaned up the crosslinked files-
Access the NAM via Monitor and keyboard.
Access the OS2 prompt.
C:\
Complete the following steps:
type cd st {enter}
type nvmutil {enter}
type shutdownnvm {enter}
type t {enter}
type q {enter}
type cd.. {enter}
from c:\ type cd access2\startup\stbin {enter}
type dir {enter}
You should see the following directory listing
Directory of C:\ACCESS2\STARTUP\STBIN
. <DIR> 11-07-99 10:37p
.. <DIR> 11-07-99 10:37p
ST EXE 630784 5-04-99 12:42p
NVMMGRSV EXE 143872 5-04-99 12:46p
MBXMGRSV EXE 96256 5-04-99 12:47p
OPRMGRSV EXE 13824 5-04-99 12:47p
SMTPSRV EXE 45056 5-04-99 12:43p
DSKTP EXE 58368 5-04-99 12:44p
8 file(s) 988160 bytes used
1530368 K bytes free
You might see other files but they will not need to be renamed
type rename st.exe st.old {enter}
type rename nvmmgrsv.exe nvmmgrsv.old {enter}
type rename mbxmgrsv.exe mbxmgrsv.old {enter}
type rename oprmgrsv.exe oprmgrsv.old {enter}
type rename smtpsrv.exe smtpsrv.old {enter}
type rename dsktp.exe dsktp.old {enter}
type cd.. {enter}
you should see c:\access2\startup
type cd.. {enter}
you should see c:\access2
type cd runtime {enter}
type del sekur*.* {enter}
Ensure that set relocation is turned off.
Re-boot the NAM
Connect the new NAM or CallPilot to the KSU and power up.
Let us know how it went.
MarvO said it
