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:18] – eidis | x68000:installing_games_to_hard_drive [2012/02/21 01:47] – 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 37: | Line 37: | ||
**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: | **Crystal Tower** is used to illustrate this example: | ||
- | Config.sys | + | Original |
< | < | ||
FILES = 15 | FILES = 15 | ||
Line 60: | Line 58: | ||
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 **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. | ||
- | Autoexec.bat | + | Original |
< | < | ||
echo off | echo off | ||
Line 73: | Line 71: | ||
</ | </ | ||
- | 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**. | + | 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:\", " | + | *Remove references to **\** **A:\** **B:\** if they are present |
+ | *Write **OPMDRV3.X** | ||
*Rename autoexec.bat to !Start.bat. | *Rename autoexec.bat to !Start.bat. | ||
x68000/installing_games_to_hard_drive.txt · Last modified: 2019/08/27 20:45 by 127.0.0.1