Post by jefferysto on Sept 21, 2005 22:46:11 GMT -5
Q-Doer is a program that is on the q-newer.d64 file that Raymond Day posted on his website:
mywebpages.comcast.net/raymondday/q-link/Q-NEWER.zip
Here is some information on the q-doer program:
The q-doer program creates a new or blank QData on
track 18/sector 15 of a disk. It uses a file call
qlink.obj as its source to create this.
The qlink.obj file contains 257 bytes.
The first two bytes are $ff $7f, which would load the
qlink.obj starting at $7fff if loaded with ,8,1
This leaves 255 bytes left in the file for writing the
18/15.
The next byte contains $0d (which helps the qlink.obj
to put starting info at $8000.
This leaves 254 bytes left in the file for writing,
but a sector is 256 bytes.
I think this info is loaded into memory starting at
$7fff-$80fd. $80fe and $80ff contain $ff's.
Memory from $8000-$80ff is written to 18/15.
The file qlink.obj, however also is missing a byte
which causes the data to be "misaligned" when
decrypted. I noticed this on Rays information when he
sent me his 18/15. After the program is run, offset
$92 on track 18/15 should be $00, not $01.
Should be:
offset $90 - fe ff 00 01 02 03 04 05
But it is:
offset $90 - fe ff 01 02 03 04 05 06
So, when you use this q-doer program, track 18/15 is
fine up to offset $91. $92 should be $00, but is $01,
they forgot the $00 here. So the rest of the bytes
are in the wrong location (for example: what is
supposed to be at $93 is at $92, what should be at $94
is at $93, etc.)
The q-doer program also puts the last two bytes at $ff
$ff (because this is memory at $80fe-$80ff), but they
should be $6c $6d.
In the whole scheme of things, i don't think that the
"misalignment" should pose a problem, but I just
wanted to let everyone know.
A fixed Qlink.obj file has been sent to jeff to fix the "misalignment".
I tested it and it works fine. Jeff will probably post the
file when he gets it.
I am close to releasing a program in c64 basic that
among other things, writes a blank QData 18/15.
Sincerely,
Jeffery S. Stone
jefferystone@yahoo.com
mywebpages.comcast.net/raymondday/q-link/Q-NEWER.zip
Here is some information on the q-doer program:
The q-doer program creates a new or blank QData on
track 18/sector 15 of a disk. It uses a file call
qlink.obj as its source to create this.
The qlink.obj file contains 257 bytes.
The first two bytes are $ff $7f, which would load the
qlink.obj starting at $7fff if loaded with ,8,1
This leaves 255 bytes left in the file for writing the
18/15.
The next byte contains $0d (which helps the qlink.obj
to put starting info at $8000.
This leaves 254 bytes left in the file for writing,
but a sector is 256 bytes.
I think this info is loaded into memory starting at
$7fff-$80fd. $80fe and $80ff contain $ff's.
Memory from $8000-$80ff is written to 18/15.
The file qlink.obj, however also is missing a byte
which causes the data to be "misaligned" when
decrypted. I noticed this on Rays information when he
sent me his 18/15. After the program is run, offset
$92 on track 18/15 should be $00, not $01.
Should be:
offset $90 - fe ff 00 01 02 03 04 05
But it is:
offset $90 - fe ff 01 02 03 04 05 06
So, when you use this q-doer program, track 18/15 is
fine up to offset $91. $92 should be $00, but is $01,
they forgot the $00 here. So the rest of the bytes
are in the wrong location (for example: what is
supposed to be at $93 is at $92, what should be at $94
is at $93, etc.)
The q-doer program also puts the last two bytes at $ff
$ff (because this is memory at $80fe-$80ff), but they
should be $6c $6d.
In the whole scheme of things, i don't think that the
"misalignment" should pose a problem, but I just
wanted to let everyone know.
A fixed Qlink.obj file has been sent to jeff to fix the "misalignment".
I tested it and it works fine. Jeff will probably post the
file when he gets it.
I am close to releasing a program in c64 basic that
among other things, writes a blank QData 18/15.
Sincerely,
Jeffery S. Stone
jefferystone@yahoo.com