SM32 Linux Setup

Linux Setup

The Following is a sample setup to get the Demos running under Linux
The Linux binaries were generated under RedHat 9 so they require libstdc++.so.5. This sample setup was tested on a Fedora 3 distribution.

On Linux:

1. Created a directory /sm

[root@localhost /]# mkdir /sm

2. Created user sm32user with password demo457

[root@localhost /]# adduser -d /sm/sm32user sm32user
[root@localhost /]# passwd sm32user
Changing password for user sm32user.
New UNIX password:
BAD PASSWORD: it is based on a dictionary word
Retype new UNIX password:
passwd: all authentication tokens updated successfully.

3. Changed owner of /sm

[root@localhost /]# chown sm32user:sm32user /sm

4.Logged on as sm32user and unzipped and untarred SM32Demo 
  and the sm32fs and sm32server executables
  
[sm32user@localhost tmp]$ cd /tmp
[sm32user@localhost tmp]$ gzip -d SM32Demo_tar
[sm32user@localhost tmp]$ gzip -d sm32fs_tar
[sm32user@localhost tmp]$ gzip -d sm32server_tar
[sm32user@localhost tmp]$ cd /sm
[sm32user@localhost sm]$ tar xf /tmp/SM32Demo_tar
[sm32user@localhost sm]$ tar xf /tmp/sm32fs_tar
[sm32user@localhost sm]$ tar xf /tmp/sm32server_tar

5. Delete a few things but mainly 
      rename server_sm32.sm32 to sm32.sm32
[sm32user@localhost sm]$ cd /sm/SM32Demo/test
[sm32user@localhost test]$ rm SM32.exe
[sm32user@localhost test]$ rm SM32.SM32
[sm32user@localhost test]$ rm client_SM32.SM32
[sm32user@localhost test]$ mv server_sm32.sm32 sm32.sm32
[sm32user@localhost test]$

6.Logged on as su and created mystart in /etc/rc.d 
                         added mystart to rc.local
                         
[root@localhost rc.d]# cat mystart
#!/bin/sh

(cd /sm ; su -c "/sm/sm32fs 50 2 5000 /sm" sm32user)
(cd /sm ; /sm/sm32server 5001)

7. executed mystart
[root@localhost rc.d]# chmod +x mystart
[root@localhost rc.d]# ./mystart

8. made sure the servers came up

[root@localhost rc.d]# ps ax | grep sm32
 9844 ?        Ss     0:00 /sm/sm32fs 50 2 5000 /sm
 9847 ?        Ss     0:00 sm32server 5001
 9849 pts/1    R+     0:00 grep sm32
[root@localhost rc.d]#

On Windows:

downloaded and extracted SM32Demo.zip into C:\SM32Demo
downloaded and extracted SM32.zip into C:\SM32
copied client_SM32.SM32  from C:\SM32Demo\test to C:\SM32 and renamed to SM32.SM32

1. First get SM32 to be a fat client
brought up free SM32.EXE in C:\SM32Demo under options selected edit an existing config and select SM32.SM32 in C:\SM32.
In Initial Statement removed the RUN"DEMOLOGON";
In Network set Initial Route to 0,2,"YOUR LINUX SERVER IP:5000" eg 192.168.1.1:5000
Under Diskio set the 4 disks so they began with "<0>/sm/SM32Demo/..."

0,<0>/sm/SM32Demo/test/PROGS
1,<0>/sm/SM32Demo/test/DATA
8,<0>/sm/SM32Demo/test/WINDOWS
9,<0>/sm/SM32Demo/test/UTIL

2. Execute SM32.exe in C:\SM32.
If it does not come up and you get an error 5 message after a long time there is something wrong with the IP/Port address. Once up:

PRINT DIR(0)
PRINT DIR(1)
PRINT DIR(8)
PRINT DIR(9)

IF YOU GET AN ERROR 17 ON ANY YOU HAVE A BAD DIRECTORY NAME.

3. Modify DEMOLOGON.
Once you are up as a fat client load the program "DEMOLOGON" and modify line 110.
You could also use "$__LOGON" and modify line 320.
RUN "DEMLOGON". You should see [LINUX] in the status line. You could also
PRINT DIR(-1)
to verify your current directory is on your Linux Box.

4. Add DEMOLOGON to properties.
Do a BYE. You should see a message that you are under WINDOWS. To verify
PRINT DIR(-1)
your current directory is on your Windows Box.
under options select edit current config
Add the RUN "DEMOLOGON"; after the CALL "$__SETUP";
back into the initial statement. Do a BYE.

If you have created a link to C:\SM32\SM32.exe on your desktop, you should be able to click it and immediately be on your Linux Box. Also C:\SM32\SM32,exe and C:\SM32\SM32.SM32 are the only 2 files that need to be distributed to other PC's.

5. Other changes
If this is to be your developement environment (SM32 programs are binary compatible between Linux and Windows) you will want to turn off Program Caching by setting the number of programs in disk cache (on The Network page) from 100 to 0. It is very annoying to get the cached version of a program a program you have just modified. When you distribute your programs to end users remember to turn caching back on. You will also want to replace the Print in "$__RPCSERVE" that lets you know you are now under windows with a BYE so that the enduser ends.