Re: [M100] Model 100 service manual scan

[BiggRanger]

Sorry Josh,
 In my excitement I completely misread your message and thought you 
scanned the manual... But still, thanks for uploading it!


Darren Clark




On 5/17/2019 1:13 PM, biggran...@tds.net wrote:

Hello Josh,
 Thanks for scanning and uploading the manual. I had a look 
through, and it looks like the image compression is way up. The 
schematics (page 83) look like pretty blurry when you zoom in on them, 
like a lossy JPG, and approaching questionable readability. What 
resolution did you scan them in at? And is it possible to save the PDF 
with the compression turned way down so the image quality is better?


Darren Clark



On 5/17/2019 11:58 AM, Josh Malone wrote:

All,

I received this scan from another member many moons ago - apologies
that I don't remember whom it was. Anyway, it seems to be much better
quality than the ones I can find posted, so I've uploaded it to the
Internet Archive.

https://archive.org/details/TandyM100ServiceManual

Hope this helps people!

-Josh

Re: [M100] Model 100 service manual scan

[BiggRanger]

Hello Josh,
 Thanks for scanning and uploading the manual. I had a look 
through, and it looks like the image compression is way up. The 
schematics (page 83) look like pretty blurry when you zoom in on them, 
like a lossy JPG, and approaching questionable readability. What 
resolution did you scan them in at? And is it possible to save the PDF 
with the compression turned way down so the image quality is better?


Darren Clark



On 5/17/2019 11:58 AM, Josh Malone wrote:

All,

I received this scan from another member many moons ago - apologies
that I don't remember whom it was. Anyway, it seems to be much better
quality than the ones I can find posted, so I've uploaded it to the
Internet Archive.

https://archive.org/details/TandyM100ServiceManual

Hope this helps people!

-Josh

[M100] Tape Header Information

[BiggRanger]

Does anybody have more information about the tape header for the 
M100/200? Specifically the file descriptor (the first block of data).



leader (long string): 0x55
magic key (1 byte): 0x7F
block type (1 byte):
    0xD0 = file descriptor for ML program (*.CO)
    0xD3 = file descriptor for tokenized BASIC program (*.BA)
    0x8D = data file
    0x9C = file descriptor for data file (*.DO)
filename (6 bytes)
file start address (2 bytes - high byte, then low byte) for .CO file
file size (2 bytes - high byte, then low byte)
file run address (2 bytes - high byte, then low byte) for .CO file
4 bytes of unknown data
checksum (1 byte) - add bytes from block type to checksum together, must 
= 0x00


I'm trying to figure out what the 4 bytes of unknown (just before the 
checksum) do, they seem to be 0x00, 0xFE, 0x02, 0x6E for everything I have.



 LEADER 0x
 MAGIC 0x557F
 0xD3
~~>>BLOCK TYPE = FILENAME (TOKENIZED BASIC)
 0x4C 'L'
 0x49 'I'
 0x46 'F'
 0x45 'E'
 0x32 '2'
 0x20 ' '
FILE NAME (6 BYTES)
 0x05
 0xF3
FILE START (2 BYTES) = 62213
 0xB7
 0x09
FILE SIZE (2 BYTES) = 2487
 0x05
 0xF3
FILE EXEC (2 BYTES) = 62213
 0x00
 0xFE
 0x02
 0x6E 'n'
 0x70 'p'
CHECKSUM GOOD - BLOCK COMPLETE



Darren Clark

Re: [M100] ba 2 wav software

[BiggRanger]

Of some interest might be the utilities WAV2CAS and CAS2WAV, they are 
available here:

http://knut.one/wav2cas.htm

Here is a nice write up of it in use with a Model 200:
http://munk.org/typecast/2014/07/25/file-transfer-for-trs-80-model-100102200-using-a-digital-audio-recorder-the-road-less-travelled/ 



and video:
https://www.youtube.com/watch?v=exdiQdjioyQ

Darren Clark


On 11/2/2018 3:37 AM, Joel Barbé wrote:

Hello,

I done some unsucceful search on internet about a ba to wav software.

Do you know if it's possible To convert ba file (from virtualt for 
example) To a wav file?


I have several cassette cables for the m100 or 200. But no serial cable.
I know serial transferts is better.  I havn't the hardware To do that 
right now.



Thanks for reading.

Re: [M100] program library in WAV format

[BiggRanger]

Of some interest might be the utilities WAV2CAS and CAS2WAV, they are 
available here:

http://knut.one/wav2cas.htm

Here is a nice write up of it in use with a Model 200:
http://munk.org/typecast/2014/07/25/file-transfer-for-trs-80-model-100102200-using-a-digital-audio-recorder-the-road-less-travelled/

and video:
https://www.youtube.com/watch?v=exdiQdjioyQ

Darren Clark

Re: [M100] Tandy Portable Disk Drive...

[BiggRanger]

TPDD1 or TPDD2? The TPDD1 uses single density disks and TPPD2 I believe 
used double density disks (not 100% sure since I only have a TPPD1). But 
in the specs the TPPD1 reads/writes 40 tracks, and the TPDD2 
reads/writes 80 tracks.


http://www.pestingers.net/pdfs/other-computers/radio-shack/pdd-man.pdf
http://www.pestingers.net/pdfs/other-computers/radio-shack/pdd2-man.pdf


On 3/24/2018 8:02 PM, Chris Kmiec wrote:
I don't think that's the issue as the drive responds to commands, and 
I can see the head move. When trying to format a blank disk, it 
actually goes through the motions, and gets to the last track, before 
it fails.


Chris

On Sat, Mar 24, 2018 at 6:57 PM, Fugu ME100 > wrote:


I/O Error generally means the drive is not being seen on the
serial port.  Does the serial port on the machine work?  Can you
check it out make sure it is working? Link to a PC and use TELECOM
to a terminal program or try the new mcomm out.


Could be a bad TPDD cable I had problems with mine it was not
making good contact into the drive, I had to have it just in the
right position to work.  I stopped using it after that :)




*From:* M100 mailto:m100-boun...@lists.bitchin100.com>> on behalf of Chris
Kmiec mailto:ckmi...@gmail.com>>
*Sent:* Saturday, March 24, 2018 23:46
*To:* m...@bitchin100.com 
*Subject:* Re: [M100] Tandy Portable Disk Drive...
Well, I have REX, with TS-DOS, and also tried the
installation/bootup procedure from the manual. Didn't work either
way - I/O Error. I looked over the board, and don't see anything
obvious. Everything cleaned, etc.

My "big score" with a DVI, TPDD, and M100 has had an issue with
every single component... At least it came with a ton of cables,
manuals, and disks!

Unless somebody can suggest anything else I can try, I'm giving up
on the TPDD for now, too many things I'm working on, including
getting the drive in the DVI to work.

Chris

On Thu, Mar 22, 2018 at 9:20 AM, Brian White mailto:bw.al...@gmail.com>> wrote:

The "M100SIG" archive contains a few programs just for dealing
with the incompatibility of different dosses. There is at
least one or two programs just for loading and unloading the
dvi dos and a tpdd dos so you can switch between them without
actually wiping and reinstalling each time.



There is (on p. 7 of the TPDD2 Manual) a cryptic related
reference that the utility disk can’t be used with a
computer in conjunction with the DVI, so maybe these can’t
all be used at once,


-- 
bkw

Re: [M100] Printers

[BiggRanger]

Many years ago I had an Epson RX-80 with my CoCo, and I'd love to get my 
hands on one again. But I picked up a Brother M-1009 with my Model 200. 
It's a serial/parallel printer (dip switch setting) so it works on my 
new CoCo3 (serial), my Model 200, and my Linux PC (parallel)! I've seen 
these on eBay for around $50.00 and you can still buy new print ribbons 
for it.


printer -> https://imgur.com/a/0a02m
whole system -> https://imgur.com/a/bfWqr

Darren Clark


On 2/8/2018 10:36 PM, ke...@kevinbecker.org wrote:

T102 just for the fun of it. Any recommendations?
  I'm also thinking of getting a CoCo at some point so I'd prefer one
with a serial interface.  I had an Epson RX-80 back in the day and I
don't want to hassle with a serial to parallel adapter again.  There
are a few DMP-130s on eBay that look okay but I'm wondering if anyone
has any experience.  Is it hard/expensive to find ribbons, etc?

Re: [M100] How to dump ROM(s)?

[BiggRanger]

The easiest way would be to PEEK through the address space (maybe 4 or 
8K at a time) and output the values somewhere (maybe over serial to 
another PC).




On 11/23/2017 11:35 AM, Bob wrote:

OK I saw a couple of request for a ROM dump of my 102/Paladin MC-1.

How do I dump the ROM or ROMs?

Re: [M100] eBay Alert

[BiggRanger]

Looking forward to it!

On 9/26/2017 12:45 PM, Stephen Adolph wrote:
When I can, I will release the "T200 dual RAM module" PCB at Oshpark.  
Seems like a good idea.


This will mean that people can build their own.

Steve


On Tue, Sep 26, 2017 at 12:30 PM, Jim Anderson > wrote:


> -Original Message-
>
> For those in need of memory for their Tandy 200

Awesome, mine arrives in the mail today (allegedly) so I get to
find out whether I need some... and if so, then try to convince
the seller to ship to canada

Re: [M100] Utility disk image from sector access

[BiggRanger]

Great to hear that!

Now that I've got a pretty good grasp on the reverse engineering of the 
PDD1 firmware, I'm wondering if it is necessary to do the PDD2?


https://github.com/BiggRanger/Tandy_PDD

Darren Clark


On 8/23/2017 12:24 PM, Kurt McCullum wrote:
Success! I’ve got my utility reading AND writing TPDD2 disk images 
with the sector access commands. I’ve got a bit of cleanup and testing 
left to do and then I’ll put it in the members area.

Re: [M100] PDD Firmware Reverse Engineering - Progress

[BiggRanger]

Yes, you're right. I just took a quick look at the T200 schematic and 
saw few gates sitting at the RS232 connector, I didn't notice the VEE at 
the bottom (plus the image is very pixelated too).




On 8/9/2017 4:20 PM, Mike Stein wrote:

I think you're right about the drive side signals being at TTL levels and not 
'true' RS232, but if you have another look at the T200 schematic (or actually 
measure) I think you'll find that like the other model Ts it does indeed 
conform to the RS232 spec with a swing of -5V to +5V.

I believe the 'special cable' takes care of the necessary translation.

m

- Original Message -
From: 
To: 
Sent: Wednesday, August 09, 2017 1:52 PM
Subject: Re: [M100] PDD Firmware Reverse Engineering - Progress



There should be a little difference in speed, the data to and from the
disk in not streamed, it is buffered in RAM in chunks on the drive
controller board and then transferred to disk (or back to serial). And
everything is done asynchronously.
I'm sure 19200 was chosen for robustness though, the RS232 interface on
the drive controller is not a proper implementation and only provides 0
to 5V signaling for "mark" and "space", not the proper -3V to -15V for a
"mark" and +3V to +15V for a "space". And looking at the schematic for
the T200, it's the same way too.

Darren


On 8/9/2017 1:27 PM, John R. Hogerhuis wrote:

Interesting! I wonder if it can actually do 76800bps since it's in
their baud rate table.  I've found that's the top speed of the model
100. I don't think the t200 can reach it though. I think the t200 will
function at 38400 but I don't remember for sure.

Not that it matters too much. It's a disk drive so we're limited by
the speed of the drive itself.

-- John.

Re: [M100] PDD Firmware Reverse Engineering - Progress

[BiggRanger]

There should be a little difference in speed, the data to and from the 
disk in not streamed, it is buffered in RAM in chunks on the drive 
controller board and then transferred to disk (or back to serial). And 
everything is done asynchronously.
I'm sure 19200 was chosen for robustness though, the RS232 interface on 
the drive controller is not a proper implementation and only provides 0 
to 5V signaling for "mark" and "space", not the proper -3V to -15V for a 
"mark" and +3V to +15V for a "space". And looking at the schematic for 
the T200, it's the same way too.


Darren


On 8/9/2017 1:27 PM, John R. Hogerhuis wrote:
Interesting! I wonder if it can actually do 76800bps since it's in 
their baud rate table.  I've found that's the top speed of the model 
100. I don't think the t200 can reach it though. I think the t200 will 
function at 38400 but I don't remember for sure.


Not that it matters too much. It's a disk drive so we're limited by 
the speed of the drive itself.


-- John.

[M100] PDD Firmware Reverse Engineering - Progress

[BiggRanger]

For those who are interested...
Getting a copy of the PDD1 Software Manual really helped out with the 
reverse engineering effort!


I've figured out a few command tables and added a bunch of documentation 
to the assembly source.


I've updated the reverse engineering project here: 
https://github.com/BiggRanger/Tandy_PDD

PDD.ASM has all the important stuff.

Findings so far:
1) The code was written in assembly and hand coded, I do not believe 
that it was compiled from a higher level language.
2) There is nothing hidden in this code, no extra commands, no Easter 
eggs, nothing.

3) There is only 6 bytes out of the 4K of ROM unused. This thing is full.
4) The software manual really filled in the gaps, the only thing not 
documented well is the S-REC stuff to inject code into the drive, and 
what really happens in INIT mode.


What's next:
1) Clean up the documentation a bit more.
2) Try and find a PDD2 (working or not, but only mechanically not as I 
need the electronics working).

3) Try and dump the contents of the PDD2 ROM and reverse engineer that too.


Darren Clark

Below is a snapshot of the major findings and updates to the assembly 
documentation


*(determine what code to run from dip switch settings)*
F04CPUL B;get the masked dip switch values from the stack
F04DCMP B0xD0;C is clear for 0xD0 and up
F04FBCC0xF081;Mode=operation jump to code
F051CMP B0x30;C is set for 0x30 and down
F053BCS0xF084;Mode=init jump to code - Fall over to FDC mode

*(mode = operation)*
FB4E_lookupTable_For_0xFAF8:DW251,147 ;operation command 0x0 
Create/Access a directory refrence

FB50DW253,2;operation command 0x1 Open a file
FB52DW252,212;operation command 0x2 Close a file
FB54DW254,112;operation command 0x3 Read data from a file
FB56DW254,192;operation command 0x4 Write data to a file
FB58DW252,115;operation command 0x5 Delete a file
FB5ADW251,122;operation command 0x6 Format a disk
FB5CDW251,114;operation command 0x7 Get drive status
FB5EDW251,102;operation command 0x8 Change to FDC mode

*(baud rate settings)*
FFB7_table_BAUD_Rates:DB1100B ;BAUD 9600
FFB8DB0100B;BAUD 19200
FFB9DB0100B;BAUD 19200
FFBADB1101B;BAUD 150
FFBBDB0111B;BAUD 300
FFBCDBB;BAUD 600
FFBDDB0011B;BAUD 1200
FFBEDB1011B;BAUD 2400
FFBFDB0010B;BAUD 4800
FFC0DB1100B;BAUD 9600
FFC1DB0100B;BAUD 19200
FFC2DB1000B;BAUD 38400
FFC3DBB;BAUD 76800
FFC4DB0010B;BAUD 4800
FFC5DB1100B;BAUD 9600
FFC6DB0100B;BAUD 19200

*(mode=FDC)*
FFC7_table_FDC_Commands:DB'F';F = FDC Format with verify
FFC8DW242,173
FFCADB'G';G = FDC Format without verify
FFCBDW242,170
FFCDDB'R';R = FDC Read one logical sector
FFCEDW241,253
FFD0DB'W';W = FDC Write one logical sector with verify
FFD1DW242,20
FFD3DB'X';X = FDC Write one logical sector without verify
FFD4DW242,17
FFD6DB'A';A = FDC Read ID section
FFD7DW242,81
FFD9DB'B';B = FDC Write ID section with verify
FFDADW242,107
FFDCDB'C';C = FDC Write ID section without verify
FFDDDW242,104
FFDFDB'S';S = FDC Search ID section
FFE0DW243,91
FFE2DB'D';D = FDC Check drive condition
FFE3DW243,200
FFE5DB'M';M = FDC Change modes
FFE6DW244,0

Re: [M100] PDD2 Question

[BiggRanger]

That's kind of what I thought, there may not even be any code in the 
firmware to look at the switches either then.
There's a PDD2 on eBay, I might try and get so I can do some reverse 
engineering.





On 8/8/2017 7:31 PM, John R. Hogerhuis wrote:

Not that you can see from the outside, anyway.

There's a little plastic cover where the DIP switches would be on a 
TPDD-1. If you take it off, you just see RF shielding.


Haven't had the whole unit apart though, who knows... might be DIP 
switches in there, or maybe an unpopulated area of the board.


On Tue, Aug 8, 2017 at 4:19 PM, > wrote:


Quick question, does the PDD2 have dip switches under it like the
PDD1?

The PDD2 Operation Manual (26-3814) does not mention dip switches,
but in the schematic in appendix B it shows an outlined dip switch.

I'm just wondering because it may be possible to put the drive
into INIT mode and use the same trick that I used to dump the PDD1
firmware for the PDD2.

[M100] PDD2 Question

[BiggRanger]

Quick question, does the PDD2 have dip switches under it like the PDD1?

The PDD2 Operation Manual (26-3814) does not mention dip switches, but 
in the schematic in appendix B it shows an outlined dip switch.


I'm just wondering because it may be possible to put the drive into INIT 
mode and use the same trick that I used to dump the PDD1 firmware for 
the PDD2.

Re: [M100] 3.5" Media

[BiggRanger]

Here is a copy I found on the internet looking for a PDD2 Software Manual.
The listing says PDD2 Software Manual, but it is the 26-3808 PDD1 
Software Manual (same as the one Kurt sent me).


http://www.classiccmp.org/cini/pdf/Tandy/PDD2%20Software%20Manual.pdf

http://www.classiccmp.org/cini/systems.htm



On 8/8/2017 4:24 PM, Mark J. Blair wrote:

On Aug 8, 2017, at 10:14 AM, Kurt McCullum  wrote:

The manual I have is 26-3808 which details the File mode and FDC mode of the 
TPDD1. I don't know the number for the TPDD2. 26-3814 is the standard user 
manual for the TPDD2 and I've got that. I'm not sure if Tandy ever published 
something for the TPDD2 like the 26-3808 manual. If they did, I'd love to get a 
hold of it.


I would also appreciate a copy of that manual. It sounds like it might be very 
useful for my MicroTPDD project.

Re: [M100] 3.5" Media

[BiggRanger]

Awesome!!! I've not seen this before and it answers quite a few 
questions I've had.


In the firmware, around address F0F0 there is, for lack of a better 
term, a switch/case block of code.

The cases are: F, G, R, W, X, A, B, C, S, D, and M
I've not seen references to these before in any documentation, but on 
page 17 of the PDF (33 of the manual), there they are!


This will help out immensely with documenting the decompiled source of 
the PDD1 firmware.


Now I just need to put the manual in order and do an OCR on it so it's 
searchable.


Thank you very much!



On 8/8/2017 2:18 PM, Kurt McCullum wrote:
Send


On Tuesday, August 8, 2017 11:13 AM, "biggran...@tds.net" 
 wrote:



Could you e-mail me your 26-3808 manual?
I have a 26-3808 Operation Manual for the PDD1, and the contents are 
very similar to the PDD2 Operation Manual 26-3814. So this would be new 
and useful.

Thanks in advance!


On 8/8/2017 1:14 PM, Kurt McCullum wrote:
The manual I have is 26-3808 which details the File mode and FDC mode of 
the TPDD1. I don't know the number for the TPDD2. 26-3814 is the 
standard user manual for the TPDD2 and I've got that. I'm not sure if 
Tandy ever published something for the TPDD2 like the 26-3808 manual. If 
they did, I'd love to get a hold of it.


Kurt


On Tuesday, August 8, 2017 9:53 AM, "biggran...@tds.net" 
<mailto:biggran...@tds.net>  
<mailto:biggran...@tds.net> wrote:



I have the following:

Tandy Portable Disk Dirve Operation Manual Cat. No. 26-3808
Tandy Portable Disk Dirve 2 Operation Manual Cat. No. 26-3814

If you want one of these I can e-mail them to you.
Do you have a service manual for the PDD? If so, could you e-mail it to 
me, I'd be very interested in it as I'm working on reverse engineering 
the firmware on the PDD1 (https://github.com/BiggRanger/Tandy_PDD).

Re: [M100] 3.5" Media

[BiggRanger]

Could you e-mail me your 26-3808 manual?
I have a 26-3808 Operation Manual for the PDD1, and the contents are 
very similar to the PDD2 Operation Manual 26-3814. So this would be new 
and useful.

Thanks in advance!


On 8/8/2017 1:14 PM, Kurt McCullum wrote:
The manual I have is 26-3808 which details the File mode and FDC mode 
of the TPDD1. I don't know the number for the TPDD2. 26-3814 is the 
standard user manual for the TPDD2 and I've got that. I'm not sure if 
Tandy ever published something for the TPDD2 like the 26-3808 manual. 
If they did, I'd love to get a hold of it.


Kurt


On Tuesday, August 8, 2017 9:53 AM, "biggran...@tds.net" 
 wrote:



I have the following:

Tandy Portable Disk Dirve Operation Manual Cat. No. 26-3808
Tandy Portable Disk Dirve 2 Operation Manual Cat. No. 26-3814

If you want one of these I can e-mail them to you.
Do you have a service manual for the PDD? If so, could you e-mail it 
to me, I'd be very interested in it as I'm working on reverse 
engineering the firmware on the PDD1 
(https://github.com/BiggRanger/Tandy_PDD).





On 8/8/2017 10:59 AM, Kurt McCullum wrote:

Does a PDF exists of "Tandy Disk Drive ll Service Manual"?

I have the one for the TPDD1 but not the 2.


On Tuesday, August 8, 2017 7:53 AM, John Gardner  
<mailto:gof...@gmail.com> wrote:



So flipping a  3.5" floppy  work,  if the housing for the disk

would let you do that.  Hmm...

And the reason HD disks are unreliable is that the signal returned

by the media when reading the disk is (presumably) too high?

Interesting...

...


On 8/8/17, biggran...@tds.net <mailto:biggran...@tds.net> 
mailto:biggran...@tds.net>> wrote:

> The specifications in the PDF for the PDD1 and PDD2 says the following:
> PDD1 (26-3808):
> Disk
>  Number of surfaces 1
>  Number of Memory Blocks
>  Total number of tracks  40
>  Total number of hard sectors80
>
>
> PDD2 (26-3814):
> Disk
>  Number of surfaces 1
>  Number of Memory Blocks
>  Total number of tracks  80
>  Total number of hard sectors160
>
>
>
>
>
>
> On 8/8/2017 12:39 AM, Gary Weber wrote:
>> > Double-sided doesn't hurt anything of course, although it's too 
bad you

>> > can't make
>> 3.5" flippy disks as easily as you could 5.25"!
>>
>> After rereading this I wanted to make one critical point. Remember,
>> if yours is truly the TPDD2, it already is double sided. It formats
>> the drive as 100K per side (200K total).  You use the "Bank" feature
>> in TS-DOS to switch between which side you're accessing.  So, no need
>> to be fantasizing about flippy-floppies.  ;-)
>>
>> It was the original TPDD that is only 100K single sided.
>>
>> Gary
>>
>>
>> On Mon, Aug 7, 2017 at 8:04 PM, Kurt McCullum 
mailto:kurt.mccul...@att.net>

>> <mailto:kurt.mccul...@att.net <mailto:kurt.mccul...@att.net>>> wrote:
>>
>>Thanks Brian & Garry,
>>
>>I suspected that to be the case but when my HD disk appeared to
>>work I thought I would ask.
>>
>>Kurt
>>
>>*From:*M100 [mailto:m100-boun...@lists.bitchin100.com 
<mailto:m100-boun...@lists.bitchin100.com>
>><mailto:m100-boun...@lists.bitchin100.com 
<mailto:m100-boun...@lists.bitchin100.com>>] *On Behalf Of *Brian

>> White
>>*Sent:* Monday, August 07, 2017 4:41 PM
>>*To:* m...@bitchin100.com <mailto:m...@bitchin100.com> 
<mailto:m...@bitchin100.com <mailto:m...@bitchin100.com>>

>>*Subject:* Re: [M100] 3.5" Media
>>
>>I wasn't using these when they were current, but... No question
>>double density. Aside from the dates when these things were sold,
>>or the fact that the actual formatting is far less than double
>>density, or the fact that the original utility disk that came with
>>it is double density, which are each solid points on their own...
>>
>>The manual for PDD-2 says to use cat 26-415 or 26-416,
>>
>>and those catalog numbers are not only double density but actually
>>single sided.
>>
>>Double-sided doesn't hurt anything of course, although it's too
>>bad you can't make 3.5" flippy disks as easily as you could 5.25"!
>>
>>But trying to use SD/DD read/write head signal strength on HD
>>media is going to either not work at all, or work very
>>poorly/unreliably, or worse, *appear to work but be corrupt*.
>>Because the HD media is more sensitive than the ol

Re: [M100] 3.5" Media

[BiggRanger]

I have the following:

Tandy Portable Disk Dirve Operation Manual Cat. No. 26-3808
Tandy Portable Disk Dirve 2 Operation Manual Cat. No. 26-3814

If you want one of these I can e-mail them to you.
Do you have a service manual for the PDD? If so, could you e-mail it to 
me, I'd be very interested in it as I'm working on reverse engineering 
the firmware on the PDD1 (https://github.com/BiggRanger/Tandy_PDD).





On 8/8/2017 10:59 AM, Kurt McCullum wrote:

Does a PDF exists of "Tandy Disk Drive ll Service Manual"?

I have the one for the TPDD1 but not the 2.


On Tuesday, August 8, 2017 7:53 AM, John Gardner  wrote:


So flipping a  3.5"  floppy  work,  if the housing for the disk

would let you do that.  Hmm...

And the reason HD disks are unreliable is that the signal returned

by the media when reading the disk is (presumably) too high?

Interesting...

...


On 8/8/17, biggran...@tds.net <mailto:biggran...@tds.net> 
mailto:biggran...@tds.net>> wrote:

> The specifications in the PDF for the PDD1 and PDD2 says the following:
> PDD1 (26-3808):
> Disk
>  Number of surfaces1
>  Number of Memory Blocks
>  Total number of tracks  40
>  Total number of hard sectors80
>
>
> PDD2 (26-3814):
> Disk
>  Number of surfaces1
>  Number of Memory Blocks
>  Total number of tracks  80
>  Total number of hard sectors160
>
>
>
>
>
>
> On 8/8/2017 12:39 AM, Gary Weber wrote:
>> > Double-sided doesn't hurt anything of course, although it's too 
bad you

>> > can't make
>> 3.5" flippy disks as easily as you could 5.25"!
>>
>> After rereading this I wanted to make one critical point.  Remember,
>> if yours is truly the TPDD2, it already is double sided.  It formats
>> the drive as 100K per side (200K total).  You use the "Bank" feature
>> in TS-DOS to switch between which side you're accessing.  So, no need
>> to be fantasizing about flippy-floppies.  ;-)
>>
>> It was the original TPDD that is only 100K single sided.
>>
>> Gary
>>
>>
>> On Mon, Aug 7, 2017 at 8:04 PM, Kurt McCullum 
mailto:kurt.mccul...@att.net>

>> <mailto:kurt.mccul...@att.net <mailto:kurt.mccul...@att.net>>> wrote:
>>
>>Thanks Brian & Garry,
>>
>>I suspected that to be the case but when my HD disk appeared to
>>work I thought I would ask.
>>
>>Kurt
>>
>>*From:*M100 [mailto:m100-boun...@lists.bitchin100.com 
<mailto:m100-boun...@lists.bitchin100.com>
>><mailto:m100-boun...@lists.bitchin100.com 
<mailto:m100-boun...@lists.bitchin100.com>>] *On Behalf Of *Brian

>> White
>>*Sent:* Monday, August 07, 2017 4:41 PM
>>*To:* m...@bitchin100.com <mailto:m...@bitchin100.com> 
<mailto:m...@bitchin100.com <mailto:m...@bitchin100.com>>

>>*Subject:* Re: [M100] 3.5" Media
>>
>>I wasn't using these when they were current, but... No question
>>double density. Aside from the dates when these things were sold,
>>or the fact that the actual formatting is far less than double
>>density, or the fact that the original utility disk that came with
>>it is double density, which are each solid points on their own...
>>
>>The manual for PDD-2 says to use cat 26-415 or 26-416,
>>
>>and those catalog numbers are not only double density but actually
>>single sided.
>>
>>Double-sided doesn't hurt anything of course, although it's too
>>bad you can't make 3.5" flippy disks as easily as you could 5.25"!
>>
>>But trying to use SD/DD read/write head signal strength on HD
>>media is going to either not work at all, or work very
>>poorly/unreliably, or worse, *appear to work but be corrupt*.
>>Because the HD media is more sensitive than the older media, and
>>operates at lower signal strengths than the older media. An SD or
>>DD drive write signal is stronger to match the weaker media it was
>>meant for. So in effect you are over-driving the newer media. In
>>plain audio you can tell when that's happening because you
>>actually hear the distortion like a ripped speaker. As data, you
>>can't hear it directly or tell it's happening, which makes it more
>>dangerous. They should have made HD disks so they don't even fit
>>in older drives. Make them slightly longer maybe, so that old
>>disks could still fit in new drive, but new disks

Re: [M100] 3.5" Media

[BiggRanger]

Looking at Wikipedia, the 3.5" DD format supports both 40 tracks and 80 
tracks.

https://en.wikipedia.org/wiki/List_of_floppy_disk_formats#Physical_composition

And yes there is a difference in the magnetic media for DD and HD too, 
using a DD head and the write currents for a DD head would not work well 
with HD media.

https://en.wikipedia.org/wiki/Coercivity





On 8/8/2017 10:53 AM, John Gardner wrote:

So flipping a  3.5"  floppy  work,  if the housing for the disk

would let you do that.  Hmm...

And the reason HD disks are unreliable is that the signal returned

by the media when reading the disk is (presumably) too high?

Interesting...

  ...


On 8/8/17, biggran...@tds.net  wrote:

The specifications in the PDF for the PDD1 and PDD2 says the following:
PDD1 (26-3808):
Disk
  Number of surfaces1
  Number of Memory Blocks
  Total number of tracks   40
  Total number of hard sectors80


PDD2 (26-3814):
Disk
  Number of surfaces1
  Number of Memory Blocks
  Total number of tracks   80
  Total number of hard sectors160






On 8/8/2017 12:39 AM, Gary Weber wrote:

Double-sided doesn't hurt anything of course, although it's too bad you
can't make

3.5" flippy disks as easily as you could 5.25"!

After rereading this I wanted to make one critical point.   Remember,
if yours is truly the TPDD2, it already is double sided.  It formats
the drive as 100K per side (200K total).  You use the "Bank" feature
in TS-DOS to switch between which side you're accessing.   So, no need
to be fantasizing about flippy-floppies.  ;-)

It was the original TPDD that is only 100K single sided.

Gary


On Mon, Aug 7, 2017 at 8:04 PM, Kurt McCullum mailto:kurt.mccul...@att.net>> wrote:

 Thanks Brian & Garry,

 I suspected that to be the case but when my HD disk appeared to
 work I thought I would ask.

 Kurt

 *From:*M100 [mailto:m100-boun...@lists.bitchin100.com
 ] *On Behalf Of *Brian
White
 *Sent:* Monday, August 07, 2017 4:41 PM
 *To:* m...@bitchin100.com 
 *Subject:* Re: [M100] 3.5" Media

 I wasn't using these when they were current, but... No question
 double density. Aside from the dates when these things were sold,
 or the fact that the actual formatting is far less than double
 density, or the fact that the original utility disk that came with
 it is double density, which are each solid points on their own...

 The manual for PDD-2 says to use cat 26-415 or 26-416,

 and those catalog numbers are not only double density but actually
 single sided.

 Double-sided doesn't hurt anything of course, although it's too
 bad you can't make 3.5" flippy disks as easily as you could 5.25"!

 But trying to use SD/DD read/write head signal strength on HD
 media is going to either not work at all, or work very
 poorly/unreliably, or worse, *appear to work but be corrupt*.
 Because the HD media is more sensitive than the older media, and
 operates at lower signal strengths than the older media. An SD or
 DD drive write signal is stronger to match the weaker media it was
 meant for. So in effect you are over-driving the newer media. In
 plain audio you can tell when that's happening because you
 actually hear the distortion like a ripped speaker. As data, you
 can't hear it directly or tell it's happening, which makes it more
 dangerous. They should have made HD disks so they don't even fit
 in older drives. Make them slightly longer maybe, so that old
 disks could still fit in new drive, but new disks couldn't fit in
 old drives. The guy who sent me my copy of the utility disk sent
 one of each type, and the HD copy actually works, which is what I
 mean by "dangerous", because, going by that, you would conclude
 "It works, so, it works."

 Jump to page 6

http://www.classiccmp.org/cini/pdf/Tandy/Portable%20Disk%20Drive%202%20Operation%20Manual.pdf



 Jump to page 41

http://www.colorcomputerarchive.com/coco/Documents/Radio%20Shack%20Catalogs/Tandy%20Computer%20Catalog%20and%20Software%20Reference%20Guide%20(1988)(Tandy).pdf



 That catalog doesn't say DD explicitly, but it does say others are
 HD and 1.44M explicitly, which makes everything else not-HD by
 omission.

 I assume that somewhere a more authoritative reference on the
 catalog numbers would show that more explicitly.

 --

 bkw

 On Mon, Aug 7, 2017 at 6:41 PM, Gary Weber mailto:g...@web8201.com>> wrote:

 Double Density fo

Re: [M100] 3.5" Media

[BiggRanger]

The specifications in the PDF for the PDD1 and PDD2 says the following:
PDD1 (26-3808):
Disk
Number of surfaces1
Number of Memory Blocks
Total number of tracks   40
Total number of hard sectors80


PDD2 (26-3814):
Disk
Number of surfaces1
Number of Memory Blocks
Total number of tracks   80
Total number of hard sectors160






On 8/8/2017 12:39 AM, Gary Weber wrote:
> Double-sided doesn't hurt anything of course, although it's too bad you can't make 
3.5" flippy disks as easily as you could 5.25"!


After rereading this I wanted to make one critical point.   Remember, 
if yours is truly the TPDD2, it already is double sided.  It formats 
the drive as 100K per side (200K total).  You use the "Bank" feature 
in TS-DOS to switch between which side you're accessing.   So, no need 
to be fantasizing about flippy-floppies.  ;-)


It was the original TPDD that is only 100K single sided.

Gary


On Mon, Aug 7, 2017 at 8:04 PM, Kurt McCullum > wrote:


Thanks Brian & Garry,

I suspected that to be the case but when my HD disk appeared to
work I thought I would ask.

Kurt

*From:*M100 [mailto:m100-boun...@lists.bitchin100.com
] *On Behalf Of *Brian White
*Sent:* Monday, August 07, 2017 4:41 PM
*To:* m...@bitchin100.com 
*Subject:* Re: [M100] 3.5" Media

I wasn't using these when they were current, but... No question
double density. Aside from the dates when these things were sold,
or the fact that the actual formatting is far less than double
density, or the fact that the original utility disk that came with
it is double density, which are each solid points on their own...

The manual for PDD-2 says to use cat 26-415 or 26-416,

and those catalog numbers are not only double density but actually
single sided.

Double-sided doesn't hurt anything of course, although it's too
bad you can't make 3.5" flippy disks as easily as you could 5.25"!

But trying to use SD/DD read/write head signal strength on HD
media is going to either not work at all, or work very
poorly/unreliably, or worse, *appear to work but be corrupt*.
Because the HD media is more sensitive than the older media, and
operates at lower signal strengths than the older media. An SD or
DD drive write signal is stronger to match the weaker media it was
meant for. So in effect you are over-driving the newer media. In
plain audio you can tell when that's happening because you
actually hear the distortion like a ripped speaker. As data, you
can't hear it directly or tell it's happening, which makes it more
dangerous. They should have made HD disks so they don't even fit
in older drives. Make them slightly longer maybe, so that old
disks could still fit in new drive, but new disks couldn't fit in
old drives. The guy who sent me my copy of the utility disk sent
one of each type, and the HD copy actually works, which is what I
mean by "dangerous", because, going by that, you would conclude
"It works, so, it works."

Jump to page 6

http://www.classiccmp.org/cini/pdf/Tandy/Portable%20Disk%20Drive%202%20Operation%20Manual.pdf



Jump to page 41

http://www.colorcomputerarchive.com/coco/Documents/Radio%20Shack%20Catalogs/Tandy%20Computer%20Catalog%20and%20Software%20Reference%20Guide%20(1988)(Tandy).pdf



That catalog doesn't say DD explicitly, but it does say others are
HD and 1.44M explicitly, which makes everything else not-HD by
omission.

I assume that somewhere a more authoritative reference on the
catalog numbers would show that more explicitly.

-- 


bkw

On Mon, Aug 7, 2017 at 6:41 PM, Gary Weber mailto:g...@web8201.com>> wrote:

Double Density for sure.  A long time ago, I had attempted to
format a
high density disk on a TPDD2 but it gave an error.   I've
always had
to use double density disks.


On Mon, Aug 7, 2017 at 2:33 PM, Kurt McCullum
mailto:kurt.mccul...@att.net>> wrote:
> For those who have used a TPDD2 in the past, I have a
question about media
> type. Do these drives prefer double density (720k) or high
density (1.44mb)
> media? I've tested with both from by using recycled media
from years gone by
> and both seem to work. My primary interest in the drive is
to see if I can
> improve mComm but as I'm testing, I'd like to actually use

Re: [M100] TPDD2 Belt

[BiggRanger]

Looks like a perfect replacement to me. The one I used was a bit longer 
at 8.6" (vs 8.5") and narrower at 0.125" (vs 0.150"), and it works just 
fine.


Darren



On 7/31/2017 10:54 AM, Kurt McCullum wrote:
I wasn't intending to but a TPDD2 but one came with an auction I won. 
So I figured I'd restore it.


I've looked through the archives of the mailing list and I think I 
have found the right belt but wanted to ask for verification. Will 
this belt work?


http://www.mcmelectronics.com/product/42-3215


Kurt

Re: [M100] Molex part number

[BiggRanger]

Wow, those came out great!

On 7/20/2017 10:39 PM, Brian White wrote:

One of my Shapeways orders came in.

This is the cheapest option Shapeways offers, and it turns out the 
cheapest lowest quality option (from Shapeways) is good enough.


The white one is the "White Strong Flexible", with no extra finishing 
options added.


The black one is the same thing just black.

The print is accurate enough that everything fits perfect, and the 
material is strong enough that it doesn't break when you install or 
remove the module from the socket.


I have a couple more still on the way, in more expensive material and 
quality options.


This is cool but not really that useful except for Model 600.

This is great for 600, because 600 takes a standard 27C256 pinout. 
Just slap a 27C256 in the carrier and you have a model 600 option rom.


But 100, 102, and 200 don't have a normal pinout, so the only way this 
could be used is if you had some kind of pcb in the carrier instead of 
a normal dip28 chip.


Hm, that might be a neat idea after all. You could pack a rex or a 
figtronix into one instead of using extraction ribbons and pieces of 
cardstock spacers. We could modify the cad file pretty easily to make 
a version customized to fit a REX exactly. Then you get the key slots 
so you can't plug the rom in backwards, and it's just a cleaner tidier 
little module than one with ribbon and cardboard.


Pretty cool!

https://photos.app.goo.gl/IHQCxST40Cp72NLj1

https://drive.google.com/folderview?id=0Bys6eLbSbYyhTFItVWZjU2xJd0E

--
bkw

Re: [M100] Off-the-Shelf AC Adapter for M100?

[BiggRanger]

I ordered a couple of these from Digkey.com for both my Tandy 200 and 
Tandy PDD.


https://www.digikey.com/products/en/power-supplies-external-internal-off-board/ac-dc-desktop-wall-adapters/130?k=EPS060100&k=&pkeyword=EPS060100&pv52=6&mnonly=0&ColumnSort=0&page=1&quantity=0&ptm=0&fid=0&pageSize=25

They are a regulated 6V switching power supply vs just a transformer 
with a bridge rectifier and capacitor (unregulated).


Darren Clark


On 7/15/2017 2:56 AM, Roger Mullins wrote:
I searched the list archive but only turned up one mention of a USB 
cable and that link is broken. Is there a readily available modern 
replacement for the 26-3804? Thought I might go ahead and pick up a 
wall charger since I'm going to be replacing the NiCd, but the used  
26-3804s that I'm finding are going for upwards of $50.


Roger



Sent from my T-Mobile 4G LTE Device

Re: [M100] Molex part number

[BiggRanger]

Looks like a part that can be 3D printed.



On 7/11/2017 4:30 PM, Mike Stein wrote:
I'm pretty sure they're obsolete, but I think this is what you're 
looking for:

http://www.allpartsdata.com/partinfo.php?q=50-57-5284&MFG=MOLEX+INC
FWIW I believe Brian White managed to find a quantity of the sockets; 
I don't think he has any of the carriers but there are alternative 
solutions available.

m

- Original Message -
*From:* Kurt McCullum 
*To:* m...@bitchin100.com 
*Sent:* Tuesday, July 11, 2017 3:17 PM
*Subject:* [M100] Molex part number

Does anyone happen to know the Molex part number that the OptRom
uses for inserts? I'm reffering to the part that the PROM wraps
around and is inserted into the OpeRom socket.

Kurt

Re: [M100] It's Alive!

[BiggRanger]

Make a GitHub account and share it?

BTW, saw your post on Reddit!


On 7/8/2017 9:02 PM, Jason Benson wrote:
I finished my version of Conway's Game of Life for M100 basic. It runs 
pretty slow, but without errors. I'm sure there's a lot of stuff I can 
do to optimize it but I'm super happy just to see it running. 
Currently it only exists in my M100's memory, but when I get it 
transferred (or just retyped on a PC) is there anywhere I should share 
it for others to peruse?

-Jason

Re: [M100] Oh no - think my internal nicad finally given up the ghost

[BiggRanger]

No, the best thing to do is to get rid of the old one before it leaks on 
the printed circuit board, and replace it with a new one (some soldering 
is involved).


The AA batteries will charge the NiCAD, as will the external charger. If 
the NiCAD isn't holding a charge anymore, it's time to replace it.



On 5/28/2017 9:48 PM, Daryn Hanright wrote:

Hey

Went to turn on my Tandy 102 yesterday. At first the screen was 
totally gabbled in different ways upon switching on. Now I just get 
nothing.


One way too fix this is too get hold of the DC Adapter huh? Charge it 
overnight?


cheers
Daryn

Re: [M100] Youtube of someone using an acoustic modem cup with m100 and cell phone to dial a BBS

[BiggRanger]

I think for 110 and 300 BAUD it would be fine, where audio 
frequency-shift keying was used. But any of the higher BAUD rates that 
use PSK or QAM wouldn't make it past the audio/data compression used in 
cell phones.



On 5/25/2017 12:50 PM, Andrew Roach wrote:

I thought cell phones couldn't be used for BBS connections?

If that works, I very much want to explore it more.

On Thu, May 25, 2017 at 11:36 AM John R. Hogerhuis > wrote:


Interesting. I would have given that a low probability of working.
Well if that works you'd think a direct connect cable would be
even better.

Opens up a whole new possibility for remote usage of Model Ts.

Does anyone know what would be needed for a direct to headphone
jack connection?


-- John.

Re: [M100] Brother M-1009 dot matrix printer, dip switch settings

[BiggRanger]

Excellent! Thanks for the tip, just asked the seller.



On 3/17/2017 1:34 PM, eddie edwards wrote:


there is a person on ebay selling a similar printer, and they have the 
manual. Perhaps you could talk to them?


pindi...@gmail.com

Re: [M100] TPDD cable

[BiggRanger]

I made one using that info for my PDD-1, it will also work on the PDD-2 
since the serial IO circuit is almost exactly the same on both drives, 
and the pinout is the same.



On 3/16/2017 9:12 PM, hargarg trurthsr wrote:

Has anyone actually made this cable  following Marty Goodman's diagram
?  Does it work on both TPDD and TPDD 2?

Re: [M100] Brother M-1009 dot matrix printer, dip switch settings

[BiggRanger]

I looked at that already, the Brother M1009 has both a Centronix port 
and a serial port, as well as 2 sets of 8 position dip switches. The 
NLQ401 only has one 8 position dip switch, only a Centronix port, and 
different firmware, so the dip switch positions do not match what I have.
The printer and PCB is the same though, just the NLQ410 has a few less 
components and the firmware is changed.


On 3/15/2017 2:50 AM, Brian White wrote:

http://www.cpcwiki.eu/index.php/NLQ401#Brother_M1009

Looks like you should be able to deduce from the german manual for 
another printer that has the same guts.


--
bkw

On Mar 14, 2017 11:35 PM, > wrote:


I have a Brother M-1009 dot matrix printer for my Tandy 200, but
no manual for it. I've tried my best google-fu, but can't dig up
anything but long dad links. Would anybody have any info on the
dip switch settings for this printer?

Thanks!

Darren

[M100] Brother M-1009 dot matrix printer, dip switch settings

[BiggRanger]

I have a Brother M-1009 dot matrix printer for my Tandy 200, but no 
manual for it. I've tried my best google-fu, but can't dig up anything 
but long dad links. Would anybody have any info on the dip switch 
settings for this printer?


Thanks!

Darren

Re: [M100] Tandy PDD firmware info

[BiggRanger]

Hello Daryl,
Thanks! And you were right, it was a very easy path to inject some 
code into in order to get the CPU to dump its protected ROM contents. If 
I can get a hold of a PDD2 (and some free time) I'd like to see how 
different the ROM is on that.


Darren


On 3/5/2017 11:26 PM, Daryl Tester wrote:

Thanks for your work on this (I was the guy who wrote the original Wiki
article, but no access to a TPDD1, so it was all conjecture).

On Sat, 4 Mar 2017 16:40:21 -0500, biggran...@tds.net wrote:

Hello all,
I haven't done much with reverse engineering work the PDD1
firmware in a while, I've been too busy with work again. But I did
drop everything I have on GitHub if you want to have a look. I've
given names to the different registers, and some subroutines in the
assembly file. The Hitachi 6301 uses the same opcodes as the Motorola
6800, and is fairly easy to follow.

https://github.com/BiggRanger/Tandy_PDD

Darren

[M100] Tandy PDD firmware info

[BiggRanger]

Hello all,
I haven't done much with reverse engineering work the PDD1 firmware 
in a while, I've been too busy with work again. But I did drop 
everything I have on GitHub if you want to have a look. I've given names 
to the different registers, and some subroutines in the assembly file. 
The Hitachi 6301 uses the same opcodes as the Motorola 6800, and is 
fairly easy to follow.


https://github.com/BiggRanger/Tandy_PDD

Darren

Re: [M100] Belt Repair/Replacement Info -> CCR-81 CCR-82 PDD

[BiggRanger]

The FBS8.6 is very close to the FRW-8.5. When I took my PDD apart to fix 
it, there was almost nothing left of the original belt, it turned into a 
black goo. So I measured the pulleys and subtracted 5% from that length, 
and took a best guess at the width. So far it's running great, it's 
reading and writing disks just fine, even 20+ year old disks. Same goes 
for the tape recorders, the original stuff was just too far gone to 
properly measure.



Here are more specs for the belts:

*FRW 8.5**(from the archive)
**Thickness: 0.024 Inches.**
**Width: 0.150 Inches*

FBS8.6 Flat Belt, Small 8.6 Inch:
.025 Inch / .6mm Thick
.125 Inch / 3mm Wide

FBS10.2 Flat Belt, Small 10.2 Inch:
.025 Inch / .6mm Thick
.125 Inch / 3mm Wide

SBS8.0 Square Belt, Small 8.0 Inch
.046 Inch / 1.2mm Thick and Wide

SBS5.1 Square Belt, Small 5.1 Inch
.046 Inch / 1.2mm Thick and Wide

SBS3.0 Square Belt, Small 3.0 Inch (I think this one is actually too 
small, 3.2" would be better)

.046 Inch / 1.2mm Thick and Wide



***
*On 12/1/2016 12:52 AM, Brian White wrote:
For PDD-2 I used "FRW-8.5" from a random ebay seller. It's a generic 
size code that several sellers list, so you just add "belt", to google 
"FRW-8.5 belt",  and buy from whoever you like. I found the number in 
a old archived forum or newsgroup post, a text file in the 
club100/bitchin100 archives.


I also tried a few other sizes in the same range and they worked, but 
this did seem to be best. But I don't think I found another size as 
close to 8.5 as 8.6, so I believe that 8.6 is perfect too, though I 
don't know how the thickness, width, and elasticity compares. I'll 
probably get one of these you found just to see. Thanks.



On Thu, Dec 1, 2016 at 12:15 AM, > wrote:


Just a little information for the list, the belts in my 2 tape
recorders and portable disk drive were all shot so I had to
replace them.

The belts are from one web store http://www.turntableneedles.com/
 all 5 belts were $30.00 with
shipping.

*CCR-81 Computer Cassette Recorder:*
Main Belt: FBS10.2 Flat Belt, Small 10.2 Inch
Counter Belt: ?? (Didn't replace it buried too deep).

*CCR-82 Computer Cassette Recorder:*
Main Belt: SBS8.0 Square Belt, Small 8.0 Inch
Take-up Belt: SBS5.1 Square Belt, Small 5.1 Inch
Counter Belt: SBS3.0 Square Belt, Small 3.0 Inch (I think this one
is actually too small, 3.2" would be better)

*PDD Portable Disk Drive:*
Main Belt: FBS8.6 Flat Belt, Small 8.6 Inch

I found the service manual for the CCR-82 here:
http://www.colorcomputerarchive.com/coco/Documents/Manuals/Hardware/

But, couldn't find a service manual for the CCR-81 or PDD, but
they were simple enough to take apart and fix the belts.

After about an hour of taking apart, cleaning, belt replacing, and
putting back together again everything is working perfectly again!




Darren Clark

Re: [M100] PDD - ROM Dump

[BiggRanger]

I'm working on the disassembly now. It's all in ASM code, and I've 
figured out a few subroutines already, I'm pretty sure I've even found 
the code that drives the stepper motor too. I'm in the process of 
finding out what some of the subroutines do and give them names like these:


   ;subroutines
   code0xF9AD_sub_ClearMemory(X=StartAddress_D=Length)
   code0xF9B6_sub_Delay_Units=14
   code0xF9BA_sub_Delay_Units=1
   code0xF9BC_sub_Delay_Units=ACCB
   code0xF9BE_sub_Delay_Private_Loop


Once I give the subs names I run the BIN file through the disassembler 
again and it assigns the subroutine names to the code calls which makes 
figuring out other things easier. So now that the code is assigned some 
names, it makes reading it easier:


   ;sub to clear memory register X contains the start address, register
   D is the length
   F9AD  _sub_ClearMemory(X=StartAddress_D=Length):
   F9AD : clr$00,x
   F9AF : inx
   F9B0 : subd#$0001
   F9B3 : bne_sub_ClearMemory(X=StartAddress_D=Length)
   F9B5 : rts


   ;sub to create a delay, multiple entry points (14 units, 1 unit, or
   number of units based on value from register B)
   F9B6 _sub_Delay_Units=14:
   F9B6 : ldab#$14
   F9B8 : bra_sub_Delay_Units=ACCB
   F9BA _sub_Delay_Units=1:
   F9BA :  ldab#$01
   F9BC _sub_Delay_Units=ACCB:
   F9BC : ldaa#$F5
   F9BE _sub_Delay_Loop(onlyLocal):
   F9BE : deca
   F9BF : nop
   F9C0 : bne_sub_Delay_Loop(onlyLocal)
   F9C2 : decb
   F9C3 : bne_sub_Delay_Units=ACCB
   F9C5 : rts

And by giving these subs names each call to these subs gets named in the 
code which makes other parts of the disassembled code easier to read:


   ;read SCI into A, read RxData into A, delay, then clear A??? and
   store it in _INT_RAM 009E and 00B0???
   FA19 : ldaa_register_SCI_TxRxControlAndStatus
   FA1B : ldaa_register_SCI_RxData
   FA1D : bsr_sub_Delay_Units=1
   FA1F : clra
   FA20 : staa X009E
   FA22 : staa X00B0

In the above code I put comments on what is happening, stuff with "???" 
means I need to look at it later because it's doing something I don't 
understand why yet. But this code example, it's probably just clearing 
out the RS232 receive register to make it ready for something. I'll have 
a better idea later.


But, this is just the tip of the iceberg so far. Printed out in Courier 
New size 8 font, this code takes up 33 pages or letter paper. I've 
identified 7 different lookup tables (see some tables below), and 2 
really big switch/case blocks. This firmware takes up almost all of the 
4096 bytes of ROM available on the HD63A01V1. Actually it looks like 
there are only 6 bytes in the ROM that are unused; FFE8 to FFED.
Now since the PDD1 takes up most of the ROM, I fully expect the PDD2 to 
be a completely different monster. Because of the differences between 
the 2 models, something had to be removed from the PDD1 source to make 
room for the changes in the PDD2, I'm just hoping the S-REC command 
stuff is still there otherwise the PDD2 will require a different hack to 
get it to spill its ROM.


   ;table for F021 - variable lookup table
   byte0xFFB7_lookupTable_For_0xF0210x10

   ;table for F498 - variable lookup table
   byte0xF4A8_lookupTable_For_0xF4980x07

   ;table for F75D - variable lookup table
   byte0xF8AC_lookupTable_For_0xF75D0x0E

   ;tables for F9A5 and F9A9 - variable lookup table (stepper motor stuff?)
   byte0xF9A5_lookupTable_For_0xF9520x04
   byte0xF9A9_lookupTable_For_0xF9900x04



Darren Clark


On 11/30/2016 1:53 AM, John R. Hogerhuis wrote:
Added to the end of the page 
http://bitchin100.com/wiki/index.php?title=TPDD_Design_Notes


Thanks again!

Now we just need to get it all disassembled.

I expect there are some hidden gems in there... undocumented commands, 
stuff like that.


The TPDD-2 is different. As far as I know we don't know if there's a 
way to get it to execute code.


-- John.

[M100] Belt Repair/Replacement Info -> CCR-81 CCR-82 PDD

[BiggRanger]

Just a little information for the list, the belts in my 2 tape recorders 
and portable disk drive were all shot so I had to replace them.


The belts are from one web store http://www.turntableneedles.com/ all 5 
belts were $30.00 with shipping.


*CCR-81 Computer Cassette Recorder:*
Main Belt: FBS10.2 Flat Belt, Small 10.2 Inch
Counter Belt: ?? (Didn't replace it buried too deep).

*CCR-82 Computer Cassette Recorder:*
Main Belt: SBS8.0 Square Belt, Small 8.0 Inch
Take-up Belt: SBS5.1 Square Belt, Small 5.1 Inch
Counter Belt: SBS3.0 Square Belt, Small 3.0 Inch (I think this one is 
actually too small, 3.2" would be better)


*PDD Portable Disk Drive:*
Main Belt: FBS8.6 Flat Belt, Small 8.6 Inch

I found the service manual for the CCR-82 here: 
http://www.colorcomputerarchive.com/coco/Documents/Manuals/Hardware/
But, couldn't find a service manual for the CCR-81 or PDD, but they were 
simple enough to take apart and fix the belts.


After about an hour of taking apart, cleaning, belt replacing, and 
putting back together again everything is working perfectly again!





Darren Clark

Re: [M100] PDD - ROM Dump

[BiggRanger]

I do not have a PDD2 to analyze, but looking at the manual for the PDD2, 
specifically the schematic, it's very similar to the PDD1. The two major 
differences between the two, from a protocol and functionality 
standpoint, seems to be:


1) The bank switching and the PDD2 handling 80 tracks instead of 40. I 
would guess that the firmware is mostly the same between the two units 
with only some small changes for the bank switching. The meat and 
potatoes is the same, 2560 bytes per track, 1280 bytes per sector, 2 
sectors per track.


2) How the file management software is loaded; the PDD1 we send commands 
to the drive to start it up and start sending data to the computer (at 
9600 BAUD), the PDD2 is always set to 19.2K BAUD and may be checking the 
state of the DSR, DTR, RTS, CTS lines at startup to determine if it 
should start reading the disk and sending data to the computer.


If the ability to send S-REC commands to the drive has been removed, 
then the vector of attack I used for the PDD1 will not work, also the 
"magical 8515 address" may be different on the PDD2, but this can be 
discovered. I would first test if the firmware on the drive will accept 
S-REC commands, and with the PDD2 this would be at 19.2K BAUD.


But let's take this one step at a time. I sent John, the site 
administrator, the firmware dump and BIN file so they can be put on the 
web page and the notes on the Wiki. I'm not very proficient with the 
Hitachi 6301 yet, but am learning fast, and started disassembling the 
firmware with a tool called DASMx V1.40. This is going to be a major 
undertaking, although 4K seems like a small number, this is ~2000 
commands, ~500 variable addresses, no variable names, and no comments 
(see below for a snippet). Once we have a good understanding of the 
firmware on the PDD1 and the functionality of the ASIC, then we should 
move to the PDD2. Unless someone wants to send me a working PDD2 to work 
experiment with (this is the less preferred route though since I do not 
want to responsible for accidentally wrecking someones good PDD2), or if 
someone has some non-working PDD2's they don't mind parting with I can 
work with those.


And about that ASIC, it may be pretty simple. It seems to only have 4 
addresses assigned to it 0x4000-0x4003, and mostly acts as glue logic 
for the RAM (address latching). It also controls the spindle motor 
(possibly acting as a PWM driver), head position motor (stepper motor), 
and simple I/O.


__
Here is a snippet so far:
F000 : 0F" "sei
F001 : 8E 87 FF"   "lds#$87FF
F004 : 86 FC"  "ldaa#$FC
F006 : 97 00"  "staa _sym_PORT1DataDirectionRegister
F008 : 86 34" 4"ldaa#$34
F00A : 97 02"  "staa_sym_PORT1DataReg
F00C : 86 FF"  "ldaa#$FF
F00E : 97 04"  "staa _sym_PORT3DataDirectionRegister
F010 : 97 05"  "staa _sym_PORT4DataDirectionRegister
F012 : 86 A0"  "ldaa#$A0
F014 : B7 40 00" @ "staa_sym_CPLD_4000
F017 : F6 40 01" @ "ldab_sym_CPLD_4001
F01A : C4 F0"  "andb#$F0
F01C : 37"7"pshb
F01D : 54"T"lsrb
F01E : 54"T"lsrb
F01F : 54"T"lsrb
F020 : 54"T"lsrb
F021 : CE FF B7"   "ldx#$FFB7
F024 : 3A":"abx
F025 : A6 00"  "ldaa$00,x
F027 : 97 80"  "staaX0080
F029 : B7 40 01" @ "staa_sym_CPLD_4001
F02C : 86 10"  "ldaa#$10
F02E : 97 01"  "staa _sym_PORT2DataDirectionRegister
F030 : 86 0C"  "ldaa#$0C
F032 : 97 10"  "staa _sym_RateAndModeControlRegister
F034 : 86 0A"  "ldaa#$0A
F036 : 97 11"  "staa _sym_TxRxControlAndStatusRegister
F038 : CE 00 81"   "ldx#$0081
F03B : CC 00 7F"   "ldd#$007F
F03E : BD F9 AD"   "jsrLF9AD
F041 : 72 FF 86"r  "oim#$FFX0086
F044 : C6 64" d"ldab#$64
F046 : BD F9 BC"   "jsrLF9BC
F049 : BD F4 51"  Q"jsrLF451
F04C : 33"3"pulb
F04D : C1 D0"  "cmpb#$D0
F04F : 24 30"$0"bccLF081
F051 : C1 30" 0"cmpb#$30
F053 : 25 2F"%/"bcsLF084
F055LF055:
F055 : BD F9 FE"   "jsrLF9FE
F058 : BD F9 B6"   "jsrLF9B6
F05BLF05B:
F05B : CE 00 8D"   "ldx#$008D
F05E : CC 00 23"  #"ldd#$0023
F061 : BD F9 AD"   "jsrLF9AD
F064 : 96 11"  "ldaa _sym_TxRxControlAndStatusRegister
F066 : 96 12"  "ldaa_sym_RxDataRegister

[M100] PDD - ROM Dump

[BiggRanger]

Hello all,
I see on the Wiki 
(http://bitchin100.com/wiki/index.php?title=TPDD_Design_Notes) that 
someone was working on trying to dump the ROM on the PDD, but that page 
was last updated in 2009. Well I took the challenge and wrote this 
little program to try it.


I've also posted the S-REC too so anybody can try it. In order to get 
the S-REC to work do the following:
1) Switch your PDD to 9600 BUAD, the switches on the bottom need to be 
set to ON.
2) Connect your PDD to a PC and connect with Hyper Terminal or another 
terminal program.
3) Settings are 9600-8-n-1, no flow control. Set the line delay and 
character delay to 20mS, otherwise we're pushing data to the CPU too 
fast and will get a blinking light.
4) Paste each line of the S-REC into the terminal program, but do not 
include the CR/LF (i.e. only highlight the text).
5) If the Low Battery light starts blinking, start over because 
something bad happened (like accidently included a CR/LF).
5) When the last line is pasted "S901FE", this triggers the program 
running in the ROM to jump to address 0x8515 and execute the program
6) The ROM (F000-) is now dumped to the terminal program in the 
following format:

F000:0F 8E 87 FF 86 FC 97 00
F008:86 34 97 02 86 FF 97 04
F010:97 05 86 A0 B7 40 00 F6
F018:40 01 C4 F0 37 54 54 54
F020:54 CE FF B7 3A A6 00 97
F028:80 B7 40 01 86 10 97 01
F030:86 0C 97 10 86 0A 97 11
F038:CE 00 81 CC 00 7F BD F9
F040:AD 72 FF 86 C6 64 BD F9
F048:BC BD F4 51 33 C1 D0 24

If anybody is interested I can send the ROM image to the list, or to 
whoever is hosting bitchin100.com, so it can be put on the web page.


Darren Clark.




Assembly Program:

;TANDY PDD ROM DUMPER
;Object is to dump the 4K of "protected" ROM at F000-
;over the SCI
;
;Target CPU: HD63A01V1
;
;Notes:
;injection address is 8515h
;total RAM needed is 92 Bytes
;
;10 OPEN "COM:88N1DNN" FOR OUTPUT AS #1
;20 PRINT #1, "S10985157C00AD7EF08B3AS901FE"
;30 LOAD "COM:88N1ENN", R
;
;S1 09 8515 7C 00 AD 7E F0 8B 3A
;S9 01 FE
;
;8515 INC  $00AD
;8518 JMP  F08B
;

.org $8515
LDX #$F000;set start to copy at F000
addressLDAB #$08;address label counter "F000: "
LDAA #$D;CR
JSRtxSendA
LDAA #$A;LF
JSRtxSendA
PSHX;put X (memory pointer) into stack
PULA;load into A the Hi byte of the pointer
CMPA #$00;check if memory pointer is at 00 (we wrapped)
BEQ done;we wrap we quit (don't care about the stack)
JSR txSendv;Send HEX value of Hi Byte
PULA;load into A the Low byte of the pointer
JSR txSendv ;Send HEX value of Low Byte
LDAA #$3A;':'
JSRtxSendA
dataLDAA ,X;Load memory value at pointer into ACCA
JSRtxSendv ;Send HEX value of ACCA byte
LDAA #$20;' '
JSRtxSendA
INX;increment memory pointer
DECB;decrement address label counter
CMPB #$00;if address counter = 0 then make new label
BEQ address;address label counter is 0, make new line
BRA data;print next piece of data
done LDAA #$58;print 'X' we're terminated
JSRtxSendA
INFBRA INF;loop infinity

txSendAPSHB;output ASCII characters to SCI, do not use IRQ2
loopLDAB $11;get serial control register
ANDB #$20;check bit 5, this is high when ready to send
BEQ loop
STAA $13;put byte into TX register
PULB
RTS

txSendvPSHA;Take value in ACCA and output 2 bytes in ASCII HEX
LSRA;move MSB to LSB
LSRA;4x, this also makes MSB 0
LSRA
LSRA
JSR report;Print first ASCII HEX value
PULA;Get A again and print second ASCII HEX value
ANDA #$0F;mask out MSB
reportCMPA #$0A
BMI add30;<0A (0-9) then only add 30h
ADDA #$07;=>0A (A-F) add 07h
add30ADDA #$30;add 30h (makes bin 0-9 into hex 30-39)
JSR txSendA
RTS

.end

S-REC:

S10E8515CEF000C608860DBD854F8621
S11385200ABD854F3C328100271EBD855A32BD8568
S11385305A863ABD854FA600BD855A8620BD854F13
S1138540085AC10027D220EE8658BD854F20FE3739
S1138550D611C42027FA971936BD12
S1138560856532840F810A2B028B078B30BD854FC2
S104857039CD
S901FE