update documentation

This commit is contained in:
Andrew Pamment 2018-06-06 21:42:25 +10:00
parent 1cc8e16b71
commit 772ec89da6
2 changed files with 6 additions and 17 deletions

View File

@ -14,17 +14,6 @@ The most recent DosBox release has some issues with DOS doors, and the most rece
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
## 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.
wget https://gist.githubusercontent.com/apamment/bb438d9be6dc8e67c36239fd64047ece/raw/3e942c68d7a970f3404bffc2408165d810c4bef7/dosbox-nullmodem.diff
cd dosbox-code-0
patch -p1 < ../dosbox-nullmodem.diff
## 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.
@ -40,7 +29,7 @@ These commands will compile and install DosBox into /usr/local/bin.
Next you will need to create a config file which enables the serial port, 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, and also mounts drives so that DosBox can access both your doors and your BBS drop files.
An example setup is here: [dosbox.conf](https://gist.github.com/apamment/2e5b00eda2f304f2bc7d298a0487bd9b) An example setup is here: [dosbox.conf](https://magickabbs.com/files/config/dosbox-ffs.conf)
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.
@ -78,11 +67,11 @@ You will also need to make the bash script executable:
if [ ! -e /home/pi/MagickaBBS/doors/ffs.inuse ]; then if [ ! -e /home/pi/MagickaBBS/doors/ffs.inuse ]; then
touch /home/pi/MagickaBBS/doors/ffs.inuse touch /home/pi/MagickaBBS/doors/ffs.inuse
/home/pi/MagickaBBS/utils/dosbox_shim/shim 9999 $NODE /home/andrew/MagickaBBS/doors/ffs.sh /home/pi/MagickaBBS/utils/dosbox_shim/shim 9999 $NODE /home/pi/MagickaBBS/doors/ffs.sh
rm /home/pi/MagickaBBS/doors/ffs.inuse rm /home/pi/MagickaBBS/doors/ffs.inuse
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 ([INUSE Door](https://github.com/apamment/inuse)), 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](http://git.magickabbs.com/cgit/inuse)), but that is outside the scope of this document.
Again be sure to change the port to match the dosbox config for this door. Again be sure to change the port to match the dosbox config for this door.

View File

@ -24,11 +24,11 @@ should work on debian and debian derivatives.
## Install Magicka ## Install Magicka
Clone the repo and checkout the branch you want, eg. v0.9-patch. Clone the repo and checkout the branch you want, eg. v0.11-patch.
git clone https://github.com/MagickaBBS/MagickaBBS git clone git://git.magickabbs.com/MagickaBBS
git checkout v0.9-patch git checkout v0.11-patch
Build the BBS Build the BBS