Initializing the S4C+ system

Occasionally, it is possible to have a corrupt image file in the S4C+ controller.

This can cause the system to only partially boot up. Rather than Cold Boot the system, it
is possible to remove the image and ReStart the controller with the downloaded system.

A null modem cable is needed for connection between the PC and the S4C+ MC/
Console port. This cable can also be used for communication between 2 PCs. This
cable uses female 9 pin D-Sub connectors.

Null Modem cable diagram

Launch HyperTerm from the Windows start menu

Create a new connection

1 of 4
 Initializing the S4C+ system

Select the Com1 port

Configure the Com port as shown above

2 of 4
 Initializing the S4C+ system

Press Enter to get a Prompt.

Type in: xdelete “image.bin”

The image.bin file will be deleted from the FlashDisk

Type in: reboot

3 of 4
 Initializing the S4C+ system

The controller will begin a boot up with the original system

NOTE: DO NOT USE UNLESS DIRECTED BY TECH SUPPORT!

rm "/hd0a/system.dir" same as an X-start

rm "image.bin" same as an I-start

BootsupEraseSystem "/hd0a/Your system" same as an C-start

X-start from console when the Image is corrupt and the controller doesn't start.
Connect the terminal to console port on the Maincomputer or the serial card (older MC)
-Power OFF the system,PowerON, press the q key on PC-keyboard frequently, 2/sec during the startup
until BOOT MENU will be shown in the terminal window.
Three choices are shown A, B or C.
This must be done quickly, be prepared to repeat the procedure when working too slow.
Use A + Enter within 5 seconds or less.

4 of 4
Connect null
modem cable to
the port.
 ll -> ll
cd -> cd".." -> cd"bob"
pwd -> pwd
mkdir -> mkdir"bob"
rm -> rm"bob" -> rm"cm.cfg"
xdelete -> xdelete"bob" -> xdelete"cm.cfg"
cp -> cp"mc.cfg","cm.cfg"
BootsupROreset -> BootsupROreset"cm.cfg"
Reboot -> reboot

What’s on the flashdisk?

-> ll
ll
-r-xr-xA-x 1 0 0 111945 Oct 20 2000 BOOTROM.SYS
-rwxrwxrwx 1 0 0 273 Mar 29 11:37 mc.cfg
dr-xr-xr-x 1 0 0 2048 Oct 20 2000 bin/
value = 0 = 0x0

What directory are we in?

-> pwd
pwd
/hd0a/
value = 7 = 0x7

Let’s make a directory!

-> mkdir"bob"
mkdir"bob"
value = 0 = 0x0
-> ll
ll
-r-xr-xA-x 1 0 0 111945 Oct 20 2000 BOOTROM.SYS
-rwxrwxrwx 1 0 0 273 Mar 29 11:37 mc.cfg
dr-xr-xr-x 1 0 0 2048 Oct 20 2000 bin/
drwxrwxrwx 1 0 0 2048 Mar 29 11:42 bob/
value = 0 = 0x0

Let’s go inside “bob”!

-> cd"bob"
cd"bob"
value = 0 = 0x0
-> ll
ll
drwxrwxrwx 1 0 0 2048 Mar 29 11:42 ./
drwxrwxrwx 1 0 0 2048 Mar 29 11:42 ../
value = 0 = 0x0
-> pwd
pwd
/hd0a/bob
value = 10 = 0xa

Let’s go back to the ‘root’ /hdoa/!

-> cd".."
cd".."
value = 0 = 0x0
-> pwd
 pwd
/hd0a/
value = 7 = 0x7
-> ll
ll
-r-xr-xA-x 1 0 0 111945 Oct 20 2000 BOOTROM.SYS
-rwxrwxrwx 1 0 0 273 Mar 29 11:37 mc.cfg
dr-xr-xr-x 1 0 0 2048 Oct 20 2000 bin/
drwxrwxrwx 1 0 0 2048 Mar 29 11:42 bob/
value = 0 = 0x0

Let’s kill “bob”!

-> rm"bob"
rm"bob"
value = 0 = 0x0
-> ll
ll
-r-xr-xA-x 1 0 0 111945 Oct 20 2000 BOOTROM.SYS
-rwxrwxrwx 1 0 0 273 Mar 29 11:37 mc.cfg
dr-xr-xr-x 1 0 0 2048 Oct 20 2000 bin/
value = 0 = 0x0

Let’s copy the ‘bootrom’ file as ‘romboot’!

-> cp"bootrom.sys","romboot.sys"
cp"bootrom.sys","romboot.sys"
copying file bootrom.sys -> romboot.sys
Copy OK: 111945 bytes copied
value = 0 = 0x0
-> ll
ll
-r-xr-xA-x 1 0 0 111945 Oct 20 2000 BOOTROM.SYS
-rwxrwxrwx 1 0 0 273 Mar 29 11:37 mc.cfg
dr-xr-xr-x 1 0 0 2048 Oct 20 2000 bin/
-rwxrwxrwx 1 0 0 273 Mar 29 11:44 cm.cfg
-r-xr-xA-x 1 0 0 111945 Mar 29 11:45 romboot.sys
value = 0 = 0x0

Let’s remove the read only protection from ‘romboot’!

-> BootsupROreset"romboot.sys"
BootsupROreset"romboot.sys"
value = 0 = 0x0
-> ll
ll
-r-xr-xA-x 1 0 0 111945 Oct 20 2000 BOOTROM.SYS
-rwxrwxrwx 1 0 0 273 Mar 29 11:37 mc.cfg
dr-xr-xr-x 1 0 0 2048 Oct 20 2000 bin/
-rwxrwxrwx 1 0 0 273 Mar 29 11:44 cm.cfg
-rwxrwxrwx 1 0 0 111945 Mar 29 11:45 romboot.sys
value = 0 = 0x0