Differences

This shows you the differences between two versions of the page.

--- x68000:installing_games_to_hard_drive [2012/02/21 00:55] – eidis
+++ x68000:installing_games_to_hard_drive [2012/02/21 01:18] – eidis
@@ Line 30: / Line 30: @@
 ==== 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 are with X or SYS extension.
+  * *.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.
@@ Line 37: / Line 40: @@
  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 for to illustrate this example:
+**Crystal Tower** is used to illustrate this example:
 Config.sys
@@ Line 55: / Line 58: @@
 </code>
-Here we can see drivers being loaded and environmental variables being set up. The very important variables 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. Most of the times those drivers which will interest us will be 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.
+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.
-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.
+Autoexec.bat
 <code>
 echo off
@@ Line 66: / Line 73: @@
 </code>
-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. Remove references to "A:\", "\" or "B:\" if they are present and after this line write the two commands from config.sys. Rename autoexec.bat to !Start.bat. The resulting !Start.bat should look like this:
+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**.
+  *Remove references to "A:\", "\" or "B:\" if they are present and after this line write the two commands from config.sys.
+  *Rename autoexec.bat to !Start.bat.
+The resulting !Start.bat should look like this:
 <code>
@@ Line 186: / Line 197: @@
 |Image files must be 1261568 bytes long. Sometimes while copying them with DiskExplorer their original size changes to 1263616.|
-|Use [[http://nfggames.com/X68000/PC_Tools/jsplit.zip|JSplit]] to cut off the excess and restore their original size. If that does not help, reimport the original image file.|
+|Use [[http://nfggames.com/X68000/PC_Tools/jsplit.zip|JSplit]] to cut off the excess and restore their original size. If that does not help, reimport the original image files.|