Compose your message:
Email Address :
Password:
OR
Your Name :
REAL Email Address :
(PRIVATE)
Subject :
Please type in your message (no HTML codes) :
[quote]On 03/25/2011 @ 23:27, Lord Crass wrote : I made a mistake in the commentary of that disassembly. In the Vorpal code, at $586-$58a, it reaches here if it read a $FF byte and branches if sync is NOT set. I originally had this the other way around (sync is set). This is due to the 1541 memory map I was using which has bit 7 of $1c00 listed as 0=data, 1=sync which is backwards. Perhaps the doc is referring to the voltage level on the actual pin instead of what the drive sees, since these are active-low. : : Also, I originally wrote that the Maverick copier writes $FF $55 at the start of the track. It's actually $FF $FF $55. I missed the 2nd BVC which occurs at $099, which, absent another STA $1C01 will just write the previous byte again. So this does indeed write a 16 bit sync mark, which is how Maverick frames the track data properly. Note that the Vorpal loader doesn't look for this sync and will handle the data either way. -- [/quote]
File to attach:
(limit 250000 bytes)
SECURITY QUESTION
I had 10 parakeets and then I acquired 5 more.
How many do I have now?
: