Hi,
I got a 24KB Model 100 about one year ago and I've been using it a lot, but
after some loss of the internal data in the last month, I've checked the
Ni-CAD battery and it seems to show signs of imminent leaking.
So I ordered a new one (3.6V / 80mA) and I would like to know if there are
some a
Hi,
I'm still waiting for my replacement Ni-Cad battery but I've been
continuing using my M100 without any other issue... until tonight.
When I turned it on, the "low battery" light was on, and the date
displayed on the first line was wrong: ◥5ÿ 00,1919 Sun 00:00:00
I switched it off and on again
Thanks to all your precious advises!
After posting my message yesterday, I've read the service manual cover
to cover (I wish I could understand everything they say in there :o) )
and tried to measure the different voltages recommended in both your
emails and the service manual.
I noticed the flick
It's not really a surprise but after a couple of hours of usage, my
M100 froze and was back being stuck on the menu... so I continued
following the service manual troubleshooting instructions.
Philip Avery wrote:
> I too had this problem of random date data & unresponsive keyboard,
> albeit with a
Fugu ME100 wrote:
> Do you have a picture of the thermistor?
I just put a few closeup pictures here: http://pics.lefauve.org/TH1/
I also added a picture of TH2 for comparison (that's supposed to be
the same component) and a few pictures of the RTC (they really didn't
put that much solder for this
It seems the first step in fixing my M100 is to change all the elec
caps, and thanks to the incredibly helpful list of Jeff Birt
(http://www.soigeneris.com/document/vintcom/TRS-80_Model_100_Cap_order_list.pdf)
I found all of them on au.mouser.com.
Now, since my TH1 Thermister/Thermistor looks comp
Eric Miller wrote:
>
> If I'm reading the documentation correctly, it appears that I need a 3.3V 5V
> TTL Bi-directional level shifter between my USB2.0 to serial cable and my
> M100. I'm pretty sure my Prolific pl-2303 is 3.3V.
Wouldn't be easier to just buy a new USB to RS232 adapter?
For wha
Talking about RS232 reminded me of a weird thing happening on my M100
which I always assumed was normal, but I now realize I've never seen
it mentioned anywhere:
Every time I plug a RS232 connector to my M100 the contrast increases
dramatically (or drop, depending of the angle you're looking at it
Thanks for the replies, I'll let you know if the replacement of caps
help the problem! (that may also be caused by my exploded TH1
thermistor... I'll try changing it too)
Kurt McCullum wrote:
> cable and my Model-T. If the RTS/CTS or DTR/DSR lines are crossed, you
> end up with major contrast issu
Mike Stein wrote:
> Sounds like a handshaking issue; what are you using at the other end of the
> cable to save & load those programs, and are they tokenized .BA versions or
> .DO plaintext?
I just use Putty. Basically, I open a connection on the com port with
the same speed, parity, etc, change
Peter Vollan wrote:
> That is just what I was gonna say: you are draining more power, thus
> the drop in screen contrast. The solution is fresh batteries or a wall
> wart adaptor. No need to recap your whole unit.
Well, the first thing I tried when starting to have issues was to use
brand new batt
Kurt McCullum wrote:
> Teeny can also be injected from mComm. It's quite a bit smaller too
> so it loads faster. I'm not sure why that error would be coming up
> with TS-DOS. Did you use the command "RUN COM:98N1E" from Basic? The
> dos injector uses xon/xoff so the flow control lines don't matter
So yesterday I bought the collection from Scotty, which was I must say
in even better condition that the pictures show :o)
Not only I'm now the proud owner of a mint condition fully functional
M100 with its TPDD2, but I should have enough parts to fix my original
M100.
Among other spare pieces, t
This week-end, I re-capped my M100 almost completely (C86 was out of
stock, but I should get one this week).
The good news is that my voltages are now looking a lot better
(especially VEE that went from -4.5V to -5.05V).
The bad news is that despite re-heating the RTC's pins, I'm still
having th
I've finish recapping my M100, and also replaced the thermistor that was fried.
I didn't have the clock display/freeze problem since then but the
contrast of my unit is still way to high and the contrast dial has
almost no effect.
When I turn it on after a long break, the contrast is OK for 2 to 3
Stephen Adolph wrote:
> It would be good to post a list of caps used to do the recapping. Is that
> posted somewhere?
I used Jeff Birt's list. The list link is in the description of his
youtube video "TRS 80 Model 100 Repair Part 2".
(I tried to post the direct link but my ISP rejected the mail
Gary Weber wrote:
> I just wish someone still could make that. As
> it stands now I think "reverse engineering" and then printing with a 3D
> printer might be the only option these days.
I wouldn't do something like that with a "home" 3D printer because PLA
(the most common "plastic" used for 3D
I found yesterday Adrian Ryan's DEBUG program on this page:
http://www.club100.org/cgi-bin/blosxom2011_06.cgi
That's when things started to go weirdly wrong.
I'm using a Rex with FW 4.9 and the TS-DOS ROM with mComm 2.50. I've
never had any issue with those before but to make it short, loading
"DE
Gary Weber wrote:
> Possibly a better approach than getting exact dimensions of an M100 would
> be to try to replicate an existing protective cover that someone already has
> (either the black or the clear). Might be tough to get someone to give
> theirs
> up for a period of time though. ;-)
It
Eric wrote:
> Also after looking into Shapeways prices, we're looking at a cost of
> at least $60/$80 each for a plastic piece of this size.
I found a "3d printing & Price Comparison Service" so I quickly made a
mock-up version of the cover (changing the size by 1 or two
millimeters shouldn't chan
Gary Weber wrote:
> I corrupted my file system over and over trying to figure out what was
> going on when loading in the various ADVx.DO files for the ADVENT adventure
> game using TS-DOS. Turns out those .DO files had an EOF character at the
> end. And that ended up in the files because I'd ma
John R. Hogerhuis wrote:
> I used the mappings in Hterm.
> Hterm maps all m100 characters to/from utf8.
>
>A Unicode filter for LaddieAlpha is a good idea
Thanks for the information. I'll have a look in HTerm sources (unless
you plan to implement the LaddieAlpha filter in the near future? ;o) )
I
Gary Weber wrote:
> As a text adventure, I think it's pretty good. There's the potential of
> creating a completely different adventure by writing your own set of
> ADV#.DO files, so that sort of thing was pretty unique at the time.
>
> Check it out!
Thank you Gary!
I will give it a try tonight
Mike Stein wrote:
> I'm curious: how did you find that page?
I was looking for a disassembler for the M100. I used Google and this
page was one of the first results.
Fwiw, DEBUG.CO is working great once you manage to install it.
Eric
I got a weird behavior this morning: Two of the files in my M100 got swapped.
I mean that when I load one of them I get the other one...
Those are files I've been working on for a few weeks already, and I've
no idea how it has happen.
Are those issues common? Should I worry about the integrity of
Well, something weirder happened just after I sent the previous email :
Note that I tried a couple of switch off/switch on and warm reset
cycles before sending the first email and none of that did change
anything...
Now, just after sending the mail, I switched the M100 on and tried
opening the MK
Thanks for your reply John!
I'm not sure however what LNKFIL is? (is that a rom subroutine? I
didn't finish reading "Hidden powers of the M100" yet :o) ).
Shortly after my last message the two files got swapped again and this
time I made a copy of the directory structure using "savem".
It took a
Thomas Morehouse wrote:
> Thanks gentlemen. I'd used serial cables (null modem) for transferring
> files between DOS and Windows machines before. Forgot about the 100/102
> Telcom method.
If you use TELCOM, I'd recommend you keep the speed at 1200 or 2400
bauds. While the M100 can do 19200, I ha
John R. Hogerhuis wrote:
> I suggest for data entry just use TEXT. You can use tabs or commas as field
> separators, CRLF as record separator and then import using tab separated
> CSV on your desktop. Very little overhead this way, maximizing use of your
T's RAM.
Thanks for the advice. That was th
Mike Stein wrote:
> That's something you read in many places, but as long
> as you've selected XON/XOFF handshaking at both ends
> there shouldn't be an issue using 19,200 baud, especially
> when uploading from the M100.
I thought this too, but I couldn't get sustainable transfer using
anything ab
VANDEN BOSSCHE JAN wrote:
> Q to list: how can I make a ROMdump from BASIC?
Here is how I did this on my M100 using TS-DOS and mComm on the PC
side (probably also works with LaddieAlpha or other disk emulators) :
- Launch TS-DOS and activate the dos extension (press F5 until it says "DOS-ON")
- Go
On Sun, Jun 2, 2019 at 5:13 PM Jeffrey Birt wrote:
> I splurged a few weeks ago and picked up that Microcolor unit on eBay. It
> will be a few more
> weeks before I can get to it but I would love to get it working and bring it
> to show.
Jeff, I happen to use the TMS9928A a lot at the moment (w
Hi,
I'm probably missing something very obvious, but I've tried everything
I could think of and I'm out of ideas :o)
I've been trying to use HTERM on my M100, but all I get is a white
screen, until I press F8 which exits the application and returns to
the menu.
I found the application on the
htt
Thanks for all your replies!
I just wasn't using the correct baud rate. I thought that even with
the wrong serial settings I should see some kind of garbage characters
on the other side, but it seems I was wrong :o)
John R. Hogerhuis wrote:
> - Match baud rate... you can rebuild with a different
John R. Hogerhuis wrote:
> It does map in both directions... what are you seeing?
> I don't map every UTF-8 character :-) There are a lot.
I was using the "é" character, but I found the problem: Since I'm
using a QWERTY keyboard, I use numpad code ALT+130 to type this
character.
When I do this in
John R. Hogerhuis wrote:
> But the coolest thing about it for me is that it lasts for almost a week
> and has an always-on transflective color display
That sounds like a PebbleWatch screen :o) It's good to know there are
alternative out there since Pebble is now out of business.
> If someone made
Eric LK wrote:
> I was using the "?" character[...]
That wasn't the question mark character of course but the "Latin Small
Letter E with Acute" which was scrapped by the mailing list :o)
You can type it on the M100 with Code+d.
John R. Hogerhuis wrote:
> Well if
>> 3. I downloaded two files: HTERM.CO and HTERM.lst. I'm guessing I only
>> need
>> the .CO file and my question is how will I get it transferred into the
>> M102?
>> Using the built in terminal ap? It seems I need to get it on the menu some
>> how.
>>
>
> Well, that can be tricky. Depends on what
Since there is some talk about REX on the list, it may be a good time
to ask a few questions I have about it :o)
I've been using the version 4.9 of the firmware with a M100 for a few months.
First, there is this thing in the documentation that I'm not sure to understand:
> REXMGR has to be locate
Thanks for your advises!
I think I'll start by backup everything on the PC, and "reformat" the
REX (deleting all RAM images).
It seems easy enough to backup whole RAM images as "BY" files from the
REXMGR so I'll do this regularly in case anything goes wrong in the
REX's flash :o)
I'll also have
Peter Noeth wrote:
> I was doing some BASIC programming on my T102 using the Text editor. I
> put it down to attend to the laundry, and came back 15 or 20 minutes later
> to continue on with the T102, where I found that typing on the computer
> produced garbage characters on the screen and then the
Brian White wrote:
> Astonishingly, I was just able to print a functional carrier in PLA on a
> Creality CR-10S. (A very common home $400 fdm printer from a year ago.)
Very nice result!
It looks like you printed it flat on the bed. If I may make a
suggestion, you may try to print it on the side (
Hi,
I usually use my M100 at least once or twice a week but I was away for
almost a full month, and when I turned it on yesterday, it decided to
take a break :o(
When I turned it on, it was OK for about 3-4 seconds (the time for me
to look at the menu clock, and to check on my watch it was still
Hi again!
John R. Hogerhuis wrote:
> That doesn't always do the trick, if it's crashed it will ignore the
> keyboard. Meanwhile the "memory power" NiCd keeps the corrupt zombie RAM in
> its corrupted state.
Thanks for the advice John.
It actually unfroze it but only for a couple of minutes during
Tom Wilson wrote:
> Some other devices, such as certain models of Sound Canvas and a
> few varieties of Yamaha XG sound models actually have a serial port
> interface built right into the machine. So you could send MIDI data to
> one of those without needing the level conversion.
>
> The only issue
Hi,
About one year ago my two "good" M100 stopped working almost at the same
time. I haven't got any time to look into them yet, but I really miss
taking notes on a M100 so I'm trying to get them working again.
The first one kind of works but the contrast is ridiculously low, and you
can only see
Thank you Josh!
Yes I'm testing them in-circuit, but that was the case in both the
tests, and I get different readings, which makes me think they were
faulty.
I did consider lifting one leg, but the reason I didn't is I'm not
sure how to re-solder it after testing because it's cut really short.
I
Well, it seems that changing C85 and C82 did the trick :o)
I got a chance to unsolder one of D14 legs and it gave a more sensible
reading (0.7V in one direction, open circuit in the other).
I tried testing C85 after removing it (with a cheap chinese components
tester) and it registered as a diode
Hi Desi,
Desi Villaescusa wrote:
> 1: Is there a good character to add to the end of my BASIC programs when I
> transfer them? ("." is working, but if there is a more apropriate one)
If you're copy/pasting your basic files into putty, you need to press
Ctrl+Z after you pasted (or typed) the BAS
I wrote one in BASIC a couple months ago. It's pretty simple (80x16
cells, can load a DO as starting generation or generate a random one)
and... very slow (about 1:15 minutes per generation).
The code is pretty awful because I used every trick I could to make it
faster, but I could upload it somew
Gregory McGill wrote:
> http://ftp.whtech.com/club100/gam/life1.ba
> http://ftp.whtech.com/club100/gam/life1.do
> http://ftp.whtech.com/club100/gam/life2.ba
I tried them on VirtualT. I love the board editor, but they don't
handle screen wrapping at all :o(
For example if you have a glider, it will
John R. Hogerhuis wrote:
> Also works on https://bitchin100.com/CloudT
Cool :o)
> I tried "Add URL" to skip a step downloading it, but it doesn't work
> because of CORS setting on lefauve.org
Thanks for the feedback John.
I just fixed this, however it will only work with
http://bitchin100.com/Cl
Since we're thinking outside of the box, couldn't we replace the FTDI
with a small arduino board?
Something like an Arduino Micro or even a Digispark should do it.
Then, it should be possible to convert the M100 additional ESC codes
to their VT100 equivalent on the fly and we will just have:
M100
Message: 9
Date: Wed, 20 Jan 2021 19:28:40 -0500
Stephen Adolph wrote:
> Eric, thanks for pointing this out:
No problem Steve, I spent a lot of time playing with those when I was
a student :o)
I don't have a real vt100 to test, but I tried on putty and if you can
lock/unlock the last line (line
About 6 months ago, my M100's LCD contrast was very weak and impossible to use.
Following your advice, I changed C82 and C85 . That gave me a solid
-5V for VEE and the contrast was back to normal.
My problem is that 6 months later, I can still read the screen
(mostly) but my VEE is now back to -3V
"Jeffrey Birt" wrote:
> On the M100s I have found most of the caps tend to leak (and cause PCB
> damage).
> While I am NOT a proponent of 'recapping' every piece of vintage gear out
> there on
> the M100 I do a full recap on every one of them.
I didn't recapped this unit because the seller I pu
Steven Ranft wrote:
> Has anyone tried using a Digital Voice Recorder?
I actually tried and was successful using a TASCAM DR-05 digital
recorder to save and load programs from a Jupiter Ace last week-end
(full disclosure, that was an Omni128HQ in Jupiter Ace mode; I'm not
the lucky owner of a rea
Le lun. 22 mars 2021 à 19:05, Eric LK a écrit :
>
> I didn't recapped this unit because the seller I purchased it from
> told me he did it a couple of years ago, but I think I'll just follow
> your advice on this (also, I'm not sure he did clean the flux).
>
> I a
"Jeffrey Birt" wrote:
> Welcome to the fun world of leaking electrolytic capacitors. Trace damage
> like this is
> very common and if someone replaces the capacitors without properly
> mitigating the
> damage the corrosion will continue to spread and get worse. 'Half-way'
> repairs cause
> as m
Peter Vollan wrote:
> My Model 100 keeps getting into that state where the menu items call up the
> wrong program. Why does this happen?
I did have the same problem for a while.
I kept refreshing the memory from a REX backup, but after a few days
the problem was back.
I thought it was my fault at
Joshua O'Keefe wrote:
> After cutting out (and not replacing) the battery, the machine
> starts, prints the menu, and then freezes. In this state the
> clock is not advancing.
My second M100 has this exact problem.
I found out that the pin 10 of M18 (D1990AC) wasn't outputting a 256
Hz clock like
B 9 wrote:
> Good idea, but I can't as I am going to be indexing into the file given a
> fixed record size.
I wrote a "very simplified" DB system where I used CO files for my data.
Basically, I just peek and poke directly when into the files without
loading them into BASIC.
It works well, allows
Hi!
B 9 wrote:
> Sorry for not replying to this before, Eric. Gmail got confused and had
> filed it as spam.
No worries, it happens to me all the time... I actually found the M100
list compilation email containing your reply in my spam folder too.
> I ended up reinventing the wheel, but then th
B 9 wrote:
> For public domain databases, what occurs to me are:
>- The CIA World Factbook
>- MAME arcade games
>- Various genomics and scientific nomenclature for the tree of life
Thanks for the idea. I found a MAME database that could be what I need.
No way to fit all the DB in 32K
Peter Noeth wrote:
>I use a Seiko DPU-414 thermal printer with my T102. It has both parallel
>(Centronix) and serial (9 pin female D-sub) connections. It runs off 6v
>external (same power barrel connector and polarity as the M100), and has
>provisions for an internal rechargeable Ni-Cd type batte
"John R. Hogerhuis" wrote:
> ?MID$(H$,A/16+1,1);MID$(H$,AMOD16+1,1);" ";
It would be slightly faster with:
?MID$(H$,A\16+1,1);MID$(H$,(AAND15)+1,1);" ";
1 iterations takes 5:43 vs 7:23 with your version (I tested on
VirtualT, so it may not be 100% accurate but that should be a good
estimate)
"John R. Hogerhuis" wrote:
> 10 DEFINTP:DEFSTRH
> 20 H=CHR$(201)
> 30 P=VARPTR(H)+1
> 1000 P=PEEK(P)+256%*(PEEK(P+1)+256%*(PEEK(P+1)>127))
> 1010 PRINTP
Very nice. That seems a little more optimized than the solution I used
for my "direct file access from RAM" implementation :o)
You could skip t
I wrote:
>FWIW, I also tried "caching" the result of "PEEK(P+1)" but again,
>it didn't change the result (in all 3 implementations, 1000
>iterations took 14 seconds, so those modifications aren't really
>interesting, except for the brain picking exercise ;o)).
Well, I managed to (almost) half this
Hiraghm wrote:
> I came across this tiny little board on the Pine64 site, and I wonder...
I considered the same thing with an ESP-01 (
https://www.ebay.com.au/itm/195354250177 ).
The idea was to find a couple of resistors on the M100 motherboard
that could be lifted to isolate the actual modem f
I've just seen the video, and this is definitely a great idea.
If I understand correctly, the working principle is that the rotary
encoder sets the higher bits of the eeprom's address pins.
The "classic" RC2014 (the original model with 32KB RAM and 8KB ROM,
not the new fancy ones with 512+KB that
John,
This was indeed a tricky one :o)
The problem is caused by the rule on lines 1602-1604 of load.php (I
don't know the internals of Mediawiki, but I suppose this PHP script
is generating a CSS file):
.mw-hide-empty-elt .mw-parser-output:not(.mw-show-empty-elt) .mw-empty-elt {
display:none
71 matches
Mail list logo
