JavaScript is required to use Bungie.net

Service Alert
Destiny 2 will be temporarily offline tomorrow for scheduled maintenance. Please stay tuned to @BungieHelp for updates.

#Halo

3/17/2011 3:29:48 AM
7

Pathways into Emulators - A Guide to Pre-Halo Bungie Games

[i]This guide works for Windows, Mac OS, and Linux-based operating systems. For those of you that prefer to figure things out for yourself, get the Basilisk II emulator [/i][url=http://www.emaculation.com/doku.php/basilisk_ii][i]here[/i][/url][i], System 7 from [/i][url=http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English-North_American/Macintosh/System/Older_System/System_7.5_Version_7.5.3/][i]this page[/i][/url][i], and download the games from [/i][url=http://www.macintoshgarden.org/][i]this site[/i][/url][i]. You are left to your own devices for the ROM image. If you know why you are here and what an emulator is, you may skip this first post entirely. It simply goes over some history and introduces basic technical concepts. Questions may be asked below. Try to be as descriptive and coherent as possible.[/i] [b][u]A Bit of History[/u][/b] It is fairly common knowledge that Bungie has been around well before the Halo series, but when and what games they released is not. For the curious, Thanatos 117 has penned a truly fascinating summary of Bungie history found [url=http://www.bungie.net/Forums/posts.aspx?postID=31450175]here[/url] - even more detail may be found in [url=http://www.bungie.net/Inside/history.aspx]the history section[/url] of Bungie.net. This guide forgoes any plot summaries or trivia in favor of the utilitarian approach - how can we get games this old to run on a modern system? The purview of this document is freeware games developed or published by Bungie prior to the release of Halo in 2001, which comprises [url=http://en.wikipedia.org/wiki/Gnop!]Gnop! (1990)[/url], [url=http://en.wikipedia.org/wiki/Operation:_Desert_Storm_(video_game)]Operation: Desert Storm (1991)[/url], [url=http://en.wikipedia.org/wiki/Minotaur:_The_Labyrinths_of_Crete]Minotaur: The Labyrinths of Crete (1992)[/url], [url=http://en.wikipedia.org/wiki/Pathways_into_darkness]Pathways into Darkness (1993)[/url], [url=http://en.wikipedia.org/wiki/Marathon_(video_game)]Marathon (1994)[/url], [url=http://en.wikipedia.org/wiki/Marathon_2:_Durandal]Marathon2: Durandal (1995)[/url],[url=http://en.wikipedia.org/wiki/Marathon_Infinity]Marathon Infinity (1996)[/url], and [url=http://en.wikipedia.org/wiki/Abuse_(video_game)]Abuse (1996)[/url]. As you can see, Bungie had quite the release schedule back in the day! Unfortunately, Oni and the Myth series are not freeware, and so will not be considered in this guide. One point I will raise about the Marathon trilogy - if you are not a pathological purist, I strongly recommend installing the modernized version found in [url=http://www.bungie.net/Forums/posts.aspx?postID=40058407]this[/url] guide. The current hub of the older Bungie games community is [url=http://www.bungie.net/fanclub/carnage/Group/GroupHome.aspx]For Carnage Apply Within[/url]. They often organize online games for games that would otherwise be dead, so they represent your last chance to capture the glory of what once was. [b][u]Basic Technical Stuff[/u][/b] The unifying characteristic of these games - the root from which all difficulty and frustration stems - is that they were written to run on obsolete Apple computers from the 90s. To those of you that are ignorant of the challenges of backward compatibility, suffice it to say that this is a very serious issue. Given the massive disparity between modern computers and these devices, you are left with just three options - actually use an old Apple computer, rewrite the software, or use emulation. Of the three, emulation is the clear winner. Emulation is the process of creating a virtual computer as a program on another computer, so the program behaves exactly like the physical computer it is meant to imitate. From the perspective of software running within this virtual machine, there is no difference. Emulation is done through the use of an [i]emulator[/i] - a program that takes a description of the computer you wish to create, constructs such a computer, and allows programs to run on it. The end result is [url=http://i.imgur.com/9YZ0C.jpg]this[/url] - a computer running within a computer. In this screenshot, we would refer to Windows 7 as the [i]host operating system[/i] and Mac OS 7 as the [i]guest operating system[/i]. The emulator we will use is called Basilisk II. There are several things we need in order to describe the computer we want to the emulator. The first is a virtual hard drive, known in this context as a [i]system volume[/i]. The virtual machine will use a system volume as a regular computer would its hard drive. In practice, the system volume is simply a file of specified size ([url=http://i.imgur.com/oOSpm.jpg]example[/url]). In order to create the system volume and transfer files to it, you will need to use a program that varies depending on your OS. This will be explained later. The second item we need is called a [i]ROM image[/i]. In this case, the ROM image is a file containing a very low-level program that would have translated software instructions into the actual manipulation of electrical charges on the hardware of an old computer. Here we begin to delve into legal difficulties - the Apple ROM images we want have not been freely released. Thus while offering them for download is completely legal, it is [i]illegal[/i] for you to download them unless you own that specific model of computer. The particular ROM image we want is from the Macintosh Quadra 650. In accordance with site policy, no discussion of where to find ROM images will be entertained here. The third and final item is the operating system we wish to install. Apple has been generous enough to freely release the System 7.x series of operating systems. The System 7.5.3 install we want is split into 19 parts (as it was meant to fit onto a series of floppy disks), and should be downloaded into a single directory from [url=http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English-North_American/Macintosh/System/Older_System/System_7.5_Version_7.5.3/]this[/url] page.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • necrobump

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Is the final link broken or just not available? If it's not available, could someone give me a link to a place where I can download System 7.5.3

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Thank you very mucho ♥

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • "Do not discuss unauthorized modification of console game hardware or software, even if you're not trying to cheat or pirate." While this topic may not conflict with the actual letter of the above statement, it could potentially conflict with the spirit and intent. That intent being that hacking/cracking proprietary code in order to "get it to do what you want it to do even if the authors/owners of the code disagree". I am unaware of any decision by Apple to release, authorize or share the boot ROM code for their PowerMac (and earlier) devices or to declare them "abandonware". Apple has a history of vigilantly protecting their IP and proprietary components. Because of that I am taking the precaution of locking this thread pending a consultation with our hosts. This is a sticky and tricky legal area and I (as a volunteer) and deciding to err on the side of caution. No insult, no attack and no personal disapproval is implied by this lock, I am just being careful. Stay tuned. [Edited on 03.18.2011 8:17 AM PDT]

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Reserved

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • [u][b]Getting and Installing Games[/b][/u] In order to extract the game files, you will need an ancient version of StuffIt that itself will only run in Basilisk II. Download it [url=http://www.pure-mac.com/downloads/stuffitexpanderclassicdl.html]here[/url], copy it into the system volume as you did with the System 7 install files above, and double-click inside Basilisk II to install it. In order to extract a file you must run StuffIt, go to the File menu on the top left, click Expand, then select the file. With the exception of Pathways into Darkness, the install process for the games is identical - copy the downloaded file into your system volume, extract it with StuffIt inside Basilisk II, and double-click the game icon in the extracted folder to launch. [b]Gnop! (1990)[/b] > [url=http://macintoshgarden.org/games/gnop]Download[/url] [i]Bungie's very first game, a Pong clone. Gnop! is Pong spelled backwards.[/i] [b]Operation: Desert Storm (1991)[/b] > [url=http://macintoshgarden.org/games/operation-desert-storm]Download[/url] [i]Desert Storm requires you to authenticate your copy with every startup. The game poses a trivia-based question, the answer for which was written in the game manual. The answers for all of the questions are available in a text file [/i][url=http://dl.dropbox.com/u/3333334/Desert%20Storm%20Codes.txt][i]here[/i][/url]. [b]Minotaur: The Labyrinths of Crete (1992)[/b] > [url=http://macintoshgarden.org/games/minotaur-the-labyrinths-of-crete]Download[/url] [i]Minotaur was actually made to be a multiplayer game played over a network - that's why there are multiple copies of the game in the extracted folder. Since getting networking to work with Basilisk II is far beyond the scope of this guide, you'll have to play the game solo against a punching-bag computer opponent and dream of what could have been.[/i] [b]Pathways into Darkness (1993)[/b] > [url=http://macintoshgarden.org/games/pathways-darkness]Download[/url] [i]For PiD, a different install procedure is followed. Extract the downloaded file within the host operating system, making note of the location of the .toast files. Then in the Basilisk II GUI, specify those files to be mounted alongside the system volume. Start up Basilisk II, and copy the game from the mounted toast files onto the desktop or elsewhere. You may now start the game.[/i] [b]Marathon (1994)[/b] > [url=http://macintoshgarden.org/games/marathon]Download[/url] [i]For Marathon and its sequels, I much recommend playing the modernized version. The process for getting and installing them is explained in [/i][url=http://www.bungie.net/Forums/posts.aspx?postID=40058407][i]this guide[/i][/url]. [b]Marathon 2: Durandal (1995)[/b] > [url=http://macintoshgarden.org/games/marathon-2]Download[/url] [i]Marathon 2: Durandal is also available on XBLA.[/i] [b]Marathon Infinity (1996)[/b] > [url=http://macintoshgarden.org/games/marathon-infinity]Download[/url] [i]Included with the Marathon Trilogy Box Set were the level creator and physics editor actually used in the development of the games, [/i][url=http://files3.bungie.org/trilogy/forge.sit][i]Forge[/i][/url][i] and [/i][url=http://files3.bungie.org/trilogy/anvil.sit][i]Anvil[/i][/url]. [b]Abuse (1996)[/b] > [url=http://macintoshgarden.org/games/abuse]Download[/url] [i]Although Bungie only published Abuse instead of developing it, the game has been included for completeness.[/i] Now that you have a working version of System 7, be sure to take a look at the other excellent games available on [url=http://www.macintoshgarden.org/]Macintosh Garden[/url]. [Edited on 03.16.2011 7:33 PM PDT]

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • [b][u]Setting Up the Emulator[/u][/b] Your now have most of what you need to install, set up, and use Basilisk II. I leave you in the capable hands of a very well-written series of guides, complete with pictures. Pick the one corresponding to your OS of choice: > [url=http://www.emaculation.com/doku.php/basilisk_ii_setup]Windows[/url] > [url=http://www.emaculation.com/doku.php/basiliskii_osx_setup]Mac OS[/url] > [url=http://www.emaculation.com/doku.php/basiliskii_linux_setup]Linux-based[/url] [b][u]Troubleshooting[/u][/b] [b]Windows[/b] [i]An error message pops up about a CD-ROM driver missing![/i] This doesn't actually affect anything, as you won't be using the CD-ROM drive. However, the error message may be prevented by putting the driver file in the correct folder as directed by the guide. Note that the driver will not work in 64-bit Windows. [i]When I start up Basilisk II, I just get a black screen![/i] There are two possible solutions - check that your screen resolution is set to 640x480 in the GUI. If that doesn't work you'll have to revert to an older version of Basilisk II, the guide for which is found [url=http://www.emaculation.com/doku.php/basilisk_142_setup]here[/url]. [i]When I boot System 7, there is just an error screen about not having enough memory![/i] What you have to do here is disable extensions on boot, which is done by holding the shift key as the boot process initiates. Note that this is a bit difficult to time on newer systems that boot near-instantly. I am working on finding a permanent solution. [i]There's no color! Everything is black, white, or gray![/i] Color may be enabled in the Mac OS control panel, under monitors. When in 256-bit colour mode, it seems to default to B&W on every startup, which is annoying. I am working to find a solution. [i]When running Basilisk II, I can't move any files around or perform operations on them![/i] Your volume may be mounted in read-only mode. To check, look at the top left corner of the file explorer in Basilisk II. If there is a tiny lock symbol, it is read-only. There are two solutions - the first is to make sure you are mounting it in read/write mode in the GUI. If this is the case, then you have to make a copy of your system volume and delete the old one, mounting the copy in its place. This will fix the problem. [b]Mac OS[/b] Submit your issues!

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon