bbs/magicka
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix errors in documentation

Browse Source
This commit is contained in:
Andrew Pamment 2018-02-03 21:19:58 +10:00
parent 8969e0efb3
commit 652c28faee
2 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/docs/guide/doors/dosbox.md
View File

@ -2,19 +2,19 @@
This guide is aimed at Raspbian Linux (Stretch) on Raspberry PI, but should work on any Linux/UNIX like system DosBox supports. This guide is aimed at Raspbian Linux (Stretch) on Raspberry PI, but should work on any Linux/UNIX like system DosBox supports.
## Step 1. Install Pre-Requisites ## Install Pre-Requisites
To compile DosBox, you will need SDL 1.2 and SDL-net in addition to the usual development toolchain. You will also need Subversion to get dosbox and patch to patch it. To compile DosBox, you will need SDL 1.2 and SDL-net in addition to the usual development toolchain. You will also need Subversion to get dosbox and patch to patch it.
sudo apt-get install build-essential libsdl1.2-dev libsdl-net1.2-dev subversion automake dos2unix sudo apt-get install build-essential libsdl1.2-dev libsdl-net1.2-dev subversion automake
## Step 2. Fetch DosBox ## Fetch DosBox
The most recent DosBox release has some issues with DOS doors, and the most recent Subversion code also has issues, so you will need a specific revision from the subversion repository. In my tests I have found r3933 to work well. Other revisions may work, but have not been tested. The most recent DosBox release has some issues with DOS doors, and the most recent Subversion code also has issues, so you will need a specific revision from the subversion repository. In my tests I have found r3933 to work well. Other revisions may work, but have not been tested.
svn checkout -r3933 svn://svn.code.sf.net/p/dosbox/code-0/dosbox/trunk dosbox-code-0 svn checkout -r3933 svn://svn.code.sf.net/p/dosbox/code-0/dosbox/trunk dosbox-code-0
## Step 3. Patch DosBox ## Patch DosBox
Now we have the DosBox code, you will probably want to patch it to fix a specific bug that happens with some doors which will appear as though when you press enter, it receives the enter command twice. Now we have the DosBox code, you will probably want to patch it to fix a specific bug that happens with some doors which will appear as though when you press enter, it receives the enter command twice.
@ -25,7 +25,7 @@ Now we have the DosBox code, you will probably want to patch it to fix a specifi
patch -p1 < ../dosbox-nullmodem.diff patch -p1 < ../dosbox-nullmodem.diff
## Step 4. Compile DosBox ## Compile DosBox
Compiling DosBox takes a long time on the Raspberry PI and will appear to have frozen a few times - particularly when compiling the render-scalers file - don't worry, just leave it it will eventually move on. Compiling DosBox takes a long time on the Raspberry PI and will appear to have frozen a few times - particularly when compiling the render-scalers file - don't worry, just leave it it will eventually move on.
@ -36,15 +36,15 @@ Compiling DosBox takes a long time on the Raspberry PI and will appear to have f
These commands will compile and install DosBox into /usr/local/bin. These commands will compile and install DosBox into /usr/local/bin.
## Step 5. Create Configuration File ## Create Configuration File
Next you will need to create a config file which enables the serial port for socket inheritance, and also mounts drives so that DosBox can access both your doors and your BBS drop files. Next you will need to create a config file which enables the serial port for socket inheritance, and also mounts drives so that DosBox can access both your doors and your BBS drop files.
An example setup is here: [[https://gist.github.com/apamment/98e42db83c452105b3e21a8bc062c5c3|dosbox.conf]] An example setup is here: [dosbox.conf](https://gist.github.com/apamment/98e42db83c452105b3e21a8bc062c5c3)
In this example, drive C: is the location where my doors are stored, dropfiles will be copied to the door directory. In this example, drive C: is the location where my doors are stored, dropfiles will be copied to the door directory.
## Step 6. Create Shell Script to Invoke DosBox ## Create Shell Script to Invoke DosBox
The shell script you need will vary from system to system, but basically, you want to: The shell script you need will vary from system to system, but basically, you want to:
@ -69,17 +69,17 @@ Here is an example script I use for Freshwater Fishing:
fi fi
This will just dump the user back to the BBS if the door is in use. You could get fancy and use the 'inuse' door I created which will display an in-use message and then quit ([[https://github.com/apamment/inuse|INUSE Door]]), but that is outside the scope of this document. This will just dump the user back to the BBS if the door is in use. You could get fancy and use the 'inuse' door I created which will display an in-use message and then quit ([INUSE Door](https://github.com/apamment/inuse)), but that is outside the scope of this document.
You will also need to make the bash script executable: You will also need to make the bash script executable:
chmod +x ffs.sh chmod +x ffs.sh
## Step 7. Create Batch File to Start Door ## Create Batch File to Start Door
Please note, you will need to setup your doors using DosBox in the normal fashion, either you set them up on a machine where you have a monitor attached and transfer the files over, or you run DosBox directly from your PI with either remote X11 or a local monitor. Please note, you will need to setup your doors using DosBox in the normal fashion, either you set them up on a machine where you have a monitor attached and transfer the files over, or you run DosBox directly from your PI with either remote X11 or a local monitor.
You will also most likely need a Fossil driver, [[http://www.pcmicro.com/bnu/|BNU]] works well. (Get the stable release 1.70). You will also most likely need a Fossil driver, [BNU](http://www.pcmicro.com/bnu/) works well. (Get the stable release 1.70).
Different doors will need to be called in different ways, but the important thing to remember is that you end the batch file with "exit" else the door will stay stuck in DosBox. Different doors will need to be called in different ways, but the important thing to remember is that you end the batch file with "exit" else the door will stay stuck in DosBox.
@ -95,7 +95,7 @@ Here is an example I use for freshwater fishing:
This loads BNU, then launches the door with the drop file. This loads BNU, then launches the door with the drop file.
## Step 8. Setup BBS ## Setup BBS
Finally, you will want to setup your BBS to call the script you made in Step 6. You also need to pass the node number and socket handle. Finally, you will want to setup your BBS to call the script you made in Step 6. You also need to pass the node number and socket handle.

4
docs/docs/guide/doors/dosemu.md
View File

@ -31,7 +31,7 @@ This is my autoexec.bat (in /home/someuser/.dosemu/drive_c/)
## Step 4. Configure a Door ===== ## Configure a Door
Firstly you want a dosemu.conf for calling the door, I use the same one for calling all my dos doors. Firstly you want a dosemu.conf for calling the door, I use the same one for calling all my dos doors.
@ -46,7 +46,7 @@ This is my dosemu.conf (in /home/someuser/MagickaBBS/doors/)
$_rawkeyboard = (0) $_rawkeyboard = (0)
$_com1 = "virtual" $_com1 = "virtual"
You will need both [[http://tinysbbs.com/files/tsoft/THANG23B.ZIP|THANG23B.ZIP]] and [[http://www.pcmicro.com/bnu/bnu170.zip|BNU170.ZIP]] You will need both [THANG23B.ZIP](http://tinysbbs.com/files/tsoft/THANG23B.ZIP) and [BNU170.ZIP](http://www.pcmicro.com/bnu/bnu170.zip)
First unzip BNU170.ZIP in /home/someuser/MagickaBBS/doors/bnu First unzip BNU170.ZIP in /home/someuser/MagickaBBS/doors/bnu