This archive should contain 3 files. The purpose of these files is to alter your StrongHold game to use Gravis's GF1MIDI.ADV ( & ULTRAMID) driver instead of sbfm.adv + SBOS. PUTAIL.EXE PUTAIL.C README.TXT My friend showed me StrongHold(tm) on his Gravis Ultrasound(tm). The music sounded kind of wimpy with SBOS 2.0B10(tm) So using his hex editor, he located the Roland(tm) .ADV file within the large file, STRONG.DAT I'm sure there could be different revisions of STRONGHOLD floating around, but his particular version held roland.adv @ offset 0x3289C5 (3312069 in decimal.) I wrote PUTAIL.C to insert the GF1MIDI.ADV file into this location. Actually, "insert" isn't the right word, more like "write-over." The length of STRONG.DAT wasn't altered after my program finished executing. --- HOW TO USE PUTAIL.EXE (with respect to StrongHold by SSI) 1) Copy PUTAIL.EXE and GF1MIDI.ADV into your STRONGHOLD directory. 2) BACKUP YOUR --STRONG.DAT-- FILE!!! I KNOW IT'S 5 MEGABYTES, BUT JUST IN CASE SOMETHING DOESN'T WORK... 3) Run PUTAIL.EXE 4) When it asks you "Enter name of file to alter", type in STRONG.DAT (The program will try to open the file for reading & writing...if not successful than the program will exit back to DOS.) 5) Now, PUTAIL will ask you to enter the .ADV file to install. Type in GF1MIDI.ADV 6) PUTAIL will ask you one final question, the "offset." This tells PUTAIL the exact (byte) location to begin writing to, in STRONG.DAT. With my friend's revision (1.00) of StrongHold, the decimal number is 3312069. 7) PUTAIL will print the number of bytes altered. There you are! 8) Load ULTRAMID, and GF166.COM (get the GUSAILxx.ZIP archive) (Use ULTRAMID -M110, otherwise the music seems to clip.) 9) Change the configuration to use ROLAND FOR MUSIC, and NONE FOR SOUND EFFECTS. Now, if all goes well, Stronghold should load. If you have GF166.COM loaded, you'll ALSO hear the digitized sound effects, despite the configuration! Apparently, the digital sound driver "searches" the PC memory for a DIGPAK driver, regardless of the configuration. Regarding digitized sfx, the config only tells STRONG.EXE which DIGPAK driver to load & execute, nothing more. On my friend's system, during the heat of combat a lot of "ERROR 27" messages pop up. Just push space bar and they'll to go away. This was an improvement over SBOS, which occasionally locked-up during intense digital sound effects. If anything goes wrong, I am not responsible for possible damage, headaches, etc.etc. No warranty with this program, if it does not work as documented. ---- Q. What if the offset doesn't work for me? A. You could try locating the Roland.ADV driver yourself. You'll need a hex editor, and just search for the keyword "Miles" in STRONG.DAT Look for the Roland Miles driver, which should come after all the DIGPAK drivers. Oh, look at GF1MIDI.ADV first. You'll notice there seem to be two bytes before the text header begins. (Keep this in mind as you write down the location of the Roland.ADV driver.) Q. Say, can't we also stick GF166.COM into STRONG.DAT? A. I couldn't get that to work. GF166 is about 5500 bytes long, and the other DIGPAK drivers are shorter than this. If you put GF166 into STRONG.DAT, it will overlap two file boundaries. This shouldn't matter, since you'll only run one of them (GF166), but my friend's system returns a QEMM exception error. The offset of the DIGPAK-PAS driver is hex 30AD49 (3190089 decimal.) The offset of the DIGPAK-SBPro driver is 309C0A (3185674 decimal.) (from v1.00 of Stronghold) Maybe you can make it work. Q. Why do the music instruments sound strange? A. Well, the game's music was composed on a Roland MT-32 or equivalent. The Gravis's supplied patches (and patch configuration) cohere to the General MIDI standard. You could try changing the patch configuration if you know how to re-map MT-32 into GM. Royce Liao I don't regularly call any of the Gravis BBS nodes. But if you have internet access, you can leave a message on the "ultrasound daily digest." I can reguarly read it.