16 Feb
2000
16 Feb
'00
10:49 a.m.
Looking at the tape, I see that the words "END OF
FILE BAS65.PTP"
are punched at the end of the tape in sort of pseudo dot-matrix
characters. Does the "PTP" extension tell us anything?
"Paper TaPe" in DEC-ese.
Looking at
the start of the tape:
"MICRO-SOFT BAS65.PTP [2601,1260] 29-JUL-77 15:27:58"
That makes sense, Microsoft was cross-assembling on PDP-10's at
the time, and [2601,1260] would be the PPN code for an account.
For the first couple of years Microsoft was using the hyphenated
form.
Looking through the first few feet of "real
data"...
No high bits, the first few bytes are:
00111011 x3b ';' (was hoping for the start of an assembly comment)
00110010 x32 '2' (nope, looks like some sort of hex...)
00110000 x30 '0'
01000001 x41 'A'
00110000 x30 '0'
00110000 x30 '0'
00110000 x30 '0'
00110011 x33 '3'
00111001 x39 '9'
01000001 x41 'A'
That makes some sense, "20" is the 6502 opcode for a JSR (jump to
subroutine). The next two bytes are presumably the subroutine's
address, and "39" is the 6502 opcode for an AND abolute,Y instruction.
Tim.
17 Feb
17 Feb
3:03 a.m.
On Wed, 16 Feb 2000 16:49:57 -0500
CLASSICCMP(a)trailing-edge.com wrote:
>Looking through the first few feet of "real
data"...
>
>No high bits, the first few bytes are:
>00111011 x3b ';' (was hoping for the start of an assembly comment)
>00110010 x32 '2' (nope, looks like some sort of hex...)
>00110000 x30 '0'
>01000001 x41 'A'
>00110000 x30 '0'
>00110000 x30 '0'
>00110000 x30 '0'
>00110011 x33 '3'
>00111001 x39 '9'
>01000001 x41 'A'
This looks to me like MOS Technologies checksum hex format,
as used on the KIM-1.
That makes some sense, "20" is the 6502
opcode for a JSR (jump to
subroutine). The next two bytes are presumably the subroutine's
address, and "39" is the 6502 opcode for an AND abolute,Y instruction.
Not if it's MOS Tech. hex! The first two digits are the
length of the block (in hex), then four digits of address,
then the hex for the data block. There'll be a checksum on
the end. In this case, we've got a 32-byte block (20 hex)
starting at address A000.
This format is also used on the UK101, and is accepted by
many types of EPROM programmer.
Tim.
--
John Honniball
Email: John.Honniball(a)uwe.ac.uk
University of the West of England
18 Feb
18 Feb
4:16 a.m.
>Looking
through the first few feet of "real data"...
>
>No high bits, the first few bytes are:
>00111011 x3b ';' (was hoping for the start of an assembly comment)
>00110010 x32 '2' (nope, looks like some sort of hex...)
>00110000 x30 '0'
>01000001 x41 'A'
>00110000 x30 '0'
>00110000 x30 '0'
>00110000 x30 '0'
>00110011 x33 '3'
>00111001 x39 '9'
>01000001 x41 'A'
This looks to me like MOS Technologies checksum hex format,
as used on the KIM-1.
That makes some sense, "20" is the 6502
opcode for a JSR (jump to
subroutine). The next two bytes are presumably the subroutine's
address, and "39" is the 6502 opcode for an AND abolute,Y instruction.
Not if it's MOS Tech. hex! The first two digits are the
length of the block (in hex), then four digits of address,
then the hex for the data block. There'll be a checksum on
the end. In this case, we've got a 32-byte block (20 hex)
starting at address A000.
8900
days inactive
8902
days old
2 comments
3 participants
participants (3)
-
bill＠chipware.com -
CLASSICCMP＠trailing-edge.com -
John.Honniball＠uwe.ac.uk