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 [2012/02/21 01:08] – eidis | x68000:installing_games_to_hard_drive [2014/05/30 18:26] – eidis | ||
---|---|---|---|
Line 30: | Line 30: | ||
==== Chapter 3: Writing !Start.bat files ==== | ==== Chapter 3: Writing !Start.bat files ==== | ||
- | Upon booting, the X68000 executes files from config.sys and usually they are with X or SYS extension. | + | 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. | * *.X files, which are required for the game to run, in almost all cases can be executed from *.BAT files or command line. | ||
Line 38: | Line 38: | ||
**Combining lines from Config.sys and Autoexec.bat** | **Combining lines from Config.sys and Autoexec.bat** | ||
- | Now that we know that most files from config.sys with extension X can be executed as standalone, its time to write them in the beginning of autoexec.bat | + | **Crystal Tower** is used to illustrate this example: |
- | " | + | Original |
- | + | ||
- | Config.sys | + | |
< | < | ||
FILES = 15 | FILES = 15 | ||
Line 59: | Line 57: | ||
Here we can see drivers being loaded and environmental variables being set up. | 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. | + | *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" | + | *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. | + | In this example |
- | autoexec.bat | + | Original Autoexec.bat |
< | < | ||
echo off | echo off | ||
Line 73: | Line 71: | ||
</ | </ | ||
- | Here we can see another environmental variable called | + | Here we can see another environmental variable called |
+ | *Remove references to **\** **A:\** **B:\** if they are present | ||
+ | *Write **OPMDRV3.X** | ||
+ | *Rename autoexec.bat to !Start.bat. | ||
+ | |||
+ | The resulting !Start.bat should look like this: | ||
< | < | ||
Line 195: | Line 198: | ||
|Use [[http:// | |Use [[http:// | ||
+ | ==== Example #6 - Installing Undeadline and running it from Hard Drive ==== | ||
+ | |||
+ | This method is similar to Example #5, was also discovered by Caius and can be very efficient with three or more floppy games which are immune to SUBST. In this example the first floppy disk is mounted as floppy drive 0:, the second and third as floppy drive 1:. The game rotates disk two and three automatically when needed. | ||
+ | |||
+ | * Make a directory in Games2 and call it Undeadline | ||
+ | * Rename first XDF floppy image file to Disk1, second to Disk2 and third to Disk3 | ||
+ | * Copy 2HDSIM.X DRIVE.X and three 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 | ||
+ | 2hdsim 1: Disk3 | ||
+ | a: | ||
+ | mxdrv.x | ||
+ | loader.x | ||
+ | </ | ||
x68000/installing_games_to_hard_drive.txt · Last modified: 2019/08/27 20:45 by 127.0.0.1