I found that the electrolyte has eaten through wires and corroded traces,
plus a coil dropped off and it's copper wire broke. So I have a cable,
wall wart, manual and spare belt to show for my investment.
I tell myself I'm fortunate to be alive, healthy and able to pursue my
interests but sometim
The power-supply board? or the drive controller board?
On Thu, Jun 25, 2020 at 10:55 AM Charles Hudson wrote:
> I found that the electrolyte has eaten through wires and corroded traces,
> plus a coil dropped off and it's copper wire broke. So I have a cable,
> wall wart, manual and spare belt t
On 6/25/20 10:54 AM, Charles Hudson wrote:
I found that the electrolyte has eaten through wires and corroded
traces, plus a coil dropped off and it's copper wire broke. So I have a
cable, wall wart, manual and spare belt to show for my investment.
It's probably still fixable, but it's definit
I may have a spare TPDD1 PCB. I have had a couple of units die for
mechanical reasons. Was it TPDD1 or TPDD2?
On Thu, Jun 25, 2020 at 11:35 AM Brian K. White
wrote:
> On 6/25/20 10:54 AM, Charles Hudson wrote:
> > I found that the electrolyte has eaten through wires and corroded
> > traces, p
While we're on the topic of fixing TPDDs, is there a known copy of a
service manual for this unit? I know it's not OEM by Tandy, so I'm guessing
it doesn't have an awesome service manual like the 100/102/200 do. I've got
a couple units sent to me for repairs that are *almost* working but I'm
suspic
I have a couple 100's with issues with the serial port.. and a 200 can't
use them with mcomm/ladde either are unreliable in transfers or don't work
at all.
for instance the 200 sends the wrong characters when i set up a term on the
pc and type back and forth between.. it receives characters corre
Check your cable. As strange as this sounds, the 200 requires RTS/CTS to be
wired properly. I verified this last year by trying to use a cable that only
had Tx,Rx, and GND wired up and it was a no go. The RTS/CTS signals are used
even in TELCOM even though the manual says it isn't. You could alw
On 6/25/20 12:03 PM, Josh Malone wrote:
While we're on the topic of fixing TPDDs, is there a known copy of a
service manual for this unit? I know it's not OEM by Tandy, so I'm
guessing it doesn't have an awesome service manual like the 100/102/200
do. I've got a couple units sent to me for repa
On 6/25/20 12:28 PM, Brian K. White wrote:
On 6/25/20 12:03 PM, Josh Malone wrote:
While we're on the topic of fixing TPDDs, is there a known copy of a
service manual for this unit? I know it's not OEM by Tandy, so I'm
guessing it doesn't have an awesome service manual like the
100/102/200 do.
I am using TeraTerm to upload BASIC files and I wasn't having any issues, but
now I am getting
this error when Sending File - ?DS Error
What does - ?DS Error mean? How can I fix the issue?
Thanks - I am sending from Model 100 with these Parameters: 47I1E,10
--
This email has be
>From the manual
?DS Error
Code = 56
Message = Direct Statement file
Meaning = An ASCII format file does not load
Sounds like you have a bad file
On Thu, Jun 25, 2020, at 10:11 AM, Robert Pellegrino wrote:
>
> I am using TeraTerm to upload BASIC files and I wasn't having any issues, but
> now I
I've seen this several times with files that I got online. It turned out to be
that some of the BASIC lines had been hard wrapped (that is, had a newline in
the middle of the line), causing direct statement lines instead of numbered
lines.
Open the file with a text editor and fix any lines wit
OK Thanks - I will check the files - I downloaded them from Club100
On 6/25/2020 1:31:18 PM, Joshua O'Keefe wrote:
I've seen this several times with files that I got online. It turned out to be
that some of the BASIC lines had been hard wrapped (that is, had a newline in
the middle of the li
If memory serves, The M100 I fixed for Randy had uni-directional serial and
it turned out to be the UART. I replaced that chip (from a donor board) and
everything was fine. I did check the signal path all the way to it and
found no issues (using scope) so I was pretty sure of the fault when I
repla
I’ve got an issue with a 102 serial port which I’ve been meaning to post about.
When I connect my NADSbox to the 102 and just go into TELCOM to try to talk to
its CLI interface, as soon as I hit F4 to go online in TELCOM the screen starts
to fill with random-seeming garbage, which is not flowing
The damage I have been describing, attributed to battery electrolyte
leakage, is limited mainly to the power supply board(s) of a TPDD1. The
drive controller board shows a little area of one corner that may have been
affected but mainly is clean: most of the corrosion is on the area directly
above
I forgot to mention.. works fine on another 100
Greg
On Thu, Jun 25, 2020 at 9:27 AM Kurt McCullum wrote:
> Check your cable. As strange as this sounds, the 200 requires RTS/CTS to
> be wired properly. I verified this last year by trying to use a cable that
> only had Tx,Rx, and GND wired up an
Jim, did you get this working? ..Steve
On Wed, Jun 24, 2020 at 8:05 PM Stephen Adolph wrote:
> Here is the exact note:
>
>
> "Make sure REXCPM is in default state, meaning RXCMGR is not running (use
> CNTL-X to remove hooks) and power cycle once."
>
>
> On Wed, Jun 24, 2020 at 7:57 PM Jim Ander
> -Original Message-
>
> Jim, did you get this working? ..Steve
> [...]
> Here is the exact note:
>
> "Make sure REXCPM is in default state, meaning RXCMGR is not running
> (use CNTL-X to remove hooks) and power cycle once."
Sorry, I missed the power-cycle part of the instructions. I wa
Just wondering, since REXCPM makes use of 76800bps large packet TPDD mode, is
there likely to be a firmware update in the near (or far) future to make
NADSbox capable of supporting this mode? (Or is it even possible with that
hardware?)
jim
On Thu, Jun 25, 2020 at 5:05 PM Jim Anderson wrote:
> Just wondering, since REXCPM makes use of 76800bps large packet TPDD mode,
> is there likely to be a firmware update in the near (or far) future to make
> NADSbox capable of supporting this mode? (Or is it even possible with that
> hardware?)
> -Original Message-
>
> Tonight I'll try it the way you specify in the note, and also (if I'm
> feeling brave) try a wipe and restore.
CTRL-X followed by power cycle works.
Wipe and restore of both the REXCPM area and the CPM area works like a charm
(eventually :) ).
jim
22 matches
Mail list logo
