[Coco] Copying a data/binary file from disk to cassette

Phil phil.salathe at gmail.com
Thu Jan 3 22:47:49 EST 2008


Bob and Tim: thanks for the info re: tokenizing!  I had a feeling it 
was something like that, though I didn't have the vocabulary to 
express it.

Tim: I've downloaded and installed ToolShed, and after a bit of 
fiddling I've gotten makewav to create a plausible-looking WAV, but 
both of my attempts are  crashing the emulated Coco, immediately 
after it parses the header and shows the incoming file name.  My 
command line looks like this (with the full path abbreviated to 
"phil"):

makewav -r /phil/TREKBOER.BIN -2 -s44100 -nTREKBOER.BIN -o/phil/trekboer.wav

I've had much the same results if I eliminate the -2 and -s flags, 
though I've also gotten the intriguing error message "?IO ERROR IN 
22404.5738".  I'm using .bin files that have worked for me when I've 
used imgtool to put them on disk. Any idea what I'm doing wrong?

...Oh, wait a minute!  Is it that I'm not setting -d and -e to tell 
makewav where the start and execution addresses should be?  But if 
that's the case, that puts me sort of back to square one, as I don't 
know how to figure those out, unless there's a tried-and-true method 
of inspecting an executable .bin to see where it's supposed to load 
(maybe there's a header file?).

(Also, the pitch of the carrier wave sounds like it's about 4-5% 
higher when I use the default setting for -s, unless Audacity is just 
choking on a 11250 Hz file.)

Otherwise, it certainly looks like this app (makewav) would solve my 
problem, at least when going from emulator to real hardware.  I'll 
try to knock something together as Bob suggested for going in the 
other direction -- let's see if I can recapture those 
twenty-years-lost BASIC chops I used to have...

Thanks for all your help!

Best,
Phil



More information about the Coco mailing list