User Tools

Site Tools


x68000:installing_games_to_hard_drive

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
x68000:installing_games_to_hard_drive [2012/02/19 10:51] eidisx68000:installing_games_to_hard_drive [2012/02/21 01:24] eidis
Line 28: Line 28:
 http://www.vector.co.jp/soft/win95/util/se151106.html http://www.vector.co.jp/soft/win95/util/se151106.html
  
-==== Chapter 3: Floppy Drive vs Hard Drive ====+==== Chapter 3: Writing !Start.bat files ==== 
 + 
 + 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. 
 + 
 + 
 +**Combining lines from Config.sys and Autoexec.bat** 
 + 
 + Now that we know that most *.X files from config.sys 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 
 +<code> 
 +FILES = 15 
 +BUFFERS = 20 1024 
 +LASTDRIVE = Z 
 +BREAK = KILL 
 +VERIFY = ON 
 +TITLE = \CONFIG\TITLE.SYS 
 +KEY = \KEY.SYS 
 +USKCG = \USKCG.SYS 
 +BELL = \CONFIG\BEEP.SYS 
 +DEVICE = \SYS\OPMDRV3.X 
 +DEVICE = \SYS\FLOAT2.X 
 +DEVICE = \SYS\IOCS.X 
 +</code> 
 + 
 +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. 
 + 
 +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 
 +<code> 
 +echo off 
 +PATH A:\;A:\SHELL;A:\SYS;A:\BIN;A:\ETC 
 +tone3.x 
 +chdir ct 
 +ctmain 
 +</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 
 +  *Write **OPMDRV3.X** and **IOCS.X** after the line which defines **PATH** 
 +  *Rename autoexec.bat to !Start.bat. 
 + 
 +The resulting !Start.bat should look like this: 
 + 
 +<code> 
 +echo off 
 +PATH SHELL;SYS;BIN;ETC 
 +OPMDRV3.X 
 +IOCS.X 
 +tone3.x 
 +chdir ct 
 +ctmain 
 +</code> 
  
- We all know that Hard drive is the ultimate thing to have on X68000 so to cut a long story short, we want games on hard drive, and we want them now ;) 
  
 ==== Example #1 - Installing Fantasy Zone and running it from Hard Drive ====  ==== Example #1 - Installing Fantasy Zone and running it from Hard Drive ==== 
Line 138: Line 198:
  
 |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://nfggames.com/X68000/PC_Tools/jsplit.zip|JSplit]] to cut off the excess and restore their original size.|+|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.|
  
  
x68000/installing_games_to_hard_drive.txt · Last modified: 2019/08/27 20:45 by 127.0.0.1