Gasboy CFN III V3.6 and Later - Manual (Page 98)

Correcting SC3 Board Set Problems
Page K-4 MDE-4739A CFN III PCI Secure Controller Software Installation/Upgrade Instructions · July 2010
Reboot;A using Dbug (Hard Boot)
To perform a Reboot;A or Hard Boot, proceed as follows:
Note: Framos.bin and Framos.cfg must exist in C:\SC3 to perform the following operation.
1 If you still cannot get a Sign On response to an Enter key press, then set memory board S1
switch for debug mode.
2 Enter the Debug Mode as described in “Preparing Before Entering Dbug Mode” on
page K-3 .
3 At the prompt “>>>--..” press U and Enter.
4 CFN III must reload the Framos.bin (SC3 OS) and Framos.cfg (SC3 configuration) located in
C:\SC3 directory. Set S1 back to its default switch positions and perform warm start. If this
does not correct the issue, a Debug memory clear may need to be performed (refer to
“Memory Clear Debug Procedures” on page K-5 ).
Cannot Enter Master Password or Update Initial User Password
This problem shows up as additional character appearing while attempting to change the initial
user password or multiple failures to enter the Master Password.
To resolve the issue proceed, as follows:
1 The default Framos.bin and Framos.cfg from the customer disk must be copied to C:\SC3
folder. Ensure that you have a copy of the site original Framos.cfg as well as a good Sysback
and Tranback DTA files. If the
“Floppy Disk Backup” on page 16 was followed these three
files must be available.
2 Set memory board S1 switch for debug mode.
3 Enter the Dbug Mode as in “Preparing Before Entering Dbug Mode” on page K-3 .
4 At the prompt “>>>--..” press U and Enter. CFN III must reload the Framos.bin (SC3 OS) and
Framos.cfg (SC3 configuration) located in C:\SC3 directory.
5 Set S1 back to its default switch positions and perform another warm start.
6 Retry entering the Master Password, run Admpass, create a new user and again attempt to
change the initial password. If this does not correct the issue a Debug memory clear may need
to be performed (refer to
“Memory Clear Debug Procedures” on page K-5 ).