HOW TO MAKE AIMDEMO USEFUL or Crutches for Crippleware I downloaded AIMDEMO.ZIP from a BBS recently. I expected crippleware, but this one is quadraplegic! You can only load DEMO.INS, and you can't save anything. You only get to listen to AIMDEMO run scales -- you never get to hear the instrument in a real musical piece. Well, I did a little checking, and found a way to produce .INS files. First, run AIMDEMO and load in DEMO.INS. (If you wish to start with something other than DEMO.INS, copy it to DEMO.INS before you run AIMDEMO.) Try the options, and when you find a sound you like, hit Print-Scrn to dump the screen to your printer. Exit AIMDEMO. Copy DEMO.INS to another name, say CROAK.INS. Use a hex editor like FIXFILE, HEXED, or NU to load CROAK.INS. Now get your screen dump. Ignore the tempo. MODE and VOICE are one byte each, and are stored in the first two bytes of the file respectively. The other 26 parameters are stored as 2-byte values, although they could fit in one byte. The MODULATOR parameters are stored at file offset 02h through 1Ah, in the order listed on the screen dump. They are followed by the CARRIER parameters, in the same order. You will have to convert all the values from decimal to hex, and remember that the low byte is stored first. (If converting to hex is a problem, you really should not be using a hex editor.) At this point, if you are using ver 1.5 of JUKEBOX and COMPOSER, you need to use BANKMNG to put the .INS into a .BNK file. This is not a convenient way to produce instrument files, but it does work. If you are serious about creating instruments, and can spare the cash, buy AdLib's instrument maker. If not, try this procedure. Note that I do not yet have an AdLib tech manual (it is on order) and I figured out the file format strictly from the AIMDEMO screen. All the .INS files I have seen are either 54 bytes or 80 bytes. AIMDEMO only manipulates the first 54 bytes, so I don't know what the the extra bytes represent. : *===|=Blade Runner==-- :