NFG Games + GameSX

User Tools

Site Tools

Trace:
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
x68000:installing_games_to_hard_drive [2012/02/20 23:22] – eidisx68000:installing_games_to_hard_drive [2019/08/27 20:45] (current) – external edit 127.0.0.1
Line 1: Line 1:
 How to install games to hard drive and make them run. How to install games to hard drive and make them run.
  
-==== Chapter 1: The Fundamentals ====+====== Chapter 1: The Fundamentals ======
  
  You will need X68000 with 2MB of ram and a keyboard. It is possible to run some small games with 1MB as well, but the majority of them require 2MB. Download the latest English version of DiskExplorer here:  You will need X68000 with 2MB of ram and a keyboard. It is possible to run some small games with 1MB as well, but the majority of them require 2MB. Download the latest English version of DiskExplorer here:
Line 13: Line 13:
 This will save you the trouble of setting up a working environment. Open the downloaded image with DiskExplorer, have a look around. This will save you the trouble of setting up a working environment. Open the downloaded image with DiskExplorer, have a look around.
  
-==== Chapter 2: HumanOS vs MS-DOS ====+====== Chapter 2: HumanOS vs MS-DOS ======
  
  Lucky for us the HumanOS is very much like ye good old MS-DOS. Now let me explain what happens when X68000 tries to boot from hard drive:  Lucky for us the HumanOS is very much like ye good old MS-DOS. Now let me explain what happens when X68000 tries to boot from hard drive:
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: 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) + Upon booting, the X68000 executes files from config.sys and usually they have X or SYS extensions.
-**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+  * *.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**
  
-Crystal Tower+**Crystal Tower** is used to illustrate this example:
  
-Config.sys+Original Config.sys
 <code> <code>
 FILES = 15 FILES = 15
Line 53: Line 56:
 </code> </code>
  
-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. 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. 
 + 
 +Original Autoexec.bat
 <code> <code>
 echo off echo off
Line 64: Line 71:
 </code> </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 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 and enjoy the show. 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**. Please note that there are games which still need **SUBST** even after modifying the **PATH** variable. 
 +  *Remove references to **\** **A:\** **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> <code>
Line 78: Line 90:
  
  
-==== Example #1 - Installing Fantasy Zone and running it from Hard Drive ==== +====== Example #1 - Installing Fantasy Zone and running it from Hard Drive ====== 
  
   * Make a directory in Games2 and call it FantasyZone   * Make a directory in Games2 and call it FantasyZone
Line 89: Line 101:
  
  
-==== Example #2 - Installing Star Cruiser and running it from Hard Drive ====+====== Example #2 - Installing Star Cruiser and running it from Hard Drive ======
  
   * Make a directory in Games2 and call it StarCruiser   * Make a directory in Games2 and call it StarCruiser
Line 111: Line 123:
   * Run !Start.bat   * Run !Start.bat
  
-==== Example #3 - Installing Dragon Buster and running it from Hard Drive ====+====== Example #3 - Installing Dragon Buster and running it from Hard Drive ======
  
   * Make a directory in Games2 and call it DragonBuster   * Make a directory in Games2 and call it DragonBuster
Line 123: Line 135:
 </code> </code>
  
-==== Example #4 - Installing Namachuukei 68 and running it from Hard Drive ====+====== Example #4 - Installing Namachuukei 68 and running it from Hard Drive ======
  
 Download ADDDRV.X from here: Download ADDDRV.X from here:
Line 144: Line 156:
 </code> </code>
  
-==== Example #5 - Installing Pipe Dream and running it from Hard Drive ====+====== Example #5 - Installing Pipe Dream and running it from Hard Drive ======
  
  This method uses 2HDSIM.X to mount XDF floppy image files and DRIVE.X to assign drive letters A and B for them. It was discovered by Caius and is the next preferred method after SUBST.  This method uses 2HDSIM.X to mount XDF floppy image files and DRIVE.X to assign drive letters A and B for them. It was discovered by Caius and is the next preferred method after SUBST.
  
-Download 2HDSIM.X and DRIVE.X from here: +Download [[http://nfggames.com/x68000/Misc/HardDisk/Tools/2hdsim_drivex.zip|2HDSIM.X and DRIVE.X]]
-http://nfggames.com/X68000/Misc/2hdsim_drivex.zip+
  
   * Make a directory in Games and call it PipeDream   * Make a directory in Games and call it PipeDream
Line 176: Line 187:
  
 |All image files must be defragmented (one continuous block).| |All image files must be defragmented (one continuous block).|
-|Use [[http://nfggames.com/X68000/Misc/liner.zip|Liner]] to defragment the images when required.|+|Use [[http://nfggames.com/x68000/Misc/HardDisk/Tools/LINER001.LZH|Liner]] to defragment the images when required.|
  
 Syntax example: Syntax example:
Line 184: Line 195:
  
 |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. If that does not help, reimport the original image file.|+|Use [[http://nfggames.com/x68000/PC_Tools/Disk/jsplit.zip|JSplit]] to cut off the excess and restore their original size. If that does not help, reimport the original image files.|
  
 +====== Example #6 - Installing Undeadline and running it from Hard Drive ======
 +
 + This method is similar to Example #5, was also discovered by Caius and can be very efficient with three or more floppy games which are immune to SUBST. In this example the first floppy disk is mounted as floppy drive 0:, the second and third as floppy drive 1:. The game rotates disk two and three automatically when needed.
 +
 +  * Make a directory in Games2 and call it Undeadline
 +  * Rename first XDF floppy image file to Disk1, second to Disk2 and third to Disk3
 +  * Copy 2HDSIM.X DRIVE.X and three renamed XDF image files to the created directory
 +  * Create new !Start.bat file and write the following lines:
 +
 +<code>
 +drive a: c:
 +drive a: b:
 +2hdsim 0: Disk1
 +2hdsim 1: Disk2
 +2hdsim 1: Disk3
 +a:
 +mxdrv.x
 +loader.x
 +</code>
  
  
x68000/installing_games_to_hard_drive.1329744171.txt.gz · Last modified: 2019/08/27 20:44 (external edit)