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:23] – eidis | x68000:installing_games_to_hard_drive [2012/02/21 01:26] – eidis | ||
|---|---|---|---|
| Line 42: | Line 42: | ||
| **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 60: | ||
| 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 | ||
x68000/installing_games_to_hard_drive.txt · Last modified: 2019/08/27 20:45 by 127.0.0.1