x68000:installing_games_to_hard_drive
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
x68000:installing_games_to_hard_drive [2011/02/16 05:39] – eidis | x68000:installing_games_to_hard_drive [2012/02/21 01:47] – eidis | ||
---|---|---|---|
Line 28: | Line 28: | ||
http:// | http:// | ||
- | ==== Chapter 3: Floppy Drive vs Hard Drive ==== | + | ==== Chapter 3: Writing !Start.bat files ==== |
+ | |||
+ | Upon booting, the X68000 executes files from config.sys and usually they have X or SYS extensions. | ||
+ | |||
+ | * *.X files, which are required for the game to run, in almost all cases can be executed from *.BAT files or command line. | ||
+ | * *.SYS files and some rare *.X files need ADDDRV (Example #4). ADDDRV is very picky and most of the times incompatible. | ||
+ | |||
+ | |||
+ | **Combining lines from Config.sys and Autoexec.bat** | ||
+ | |||
+ | **Crystal Tower** is used to illustrate this example: | ||
+ | |||
+ | Original Config.sys | ||
+ | < | ||
+ | FILES = 15 | ||
+ | BUFFERS = 20 1024 | ||
+ | LASTDRIVE = Z | ||
+ | BREAK = KILL | ||
+ | VERIFY = ON | ||
+ | TITLE = \CONFIG\TITLE.SYS | ||
+ | KEY = \KEY.SYS | ||
+ | USKCG = \USKCG.SYS | ||
+ | BELL = \CONFIG\BEEP.SYS | ||
+ | DEVICE = \SYS\OPMDRV3.X | ||
+ | DEVICE = \SYS\FLOAT2.X | ||
+ | DEVICE = \SYS\IOCS.X | ||
+ | </ | ||
+ | |||
+ | Here we can see drivers being loaded and environmental variables being set up. | ||
+ | *The mandatory variables and drivers like **USKCG.SYS** and **FLOAT2.X** are being set up each time when booting from HDD so most of these lines can be safely ignored. | ||
+ | *Drivers are usually loaded from **SYS** and **BIN** directories. | ||
+ | |||
+ | In this example **OPMDRV3.X** and **IOCS.X** are the ones which interest us. First we must check if they can be executed after the system has fully booted. If yes, then there is a good chance that the game can be installed to HDD. | ||
+ | |||
+ | Original Autoexec.bat | ||
+ | < | ||
+ | echo off | ||
+ | PATH A: | ||
+ | tone3.x | ||
+ | chdir ct | ||
+ | ctmain | ||
+ | </ | ||
+ | |||
+ | Here we can see another environmental variable called **PATH** being set up. In this case we can go with the lazy method and **SUBST** to the directory (Example #2) where we have copied the game or we can change the paths so that we don't have to do **SUBST**. Please note that there are games which still need **SUBST** even after modifying the **PATH** variable. | ||
+ | *Remove references to **\** **A:\** **B:\** if they are present | ||
+ | *Write **OPMDRV3.X** and **IOCS.X** after the line which defines **PATH** | ||
+ | *Rename autoexec.bat to !Start.bat. | ||
+ | |||
+ | The resulting !Start.bat should look like this: | ||
+ | |||
+ | < | ||
+ | echo off | ||
+ | PATH SHELL; | ||
+ | OPMDRV3.X | ||
+ | IOCS.X | ||
+ | tone3.x | ||
+ | chdir ct | ||
+ | ctmain | ||
+ | </ | ||
- | We all know that Hard drive is the ultimate thing to have on X68000 so to cut a long story short, we want games on hard drive, and we want them now ;) | ||
==== Example #1 - Installing Fantasy Zone and running it from Hard Drive ==== | ==== Example #1 - Installing Fantasy Zone and running it from Hard Drive ==== | ||
Line 50: | Line 108: | ||
* Rename AUTOEXEC.BAT to !Start.bat and add the following two lines at the very beginning: | * Rename AUTOEXEC.BAT to !Start.bat and add the following two lines at the very beginning: | ||
+ | < | ||
SUBST B: A: | SUBST B: A: | ||
- | |||
SUBST A: A: | SUBST A: A: | ||
+ | </ | ||
The resulting !Start.bat should look like this: | The resulting !Start.bat should look like this: | ||
+ | < | ||
SUBST B: A: | SUBST B: A: | ||
- | |||
SUBST A: A: | SUBST A: A: | ||
- | |||
CRUISER | CRUISER | ||
+ | </ | ||
* Run !Start.bat | * Run !Start.bat | ||
Line 72: | Line 131: | ||
Please note that there is no CONFIG.SYS or AUTOEXEC.BAT. Now search for files with *.R or *.X file extension. Those files are executable. Most of the times the names of those files give hints on which one of them is the main. If in doubt, try to execute them one by one until you find the right one. Then create a new !Start.bat file and write the name of the file which launches game. In this case !Start.bat should look like this: | Please note that there is no CONFIG.SYS or AUTOEXEC.BAT. Now search for files with *.R or *.X file extension. Those files are executable. Most of the times the names of those files give hints on which one of them is the main. If in doubt, try to execute them one by one until you find the right one. Then create a new !Start.bat file and write the name of the file which launches game. In this case !Start.bat should look like this: | ||
+ | < | ||
BOOT.X | BOOT.X | ||
+ | </ | ||
+ | |||
+ | ==== Example #4 - Installing Namachuukei 68 and running it from Hard Drive ==== | ||
+ | |||
+ | Download ADDDRV.X from here: | ||
+ | http:// | ||
+ | |||
+ | * Make a directory in Games2 and call it Nama68 | ||
+ | * Copy ADDDRV.X and the contents of both floppies to created directory | ||
+ | * Delete HUMAN.SYS and COMMAND.X from directory Nama68 | ||
+ | * Rename config.sys to !Start.bat | ||
+ | * Use SUBST, as mentioned in Exapmle #2, to map both drives to Nama68 directory | ||
+ | * Use ADDDRV.X to load OPMXDRV.X | ||
+ | |||
+ | ADDDRV.X is very useful for games which load drivers from config.sys. The syntax for ADDDRV.X is exactly the same as in config.sys, just replace the " | ||
+ | |||
+ | < | ||
+ | SUBST B: A: | ||
+ | SUBST A: A: | ||
+ | ADDDRV.X OPMXDRV.X | ||
+ | NAMA68.X | ||
+ | </ | ||
+ | |||
+ | ==== Example #5 - Installing Pipe Dream and running it from Hard Drive ==== | ||
+ | |||
+ | This method uses 2HDSIM.X to mount XDF floppy image files and DRIVE.X to assign drive letters A and B for them. It was discovered by Caius and is the next preferred method after SUBST. | ||
+ | |||
+ | Download 2HDSIM.X and DRIVE.X from here: | ||
+ | http:// | ||
+ | |||
+ | * Make a directory in Games and call it PipeDream | ||
+ | * Rename first XDF floppy image file to Disk1 and second to Disk2 | ||
+ | * Copy 2HDSIM.X DRIVE.X and both renamed XDF image files to the created directory | ||
+ | * Create new !Start.bat file and write the following lines: | ||
+ | |||
+ | < | ||
+ | drive a: c: | ||
+ | drive a: b: | ||
+ | 2hdsim 0: Disk1 | ||
+ | 2hdsim 1: Disk2 | ||
+ | a: | ||
+ | autoexec | ||
+ | </ | ||
+ | |||
+ | The first four lines arrange the following drive mappings: | ||
+ | |||
+ | *A: = Disk1 | ||
+ | *B: = Disk2 | ||
+ | *C: = Hard Disk | ||
+ | |||
+ | The same principle applies to one disk games as well, just omit the fourth line. After the drives have been mapped and image files mounted, !Start.bat changes to drive A: and executes autoexec.bat. Please note that every game is individual and sometimes requires combining lines from config.sys and autoexec.bat files. | ||
+ | |||
+ | **The following rules must be met for image files to mount:** | ||
+ | |||
+ | |All image files must be defragmented (one continuous block).| | ||
+ | |Use [[http:// | ||
+ | |||
+ | Syntax example: | ||
+ | < | ||
+ | liner disk1 | ||
+ | </ | ||
+ | |||
+ | |Image files must be 1261568 bytes long. Sometimes while copying them with DiskExplorer their original size changes to 1263616.| | ||
+ | |Use [[http:// | ||
+ | |||
x68000/installing_games_to_hard_drive.txt · Last modified: 2019/08/27 20:45 by 127.0.0.1