Mike Thaler uses Riddle Magic to come up with his stand-up material. Here he is honing his Kamala Harris routine. Classic.

Followers of this site (ed. yeah like that’s a thing) will remember a few years ago I created a in-browser playable version of the Applesoft BASIC game Haunted House for this site. Over the past month or so I got it in my head to push my skills as a programmer and make a much more fully realized version of the game. Today I am releasing my new version of the game, Haunted House: Remastered! It’s a vast improvement on the original in almost every way possible. In other words, it’s actually fun to play.

While it’s nowhere near the level of sophistication of an Infocom game, I think it does some pretty impressive stuff (for my skill level as a programmer). It’s still a two word parser, but the vocabulary is increased. There are full-page help screens, triggered story events, a retro-styled monochrome monitor look, and a bunch of scary sound effects! Please take a few minutes and give the game a try. It’s not too long and I try to keep the puzzle reasonably fair.

In Applesoft you can prompt for user input in two ways. First there is INPUT A$ which will display a question mark on the screen and await user input followed by a RETURN. That user response then fills the variable A$. Similarly there is GET A$ which also displays a question mark but GET will only accept a single keypress as user input. My main problem with both of these is an aesthetic one: that darn question mark.

The solution is to write your own input routine leveraging machine code routines via PEEKs and POKEs. To do this, first I simulate a cursor by placing a flashing underscore character at the bottom of the screen.

101 VTAB 24 : HTAB 1 : CALL -868 : PRINT ":"; : FLASH : PRINT "_"; : NORMAL : GOSUB 55

A lot is going on in this line. The VTAB and HTAB commands position the screen cursor at line 24 and character 1. CALL -868 is a special machine code call that clears that single line of text. Now that we have an empty line we type a colon and then a flashing underscore. The result looks like this:

This looks like a user input prompt, but at this point it does nothing. The magic happens at the subroutine which is GOSUB’d at the end of that line.

55 KEY = PEEK (49152) : IF KEY < 128 THEN 55
56 IF KEY > 224 AND KEY < 251 THEN KEY = KEY - 32 : REM UPPERCASE
57 POKE 49168,0 : BUZZ = PEEK (49200) : RETURN

In line 55 we are creating a variable KEY and assigning to it the contents of memory location 49,152 to it ($C000 for you hex-heads). Turns out location 49,152 will read the keyboard and return the ASCII value of the currently pressed key. If that value is a character then we break out of the loop and go to line 56.

Line 56 insures that, if the ASCII value of the key denotes a lowercase key, it is converted to uppercase by shifting the ASCII value. POKE 49168,0 clears the keyboard buffer so that the PEEK in 55 will work next time around and not just register the same value. Finally, that BUZZ = PEEK (49200) bit triggers a speaker click so that the player’s keystroke has and audible sound.

When we return to the main game loop we now have a variable KEY which contains an ASCII value of the key pressed. I can then branch the program based on this value. I can also test if it’s a RETURN keypress and then toggle text display. Later in my program I can concatenate keypresses into a single string value by returning to that subroutine again and again until a return press is detected. That’s how I collect the OBJECT half of the VERB OBJECT pair.

I think the issue is the number of arrays that I am defining. For now I think I have a fix. I have set LOMEM: 24576 at the top of my program. Supposedly, this will force the interpreter to define variables in a memory location after the hi-res pages. We shall see.

In any event, the game is back and running again. And the text screen now has some text formatting enhancements:

One of the cooler things I have implemented is this text screen. If at any prompt you hit RETURN you turn off the hi-res graphics and can see this text screen. Here will be some valuable game info included the location’s name, exits and any TAKE-able objects. The code for this is rather simple:

58 IF GM = 1 THEN GM = 0 : TEXT : RETURN
59 GM = 1 : CALL -3100 : RETURN

GM is a flag which tracks where you are in graphics mode (1) or text mode (0). CALL -3100 triggers the hi-res graphics screen without erasing its contents. So exciting, right!?!

Continued in Part V

Verbs

Haunted House used a simple, two-word input parser: VERB NOUN. But I wanted this new game to simplify the number of verb choices in the same way the LucasArts adventures streamlined the interface of Sierra-style adventure games. The player will be limited to around a dozen verbs that are entered with a single keystroke.

The verb list is largely based on the options in Monkey Island. PUSH and PULL have been combined into MOVE. To move you must hit Go then enter either North, South, East, West, Up or Down. This is a little annoying, but there are only so many letters in on the keyboard and I needed that D, U and S elsewhere. Other commands require you to hit the keystroke, then type out an object NOUN and then hit Return. “Guess the verb” will no longer be an issue… welcome to 21st century “guess the noun” technology!

Each verb then get’s its own subroutine which contains the logic that triggers the various game actions (or provides a default message if nothing special happens). By assigning a number value VB to each verb, I can use the following to branch to the various subroutines: ON VB GOSUB 1000,600,800,850, ...

Game Data

The game data is set in the program by assigning strings and numbers to several arrays. In Applesoft you need to declare the size of an array by dimensioning it with the DIM command. For the rooms I will set the size of the rooms array to the number of rooms RM by declaring DIM RM$(RM). Then, near the start of my program I read data into the array by using GOSUB to a loop like this:

5000 DATA "Room description 1","Room Description 2", [...]
5005 FOR I = 1 to RM : READ RM$(I) : NEXT
5010 RETURN

The DATA can be listed anywhere in the code and it’s important to make sure that there are exactly as many data strings as READ commands. Otherwise, you might get OUT OF DATA errors.

This method of declaring rooms and object will eventually make your Applesoft program very long and hard to edit. I was pretty sure that I could figure out a way to read the data in from an external text file. But more on that later.

Continued in Part IV

So, Applesoft BASIC it is! With emulation and modern computing I have been able to develop my code on a Windows PC and then quickly run it in emulation. My workflow isn’t nearly as fancy as some other retro-programmers. I type my Applesoft in a text editor, then in AppleWin I paste the entire code listing into an emulated apple using SHIFT+INSERT. The benefit of using emulation as a development environment is that you can throttle the emulation to run hundreds of times faster (hit ScrLK) than real hardware. This makes testing small changes a breeze.

My first task was to see if I could successfully load a Graphics Magician image into a program. The program itself is a bit of a UI nightmare. Without a manual or reference card, it’s nearly impossible to know what keys do what. On top of that, the program requires that you use a joystick to move the drawing cursor on the screen. Fortunately, the manual can be found online and you can use a PC mouse as a joystick within AppleWin. I managed to crank out a couple of silly images for testing and save them to my game disk.

I then used to code provided in the manual to write a simple Applesoft program that displays the image:

1 PRINT CHR$ (4);"MAXFILES1"5 HIMEM: 32768
10 PRINT CHR$ (4);"BLOAD PICDRAWH"
20 PRINT CHR$ (4);"BLOAD ROOM1.SPC,A32768"
30 HGR
40 A = 32768:HI = INT (A / 256):LO = A - HI * 256: POKE 0,LO: POKE 1,HI50 CALL 36096

In order for this code to work, you are required to copy PICDRAWH from the Graphics Magician disk to your disk. This is the machine code rendering engine that is loaded into memory at the top of this program. The MAXFILES1 DOS command apparently frees up some memory by limiting the amount of open files. This command needs to be the first one in your code, before any string assignments, etc. I think HIMEM does something similar with allocating memory locations. I have never written an Applesoft program so large that it required memory management so the purpose of these commands alludes me somewhat. As this project grows, I may have to familiarize myself with them.

You will see CHR$(4) often in Applesoft programs. CHR$() is a function that retrieves the keyboard character in assigned to the numerical value in then parenthesis. For example, PRINT CHR$(65) prints the letter A. In this case, character number four is the equivalent of keying in CTRL+D. That instructs the computer that the next PRINTed string should be executed as a DOS command rather than PRINTed to the screen.

The Graphics Magician file is ROOM1.SPC. BLOAD ROOM1.SPC,A32768 loads the drawing code into memory location 32768. That seems like a crazy random number but it is actually $8000 in hexidecimal. HGR switches to high-resolution graphics mode and then line 40 stores the memory address of the picture into a location PICDRAWH will know to look. Finally, the CALL 36096 triggers the PICDRAWH draw routines.

There’s a lot of fancy stuff going on here, but it does the job as advertised. The Graphics Magician manual also goes deeper with more code that shows how to string multiple images into slide shows and how to overlay objects over backgrounds. More on that when I get to my object code. For now, this proof-of-concept was enough to get a simple working prototype up and running.

Continued in Part III

My go to art program back in the day was always Alpha Plot from Beagle Bros. It wasn’t the easiest software to use. In fact, it came bundled with a cardboard overlay for your keyboard so you had an immediate reference as to what the various keys did. Still, I managed to draw pixel by pixel and create masterpieces like this:

The Graphics Magician is something altogether different though. Instead of meticulously drawing each point on the screen, you create images programatically using a language of lines, fills and brushes. The end product is what today we would call vector art.

The advantage of vector art is that file sizes are small. The other advantage is that these drawing routines can be used within one’s own Apple ][ programs.

This gave me an idea for a project. Take the text-based adventure game I had made years ago, and use these routines to add graphics to the game. As I type this, I am already pretty far along in the project, but I will be going back and documenting my progress. Hopefully someone might find this informative and, if I am able to follow through, maybe I will have a releasable game in the end. It’s doing more than I ever imagined already:

Continue to Part II

I recently took the time to sample all of the default sounds from the Apple IIgs music composition program The Music Studio for use with my new sampler. The sounds were recorded directly out of my IIgs via an Applied Engineering sound card and into the Octatrack. I then took the WAV files into my PC and cleaned up the audio a bit. The IIgs outputs a rather noisy signal.

The samples are organized into four sets: Jazz, Rock, Classical and Voices. Each set has about fifteen instruments and each instrument was sampled at six octaves of C. Jazz also contains a couple drum kits which I broke apart and sliced into eight notes each. I tried to create nice evenly sliced sample chains but they are a tad off so they require a little manual tweaking after auto-slicing them.

The Music Studio was one of the first music composition programs I ever used. Certainly, it was the best one I had used up until that time. Technically, the first would have been Will Harvey’s Music Construction Set on the Apple ][+ with a Mockingboard sound card, but I don’t think any of my compositions from that program have survived (I’ll have to dig around my old disks one of these days). Fortunately(?), my IIgs compositions have survived and have been imaged and archived. Now such classics as “Kill Your Mama” and “Robert is Coll” have been preserved for the ages. Most of what we did in The Music Studio was transcribe my brother’s heavy metal guitar tab sheet music. So there’s a lot of G’n’R and Metallica riffs.

What made the program so cool (or “coll” if your are my typo prone teen aged self) was the inclusion of drum sounds. In hindsight, really bad drum sounds but drums nonetheless. It was my first real go at creating electronic music. I had no idea how performers like Cabaret Voltaire or even Devo were able to program their keyboards to play music automatically. There was that Jan Hammer Miami Vice video where you actually got a glimpse of a computerized rig (probably a Fairlight or something else that cost more than a car) and this seemed about as close to that as I could ever get.

Unfortunately, The Music Studio had a lot of quirks that made it really difficult to use. Although it uses a standard music staff for notation, it really plays notes like a piano roll. Meaning, if you have a whole note you want to ring out under several quarter notes you have to insert a bunch of redundant looking rests above the whole note. Otherwise, it plays the entirety of that long note before playing the quarter notes that are after it. Confusing, yes. Practically speaking, what this means for the composer is they have to put a bunch of evenly spaced rests across the top of the song scroll to insure the play head keeps moving along. The other major limitation is that you can’t have two instruments play the same note at the same time. That made any sort of complex arrangement a matter of spacing instruments across the staff all while avoiding your kludge of rests.

Until I was exposed to MOD files and tracking software on my PC this is how I thought music was made on a computer. Even Q-Bob’s music was created using a similar looking MIDI composition program. FastTracker and MadTracker freed me of this notion and from there on I began to make music more in line with what I wanted to do as a teen.

The Music Studio did have a very recognizable sound though. If you ever played Dream Zone you know exactly what I mean. These samples now allow us to get some of that distinctive sound into modern music apps and hardware. So, use the link at the bottom to download the set for yourself. In the meantime, here’s the first composition I made using the samples:

Now, I am pretty familiar with Applesoft Basic programming, but I was always in awe of commercially released software on the Apple ][ that ran so fast, had fancy hi-res graphics and used sounds other than the system beep. What was the secret of these mythical programs that required you to type “BRUN” in order to get them to load? The secret was machine language.

This image shows you just how intuitive and user-friendly machine code is. It’s almost like it was written by the Terminator himself (just after he finished cutting out his eyeball with an Xacto knife). Despite the seeming impenetrability of machine code, in the past I made a few attempts to learn it. I would get a few chapters into Apple Machine Language and then the endless diversions into binary math would addle my art-school trained brain. It never really clicked for me.

What I didn’t know is that there was this thing called “assembly language” which is a human-readable method of creating machine code. It still is pretty brutal compared with Basic or JavaScript, but for the first time I think I am starting to understand machine language and, more generally, just how the Apple ][ works. Cryptic hex numbers and even the aforementioned binary math are still a part of assembly, but it uses three letter abbreviations for various functions and allows for comments and labels. The assembler will translate the letters into their numeric machine language equivalents and assemble the source code into a BRUN-able program. Woo-hoo!

The first hundred pages or so of Assembly Lines has been very informative and I have dutifully typed in many of the example programs. At one point I had a pretty nice “ah ha!” moment when I was messing around with creating tones. I created a small program that generated an annoying high pitch noise and decided I would further enhance the interactivity by outputting a stream of numbers to the screen showing the paddle positions. Before I got very far beyond just reading the paddles I noticed that I could use the joystick to change the pitch of the sound. I had no idea why this would change the pitch so I decided to look at the machine code in the built-in paddle routine. To my surprise, I was able to see that it got the paddle value by using a count down loop. The longer the count down, the lower the tone. I couldn’t really say why this was the case, but at least I was starting to be able to decipher that wall of hex values.

Now, back in the late eighties I got my hands on an issue of Compute! magazine. Kids nowadays with their fancy iWatches and download services may not believe this, but in the olden days there would be program listings in computer magazines. Readers could carefully type in the program and, “Voila!”, you had new software to use. This issue contained a listing for a game called Space Dodger, with a separate listing for just about every machine available at the time. Most were written in basic, but the one for Apple ][ was pure machine code. I had no idea what any of it meant, but I dutifully typed every line into my Apple’s monitor. The result was a pretty slick little arcade game:

You moved your ship to avoid the space junk which flew by from right to left at varying speeds. However, playing the game in emulation, I noticed a slight problem: the ship movement was mapped to the wrong joystick axis.

And now we get to my second assembly language “Ah ha!” moment. I now know the memory address where the paddles are read. I just needed to search the code listing for 00 1E FB and it would just be a matter of changing the 00 to 01. I found the values at $706B, made my edit and, magically, the joystick now worked correctly!

I still have no clue as to what the other 99% of the code does, but this was a breakthrough. Assembly language… I think I can do this. In the meantime, download Space Dodger and play it in your favorite emulator.

Apparently there is something wrong with my IIgs. A couple of weeks ago I noticed that Briel Computers (a small company dedicated to making retro computer kits) put their 4 meg Apple IIgs RAM card on sale on eBay. My IIgs runs pretty well, but I that extra 2.8 megs of RAM would make things run a lot better (it would be nice to have more than 5 windows open in Finder without getting memory warnings). I clicked the “Buy it now” button and waited patiently for my card to arrive so I could supercharge my nerditude. Well, when the card came I carefully installed it and powered up the Apple II. At first everything seemed cool. The control panel indicated I was brimming with RAM and the CFFA3000 was not showing any problems. But when I attempted to boot into System 6, everything just froze.

Fortunately, Briel was about as helpful as could be and offered to send me a new card. Something must have broken in transit, right? Well, the second card came and I had the same problems. We were never able to figure out what was going on. We thought it may be that my motherboard is the issue. I wouldn’t doubt that, but, personally, I think my power supply is very suspect. That thing emits buzzing noises that only my daughter can hear. She refuses to come into my room when the GS is fired up.

In any event, I am back down to a whopping 1.2 meg ram and am now keeping my eye open for another GS. In the end I got my money back and, but if I ever get a new Apple IIgs, I will contact Briel again about buying RAM. So, if you live in the Chicago area and have an old Apple IIgs you want to unload for cheap, drop me a line.

This evening I took the time to archive all my old Apple IIgs floppies. This is something I have been meaning to do since I got my CFFA3000 card. I have been pretty lucky in that, having been told since the early nineties that floppy discs will just disintegrate over time, all of my disks are in good shape and I have never had one fail on me. But I know it will eventually happen, and probably soon. Ripping floppies to disc images on the CFFA is a piece of cake. Each of these discs took about 3 minutes to pull down onto a thumb drive as a .PO disk image. The most difficult part of the process was scanning the actual disks into photoshop so that I could have a nice digital record of my horrible teenage handwriting (seen above). The best labels are the ones where I crossed out the name of some old pirated game and reused the disk for my files. You’d think there would be a nice application on the IIgs for printing disk labels?

For as much as I loved my old Apple IIgs (and the Apple ][+ before that), I didn’t really have that much personal data to save. I guess I wasn’t using the raw computing power of the Apple II for productivity and content creation and was more focused on gaming. What I do have is a bunch of college term papers and essays that are filled with the grammatical atrocities you’ve come to expect on this Web site. There is also a fair share of musical compositions that my brother and I churned out in Music Studio. Classics like “Robert is Coll” (sic) and “Ultra Coolness.” Yeah, I was really concerned about my cool factor in those days (but too lazy to fix my coll typo). Finally, there are a few discs of drawings and images that we created in Deluxepaint and PaintWorks Gold. I may post some of those in the near future. They are quite.. ahem… cool.

The book takes you step-by-step through the process of creating a simple text adventure game using Applesoft Basic. The final product is an adventure called “Haunted House.” It’s about as crude and bare bones as a work of interactive fiction can be, but it does what it needs to: there are objects, rooms and key puzzles.

Well, in a recent flurry of Apple retro computing I got side tracked into porting this game into JavaScript. The result is here. Click the screenshot to launch the game in a new browser window (requires JavaScript, duh – View the actual page if you are viewing this in an RSS feed reader). It’s a fully working port of the original, with all its flaws and quirks. The only additions I made were to make the EXITS display more cleanly and added the verb “drop” to the vocabulary.

One of the more popular pages on this site is my guide to coverting Apple ][gs disk images into real, working ][gs floppies. In order to ease this process and bring some life back to my old computer, this year I splurged and bought a CFFA3000 for my birthday.

CFFA3000 is an expansion card for the Apple 2 series of computers that allows you to use a standard USB flash stick or compact flash card as a storage media for all your Apple ][ disk images. Now you can take a standard Apple disk image, such as a .2MG, .DSK or .PO file, and save it to a USB stick. The USB stick can then be plugged into the CFFA3000, and, with a few settings tweaks, you can boot that disk image on your original Apple ][ hardware. Really cool!

Installing the card is just a matter of opening the Apple ][, and inserting the card into an empty slot (I used slot 7). I hooked up a short USB extension cable to the card which allows me to swap out a USB stick without having to open up the computer case. The CFFA3000 even allows you to swap out the flash memory while the computer is up and running. I also have a compact flash card directly plugged in to the card. I have put a few essentials like system software and utilities on that card, but the set up program allows me to pull disk images from both the USB and compact flash at the same time.

Disk images are mounted from a simple and intuitive menu system that is access via the IIgs control panel access screen. For the first time ever I have been able to run System 6 without having constantly to swap disks (I never owned a hard drive for my IIgs) and it only takes seconds to boot up. Booting system software from a floppy literally used to take minutes for me. 32MB disk images are easily created and can be use to then store all my documents like this kick ass Paintworks drawing I did of Adam Ant:

The CFFA3000 is not only about IIgs software. It can also can be used to mount and run disk images of 5.25″ floppies. Now I can Lode Runner and Alpha Plot without worrying about the fragile disk media getting eaten alive by my ancient disk drives. This isn’t perfect. I have noticed that one of my favorite Apple games of all time, Beyond Castle Wolfenstein, does not work when running off of the card (same disk image runs fine from booted from a floppy in the real drive).

One additional benefit is that the CFFA3000 makes it dead simple to rip physical disks, 3.5″ or 5.25″, into disk images for use on a PC emulator or the CFFA itself. I’m still getting the hang of that process. It won’t work for copy protected disks.

So far my only problem with it is that there is a limit to the amount of images you can pack on the flash media. This is somewhere around 250 disk images. But all-in-all, this is a great product and an essential add-on if you want to get serious about turning that old Apple ][ back on.

I still own an Apple IIgs—the last of the Apple 2 computers before Apple went all Macintoshy—and Apple’s direct competitor to the Commodore Amiga. It’s fun to fire it up every now and again and listen to those 5.25″ drives grind away. What’s great about playing around with a twenty year old computer is that all that software that looked so cool, expensive and unattainable back in the day is now widely available for download on the Internet.

Disk Images and Emulators

The ultimate resource for all things Apple //e and earlier is Asimov FTP Archive. From here you can find just about every piece of software ever created for the Apple II in disk image format (usually a .DSK, .PO or .NIB file). Be warned, even though most of the companies that created this software are long gone, downloading old “Abandoned” software is still a legal gray area and there’s always a chance, albeit quite slim, that you may get in trouble for this.

On a PC you can get these disk images running quite easily in AppleWin by just dragging the .DSK file into the program window. AppleWin is an Apple II emulator, a program that mimics the hardware of another computer in software. There are several Apple emulators out there, but this one is the best.

There is also a great resource for IIgs called What Is the Apple IIgs? In addition to being a pretty complete history of the system, they also host disk images and packaging for most of the software ever released for the IIgs. In this case the file format is the .2MG disk image format. AppleWin can’t emulate the IIgs so you will need to use another program.

Emulators for the IIgs are not nearly as good as AppleWin. There seem to be many choices if you are running OSX. However, if you are running Windows, you are a bit limited. The one that I have gotten familiar with is Kegs32 (a Geocities link… you’ve been warned) ActiveGS. It is far from perfect and can’t run everything. The developers could learn a thing or two about usability from AppleWin. Flaws aside, once you get over the initial learning curve it can do a fairly good job with several IIgs programs, especially system software.

If all this downloading is a bit much for you, the easiest way to explore Apple II software is via a browser applet/plug-in/activex widget at Virtual Apple ][.

Using Disk Images on an Actual Apple II

Running old software in emulation can be good and bad. Most of the times emulation is much faster and convenient. In the case of AppleWin you can save the state of the machine. This means you can save your game even in a program that doesn’t natively support save games. Also, you can throttle the disk speed and machine speed to make productivity software run much better than it ever ran on the actual hardware. As good as the programs look on a modern LCD-type screen, they still look better on a nice tiny tube monitor. It gives the graphics a pleasant contrasty glow.

In the case of the IIgs, no one has quite nailed the emulation as accurate as they could. For this reason, you’ll be pleased to know that you can take those disk images you grabbed off of the Web and transfer them to actual floppy disks! I was really excited when I discovered this, but my hopes were squashed when I actually tried to get files from my PC to my IIgs. It took me a very long time combing through usenet and other on-line resources to figure out just how to do it with my set up. There are a few ways to accomplish this, but many of the methods involve things like null modems and SSH. A bit too nerdy even for me. On this page I will go through my process step-by-step to show you how it’s done.

The Tools You’ll Need

Hardware requirements are one of the biggest hurdles in this process. Here is the list of things you will need to get disk images off your PC and on to your Apple 2:

1. An Apple IIgs with 3.5″ and 5.25″ floppy drives.
   If you don’t have a IIgs, I can’t help you. All of the software I use is IIgs specific, so if you only have your //e you’ll have to look elsewhere for help
2. A PC with 3.5″ floppy drive.
   Seems simple enough, except that they don’t build 3.5″ drives into PC these days. I bought a Sony USB floppy drive from NewEgg.com for around $20 and it does the job very well.
3. A Macintosh computer running System 9 or earlier.
   This is the biggie. Not many people have old Macs just lying around. Fortunately, I inherited one from my office, but you may have to troll eBay or Freecycle to find one. OS X will not cut it. System 7,8,9 supported the ProDos disk format, which is the Apple II format, and I don’t think OS X supports this (besides, most OS X Macs don’t have floppy drives either)
4. Lots of Blank 3.5″ or 5.25″ disks!
   These are getting quite hard to find nowadays, but there are still sources out on the net if you search. I have tons of 3.5″ floppies from a 32 disk backup installation of Windows 95 that I never needed to use.

Step 1: Getting Files Off Your PC

So you found a .2MG file that you want to get on your IIgs. The problem with .2mg files is that the IIgs doesn’t know what to do with them, and, in most cases, a .2MG file is larger than the 800K that can fit on a ProDos floppy. You will need to compress the .2MG file into a ShrinkIt file. ShrinkIt is the .ZIP file equivalent for the IIgs. In addition to being able to archive a group of files you can also use it to create a compressed disk image.

(What Is the Apple IIgs? used to allow you to download files in .SHK ShrinkIt format. Due to bandwidth issues, they now only offer the .2MG files. Oh well)

Never fear. There is an open-source Windows software out there than can decipher and convert all sorts of Apple ][ files and disk images: CiderPress. After installing CiderPress, run it and choose the Disk Image Converter function from the Tools menu. Simply select your .2MG file then choose ShrinkIt Disk Archive (.SDK) from the options and save your converted file. This .SDK file can now be saved to a PC formatted floppy. You will notice that this file is actually compressed and smaller in file size than the original.

Step 2: Transferring the Image to a ProDos Disk.

This next step is simple, but is dependent on you having access to an older Macintosh computer running System 7, 8 or 9. If you are lucky enough to have one of these machines, you can simply insert your PC formatted floppy in the drive and drag the .SDK file on to your desktop. Then format a ProDos floppy (either on the Mac or your IIgs) and insert it into your Mac’s floppy drive. Next, drag the .SDK file from your Mac desktop on to this ProDos floppy. Now your disk image is ready to make its way to your IIgs via good old fashioned sneaker net.

Step 3: Creating and Actual Disk from the Disk Image

Now, the rest of the action will take place on your Apple IIgs. Boot up your IIgs System disk. The essential piece of software that you will need is GS ShrinkIt. ShrinkIt is a common compression format on the Apple 2. If you don’t already have GS ShrinkIt for your ][gs, getting it up and running can be a bit of a challenge. I was lucky to have it already from back in the day, but if you need it, I’d suggest reading this page from the Apple II Csa2 FAQ.

Run GS ShrinkIt and select OPEN ARCHIVE from the FILE menu. Now insert your disk with the .SDK file on it and open the file. You may need to check the “Show All Files” radio button in order to find the file. If all went well, you should be able to open the file and see the contents of the compressed .SDK file.

Have a blank 3.5″ floppy ready and click the Extract button. Insert your floppy and follow the prompts to select the drive in which your blank disk resides. You will then have to wait while the computer grinds away and copies your disk image to the floppy. If all goes well you should now have a working copy of the software which you downloaded off the Internet. Have fun!

UPDATE: I no longer need to follow this method. To find out why, read my post about the CFFA 3000.