| 1 |
=========================================================================== |
| 2 |
--------------------------------------------------------------------------- |
| 3 |
| READ THIS FILE ALL THE WAY THROUGH BEFORE ATTEMPTING TO INSTALL FROTZ | |
| 4 |
--------------------------------------------------------------------------- |
| 5 |
=========================================================================== |
| 6 |
|
| 7 |
|
| 8 |
Because Frotz was originally written specifically for MS/PC DOS and then |
| 9 |
ported to Unix machines. As such, nothing about it was written with |
| 10 |
36-bit systems in mind. The initial job of porting to the PDP-10 mostly |
| 11 |
involves taking the differences between 32-bitness and 36-bitness. This |
| 12 |
was sufficient for porting the dumb interface. The ongoing job of |
| 13 |
adding full screen handling will involve coming up with an old version |
| 14 |
of curses or writing a cut-down version that supports only VT100/ANSI |
| 15 |
and maybe VT52. |
| 16 |
|
| 17 |
Currently the porting effort is focusing on TOPS20. |
| 18 |
|
| 19 |
The porting effort used Mark Crispin's Panda TOPS20 distribution from |
| 20 |
http://panda.trailing-edge.com/ and the KCC C compiler which is included. |
| 21 |
|
| 22 |
To compile, do "make tops20". This will copy the needed source files to |
| 23 |
the "snavig/" directory and process them to fit TOPS20's limit of six |
| 24 |
alphanumeric caps-insensitive characters on extern symbols and |
| 25 |
filenames. This requires the GNU version of sed. So if you're on |
| 26 |
macOS, *BSD, or something else non-GNU; install GNU sed before |
| 27 |
proceeding. I was unable to adapt the snavig script to do all the |
| 28 |
processing itself. |
| 29 |
|
| 30 |
The contents of this "snavig/" directory then needs to be uploaded to a |
| 31 |
subdirectory on a PDP10. Then while in the directory with the source, |
| 32 |
the following command will then compile and link the code to produce an |
| 33 |
executable: |
| 34 |
|
| 35 |
cc -o dfrotz.exe *.c |
| 36 |
|
| 37 |
There will be some complaints of unused parameters for some functions. |
| 38 |
This is to be expected because the usual means of making the compiler to |
| 39 |
keep quiet about these things don't work for KCC. A considerable amount |
| 40 |
of disk quota is required to complete the linking, but how much is not |
| 41 |
entirely known. |
| 42 |
|
| 43 |
If you get a complaint that you're out of disk space, look at the TOPS20 |
| 44 |
manuals for how to add yourself to the WHEEL and OPERATOR groups. Then |
| 45 |
you can set disk quotas yourself. You'll want to do something like this: |
| 46 |
|
| 47 |
enable |
| 48 |
build <username> |
| 49 |
permanent infinity |
| 50 |
working infinity |
| 51 |
disable |
| 52 |
|
| 53 |
Then for any subdirectories |
| 54 |
|
| 55 |
enable |
| 56 |
build <username.frotz> |
| 57 |
permanent infinity |
| 58 |
working infinity |
| 59 |
disable |
| 60 |
connect <username.frotz> |
| 61 |
|
| 62 |
Now you're in the directory <username.frotz>. To get source code into |
| 63 |
the machine, FTP is probably your best bet. |
| 64 |
|
| 65 |
ftp ftp.foobar.com |
| 66 |
login ftp |
| 67 |
set no confirmation all |
| 68 |
cd <wherever the source is> |
| 69 |
get * |
| 70 |
quit |
| 71 |
reset ftp |
| 72 |
|
| 73 |
Now compile. |
| 74 |
|
| 75 |
cc -o dfrotz.exe *.c |
| 76 |
|
| 77 |
|
| 78 |
There are some irritating characteristics of TOPS20 that need to be |
| 79 |
addressed. So far, the only serious one deals with the terminal width. |
| 80 |
TOPS20 will automatically insert a newline every N characters where N is |
| 81 |
the terminal width setting. You can see these by typing INFO TERM. To |
| 82 |
make TOPS20 not do this, you need to set the width to zero -- like this |
| 83 |
"TERM WIDTH 0". It's best to do these terminal setup things in your |
| 84 |
LOGIN.CMD file, which is akin to a .profile or .bashrc file on a Unix |
| 85 |
machine. Add the following lines in the following order to LOGIN.CMD: |
| 86 |
|
| 87 |
TERM VT100 |
| 88 |
TERM WIDTH 0 |
| 89 |
|
| 90 |
When setting TERM VT100, this implies a width of 80. Therefore the |
| 91 |
width needs to be set AFTER the terminal type in order for the width |
| 92 |
setting to stick. |