It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
JDelekto: For the time, it actually makes sense. Reading audio for your data isn't an "instant on" and you always have that lead-in issue when it starts to play. To bad we didn't have today's technology back then. :)
I don't think we're on the same page... How about i show you what i mean... I'll look over and mark the inserted extra blocks in RED.. I'll also mark it's appropriate pre/post areas in green..
Attachments:
avatar
JDelekto: For the time, it actually makes sense. Reading audio for your data isn't an "instant on" and you always have that lead-in issue when it starts to play. To bad we didn't have today's technology back then. :)
avatar
rtcvb32: I don't think we're on the same page... How about i show you what i mean... I'll look over and mark the inserted extra blocks in RED.. I'll also mark it's appropriate pre/post areas in green..
OK, that's interesting, does the data change between each read? I believe at the time, the easiest way to pirate software on cassette was a dub, most hardware at the time didn't have the 'care' to look for special markers.
avatar
JDelekto: OK, that's interesting, does the data change between each read? I believe at the time, the easiest way to pirate software on cassette was a dub, most hardware at the time didn't have the 'care' to look for special markers.
I guess i wasn't very specific on the data. The data is what i typed in. I remember while making my detokenizer that i could just user cload to get the data, and it loaded perfectly regardless of size. So i thought the reverse would be true with csave (and saving as a cassette file)... And for very tiny sources i was experimenting with, that was fine (under 128 bytes)...

However i didn't actually write cassette reading support in my detokenizer and so when it ran into the sector blocks (the timers, the data blocks, the checksum) it just tried to decode it and would fail... Which comes to the 4 hours i wasted.

I thought maybe with some numbers it was making and referencing an array to save space, but when i looked at the raw memory in the Atari800 emulator, i didn't see those markers... making me realize it was part of the csave statement... Once i went to a page going into the details and noticed the 0x55 0x55 marker reference, i knew my guess was correct. That just means my detokenizer now refuses to work on cassette files and you have to strip out the header and block information first (which i wrote a little program for).
avatar
JDelekto: OK, that's interesting, does the data change between each read? I believe at the time, the easiest way to pirate software on cassette was a dub, most hardware at the time didn't have the 'care' to look for special markers.
avatar
rtcvb32: I guess i wasn't very specific on the data. The data is what i typed in. I remember while making my detokenizer that i could just user cload to get the data, and it loaded perfectly regardless of size. So i thought the reverse would be true with csave (and saving as a cassette file)... And for very tiny sources i was experimenting with, that was fine (under 128 bytes)...

However i didn't actually write cassette reading support in my detokenizer and so when it ran into the sector blocks (the timers, the data blocks, the checksum) it just tried to decode it and would fail... Which comes to the 4 hours i wasted.

I thought maybe with some numbers it was making and referencing an array to save space, but when i looked at the raw memory in the Atari800 emulator, i didn't see those markers... making me realize it was part of the csave statement... Once i went to a page going into the details and noticed the 0x55 0x55 marker reference, i knew my guess was correct. That just means my detokenizer now refuses to work on cassette files and you have to strip out the header and block information first (which i wrote a little program for).
Excellent observation.
Internet Archive has a collection of books for/about Atari computers. Including Basic/Asm manuals for Atari 400/600/800 XL. Maybe you can find something useful. ;)
Post edited July 19, 2015 by astropup
avatar
astropup: Internet Archive has a collection of books for/about Atari computers. Including Basic/Asm manuals for Atari 400/600/800 XL. Maybe you can find something useful. ;)
Believe me that's where this all started originally, specifically with the tokens and how to read the format before i realized i'd be making a detokenizer...

Curiously i got the book references from here, although from what i understand it's just an offshoot of the archive.org site so... (But much easier to navigate... well i think so)
avatar
rtcvb32: Believe me that's where this all started originally, specifically with the tokens and how to read the format before i realized i'd be making a detokenizer...
Ah, ok. :)

avatar
rtcvb32: Curiously i got the book references from here, although from what i understand it's just an offshoot of the archive.org site so... (But much easier to navigate... well i think so)
I think Atari Archives is a site that goes way back and that there is a high probability they were the ones who originally contributed to Archive.org collection. I can't say for sure without checking, though. :)
avatar
astropup: I think Atari Archives is a site that goes way back and that there is a high probability they were the ones who originally contributed to Archive.org collection. I can't say for sure without checking, though. :)
Well when i contacted them to offer assistance they referred me to archive.org... so...