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/20 23:27] – 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. Those with X extension, which are required for the game to run, almost in all cases can be executed from files with BAT extension or command line. The SYS files and some rare X files need ADDDRV (Example #4). ADDDRV is very picky about what it will or will not load so don't expect it to do magic. | + | 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** | ||
- | 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 | + | **Combining lines from Config.sys and Autoexec.bat** |
- | Crystal Tower | + | **Crystal Tower** is used to illustrate this example: |
- | Config.sys | + | Original |
< | < | ||
FILES = 15 | FILES = 15 | ||
Line 55: | Line 56: | ||
</ | </ | ||
- | Here we can see drivers being loaded and environmental variables being set up. The very important ones and drivers like USKCG.SYS and FLOAT2.X are being set up each time when booting from HDD so most of these can be safely ignored. | + | Here we can see drivers being loaded and environmental variables being set up. |
+ | *The mandatory variables | ||
+ | *Drivers are usually | ||
- | autoexec.bat | + | 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 | echo off | ||
Line 66: | 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 186: | Line 196: | ||
|Image files must be 1261568 bytes long. Sometimes while copying them with DiskExplorer their original size changes to 1263616.| | |Image files must be 1261568 bytes long. Sometimes while copying them with DiskExplorer their original size changes to 1263616.| | ||
- | |Use [[http:// | + | |Use [[http:// |
x68000/installing_games_to_hard_drive.txt · Last modified: 2019/08/27 20:45 by 127.0.0.1