Re: [M100] Does anyone actually use MFORTH?

[John Gardner]

  "8)

Re: [M100] compile and execute Turbo Pascal (Stephen Adolph)

[John Gardner]

FWIW,  Turbo Pascal 7 blew the doors off Turbo C 2.1;  fast & efficient,

at least on my HP200LX  -  Fun times...   "8)

  ...


On 10/2/20, Bert Put  wrote:
> Hi Joshua,
>
> On 10/2/20 4:02 PM, Joshua O'Keefe wrote:
>> On Oct 2, 2020, at 1:46 PM, Bert Put  wrote:
>>> Yep, I did COBOL too, busted away from it for a few years, and then a
>>> year ago went back to it.  Fun.  How about some mainframe assembler?
>>
>> One of the things I want to spend my dwindling supply of round tuits on is
>> picking up some big iron skills.  I even got as far as spinning up the
>> tk4- Hercules distribution so I can have a local MVS environment on an
>> emulated 3033.  I have no idea where to even begin learning, though.  My
>> entire life, including my career and several of my hobbies have been based
>> around micros!
>>
>>
> This is not a subject that we should probably have on the list, since
> it's not Tandy slab related, but I can tell you it's not just COBOL.
> You have to know how to build, submit and run jobs, and monitor them as
> you go.  Also, Jay Moseley's MVS distro is good, but is not exactly the
> same as the "real" big iron, because of copyright issues.  So you'll get
> a good flavor of it but it still won't be the "real deal".  You won't
> get to play with VSAM, IMS, or DB2 at all on Hercules, and those skills
> are important.  Email me directly if you want to talk more about this
> in-depth.
>
> Cheers,Bert
>

Re: [M100] Preemptive recapping

[John Gardner]

Hi all...

If you're a sucker with "poor solder-sucker" RS desoldering braid,

try putting a little flux on the braid before use...

  ...


On 8/19/20, B 9  wrote:
> On Tue, Aug 18, 2020 at 7:58 PM Joshua O'Keefe 
> wrote:
>
>> Given that my T is something I use almost daily that brings me a great
>> deal of enjoyment and utility I consider the effort having been
>> worthwhile
>> even though it changed nothing about its behavior.  If nothing else, it
>> will live longer.
>
>
> Thank you, that's a good point that I forget.  All capacitors are supposed
> to have a finite service lifetime, right? I'm not sure, but it looks like
> 5,000 hours is typical and 8,000 is considered "good". If you use your
> model T for eight hours a day, except weekends, the capacitors would be
> shot within four years.  … wait, I just double-checked before sending this
> and learned about the "Arrhenius equation".
> [image: image.png]
> Manufacturers rate capacitors at the *maximum* temperature (105°C), and the
> lifetime doubles for every 10°C reduction in ambient temperature. I don't
> think Model T's run very hot — has anybody measured? — so maybe we can
> expect them to live quite a bit longer.
>
>
> On Wed, Aug 19, 2020 at 3:59 AM Josh Malone  wrote:
>
>> [...] That said, console5 is a reputable supplier and if you have the
>> experience and tools to recap the machine entirely, it probably won't
>> hurt.
>>
>
> When I was in school, I was taught that *“Experience is directly
> proportional to the amount of equipment destroyed.”*  I have not yet
> destroyed enough equipment by desoldering, so I'll probably hold off on
> recapping.
>
>
>> [...] people damaging the machine because they don't know how to do the
>> replacement properly (improper dwell times, wrong temps, clipping leads
>> and
>> soldering to existing joints), or use poor tools (unregulated irons, poor
>> solder suckers).
>>
>
> For desoldering, dwell time should be low and temp should be high, right?
> I've got a regulated iron, but the desoldering braid I got from Radio-Shack
> is so bad, it might as well have been labelled "this is a poor solder
> sucker, but if you pay money for it, you'll be one too!"
>
>
> On Wed, Aug 19, 2020 at 7:24 AM Gregory McGill 
> wrote:
>
>> I sell the same kit in my store
>>
>
> Thanks! I always prefer to shop from people I "know", even if only from
> seeing them on mailing lists. For anyone searching, here's the link:
> https://www.arcadeshopper.com/wp/store/#!/model-100-102-capacitor-kit/p/139509791/category=28313042
>
>
> On Wed, Aug 19, 2020 at 9:28 AM Jeffrey Birt  wrote:
>
>> I generally don’t recommend recapping any piece of vintage gear as a
>> matter of course unless it has a history of cap problems or there is
>> signs
>> of leaking or other failures. As others have said many times folks make
>> things worse by trying to install new capacitors without the proper tools
>> or experience to do so. [...]
>>
>
> Thank you. That's good advice! I enjoy watching your videos, by the way.
>
> If I’m doing a Model 100/102 for someone else I will more than likely recap
>> it as the parts are cheap and the M100 is known for leaking caps.
>>
>
> Do you know if the Tandy 200 had similar problems?
>
> —b9
>

Re: [M100] NDC800 conversion was Re: dual CPU project

[John Gardner]

...I found an optimization in how the video code worked...

Wow.  Good show Steve!  OK,  Gary - Let's see your stuff...   "8)

  ...

Re: [M100] Maybe of some tangential interest - Intel 8085 development kit

[John Gardner]

Me two!   "8)

  ...


On 5/29/20, Tom Wilson  wrote:
> I used the 8085 trainer at my college when I learned assembly language. In
> some ways, that's my favorite computer, ever. I'd love to have one of those
> with more RAM on board.
>
>
> Tom Wilson
> wilso...@gmail.com
> (619)940-6311
> K6ABZ
>
>
> On Fri, May 29, 2020 at 2:23 PM Russell Flowers  wrote:
>
>> From the 70s/80s.
>>
>> https://www.youtube.com/watch?v=SBkW_pzhUSs
>>
>

Re: [M100] CP/M mailing list, REXCPM

[John Gardner]

My two cents - One list works better for me.

Thanks to the guys doing the heavy lifting...

  ...


On 5/11/20, Philip Avery  wrote:
> Yeah, I think keep it on this list. Then it covers the REX part of REXCPM.
>
> Philip
>
> On 12/05/2020 3:52 pm, Stephen Adolph wrote:
>> After I wrote the note, I wondered if using the other list really made
>> sense; it would divide the discussions.
>>
>> On Mon, May 11, 2020 at 10:57 PM David Rogers > > wrote:
>>
>> What Kevin said, except I just happen to still have the 100, 102,
>> 200 and NEC units from the days when they were the latest thing.
>> But I used CP/M in those days and found it to be easy to use and
>> effective for the relative simplicity of the computers of the day.
>> CP/M over, e.g., WordPerfect any day.  But I like one mailing list
>> to cover them all.
>>
>> David
>>
>> */C’est la vie, c’est la guerre,  viva la salade de pommes de
>> terre./*
>>
>> On May 11, 2020, at 7:49 PM, Kevin Becker > > wrote:
>>
>>> I'd prefer one list for all M100 stuff but I suppose it doesn't
>>> matter
>>> much either way. I'm not likely to be much of a contributor but I'm
>>> very interested in trying out CP/M and even bought a (okay several)
>>> M100 just for this purpose.
>>>
>>>
>>> On Mon, 2020-05-11 at 22:40 -0400, Stephen Adolph wrote:
 Hi folks,

 I have started to update the REX wiki for my new projects:
 REXCPM
 and
 REX# aka REXsharp

 a work in progress.

 Anyhow, we have a mailing list for CP/M use on Model 100 called
 MTCPM.  I wonder if we should revive that for CP/M discussions now,
 or should we keep CP/M here on this list?

 thoughts?

 Steve
>>>
>
>

Re: [M100] Missing ROM elements

[John Gardner]

Eneloops don't seem to suffer unduly from leakage.  So far.

Almost all this stuff is made in China.  In China,  nothing is ever

thrown away.  Including rejects from manufacturers supervised

by "1st-World" corporations...  Guess where rejects end up...

  ...


On 4/28/20, Joshua O'Keefe  wrote:
> I've started to go "off" the Costco Duracells as well, for similar
> reasons.  I recently had leakage suddenly appear multiple times in recent
> history.  I don't know if they have changed their manufacturing processes
> or if it's just the grade of battery that Costco is sourcing from them, but
> I've transitioned even more things on the cheap little NiMH cells from IKEA
> -- I had them in the mix for years -- and the important stuff (M102!) is on
> the Panasonic eneloops.
>
> I have never had a NiMH cell leak, although they do fail eventually.
>
> On Tue, Apr 28, 2020 at 12:41 PM Kevin Becker 
> wrote:
>
>> That’s interesting. I had a bad battery leakage issue recently. It was in
>> an Apple Magic Trackpad and was so bad I could not get the battery cover
>> unscrewed at all. I broke the glass trying and so I just threw the whole
>> thing out. I don’t know for sure if it was Costco Duracells but we often
>> buy those so most likely it was.
>>
>> > On Apr 28, 2020, at 3:36 PM, Jim Anderson  wrote:
>> >
>> > 
>> >>
>> >> -Original Message-
>> >> multimeter and all but a few of them were near dead. After returning
>> >> them to Costco, I obtained a fresh pack of AA duracell's and tested
>> >> them
>> >> before putting them into the machine.
>> >> [...]
>> >> As a 46 year old, this is the first time I've ever bought batteries
>> >> from
>> >> such a major manufacturer of batteries that were already dead. So
>> >> bazaar, but now I know to test them. Sheesh.
>> >
>> > Just a remark about batteries (catching up on list messages that are
>> kind of old, as I've been kind of burned out working on my computer from
>> home all day):
>> >
>> > I've had really poor results with leakage from the big Duracell packs
>> from Costco, particularly the AA cells, over a span of many years.  I
>> never
>> used to have big problems with batteries leaking but I can't even tell
>> you
>> how many things I've found with substantial leakage and corrosion from
>> these cells, even when they have not reached their 'use before' date.
>> >
>> > I don't have conclusive evidence of this, but it seems to me that the
>> devices most prone to experiencing leaking batteries were those with
>> strong
>> spring tension - I have an analog wall clock which takes a single AA cell
>> and keeps a vice-like grip on the battery, and it used to be leaking
>> every
>> year even though the battery was still working fine.  The gaskets just
>> don't seem to be able to take the pressure.  Having said that, I have had
>> other devices with weaker battery compartment springs experience leakage
>> too, it just feels like it happens more frequently in things with strong
>> springs.
>> >
>> > I'm not sure if the problem is with all modern Duracell AA cells in
>> general, or just the ones Costco sells, but I've since given up and
>> switched to Energizer which I try to buy in 20-packs at my local
>> drugstore
>> whenever I spot them on sale.  Not quite as good a price per cell as the
>> Costco packs but Energizer does at least have an explicit warranty
>> against
>> damage caused by leakage, and I've had good success with them thusfar.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >jim
>> >
>>
>>
>

Re: [M100] Just got my 100

[John Gardner]

The "engineered-rot" affecting capacitors was already visible in the 80s.

But nothing lasts forever - By all means replace the caps;  if the replace-

ments don't last 30 years,  well,  what a surprise..."8)

  ...




On 4/1/20, Gregory McGill  wrote:
> I'm actually amazed at how many of my "vintage computers" still work.. also
> vintage arcade games from the 1970s that work with the caps all dried out
>
>
> On Wed, Apr 1, 2020 at 1:05 PM Jeffrey Birt  wrote:
>
>> B4 Me100,
>>
>> A year or so ago I did a video showing how to replace the capacitors and
>> backup battery on a M100. This is the link to part 2 where that work was
>> done, in Part 1 I was tracking down a RAM module failure. In the
>> description
>> is a color-coded list of capacitors, part numbers and locations on the
>> PCB.
>> Note that in this video I swapped in a super cap instead of a battery,
>> but
>> this was just an experiment. For other M100 repairs and used a NiMh
>> battery
>> and still have a few extra on hand too.
>>
>> https://youtu.be/IGTdNMx1V1w
>>
>> Soldering is not difficult, but it is a skill that requires practice.
>> Don't
>> practice on something you care about. Find an old junk PCB and practice
>> on
>> that. If it is something you don't want to mess with feel free to drop me
>> an
>> email about repairing it for you
>>
>> Jeff Birt (Hey Birt!)
>>
>> -Original Message-
>> From: M100  On Behalf Of B4 Me100
>> Sent: Wednesday, April 1, 2020 2:50 PM
>> To: m...@bitchin100.com
>> Subject: Re: [M100] Just got my 100
>>
>> There are a few folks on the list that sometimes will repair units, they
>> might be able to offer more hands on help - although with the current
>> situation that might be difficult.
>>
>>
>> On 1/4/20, 12:40 PM, "M100 on behalf of me"
>>  wrote:
>>
>> >
>> >I have never soldered a thing in my life. Nor have I ever bought
>> >capacitors.
>> >
>> >Add this to a pile of retro gear 'tested' before I bought it to be dead
>> >or near doa. When will I learn?
>> >
>> >I'll have good luck if I can find time for this. If I do, I'll keep you
>> >posted.
>>
>> 
>> >
>>
>>
>>
>>
>>
>>
>

Re: [M100] NEC PC8201-A Hide Function Line?

[John Gardner]

Actually,  "SCREEN 0,"  is sufficient,  IIRC.

On 3/30/20, D10D3 Data  wrote:
> The NEC doesn't have a Label button, but I did finally find the command:
> SCREEN 0,1 displays the line
> SCREEN 0,0 hides it
>

Re: [M100] Dungeon Master's Personnel Service

[John Gardner]

... more proof...

BASIC deemed harmful..."8)

  ...

Re: [M100] Multiplan for M10

[John Gardner]

Hi Kurt - There is a version for the 8201a out there,  somewhere...

On 8/12/19, Kurt McCullum  wrote:
> I saw this listing on eBay for an Olivetti M10 today that has a screen shot
> of Multiplan. I keep hoping that a version will be found for the NEC 8201.
> This listing lends a bit of hope on the possibility that one might actually
> exist.
>
> https://www.ebay.com/itm/Olivetti-M10/113850794471
> 
>
> Kurt

Re: [M100] In the hospital

[John Gardner]

C'mon,  Ken - You can't let me outlive you!"8)

Get well.

Re: [M100] Posits versus floating point

[John Gardner]

I've wondered about that too - "Radix-100" FP used on TI CC40/TI74/TI95

programmables  used an 8-byte format,  byte 0 being the exponent biased

so that 40 = 0,  and a 7-byte BCD mantissa.

  ...


On 7/18/19, John R. Hogerhuis  wrote:
> Actually thinking some more about it, why would BCD floating point code be
> more compact even in ROM?
>
> Seems like BCD floats would be inefficient in every way.
>
> -- John.
>

Re: [M100] Mikrokolor

[John Gardner]

ROMADs - There's a blast from the past...

  ...


On 5/17/19, Lee Kelley  wrote:
> Hey to the group,
>
> I had a conversation with Paul back in 2009 and this is the e-mail for your
> information.
>
> "Wow, Lee! LONG time ago!! I am not sure it is true, but have been told the
> Smithsonian has a Mikrokolor in a early computer display somewhere! (they
> would never answer when asked about it)
> I doubt I have any data but the original prototype (handmade) with a home
> made, single sided, etched board. I kept it as a momento, as we lost our
> butt selling them. Olivetti came to us about licensing the design, then
> went back overseas and just copied it, part by part, for their European
> Commodore. Radio Shack did license it, but then produced their own black &
> white version. I just retired (owned a computer repair shop for 25 years)
> at the end of the year. I plan on doing some garage cleaning, and might
> find some of that stuff. I think I actually may have "archived" some
> drawings, and everything, but the only software would be a hard copy
> printout (on a dot-matrix printer!) that I wouldn't retype for all the
> money on the planet!! Keep bugging me and maybe I will see. (It's a little
> scary thinking about going up top of my garage!) It won't be for several
> months, but keep jogging me every few months, and we will see.  You could
> build it, as all the parts are available still, even though scarce. hell,
> maybe I have some of them too!
> I haven't been on the list for years. I DID get a never unwrapped M100 at a
> garage sale last fall for $1, and when I popped in 4 AA's, it booted right
> up! Quality WAS available once!!  Send me the info on the mailing lit and
> the New Age stuff if you would. Maybe with time on my hands again, I might
> enjoy playing with my "past"! I plan on getting "back" into ham radio, and
> there have been a lot of things done with it there. Those days were FUN!
> Someone would say "I wish you could...", and we would start breathing hard
> and go do it! Wound up with several patents, and LOTS of money from Tandy
> for improvements we made to the Model 1 (but weren't allowed to admit then)
> Now, you just pull out more money! Where's the fun in that?
> Paul Andreasen, TSgt, USAF (Ret)
> ROMAD, 601st DASS (another unit that "never was")
> (There's no such thing as an Ex-ROMAD!)
> Oh, yeah! Also K1JAN (www.k1jan.com, www.mdw.us, www/en500.us"
> 
>
> --
> *"I will never in my lifetime make a film that cannot be seen by the whole
> family"*  Arther P. Jacobs
>
> 
> Virus-free.
> www.avg.com
> 
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

Re: [M100] NEC Memory Module Bank 3

[John Gardner]

The sidecar connector is quite robust,  too.


 ...


On 4/16/19, John Gardner  wrote:
> Think 512K SRAM...   "8)
>
> On 4/16/19, Kurt McCullum  wrote:
>> That was my thought. To have a module that inserted into the existing
>> "sidecar" or bus slot and then got secured for a permanent 3rd bank that
>> sits inside. Not much more than one 32k SRAM chip and a latch IC to
>> decode
>> the I/O address pins. But I'm certainly a complete hardware novice when
>> it
>> comes to these things so take all that for what it's worth. I asked
>> because
>> many times there are those who have already done this kind of a thing and
>> there may already be a solution. Sounds like Steve looked into it and
>> decided it wasn't a road worth going down. I trust his knowledge on these
>> things far more than mine.
>>
>> I've got a SideCar with 96k but it isn't the most portable of units.
>> Having
>> the extra 32k inside would be nice.
>>
>> Kurt
>>
>> On Tue, Apr 16, 2019, at 1:50 PM, John Gardner wrote:
>>> I meant the "sidecar" expansion connector.
>>>
>>> ...
>>>
>>>
>>> On 4/16/19, John R. Hogerhuis  wrote:
>>> > On Tue, Apr 16, 2019 at 1:27 PM John Gardner  wrote:
>>> >
>>> >> Yeah. Especially if you don't mind splitting the case
>>> >>
>>> >> to plug your board in...
>>> >>
>>> >>
>>> > The NECs have a screw down panel that covers the socketed RAM.
>>> >
>>> > -- John.
>>> >
>>>
>>
>

Re: [M100] NEC Memory Module Bank 3

[John Gardner]

Think 512K SRAM...   "8)

On 4/16/19, Kurt McCullum  wrote:
> That was my thought. To have a module that inserted into the existing
> "sidecar" or bus slot and then got secured for a permanent 3rd bank that
> sits inside. Not much more than one 32k SRAM chip and a latch IC to decode
> the I/O address pins. But I'm certainly a complete hardware novice when it
> comes to these things so take all that for what it's worth. I asked because
> many times there are those who have already done this kind of a thing and
> there may already be a solution. Sounds like Steve looked into it and
> decided it wasn't a road worth going down. I trust his knowledge on these
> things far more than mine.
>
> I've got a SideCar with 96k but it isn't the most portable of units. Having
> the extra 32k inside would be nice.
>
> Kurt
>
> On Tue, Apr 16, 2019, at 1:50 PM, John Gardner wrote:
>> I meant the "sidecar" expansion connector.
>>
>> ...
>>
>>
>> On 4/16/19, John R. Hogerhuis  wrote:
>> > On Tue, Apr 16, 2019 at 1:27 PM John Gardner  wrote:
>> >
>> >> Yeah. Especially if you don't mind splitting the case
>> >>
>> >> to plug your board in...
>> >>
>> >>
>> > The NECs have a screw down panel that covers the socketed RAM.
>> >
>> > -- John.
>> >
>>
>

Re: [M100] NEC Memory Module Bank 3

[John Gardner]

I meant the "sidecar" expansion connector.

 ...


On 4/16/19, John R. Hogerhuis  wrote:
> On Tue, Apr 16, 2019 at 1:27 PM John Gardner  wrote:
>
>> Yeah.  Especially if you don't mind splitting the case
>>
>> to plug your board in...
>>
>>
> The NECs have a screw down panel that covers the socketed RAM.
>
> -- John.
>

Re: [M100] NEC Memory Module Bank 3

[John Gardner]

Yeah.  Especially if you don't mind splitting the case

to plug your board in...

 ...


On 4/16/19, Kurt McCullum  wrote:
> I was thinking more along the lines of something that would live inside the
> case itself so a housing wouldn't be needed. Is there enough room for that?
>
> On Tue, Apr 16, 2019, at 11:30 AM, Stephen Adolph wrote:
>> Thought about it but never pulled the trigger since I would for sure need
>> a solution for a housing.
>>
>>
>> On Tuesday, April 16, 2019, Kurt McCullum  wrote:
>>> __
>>> Quick question for you hardware designers on the list. Have any of you
>>> designed a RAM module that plugs into the system bus on the NEC 8201,
>>> similar to the SideCar that Purple Computing created. I would imagine
>>> that with todays chips, adding the 3rd bank of RAM to the NEC could all
>>> be done with a module that fits inside the NEC rather than sticking out
>>> the side.
>>>
>>> Kurt
>

Re: [M100] TeraTerm - still not communicating

[John Gardner]

When beating your head against a wall,  it helps

to have a hard head..."8)

On 4/8/19, Mike Stein  wrote:
> Seems like many people prefer 1200bd for some reason ;-)
>
> With custom software (like your HTERM for example) one can even go _above_
> TELCOM's limit of 19,200 up to 38,400 and even 76,800 if the other end
> supports it.
>   - Original Message -
>   From: John R. Hogerhuis
>   To: m...@bitchin100.com
>   Sent: Monday, April 08, 2019 6:16 PM
>   Subject: Re: [M100] TeraTerm - still not communicating
>
>
>
>
>
>
>   On Mon, Apr 8, 2019 at 3:10 PM Thomas Morehouse 
> wrote:
>
> Ladies and gentlemen, and children of all ages -
>
>
> It works.  I got the gender changer so I could finally test M102 Telcom
> to Win10 TeraTerm.
>
>
>
>   Glad you got it working :-) Science!
>
>   Now you can ratchet up the parameters, like turning on software flow
> control on both sides,and trying some file transfers at higher speeds.
>
>   And eventually, binary file transfers.
>
>
>   -- John.

Re: [M100] TeraTerm - still not communicating

[John Gardner]

... you need to prove out the transmit and receive lines on your
adapter, and on the model T.

Yep.  RS232 has'nt been Plug 'n Play for decades.

If it ever was...   "8)

  ...






On 4/5/19, John R. Hogerhuis  wrote:
> I agree with all this anti-prolific sentiment, but Thomas has what he has.
>
> Thomas if you want to prove out your cabling without buying a new USB
> adapter you will need to come up with a way to rig up a loopback adapter.
> If the device can send a byte and receive it back over the loopback, then
> it is good enough for what you are trying to do.
>
> There is more than one way to do this, but you need to prove out the
> transmit and receive lines on your adapter, and on the model T.
>
> -- John.
>

Re: [M100] TeraTerm - still not communicating

[John Gardner]

Prolific chipsets are often counterfeits.  FTDI aggressively

goes after counterfeiters - Sometimes too enthusiastically,

viz FTDI drivers which detect counterfeits & brick your device...


Probably most important is the chain of custody from OEM

to end user - I recommend Adafruit because,  so far,  they

value their reputation.  Which does'nt mean next quarter they

won't decide to cash in...

Welcome to the real world,  unfortunately...



On 4/5/19, Brian K. White  wrote:
> I've actually never had a problem with a Prolific based adapter either,
> but I know that it is a real problem anyway.
>
> Pick any random cable purchased off amazon or ebay, and it might or
> might not be garbage, until you prove it by actually using it.
> I've bought probably 20 or more if you count both work and hobby stuff
> over the last 15-20 years, and they've all actually worked ok, but that
> is just luck. The bad ones do actually exist, and they look just like
> the good ones, unless you stick to a few name brands.
>
> And it's also a real thing that even when you have a "good" one where
> the chip isn't counterfeit, the chip and the driver even at their best,
> still lacks certain features that matter.
> John Hogerhuis has explained before (maybe on the fb list instead of
> here) that the Prolific interface doesn't allow you to avoid a certain
> amount of usb buffering, which can screw up the timing of signals, and
> can prevent flow control from actually working, because the flow control
> signal itself is queued up and sent only when the next packet is full
> and ready, and by then you may have already overrun the M100's receive
> buffer etc.
>
> That's the kind of problem that isn't disproved by simply having the
> good luck to not have hit it yet.
> It's still there and will still hit someone else under some other
> condition, or may still hit you tomorrow even if it never has before,
> because it's dependent on variables and variable conditions and usage
> pattern.
>
> In the specific case of TPDD emulation, I think you can actually get
> away with Prolific, and a total lack of flow control, because of the way
> the TPDD protocol happens to work. It works in fixed small size packets,
> where the entire packet fits inside the M100 receive buffer, and, you
> only ever get one packet at a time because the TPDD doesn't send a new
> packet until after the M100 sends an ack after ingesting the previous
> packet. So the tpdd protocol implements a flow control itself, instead
> of relying on the underlying serial channel to be doing that right. So
> it's another way you can think there is no problem when there still is.
> Or, there is no problem *only* as long as you only keep using it for
> exactly that one purpose which happens to work.
>
> --
> bkw
>
>
> On 4/5/19 12:31 PM, Jonathan Yuen wrote:
>> Hello All,
>>
>> I've used a prolific usb-serial cable to connect my laptop to a raspberry
>> pi and it didn't have any handshaking at all, just tx, rx, gnd, and a
>> constant 5V to power whatever (like the pi itself).  This wasn't real
>> rs-232, just the ttl level serial commmunication, but the pi wanted ttl,
>> not real rs-232.
>>
>> jonathan.y...@mykopat.slu.se
>> ---
>> När du skickar e-post till SLU så innebär detta att SLU behandlar dina
>> personuppgifter. För att läsa mer om hur detta går till, klicka här
>> 
>> E-mailing SLU will result in SLU processing your personal data. For more
>> information on how this is done, click here
>> 
>
>

Re: [M100] TeraTerm - still not communicating

[John Gardner]

Yes,  but tieing the TX & RX pins together physically tests

the whole TX & RX path  -  And the convertor,  on the PC

side.  Like Birt,  I suspect your Prolific device.



On 4/5/19, Thomas Morehouse  wrote:
> John - isn't that the same as using half/full duplex?  TeraTerm on Win10
> lets me "echo" sent characters; duplex on TELCOM lets me do the same on the
> 102.
>
> Tom M.
>
>
> On Fri, Apr 5, 2019 at 9:11 AM John Gardner  wrote:
>
>> You should be able to tie ("loop back") the TX pin of
>>
>> your convertor to the RX pin,  so that sent characters
>>
>> are echoed to the display.  Same deal on the MT side.
>>
>>
>>
>> On 4/5/19, John Gardner  wrote:
>> > Been there,  done that - I've had good luck with the FTDI-based
>> >
>> > convertors sold by Adafruit.  Some good tutorials on that site too.
>> >
>> >  https://www.adafruit.com/product/284
>> >
>> > On 4/5/19, Jeffrey Birt  wrote:
>> >> FWIW, I have had very bad luck with Prolific USB<->Serial converters.
>> The
>> >> have failed to work 90% of the time when I have tried them (on
>> >> multiple
>> >> platforms, applications, etc.)
>> >>
>> >>
>> >>
>> >> FDTI converters are much better, far, far fewer issues.
>> >>
>> >>
>> >>
>> >> I’m not saying for certain that the Prolific adapter is your issue but
>> if
>> >> it
>> >> were me, I would suspect it.
>> >>
>> >>
>> >>
>> >> Jeff_Birt (Hey Birt!)
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> From: M100  On Behalf Of Thomas
>> >> Morehouse
>> >> Sent: Friday, April 5, 2019 7:15 AM
>> >> To: m...@bitchin100.com
>> >> Subject: Re: [M100] TeraTerm - still not communicating
>> >>
>> >>
>> >>
>> >> John - sorry, but I'm a dolt.  Unfortunately I have no idea what
>> "looping
>> >> back both sides" means.
>> >>
>> >>
>> >>
>> >> Hitting a brick wall!
>> >>
>> >> TM
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On Fri, Apr 5, 2019 at 8:08 AM John Gardner > >> <mailto:gof...@gmail.com> > wrote:
>> >>
>> >> OK.  sounds like you know what you're doing.
>> >>
>> >> Have you tried looping back both sides of the connection?
>> >>
>> >> On 4/5/19, John Gardner mailto:gof...@gmail.com> >
>> >> wrote:
>> >>> On the Device Manager toolbar,  click View & select "Show
>> >>>
>> >>> hidden devices".  What do you see now?
>> >>>
>> >>> I'm not familiar with Prolific-based USB to Serial devices;
>> >>>
>> >>> do you have the requisite driver loaded?
>> >>>
>> >>> On 4/5/19, John Gardner mailto:gof...@gmail.com> >
>> >>> wrote:
>> >>>> In W10,  open the Control Panel,  click on Device Manager,
>> >>>>
>> >>>> click Ports (COM & LPT) - COM1 is normally the default - Is
>> >>>>
>> >>>> that what you see?
>> >>>>
>> >>>> On 4/5/19, Thomas Morehouse > >>>> <mailto:nutmegfl...@gmail.com> > wrote:
>> >>>>> Gentlemen -
>> >>>>>
>> >>>>> I've got my 102 connected to my Win10 laptop.
>> >>>>>
>> >>>>> USB to serial cable, with null modem adapter.
>> >>>>>
>> >>>>> I've got Telcom STAT set to 57E1E.  Then I choose TERM.
>> >>>>>
>> >>>>> I've got TeraTerm set to Com6/Prolific, with port set to 1200 bps,
>> >>>>> 7E1,
>> >>>>> xon/off.
>> >>>>>
>> >>>>> Still no comms either way.  Characters typed on either device don't
>> >>>>> appear
>> >>>>> on the other device.
>> >>>>>
>> >>>>> I'm just guessing at how to use TeraTerm, as even in the help files
>> >>>>> I
>> >>>>> find
>> >>>>> no "step by step" to connecting.  In other words, what to do when.
>> >>>>>
>> >>>>> Advice from a TeraTerm user needed!
>> >>>>> Thanks.
>> >>>>> Tom M.
>> >>>>>
>> >>>>
>> >>>
>> >>
>> >>
>> >
>>
>

Re: [M100] TeraTerm - still not communicating

[John Gardner]

You should be able to tie ("loop back") the TX pin of

your convertor to the RX pin,  so that sent characters

are echoed to the display.  Same deal on the MT side.



On 4/5/19, John Gardner  wrote:
> Been there,  done that - I've had good luck with the FTDI-based
>
> convertors sold by Adafruit.  Some good tutorials on that site too.
>
>  https://www.adafruit.com/product/284
>
> On 4/5/19, Jeffrey Birt  wrote:
>> FWIW, I have had very bad luck with Prolific USB<->Serial converters. The
>> have failed to work 90% of the time when I have tried them (on multiple
>> platforms, applications, etc.)
>>
>>
>>
>> FDTI converters are much better, far, far fewer issues.
>>
>>
>>
>> I’m not saying for certain that the Prolific adapter is your issue but if
>> it
>> were me, I would suspect it.
>>
>>
>>
>> Jeff_Birt (Hey Birt!)
>>
>>
>>
>>
>>
>> From: M100  On Behalf Of Thomas
>> Morehouse
>> Sent: Friday, April 5, 2019 7:15 AM
>> To: m...@bitchin100.com
>> Subject: Re: [M100] TeraTerm - still not communicating
>>
>>
>>
>> John - sorry, but I'm a dolt.  Unfortunately I have no idea what "looping
>> back both sides" means.
>>
>>
>>
>> Hitting a brick wall!
>>
>> TM
>>
>>
>>
>>
>>
>> On Fri, Apr 5, 2019 at 8:08 AM John Gardner > <mailto:gof...@gmail.com> > wrote:
>>
>> OK.  sounds like you know what you're doing.
>>
>> Have you tried looping back both sides of the connection?
>>
>> On 4/5/19, John Gardner mailto:gof...@gmail.com> >
>> wrote:
>>> On the Device Manager toolbar,  click View & select "Show
>>>
>>> hidden devices".  What do you see now?
>>>
>>> I'm not familiar with Prolific-based USB to Serial devices;
>>>
>>> do you have the requisite driver loaded?
>>>
>>> On 4/5/19, John Gardner mailto:gof...@gmail.com> >
>>> wrote:
>>>> In W10,  open the Control Panel,  click on Device Manager,
>>>>
>>>> click Ports (COM & LPT) - COM1 is normally the default - Is
>>>>
>>>> that what you see?
>>>>
>>>> On 4/5/19, Thomas Morehouse >>> <mailto:nutmegfl...@gmail.com> > wrote:
>>>>> Gentlemen -
>>>>>
>>>>> I've got my 102 connected to my Win10 laptop.
>>>>>
>>>>> USB to serial cable, with null modem adapter.
>>>>>
>>>>> I've got Telcom STAT set to 57E1E.  Then I choose TERM.
>>>>>
>>>>> I've got TeraTerm set to Com6/Prolific, with port set to 1200 bps,
>>>>> 7E1,
>>>>> xon/off.
>>>>>
>>>>> Still no comms either way.  Characters typed on either device don't
>>>>> appear
>>>>> on the other device.
>>>>>
>>>>> I'm just guessing at how to use TeraTerm, as even in the help files I
>>>>> find
>>>>> no "step by step" to connecting.  In other words, what to do when.
>>>>>
>>>>> Advice from a TeraTerm user needed!
>>>>> Thanks.
>>>>> Tom M.
>>>>>
>>>>
>>>
>>
>>
>

Re: [M100] TeraTerm - still not communicating

[John Gardner]

Been there,  done that - I've had good luck with the FTDI-based

convertors sold by Adafruit.  Some good tutorials on that site too.

 https://www.adafruit.com/product/284

On 4/5/19, Jeffrey Birt  wrote:
> FWIW, I have had very bad luck with Prolific USB<->Serial converters. The
> have failed to work 90% of the time when I have tried them (on multiple
> platforms, applications, etc.)
>
>
>
> FDTI converters are much better, far, far fewer issues.
>
>
>
> I’m not saying for certain that the Prolific adapter is your issue but if it
> were me, I would suspect it.
>
>
>
> Jeff_Birt (Hey Birt!)
>
>
>
>
>
> From: M100  On Behalf Of Thomas
> Morehouse
> Sent: Friday, April 5, 2019 7:15 AM
> To: m...@bitchin100.com
> Subject: Re: [M100] TeraTerm - still not communicating
>
>
>
> John - sorry, but I'm a dolt.  Unfortunately I have no idea what "looping
> back both sides" means.
>
>
>
> Hitting a brick wall!
>
> TM
>
>
>
>
>
> On Fri, Apr 5, 2019 at 8:08 AM John Gardner  <mailto:gof...@gmail.com> > wrote:
>
> OK.  sounds like you know what you're doing.
>
> Have you tried looping back both sides of the connection?
>
> On 4/5/19, John Gardner mailto:gof...@gmail.com> >
> wrote:
>> On the Device Manager toolbar,  click View & select "Show
>>
>> hidden devices".  What do you see now?
>>
>> I'm not familiar with Prolific-based USB to Serial devices;
>>
>> do you have the requisite driver loaded?
>>
>> On 4/5/19, John Gardner mailto:gof...@gmail.com> >
>> wrote:
>>> In W10,  open the Control Panel,  click on Device Manager,
>>>
>>> click Ports (COM & LPT) - COM1 is normally the default - Is
>>>
>>> that what you see?
>>>
>>> On 4/5/19, Thomas Morehouse >> <mailto:nutmegfl...@gmail.com> > wrote:
>>>> Gentlemen -
>>>>
>>>> I've got my 102 connected to my Win10 laptop.
>>>>
>>>> USB to serial cable, with null modem adapter.
>>>>
>>>> I've got Telcom STAT set to 57E1E.  Then I choose TERM.
>>>>
>>>> I've got TeraTerm set to Com6/Prolific, with port set to 1200 bps, 7E1,
>>>> xon/off.
>>>>
>>>> Still no comms either way.  Characters typed on either device don't
>>>> appear
>>>> on the other device.
>>>>
>>>> I'm just guessing at how to use TeraTerm, as even in the help files I
>>>> find
>>>> no "step by step" to connecting.  In other words, what to do when.
>>>>
>>>> Advice from a TeraTerm user needed!
>>>> Thanks.
>>>> Tom M.
>>>>
>>>
>>
>
>

Re: [M100] TeraTerm - still not communicating

[John Gardner]

OK.  sounds like you know what you're doing.

Have you tried looping back both sides of the connection?

On 4/5/19, John Gardner  wrote:
> On the Device Manager toolbar,  click View & select "Show
>
> hidden devices".  What do you see now?
>
> I'm not familiar with Prolific-based USB to Serial devices;
>
> do you have the requisite driver loaded?
>
> On 4/5/19, John Gardner  wrote:
>> In W10,  open the Control Panel,  click on Device Manager,
>>
>> click Ports (COM & LPT) - COM1 is normally the default - Is
>>
>> that what you see?
>>
>> On 4/5/19, Thomas Morehouse  wrote:
>>> Gentlemen -
>>>
>>> I've got my 102 connected to my Win10 laptop.
>>>
>>> USB to serial cable, with null modem adapter.
>>>
>>> I've got Telcom STAT set to 57E1E.  Then I choose TERM.
>>>
>>> I've got TeraTerm set to Com6/Prolific, with port set to 1200 bps, 7E1,
>>> xon/off.
>>>
>>> Still no comms either way.  Characters typed on either device don't
>>> appear
>>> on the other device.
>>>
>>> I'm just guessing at how to use TeraTerm, as even in the help files I
>>> find
>>> no "step by step" to connecting.  In other words, what to do when.
>>>
>>> Advice from a TeraTerm user needed!
>>> Thanks.
>>> Tom M.
>>>
>>
>

Re: [M100] TeraTerm - still not communicating

[John Gardner]

On the Device Manager toolbar,  click View & select "Show

hidden devices".  What do you see now?

I'm not familiar with Prolific-based USB to Serial devices;

do you have the requisite driver loaded?

On 4/5/19, John Gardner  wrote:
> In W10,  open the Control Panel,  click on Device Manager,
>
> click Ports (COM & LPT) - COM1 is normally the default - Is
>
> that what you see?
>
> On 4/5/19, Thomas Morehouse  wrote:
>> Gentlemen -
>>
>> I've got my 102 connected to my Win10 laptop.
>>
>> USB to serial cable, with null modem adapter.
>>
>> I've got Telcom STAT set to 57E1E.  Then I choose TERM.
>>
>> I've got TeraTerm set to Com6/Prolific, with port set to 1200 bps, 7E1,
>> xon/off.
>>
>> Still no comms either way.  Characters typed on either device don't
>> appear
>> on the other device.
>>
>> I'm just guessing at how to use TeraTerm, as even in the help files I
>> find
>> no "step by step" to connecting.  In other words, what to do when.
>>
>> Advice from a TeraTerm user needed!
>> Thanks.
>> Tom M.
>>
>

Re: [M100] TeraTerm - still not communicating

[John Gardner]

In W10,  open the Control Panel,  click on Device Manager,

click Ports (COM & LPT) - COM1 is normally the default - Is

that what you see?

On 4/5/19, Thomas Morehouse  wrote:
> Gentlemen -
>
> I've got my 102 connected to my Win10 laptop.
>
> USB to serial cable, with null modem adapter.
>
> I've got Telcom STAT set to 57E1E.  Then I choose TERM.
>
> I've got TeraTerm set to Com6/Prolific, with port set to 1200 bps, 7E1,
> xon/off.
>
> Still no comms either way.  Characters typed on either device don't appear
> on the other device.
>
> I'm just guessing at how to use TeraTerm, as even in the help files I find
> no "step by step" to connecting.  In other words, what to do when.
>
> Advice from a TeraTerm user needed!
> Thanks.
> Tom M.
>

Re: [M100] Display goes blank when plugged into power adapter

[John Gardner]

We've all done it,  Eric.  Welcome to the club..."8(

 ...


On 4/2/19, Eric Miller  wrote:
> Well, I feel silly. I tried it again and it’s working. Is it a mechanical
> switch on the power adapter port that switches off the battery supply?
>
> The power strip it was plugged into wasn’t plugged into the wall outlet!
>
> #SlapPalmToForehead
>
> On Tue, Apr 2, 2019 at 7:12 PM Josh Malone  wrote:
>
>> Study the Tandy 100 service manual. It's really excellent. You can find
>> it
>> in the internet archive or club 100.
>>
>> On Tue, Apr 2, 2019, 6:54 PM Eric Miller 
>> wrote:
>>
>>> Thanks for the advice. This will be a learning experience for me. I’ve
>>> done some minor assembly projects - mostly Raspberry PI stuff.
>>> Diagnostics
>>> and repair is new to me.
>>>
>>> Time to break out the books and YouTube videos!
>>>
>>> On Tue, Apr 2, 2019 at 2:39 PM Josh Malone 
>>> wrote:
>>>
 I salvaged one from a parts machine. But I used a M100 xfrmr in a M102
 and it worked fine. It's a fugly dead-bug install, but functional. I
 have a vague feeling that I located an electrically-compatible but
 physically wrong part online but have no notes to that effect.

 -Josh

 On Tue, Apr 2, 2019 at 2:33 PM Fugu ME100  wrote:
 >
 > Which model transformer did you use?
 >
 > I have been looking for a replacement but have not really found one.
 > Thanks!
 >
 > On 2/4/19, 11:28 AM, "M100 on behalf of Josh Malone"
 > >>> > josh.mal...@gmail.com>
 > wrote:
 >
 > I've also had to replace the transformer on a unit, though that one
 > was
 > exhibiting complete power-on failure.
 >
 >

>>> --
>>> Eric Miller
>>> http://pragmaticpizza.blogspot.com/
>>> https://github.com/eric-john-miller
>>>
>> --
> Eric Miller
> http://pragmaticpizza.blogspot.com/
> https://github.com/eric-john-miller
>

Re: [M100] Multiplan Question

[John Gardner]

Still moving,  Kurt,  but I won't forget.

 ...

Re: [M100] Noob squared

[John Gardner]

While you contemplate your options,  stop charging the internal

NiCd  -  As in,  remove the AAs,  and unplug external power.

 ...


On 12/17/18, Kevin Becker  wrote:
> I replaced mine with a NiMH battery from eBay.  The description claimed it
> was NiCad but the actual product was not.  There has been some debate about
> NiMH vs NiCad on the list.  I’ve had no trouble with my NiMH.  Arcade
> shopper sells both NiCad and NiMH.
>
> https://www.arcadeshopper.com/wp/?page_id=11#!/100-102-200/c/28313042/offset=0=nameAsc
>
>
>
>> On Dec 17, 2018, at 3:13 PM, Jeffrey Birt  wrote:
>>
>> I did a video last year on fixing a M100 with the same issues. There is a
>> link in the description to a color-coded map of the electrolytic caps and
>> part number for replacements. I used a super-cap instead of a battery, but
>> it won’t last as long backing up the memory (perhaps 3-4 days compared to
>> a few weeks or more with a battery.) For a battery use a NiMh I don’t have
>> a part number to hand but I’m sure somebody will chime in with one.
>>
>> https://www.youtube.com/edit?o=U_id=hbLWk7ir9sI
>> 
>>
>> Jeff_Birt
>>
>> From: M100 > > On Behalf Of Charles Hudson
>> Sent: Monday, December 17, 2018 1:48 PM
>> To: m100@lists.bitchin100.com 
>> Subject: [M100] Noob squared
>>
>> Thank you for your replies.  I found them in the archives; I'm not sure
>> how to access the (current) list itself.  I couldn't find a "reply" option
>> on any of the messages.  I'm also not sure why the JPG picture I attached
>> was "scrubbed" from my initial message.  As I said, I've got a lot to
>> learn...
>>
>> But THANK YOU for pointing out the possible problem with the rechargeable
>> battery.  When I first got the machine, seven days ago, I tried turning it
>> on; nothing happened.  Then I tried turning it on with a 6 VDC adapter -
>> again nothing - and finally inserted four fresh AA alkaline batteries.
>> Eventually it came up.  I knew there was a rechargeable battery that
>> maintained settings but I would have assumed it merely needed to be
>> recharged.  I opened the case just now and found that the battery had
>> indeed corroded its case and possibly leaked onto the circuits adjacent.
>> I'd show you a picture but I don't know how to post one...
>>
>> However, this repair, now prioritized, raises some questions of its own.
>> I didn't see a wiki on how to make this repair so allow me to ask:
>>
>> - What do I need to look out for when removing the circuit board?
>> - Which battery and what voltage for a replacement? 3.6 V?  NiCd? Li?
>> - What do the gurus recommend for cleaning the traces?
>>
>> Gonna get right on this.  Thanks again.
>>
>> -CH-
>>
>>
>>
>>
>>
>> 
>> 
>>   
>> Virus-free. www.avast.com
>> 
>>
>
>

Re: [M100] Multiplan Question

[John Gardner]

Will do.  Memory claims there were two ROMs - One

marked "TS-DOS",  & an unmarked chip  I assumed

was the OEM 8201a ROM.

Its possible that's what it really was,  I suppose...

 ...


On 12/17/18, Kurt McCullum  wrote:
> John,
>
> If you get a chance to check, and it does contain the ROM, please let me
> know. That is one ROM that has fallen through the cracks over time.
> Kurt
>
>
> On Mon, Dec 17, 2018, at 10:25 AM, John Gardner wrote:
>> I still have the machine - Not sure about the ROM / manual.
>>
>> ...
>>
>>
>> On 12/17/18, Kurt McCullum  wrote:
>>> An NEC version or a Tandy version? The Tandy 100/102 ROM is on the
>>> Club100 site and on the REX download ZIPs. If you have the NEC
>>> versions,>> I'd love to get a download of the ROM image.
>>>
>>> On Mon, Dec 17, 2018, at 10:19 AM, Wayne Talbot wrote:
>>>> I have a machine and a Multiple rom. I used it quite a bit doing
>>>> financials.>
>>>>
>>>> On Mon, Dec 17, 2018, 11:53 AM Kurt McCullum
>>>> > __
>>>>> Thanks Jack,
>>>>>
>>>>> That's the first confirmation that I have received that the ROM
>>>>> actually exits. I take it you not longer have the machine or ROM?>>>>>>
>>>>> Kurt
>>>>>
>>>>>
>>>>> On Mon, Dec 17, 2018, at 9:50 AM, John Gardner wrote:
>>>>>> Kurt,  it's a long time ago now (1994?) but an 8201a
>>>>>>
>>>>>> I purchased at a surplus store came with a Multiplan
>>>>>>
>>>>>> manual in a Ring Binder.  I'm pretty sure there was a
>>>>>>
>>>>>> ROM too,  but so far don't remember what became of it.
>>>>>>
>>>>>> HTH...
>>>>>>
>>>>>> Jack
>>>>>>
>>>>>> ...
>>>>>
>>>
>>>
>
>

Re: [M100] Multiplan Question

[John Gardner]

Kurt,  it's a long time ago now (1994?) but an 8201a

I purchased at a surplus store came with a Multiplan

manual in a Ring Binder.  I'm pretty sure there was a

ROM too,  but so far don't remember what became of it.

HTH...

   Jack

 ...

Re: [M100] Olivetti M-10's for a new home

[John Gardner]

Suggestion - Remove all power,  connect a 1K resistor across

the NiCd.  Let it percolate overnight & remove the resistor, plug

it back in.

On 12/3/18, Mauro Pintus  wrote:
> Unfortunately the unit is not working and yes I tried the cold start
> (CTRL+PAUSE then Reset) without luck.
>
> Thanks
>Mauro
>
> Sent from my iPad
>
> On 04/dic/2018, at 00:02, "John R. Hogerhuis"  wrote:
>
>> So is it working now? Did you do a cold start?
>>
>> On Mon, Dec 3, 2018, 2:57 PM Mauro Pintus >> Hi Mike,
>>> I tried to replace the NiCd battery leaving the unit without battery
>>> for few days and when I applied the new one I left it on charge without
>>> turning on the unit for couple of days.
>>> I think this should have cleared the garbage in the RAM :)
>>> I also replaced most of the electrolitic capacitors and the voltage
>>> levels are fine.
>>> I managed to test also the LCD and it works correctly.
>>>
>>> Thank you
>>> Mauro
>>>
>>> Sent from my iPad
>>>
>>> On 03/dic/2018, at 23:14, "Mike Stein"  wrote:
>>>
 Might just need a short rest and a cold boot; turning off the memory
 switch might well have scrambled the RAM contents.
 - Original Message -
 From: Mauro Pintus
 To: m...@bitchin100.com
 Sent: Monday, December 03, 2018 5:00 PM
 Subject: Re: [M100] Olivetti M-10's for a new home

 Hi Jan,
i actually don't know for sure which component is preventing it to
 complete the boot.
 It was warking fine while accidentally I flipped off the NiCd battery
 switch.
 Now if I turn it on nothing appear on the display, I can just regulate
 the contrast...
 I tried to blindly write a basic loop to make it beep but it doesn't
 work.
 My hope was to have a working unit to use as a reference.
 I discussed this repair couple of time here in the list and several
 people provided so many useful informations.
 Non i know better my M10 but I havent identifyed yet the culprit.

 Checking some signals with the oscilloscope it looks like it is looping
 after a fix time without completing the boot.

 Francesco Messineo (another user of this list) wrote me in this days to
 offer some help and he suspect I damaged the RAM. Thank you again
 Francesco.
 I bought a desoldering iron and I hope in the next few days I'll find
 the time to try removing all RAM modules and fit one at a time in the
 first socket (hoping one module is still alive).

 Before I'll do this I was wondering if someone have a custom ROM that
 will test the RAM or other hardware peripherals providing some kind of
 feedback on a GPIO or something like that.

 Mauro

 BTW Francesco has a Youtube channel related to retro computer that worth
 mention:

 https://www.youtube.com/iz8dwf



 Sent from my iPad

 On 03/dic/2018, at 19:06, Jan Vanden Bossche 
 wrote:

> Mauro,
>
> What do you need to repair your M-10?
>
> Greetings from the TyRannoSaurus
> Jan-80
>
>
> From: Mauro Pintus 
> To: m...@bitchin100.com
> Sent: Saturday, 1 December 2018, 16:12
> Subject: Re: [M100] Olivetti M-10's for a new home
>
> Thank you Jeff, really appreciated.
> Now I keep my finger crossed :)
>
> Have a nice day
>
> Mauro
>
>
>
> On Dec 1, 2018, at 3:59 PM, Jeffrey Birt wrote:
>
>> Mauro,
>>
>> You have a need for them, so you should have them if the original
>> person does not speak up. Fixing your machine is a better use. I have
>> no specific need, just thought it would be neat to have a machine with
>> AZERTY keyboard.
>>
>> Jeff_Birt
>>
>> From: M100  On Behalf Of Mauro
>> Pintus
>> Sent: Saturday, December 1, 2018 7:50 AM
>> To: m...@bitchin100.com
>> Subject: Re: [M100] Olivetti M-10's for a new home
>>
>> I was soo exited I didn't see the other answer from Jeffrey, I'm
>> sorry...
>> Hope we can find an agreement, I'm really interested but I don't want
>> bother anyone.
>>
>> Mauro
>>
>>
>>
>> On
>
>
>
>

Re: [M100] Always connect

[John Gardner]

 ... she thought I was a weirdo...

And that was before she found out about MTs,  eh?

She must be quite a gal...  "8)

Re: [M100] Magic Goto

[John Gardner]

...a small bit of machine code would go a long way...

Indeed.  A small bit of embedded machine code even

more so...

 ...


On 11/16/18, John R. Hogerhuis  wrote:
> Interesting. Well if you can get to line zero you can probably get the
> string token that follows the gosub without a huge amount of trouble. I
> wouldn't expect performance to be great though. A small bit of machine code
> would go a long way.
>
> -- John.
>

Re: [M100] NaNoWriMo

[John Gardner]

Can't speak to Tandys,  but it works fine on my NECs, &

other senescent stuff like HPLXs,   (TI) CC40s & TI-74s...

On 11/1/18, Josh Malone  wrote:
> On Thu, Nov 1, 2018 at 4:38 PM John Gardner  wrote:
>>
>> If you need a serial port for your W8/W10 PC,  spring for one
>> of these:  https://www.adafruit.com/product/284($14.50 USD)
>> and install a (free) terminal emulator if you don't have one (Tera
>
> That's a TTL-level device - not the RS-232 level type needed to use
> the serial port on the M100. Does this work for you to the Tandy??
>
> -Josh
>

Re: [M100] NaNoWriMo

[John Gardner]

If you need a serial port for your W8/W10 PC,  spring for one

of these:  https://www.adafruit.com/product/284($14.50 USD)

and install a (free) terminal emulator if you don't have one (Tera

Term is one of many) and you're in business.

Guaranteed genuine FTDI,  & works great.

On 11/1/18, Russell Flowers  wrote:
> I used my M100 way back in 2005. It was perfect for writing close to the
> 1700 words per day I needed during my lunch hour. At night I would transfer
> the text through the serial port. (I think back then my desktop had an
> RS-232 serial port as well as USB.)
>
> On Thu, Nov 1, 2018 at 2:50 PM Josh Malone  wrote:
>
>> How did it go using the Tandy? My quick estimate says you can't store
>> anywhere close to 50k words in the Tandy memory. Did you use a tpdd
>> device
>> of some kind? Split into chapters?
>>
>> -Josh
>>
>> On Thu, Nov 1, 2018, 15:31 Kevin Becker >
>>> It’s that time of the year again and the perfect reason to break out
>>> you Model 100/102 for an hour or so each day.
>>>
>>> Anyone else participating? Last year was my first attempt and I really
>>> liked using my T102 as a distraction-free writing tool.
>>>
>>
>

Re: [M100] NEC 8201 rechargeable battery packs and BERG jacks

[John Gardner]

As far as I'm aware,  no NiMH manufacturer recommends

trickle-charging;  the OEM rechargeable pack used NiCd,

not NiMH.  Using NiMH in the regular pack works fine,  and

if you charge the cells individually in a smart charger like the

Maha C-9000 you'll get quite a few more cycles,  IME.

On 10/28/18, Anthony Coghlan  wrote:
> Hi - hope everyone is having a good weekend.  Has anyone ever used the
> DuPont BERG jacks on the NEC-8201?  The manual describes them as 19,200
> baud serial ports, basically.  Wondering for what they might be useful.
>
> Also, does anyone have experience refurbishing a rechargeable battery pack
> for the 8201 with modern rechargeable batteries?  Does this work and does
> the battery pack still charge well from the original power supply, despite
> much higher modern capacities?  Is one better off just using rechargeable
> batteries in a regular battery pack?  Is there a way to adapt a regular
> pack to charge rechargeable batteries?  Thanks - lots of questions...
>
> Best wishes,
> Anthony
>

Re: [M100] Audacity

[John Gardner]

 "8)

On 10/5/18, John R. Hogerhuis  wrote:
> What's a curd bypass? Google sends me to weight watchers.
>
> On Fri, Oct 5, 2018, 4:33 PM Jesus R  wrote:
>
>> This week I have been working with Stephen off line to find the "issue".
>> At first I didn't think there was an "issue", but Stephen rightfully
>> stuck
>> to his conviction and made me curious. Two computers, two Audacity, T100,
>> T200, Logitech A/D, and PS Audio A/D where all systematically tested and
>> nothing would produce a square wave. Since the only thing left to check
>> was
>> the cable I made a curd bypass and BAM square wave at last. I'm going to
>> make a cable today to continue with the archive operation, but is anyone
>> making a new cable?
>>
>> Jesus R
>>
>

Re: [M100] laser pc4

[John Gardner]

Hi Bert -

The seeming conundrum of 16-bit addressing of > 64K

is accomplished by switching "Banks" of memory - For

instance my 8201a has a 32K ROM,  & 3 banks of 32K

RAM which may be addressed at any one time.

Further,  there's a system bus connector which allows a

plug-in 128K RAM cartridge - Which is also expandable;

pretty slick,  really...

   Jack

On 9/29/18, John R. Hogerhuis  wrote:
> On Sat, Sep 29, 2018, 7:02 AM Bert Put  wrote:
>
>> Is that correct?  2 Meg of ROM but only 32K of RAM?  I thought the Z80
>> could only address 64K of memory at a time.
>>
>> And BTW, in case no one has said it, thank you for helping keep the list
>> a fun place to be. :-)
>>
>
> Well the 8085 only has 64k of address space but we have 64k of rom and 32k
> of ram. Unless you have a REX in which case it's comparable to the Laser.
>
> It's good to be able to fit more applications.
>
> As to the list, I just sweep the floors :-) Everyone who participates in
> these discussions, brings new programs and hardware to the group, supports
> each other make it fun.
>
> -- John
>
>>
>

Re: [M100] PC to T102 transfer using T-Dos problems

[John Gardner]

You're right - Thanks.

 ...


On 9/14/18, John R. Hogerhuis  wrote:
> That's my understanding.
>
> Correction on the name, LapDOS
>
> http://www.club100.org/library/doc/lapdosii.html
>
> On Fri, Sep 14, 2018 at 1:12 PM Kurt McCullum  wrote:
>
>> Does Laplink require a client on the Model T?
>>
>>
>

Re: [M100] PC to T102 transfer using T-Dos problems

[John Gardner]

Laplink in DOSBox or Virtual PC worked fine on the 8201a,

is my recollection.

 ...

Re: [M100] call for programs and games

[John Gardner]

Zmodem's a load,  Roger that...   "8)

Re: [M100] call for programs and games

[John Gardner]

...If you could make room for only one thing in the main rom, would it
be a tpdd dos, or xmodem?

How about Z-Modem?   "8)

On 9/11/18, Kurt McCullum  wrote:
> UR-II and Sardine both have TS-DOS code that is stripped down to the
> bare minimum. Basically just a loader for a specific filename (DOS100.CO
> or SAR100.CO). Sardine has the same loader plus a couple other features.
> The TPDD protocol works. It may not be the 'standard' for anything but
> our Model-Ts but after all these years that's what we've got. Having TS-
> DOS in ROM solves a lot of problems.
> Kurt
>
>
> On Tue, Sep 11, 2018, at 3:19 PM, Brian White wrote:
>> If you could make room for only one thing in the main rom, would it be
>> a tpdd dos, or xmodem?>
>> Remember, tpdd was only one of a few different kinds of disks, it's
>> only a sort of defacto standard now because of various reasons,
>> probably mostly because it works over the serial port and the protocol
>> was simple enough to be reverse engineered and re-implimented by
>> others, making all the emulators possible.> If I had to choose one thing
>> to go right into the main rom, I think I
>> might actually go with xmodem or y or zmodem or kermit etc, some
>> standard generic binary capable serial protocol, rather than tpdd. And
>> rts/cts support in TELCOM & BASIC.> That's probably the single thing about
>> the 600 that I like. It has
>> xmodem built in to it's telcom app, and that makes it no problem to
>> recover from resets any time any where. You can regenerate the utility
>> disk and install BASIC from scratch with just a serial cable and the
>> downloaded files.> What other things would people say should be in there,
>> after 30 years
>> of hindsight? How about, rather than some more software baked in, just
>> more, and more useful hooks? Like how UR2 loads TS-DOS without
>> containing TS-DOS, or like the few hooks that do exist that the DVI
>> uses, but more and better?> How about... the MFORTH rom with a minimal set
>> of baked-in features,
>> maybe implemented in forth themselves. Like right now there are a
>> bunch of ML routines that various utils and BASIC all use, while this
>> would be forth has all the ml, and everything else just uses forth.
>> And the bulk of apps and utils would be forth programs in ram and as
>> little as possible in rom. Use as much of the rom space as possible to
>> make forth itself as good as possible. And the rom just has enough
>> features baked-in to make it easy to load the real apps from elsewhere
>> any time.> I guess really I wouldn't want any rom at all except just
>> something
>> tiny that didn't do anything except load the real "os" from somewhere
>> else, so you could do that forth idea and then have an updated forth
>> the next year, but I'm trying to stay within the context of 1983 and
>> Tandy's cost and time limits.>
>>
>>
>> On Tue, Sep 11, 2018 at 4:03 PM Kevin Becker
>>  wrote:>> SCHEDL and ADDRSS could both go for me,
>> but I suspect they are
>>> pretty small>>
>>> On Tue, Sep 11, 2018 at 3:56 PM, you got me
>>>  wrote:>>> would ts-dos fit on the main rom if
>>> SCHEDULE was taken off? Who
 uses that?>>>
 *From:* M100  on behalf of Kurt
 McCullum  *Sent:* Tuesday, September 11, 2018
 7:42:24 PM *To:* m100@lists.bitchin100.com *Subject:* Re: [M100]
 call for programs and games>>>

 This brings a question to mind. The Tandy 200 and NEC 8201 (and
 8300) have multiple banks. Since the 27c512 is identical to the
 27c256 ROM with the exception of pin 1 which is for address 15.
 Could a 27C512 be inserted with pin 1 bent to stick out to the side
 and then a wire run from pin 1 to the enable pin of bank 2? So
 switching banks also switches OptRoms?>>>
 I have read an article about installing a switch to do this but I
 wasn't sure if this could be done by taping the existing hardware.>>>
 Kurt


 On Tue, Sep 11, 2018, at 9:36 AM, Mike Stein wrote:
> 
> Another simple approach that's often used is to have an adapter
> with an (E)EPROM large enough to hold several ROM images and a
> physical (or logical) switch to select among them (essentially what
> my adapter does, but with only one OptROM image).
> Unfortunately there's very little vertical clearance in these
> babies so there's not much room to use the old trick of stacking
> several chips with the select lines brought out the side. I haven't
> looked at my T102 but in the M100 there is enough room for one piggy-
> backed chip which would give you at least three 32KB OptROM images,
> but it does lift the keyboard slightly unless you remove the
> socket; depending on the socket used you might also gain some
> clearance if you trim the IC leads.
> Another approach to using several and/or larger ROMs is to make a
> little board that puts the chips upside down in the space beside
> the system ROM; as  a matter of fact the plan with this 

Re: [M100] Question 8085 Model T assembly - RST 4

[John Gardner]

RSTs are software interrupts.  Intel's 8085 manual is a good

source for this stuff,  or you can look at this...

http://www.idc-online.com/control1/Interrupts_of_intel_8085.pdf

On 9/10/18, Bob Pigford  wrote:
> Hello,
>
>
>
> From time to time when studying others' asm listings for ModelT's, I find
> an
> opcode called RST 4.
>
> I have not yet found this documented anywhere.  What does RST 4 do?
>
>
>
> Thanks for your help,
>
>
>
> Bob
>
>

Re: [M100] Power on/off issues on M100

[John Gardner]

All good points - I switched my two 8201a's to 3F supercaps after

losing a 20-year-old 386 to a leaking NiCd RTC battery,  some 8

years ago now.  Basically a drop-in replacement,  with no issues

to date.  My memory retention scheme is to keep Eneloop AAs in

the laptops - Their low self-discharge seems to keep RAM alive

forever,  & the supercaps cover battery replacement,  for several

weeks in the few tests I've run -  I don't actually know how long the

caps will retain memory without the battery.

Do Eneloops/supercaps leak?  There are a few reports online,  but

it seems to be an unusual problem  -  Which is'nt the case with NiCds.

If NiCd is the only option I'd change it regularly -  5 years is probably

overkill - 10 years probably is'nt.





On 9/10/18, Brian White  wrote:
> I believe other people have reported mixed results replacing the battery
> with a cap. Some people have had good luck, others not, and some said it
> worked fine on their 100's but not their 200, etc.
> The battery should really only be a nicd or nimh. I think the idea for the
> caps was they wouldn't leak, but they leak and degrade too because they are
> not solid state.
>
> The only advantage I can see to caps is that caps aren't hurt by sitting
> dead, even for long periods, while draining all the way dead, and
> especially staying dead for any time does hurt batteries.
>
>
> On Mon, Sep 10, 2018 at 9:50 AM Josh Malone  wrote:
>
>> On Mon, Sep 10, 2018 at 9:32 AM Gregory McGill 
>> wrote:
>> >
>> > Flakey memory power switch?
>>
>> When I got the machine, I was initially suspicious of the memory power
>> switch, so I cleaned it with alcohol.
>>
>> However, if it were the memory power switch, why would it power up
>> after the external power was removed and re-applied. Genuinely curious
>> as to ways this could happen. I'm not familiar enough with the M100
>> power circuit and I haven't had time to study the schematic like I'd
>> hoped. :-/
>>
>> -Josh
>>
>
>
> --
> bkw
>

Re: [M100] Serial data receive problems

[John Gardner]

"Lack of proper transient protection" ...  Would'nt be the first time...

On 8/23/18, Josh Malone  wrote:
> On Thu, Aug 23, 2018 at 3:25 PM Jeffrey Birt  wrote:
>>
>> It is interesting that all of them had the same failure. Given that we
>> don’t know what percentage of Inerstil vs. other brands they might have
>> used it is always hard to say if the issue is a bad chip design, lack of
>> proper transient protection on the rx, or dumb luck. In other words if
>> they used the same Inerstil chip 95% of the time and it had the made
>> failure rate as brand x then 95% of the failed UARTs you would come across
>> would be Inerstill. Hope that makes sense…
>
>
> Yes - it makes perfect sense and that's what I was thinking as well. I
> have 3 100s in my possession currently -- 2 use Harris, 1 uses
> Intersil. The two other failures I've heard about use Intersil. We'd
> need a LOT more data points to confirm it, but I think we might be
> looking at a correlation here. The failure mode also seems consistent:
> The UART fails to assert DR when the RX buffer receives data. At least
> that can be documented as a likely cause for serial (TELCOM, TS-DOS,
> etc.) comms issues with the M100.
>
> Has anybody seen this is a 102?
>
> -Josh
>

Re: [M100] New Age Digital Storage Box (NADSBox)

[John Gardner]

Feel better now?   "8)   OK,  suit yourself.

On 8/21/18, Brian White  wrote:
> On Mon, Aug 20, 2018, 8:16 PM John Gardner  wrote:
>
> Brian,  here's an idea - How about junking the html so I can read
>
> your interesting posts without converting them to text files first...
>
> Just a suggestion - My 70-year-old eyesight would appreciate it.
>
>
> Ok, just remember who started this conversation...
>
> You have the burden of obligation and consideration backwards.
>
> Whatever validity of argument you might have had about violating
> traditional old standards in email, or about being considerate to others in
> formatting email, fell apart when you presented that argument in a
> top-post, and quoted the entire thread instead of only the relevant bit. ;)
>
> Not to mention, without a client that understands html, or at least mime,
> to supply metadata about such things as character encoding and font spacing
> type, then you are essentially expecting everyone in the world to have the
> same native default character encoding and font as you.
>
> My email is gmail, which, at least the standard Android app for it, does
> not offer any setting for composing in plain-text only, but, as has been
> mentioned, does apparently generate a multipart mime formatted mail with a
> plain-text part. Today, I don't think it's reasonable to ask someone else
> not to use gmail.
>
> If you are reading email in pine or mutt in 2018, well I applaud you, but I
> consider that your choice to self-flaggelate, not anyone else's reasonable
> obligation to cater to.
>
>
> --
> bkw
>

Re: [M100] New Age Digital Storage Box (NADSBox)

[John Gardner]

Brian,  here's an idea - How about junking the html so I can read

your interesting posts without converting them to text files first...

Just a suggestion - My 70-year-old eyesight would appreciate it.

thanks,

Jack

On 8/20/18, c646581  wrote:
> I'm sure it'd be possible to program a M100 simulator for the
> Arduino/Arduino Mega, but it'd be difficult and have tons of overhead.
> Running one of the off-the-shelf simulators on a Raspberry Pi is much more
> doable, but you're just slaving a much more powerful device to the M100.
>
> I like using Arduino devices because they're not extremely overkill for the
> task. My SD2TPDD emulator will run on a regular Arduino, but I want room to
> expand for more features in the future.
>
> On Mon, Aug 20, 2018, 16:40 Jeff Gonzales  wrote:
>
>> Yeah, but if you're bringing an Arduino into the picture why not just
>> build a new unit around it?  Or gut an m100 and use it directly with the
>> keyboard and screen?
>>
>> On Mon, Aug 20, 2018 at 4:38 PM, Kurt McCullum 
>> wrote:
>>
>>> Not for loading and storing files. That requires a TPDD client running
>>> on
>>> the m100. But when you go to TELCOM to do anything, you are basically a
>>> vt52 terminal.
>>>
>>> Kurt
>>>
>>>
>>> On Mon, Aug 20, 2018, at 1:34 PM, Jeff Gonzales wrote:
>>>
>>> at this point is the m100 just a keyboard/dumb terminal?
>>>
>>> On Mon, Aug 20, 2018 at 4:31 PM, c646581  wrote:
>>>
>>> I have a project that uses an Arduino Mega to emulate a TPDD.
>>>
>>> https://github.com/TangentDelta/SD2TPDD
>>>
>>> I have plans to eventually sell easy-to-use shields that provide the
>>> RS232 level shifting and SD card interface.
>>>
>>> On Mon, Aug 20, 2018, 16:02 Brian White  wrote:
>>>
>>> A tpdd emulated in low level basic hardware in line with the tpdd itself
>>> really appeals to me.
>>>
>>> I would love to try to make it work on a tinyduino, or maybe a gotek.
>>> Tinyduino may not seem "basic" being so small and modern, but it's a
>>> microcontroller not a PC. It doesn't run linux and systemd and bash and
>>> getty and python and a tcp stack and ssl and X and gnome etc etc etc.
>>> The fact that an entire pc fits in a tiny space and uses no power and
>>> costs $5 today thanks to the plain advancement over the passage of time,
>>> is
>>> sort of beside the point. Sure it's practical, but it's not *elegant*,
>>> in
>>> some intangible abstract mental way.
>>> You could run dlplus or laddie from an init script on an Omega2 and
>>> stuff
>>> the entire thing inside of a db25 connector shell, and probably even
>>> scavenge enough power right from the usb port with charge pumps, and the
>>> entire thing would be small and cheap and relatively easy to do, since
>>> it's
>>> just sticking a few existing things together like legos. Outwardly this
>>> makes all the sense in the world. But it's just such a brute-force kind
>>> of
>>> solution. I'd rather spend all kinds of time and effort to do the same
>>> thing with a controller in place of the computer.
>>>
>>> Though, you can sure get a lot more functionality out of a computer,
>>> like
>>> that virtual modem in mcomm. And the computer is infinitely more
>>> end-user
>>> hackable. It would be neat to play with hacking together some sort of
>>> front-end dispatcher script, kind of like inetd for serial or I guess
>>> that
>>> would just be an amped-up getty, maybe even with an interactive menu
>>> that
>>> you can access via TELCOM, and the front end runs a tpdd server or a dos
>>> injector or ssh client or lynx or virtual modem or something else and
>>> hooks
>>> it to the tty. It could stay in the loop monitoring the tty for special
>>> escape commands to break out into a command mode just like modems,
>>> telnet,
>>> ssh, cu etc all do, so you could always switch between functions from
>>> the
>>> M100 even after starting one.
>>> gahh ideas are sure easy to throw around :)
>>>
>>>
>>>
>>
>

Re: [M100] TPDD Specifics

[John Gardner]

How about those who've benefited from the research of others,

or even the researchers themselves,  publishing the protocol?

Nah..."8)

On 7/17/18, you got me  wrote:
> If I'm not mistaken, the program Desklink emulates a TPDD. Perhaps a
> combination of DOSbox or virtual software running Desklink can help you to
> communicate and transfer files to and from a m100. Another program can be
> used to capture to/from serial data and reveal protocols for different use
> case conditions.
>
>
> It may be possible to do things the other way around: the virtual m100
> program can log serial port data I believe. Perhaps a TPDD could be
> connected to the host computer via a serial or usb to  serial adapter?
>
>
> Any more experienced people with thoughts on this?
>
> 
> From: M100  on behalf of c646581
> 
> Sent: Tuesday, July 17, 2018 10:50:58 PM
> To: m100@lists.bitchin100.com
> Subject: [M100] TPDD Specifics
>
> Hello!
>
> I'm working on a TPDD hardware emulator using low-cost
> off-the-shelf-components. I can't find much online about the specifics of
> the serial connection between the M100 and the TPDD. The TPDD protocol page
> on the wiki mentions 19200/9600 baud, but nothing about flow control or how
> it negotiates the speed.
>
> Based on trial-and-error, I did figure out that hardware flow control is
> needed before TS-DOS will try sending any data. This gives me something to
> work off of, but more details would be great.
>
> Thanks,
> Jimmy
>

Re: [M100] Low power check

[John Gardner]

I'm guessing D8.7 is write-only,  and reading that bit might produce

a meaningless result.

Its also possible there's a read-modify-write problem with reading

& writing the ports directly - Some test routines use logical operators

rather than direct reads/writes...

On 6/28/18, Kurt McCullum  wrote:
> Thanks for the tip. I just tried that one but I get 128 for both. It
> almost seems like that flag is an indicator for the power switch. Though
> I don't know what use that is.
>
> On Thu, Jun 28, 2018, at 8:14 PM, John Gardner wrote:
>> Take a look at p. 5-30 in the 8201a Svc Manual,  figs. 5-47  &  5-48.>
>> On 6/28/18, Kurt McCullum  wrote:
>>> I wish I could say it works. but I have two 8201s here. One
>>> with a low>> battery and one without. Both show 208 when I try
>>> print inp(216)
>>>
>>> It was worth a try. I'd be interested if anyone else figures
>>> this out.>>
>>> Kurt
>>>
>>>
>>> On Thu, Jun 28, 2018, at 11:53 AM, MikeS wrote:
>>>> 
>>>> Yeah; how could we have missed that /LPS signal all this time...
>>>>
>>>> Thanks, Kurt!
>>>>> - Original Message -
>>>>> **From:** Stephen Adolph[1]
>>>>> **To:** m...@bitchin100.com
>>>>> **Sent:** Thursday, June 28, 2018 1:58 PM
>>>>> **Subject:** Re: [M100] Low power check
>>>>>
>>>>> Wow.  Very nice.  Learn something new every day.
>>>>>
>>>>> On Thursday, June 28, 2018, Kurt McCullum 
>>>>> wrote:>>>>>>> __
>>>>>> Will,
>>>>>>
>>>>>> Found it in the Robert Covington's M100 ports/registers file.
>>>>>> Port>>>>> D0 (208) is where the low power signal is. The file
>>>>>> indicates this>>>>> is the same for both the 100 and 200.>>>
>>>>>> PRINT INP(208)
>>>>>>
>>>>>> That command should give you the status of the power. Bit 7 is
>>>>>> the>>>>> indicator so the value will change by 128.>>>
>>>>>> Kurt
>>>>>>
>>>>>>
>>>>>> On Thu, Jun 28, 2018, at 10:32 AM, Kurt McCullum wrote:
>>>>>>> It's actually a INP(216) command not a PEEK(216). I didn't
>>>>>>> realize>>>>>> that when I first posted. But the memory locations on
>>>>>>> the 200
>>>>>>> would>>>>>> be different than the NEC.>>>>
>>>>>>> So for the NEC, in BASIC the following command would show the
>>>>>>> value:>>>> PRINT INP(216)
>>>>>>>
>>>>>>> Kurt
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Jun 28, 2018, at 9:53 AM, William Winter wrote:
>>>>>>>> FYI... I just tried the PEEK (216) on my Model 100 and it
>>>>>>>> returned>>>>>>> 85 with both the battery light on and off.>>>>>
>>>>>>>> -Will
>>>>>>>>
>>>>>>>> On Thu, Jun 28, 2018 at 12:42 PM Kurt McCullum
>>>>>>>>  wrote:>>>>>> __
>>>>>>>>> That's what I was afraid of. However, I did find something
>>>>>>>>> that>>>>>>>> is worth a try when I get home tonight. In the NEC
>>>>>>>>> 8201
>>>>>>>>> technical>>>>>>>> manual (yes I read these things) on page 256, it
>>>>>>>>> looks like bit
>>>>>>>>> 7>>>>>>>> of memory location D8 (216) is set when there is a low
>>>>>>>>> power
>>>>>>>>> signal.  If that is correct, a PEAK(216) which returns a
>>>>>>>>> value>>>>>>>> greater than 127 should indicate a low power state.
>>>>>>>>> But I'll
>>>>>>>>> have>>>>>>>> to test this later since I am not in front of the
>>>>>>>>> machine.>>>>>>>>>>>>>> Kurt
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Jun 28, 2018, at 9:16 AM, Stephen Adolph wrote:
>>>>>>>>>> no, I don't think so.  there is no A/D function or alarm
>>>>>>>>>> point>>>>>>>>> that is readable.  would have been a good
>>>>>>>>>> idea.>>>>>>>
>>>>>>>>>> On Thu, Jun 28, 2018 at 12:11 PM, Kurt McCullum
>>>>>>>>>>  wrote:>>>>>>>> __
>>>>>>>>>>> Is there a PEEK I can do in BASIC to see if the low power
>>>>>>>>>>> light>>>>>>>>>> is on. I would assume that the 100/200/NEC all
>>>>>>>>>>> have different>>>>>>>>>> locations in memory but is this
>>>>>>>>>>> possible?>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Kurt
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>
>>>
>>>
>>> Links:
>>>
>>> 1. mailto:twospru...@gmail.com
>>>
>
>

Re: [M100] Low power check

[John Gardner]

Take a look at p. 5-30 in the 8201a Svc Manual,  figs. 5-47  &  5-48.

On 6/28/18, Kurt McCullum  wrote:
> I wish I could say it works. but I have two 8201s here. One with a low
> battery and one without. Both show 208 when I try
> print inp(216)
>
> It was worth a try. I'd be interested if anyone else figures this out.
>
> Kurt
>
>
> On Thu, Jun 28, 2018, at 11:53 AM, MikeS wrote:
>> 
>> Yeah; how could we have missed that /LPS signal all this time...
>>
>> Thanks, Kurt!
>>> - Original Message -
>>> *From:* Stephen Adolph[1]
>>> *To:* m...@bitchin100.com
>>> *Sent:* Thursday, June 28, 2018 1:58 PM
>>> *Subject:* Re: [M100] Low power check
>>>
>>> Wow.  Very nice.  Learn something new every day.
>>>
>>> On Thursday, June 28, 2018, Kurt McCullum  wrote:>>
 __
 Will,

 Found it in the Robert Covington's M100 ports/registers file. Port
 D0 (208) is where the low power signal is. The file indicates this
 is the same for both the 100 and 200.>>>
 PRINT INP(208)

 That command should give you the status of the power. Bit 7 is the
 indicator so the value will change by 128.>>>
 Kurt


 On Thu, Jun 28, 2018, at 10:32 AM, Kurt McCullum wrote:
> It's actually a INP(216) command not a PEEK(216). I didn't realize
> that when I first posted. But the memory locations on the 200 would
> be different than the NEC.
> So for the NEC, in BASIC the following command would show the
> value: PRINT INP(216)
>
> Kurt
>
>
> On Thu, Jun 28, 2018, at 9:53 AM, William Winter wrote:
>> FYI... I just tried the PEEK (216) on my Model 100 and it returned
>> 85 with both the battery light on and off.>
>> -Will
>>
>> On Thu, Jun 28, 2018 at 12:42 PM Kurt McCullum
>>  wrote:>> __
>>> That's what I was afraid of. However, I did find something that
>>> is worth a try when I get home tonight. In the NEC 8201 technical
>>> manual (yes I read these things) on page 256, it looks like bit 7
>>> of memory location D8 (216) is set when there is a low power
>>> signal.  If that is correct, a PEAK(216) which returns a value
>>> greater than 127 should indicate a low power state. But I'll have
>>> to test this later since I am not in front of the machine.>>
>>> Kurt
>>>
>>>
>>> On Thu, Jun 28, 2018, at 9:16 AM, Stephen Adolph wrote:
 no, I don't think so.  there is no A/D function or alarm point
 that is readable.  would have been a good idea.>>>
 On Thu, Jun 28, 2018 at 12:11 PM, Kurt McCullum
  wrote: __
> Is there a PEEK I can do in BASIC to see if the low power light
> is on. I would assume that the 100/200/NEC all have different
> locations in memory but is this possible?
>
> Kurt
>
>>>
>

>
>
> Links:
>
>   1. mailto:twospru...@gmail.com
>

Re: [M100] Leads/Legs for Mike Stein System ROM PCB

[John Gardner]

...The reason it costs us 4x as much to ship small parcel 100 miles as
it does for someone in China to send us the same parcel is because we
are paying extra to subsidize what our governments lose on each parcel
Chins sends to us


I ttought it might bear repeating...

On 6/18/18, Daryl Tester  wrote:
>  On Mon, 18 Jun 2018 19:04:08 -0500, Jeffrey Birt wrote:
>
>> I meant to reply earlier when someone mentioned postage rates. If you
>> are a glutton for punishment Google the 'International Postal Union'
>> w.r.t. the subsidized shipping rates China gets on account of their
>> 'third world' status.
>
>  Thanks for this. I have been curious about the economics behind this,
>  but didn't know the right magic Google words to find out how it was
>  being achieved.
>
> --
>  Regards,
>Daryl Tester
>Handcrafted Computers Pty. Ltd.
>

Re: [M100] Leads/Legs for Mike Stein System ROM PCB

[John Gardner]

US subsidy of Chinese mail,  among other things.

 ...


On 6/17/18, Mike Stein  wrote:
> Don't know how the Chinese do it; 10 of them cost $6.00 ppd.
>
> m
>
> - Original Message -
> From: "John Gardner" 
> To: 
> Sent: Sunday, June 17, 2018 5:40 PM
> Subject: Re: [M100] Leads/Legs for Mike Stein System ROM PCB
>
>
>> Good thing you were'nt in Oz...   "8)
>>
>> ...
>>
>>
>> On 6/17/18, Mike Stein  wrote:
>>> Everybody still alive? Awfully quiet...
>>>
>>> Did you get the envelope, Greg? If I'd known that it was going to cost
>>> $8.00
>>> to send a $0.60 part I might have had second thoughts... ;-)
>>>
>>> m
>>>
>>> - Original Message -
>>> From: "Mike Stein" 
>>> To: 
>>> Sent: Monday, June 11, 2018 3:57 PM
>>> Subject: Re: [M100] Leads/Legs for Mike Stein System ROM PCB
>>>
>>>
>>> I have jars full of  bits of different diameter wire trimmed from leads
>>> of
>>> components used in volume manufacturing and I also thought of using
>>> them,
>>> but it just didn't work out; anything strong enough was usually too
>>> thick,
>>> especially when inserting into machined pin sockets.
>>>
>>> Send me your address off-list and I'll mail you one to try out.
>>>
>>> m
>>>
>>> - Original Message -
>>> From: "Greg Swallow" 
>>> To: 
>>> Sent: Monday, June 11, 2018 3:26 PM
>>> Subject: Re: [M100] Leads/Legs for Mike Stein System ROM PCB
>>>
>>>
>>>>I didn't think about what it would do to the socket. I guess I got too
>>>> worried about what the socket would do to the pins. Hmm, maybe I'll
>>>> have
>>>> to use the bare copper and flatten it a bit. Else the items you you
>>>> noted
>>>> on eBay do look like a darn good answer. Order the later for the pins.
>>>> O'll try what I can with wire while waiting for delivery from China.
>>>>
>>>> Thanks,
>>>>
>>>> GregS <><
>>>>
>>>> - Original Message -
>>>> From: "Mike Stein" 
>>>> To: m...@bitchin100.com
>>>> Sent: Monday, June 11, 2018 10:54:31 AM
>>>> Subject: Re: [M100] Leads/Legs for Mike Stein System ROM PCB
>>>>
>>>> Hi,
>>>>
>>>> Nice to see someone using those adapters; thanks!
>>>>
>>>> Of course once you've installed one you'll never want to remove it
>>>> again
>>>> ;-), but I'm always reluctant to plug anything into an IC socket that
>>>> might deform the socket (just in case).
>>>>
>>>> DIP IC pins are .010" thick whereas 20 AWG wire is around .030"; not
>>>> only
>>>> is that snug in the PCB holes but also a little thick for the socket.
>>>>
>>>> I prefer to use something with .010" pins, intended for plugging into
>>>> an
>>>> IC socket like this:
>>>>
>>>> eBay# 172138163630
>>>>
>>>> Or an even better deal (more pins for the money):
>>>>
>>>> eBay# 17115136
>>>>
>>>> It takes a few minutes during a lull watching baseball to pull the pins
>>>> and adds about $0.50 to the cost, but they are plated and well worth it
>>>> IMO..
>>>>
>>>> Insert the pins from the top (with one of those solderless breadboards
>>>> underneath to hold and align them), solder, and trim off the top part.
>>>
>

Re: [M100] Leads/Legs for Mike Stein System ROM PCB

[John Gardner]

Good thing you were'nt in Oz...   "8)

 ...


On 6/17/18, Mike Stein  wrote:
> Everybody still alive? Awfully quiet...
>
> Did you get the envelope, Greg? If I'd known that it was going to cost $8.00
> to send a $0.60 part I might have had second thoughts... ;-)
>
> m
>
> - Original Message -
> From: "Mike Stein" 
> To: 
> Sent: Monday, June 11, 2018 3:57 PM
> Subject: Re: [M100] Leads/Legs for Mike Stein System ROM PCB
>
>
> I have jars full of  bits of different diameter wire trimmed from leads of
> components used in volume manufacturing and I also thought of using them,
> but it just didn't work out; anything strong enough was usually too thick,
> especially when inserting into machined pin sockets.
>
> Send me your address off-list and I'll mail you one to try out.
>
> m
>
> - Original Message -
> From: "Greg Swallow" 
> To: 
> Sent: Monday, June 11, 2018 3:26 PM
> Subject: Re: [M100] Leads/Legs for Mike Stein System ROM PCB
>
>
>>I didn't think about what it would do to the socket. I guess I got too
>> worried about what the socket would do to the pins. Hmm, maybe I'll have
>> to use the bare copper and flatten it a bit. Else the items you you noted
>> on eBay do look like a darn good answer. Order the later for the pins.
>> O'll try what I can with wire while waiting for delivery from China.
>>
>> Thanks,
>>
>> GregS <><
>>
>> - Original Message -
>> From: "Mike Stein" 
>> To: m...@bitchin100.com
>> Sent: Monday, June 11, 2018 10:54:31 AM
>> Subject: Re: [M100] Leads/Legs for Mike Stein System ROM PCB
>>
>> Hi,
>>
>> Nice to see someone using those adapters; thanks!
>>
>> Of course once you've installed one you'll never want to remove it again
>> ;-), but I'm always reluctant to plug anything into an IC socket that
>> might deform the socket (just in case).
>>
>> DIP IC pins are .010" thick whereas 20 AWG wire is around .030"; not only
>> is that snug in the PCB holes but also a little thick for the socket.
>>
>> I prefer to use something with .010" pins, intended for plugging into an
>> IC socket like this:
>>
>> eBay# 172138163630
>>
>> Or an even better deal (more pins for the money):
>>
>> eBay# 17115136
>>
>> It takes a few minutes during a lull watching baseball to pull the pins
>> and adds about $0.50 to the cost, but they are plated and well worth it
>> IMO..
>>
>> Insert the pins from the top (with one of those solderless breadboards
>> underneath to hold and align them), solder, and trim off the top part.
>

Re: [M100] Battery Question

[John Gardner]

Hi Kurt -

"Watchdog" is a Tracy Allen pgm that's documented here -

Scroll down a bit...

http://ftp.whtech.com/club100/ref/

My stuff is in storage right now,  but what I did is use the background

task interrupt to increment a secs/mins/hours counter,  & display the

result where the M$ blurb is located on top - Pretty easy...

   Jack

On 6/13/18, Kurt McCullum  wrote:
> Jack,
>
> Glad to here it isn't just my experience. Is your watchdog.co available?
> I've toyed with building a battery pack with 10 1/3 AA cells (2 banks of
> 5). This would give me 6v but the capacity would be less than just using
> 4 regular cells.
> I have two dead 8201's that both still have good power supplies so I
> may try it on one of those. I believe the resistor change would be on
> the power supply itself. It's nice to have a bone yard of parts to
> test with.
> Kurt
>
>
> On Wed, Jun 13, 2018, at 9:03 AM, John Gardner wrote:
>> Kurt -
>>
>> NiCds are all I use in my 8201a's  -  They both act identically
>> to yours.>
>> Years ago I rearranged WATCHDOG.CO to display elapsed-time where
>>
>> the M$ blurb usually appears,  which scratched my itch for a
>> little more>
>> battery certainty.  I reset it when I change batteries  -  Not
>> perfect,  but>
>> good enough.
>>
>> If you pursue tweaking the battery light circuit I hope you write
>> it up...>
>>   Jack
>>
>>
>>
>>
>>
>> On 6/12/18, Kurt McCullum  wrote:
>>> Yes, I'm comfortable with soldering a new resistor, but the NEC was
>>> originally sold with both a NiCd battery pack and a standard Alkaline>>
>>> battery pack. The only difference between the two is the charging
>>> resistor and a jumper. I would assume that the power supply
>>> would know,>> based on the type of pack plugged in, how to adjust for
>>> this. But I
>>> have no evidence of this. I have restored both an original NiCd
>>> battery>> pack and converted a standard pack to be rechargeable. Both
>>> show the>> same behavior.
>>> Kurt
>>>
>>>
>>> On Tue, Jun 12, 2018, at 8:17 PM, Doug Jackson wrote:
>>>> Kurt,
>>>>
>>>> I'm sure it would be possible to adjust the threshold where the LED>>>
>>>> illuminates to match the new battery chemistry.  It's probably a
>>>> resistor change.>
>>>> Are you comfortable with soldering on the logic board?
>>>>
>>>> Doug
>>>>
>>>> On Wed, 13 Jun. 2018, 12:36 pm Kurt McCullum,
>>>>  wrote:>> __
>>>>> I've got several battery holders for my NEC units. I have
>>>>> converted a>>>> couple to recharge batteries by following the
>>>>> instructions on
>>>>> Web8201.net. The 71.5k resistor was the hardest part to find and in>>>>
>>>>> the end I bought 100 of them. The batteries charge fine, and
>>>>> work ok.>>>> But what I notice is that the low battery light comes one
>>>>> after only>>>> an hour or so. I can still run the machine for another
>>>>> 15+
>>>>> hours but>>>> the light is always on. This I assume is due to the fact
>>>>> that the
>>>>> batteries are 1.2v rechargeable instead of 1.5 alkaline.>>
>>>>> So my question, has anyone tried using the 1.5 rechargeable
>>>>> alkaline>>>> batteries? if so, how did it work for you.>>
>>>>> Kurt
>>>
>>>
>
>

Re: [M100] Battery Question

[John Gardner]

Kurt -

NiCds are all I use in my 8201a's  -  They both act identically to yours.

Years ago I rearranged WATCHDOG.CO to display elapsed-time where

the M$ blurb usually appears,  which scratched my itch for a little more

battery certainty.  I reset it when I change batteries  -  Not perfect,  but

good enough.

If you pursue tweaking the battery light circuit I hope you write it up...

   Jack





On 6/12/18, Kurt McCullum  wrote:
> Yes, I'm comfortable with soldering a new resistor, but the NEC was
> originally sold with both a NiCd battery pack and a standard Alkaline
> battery pack. The only difference between the two is the charging
> resistor and a jumper. I would assume that the power supply would know,
> based on the type of pack plugged in, how to adjust for this. But I
> have no evidence of this. I have restored both an original NiCd battery
> pack and converted a standard pack to be rechargeable. Both show the
> same behavior.
> Kurt
>
>
> On Tue, Jun 12, 2018, at 8:17 PM, Doug Jackson wrote:
>> Kurt,
>>
>> I'm sure it would be possible to adjust the threshold where the LED
>> illuminates to match the new battery chemistry.  It's probably a
>> resistor change.>
>> Are you comfortable with soldering on the logic board?
>>
>> Doug
>>
>> On Wed, 13 Jun. 2018, 12:36 pm Kurt McCullum,
>>  wrote:>> __
>>> I've got several battery holders for my NEC units. I have converted a
>>> couple to recharge batteries by following the instructions on
>>> Web8201.net. The 71.5k resistor was the hardest part to find and in
>>> the end I bought 100 of them. The batteries charge fine, and work ok.
>>> But what I notice is that the low battery light comes one after only
>>> an hour or so. I can still run the machine for another 15+ hours but
>>> the light is always on. This I assume is due to the fact that the
>>> batteries are 1.2v rechargeable instead of 1.5 alkaline.>>
>>> So my question, has anyone tried using the 1.5 rechargeable alkaline
>>> batteries? if so, how did it work for you.>>
>>> Kurt
>
>

Re: [M100] XIP ML in BAISC

[John Gardner]

Another use for DATA statements is parameter passing

& storage.

On 6/5/18, Ken Pettit  wrote:
> Hey Steve,
>
> A minor edit to your summary.  For the hidden lines, you don't need to
> avoid codes < 32 decimal, other than 00h, quote and comma as identified,
> though they are harder to edit if you do use codes < 32.
>
> Ken
>
> On 6/5/18 4:31 AM, Stephen Adolph wrote:
>> so, As a summary, I think this is what is new here:
>>
>> * Ken has demonstrated that XIP ML can be embedded in a basic program
>> that can run anywhere
>> * John has illuminated the fact that there are hidden basic lines
>> * by using hidden lines, one can create a very compact hybrid ML/BASIC
>> program that can safely be edited in BASIC
>> * hidden lines can be executed in BASIC or not
>> *if not executed then RAW ML can be embedded - avoid code 00
>> *if executed
>> ***hide the ML in strings - avoid " and codes <32 decimal
>> ***hide the ML in data structures - avoid comma, and <32 decimal
>>
>>
>> We've already had Basic with embedded ML, we've just never had it with
>> next to no overhead - both in time and memory - and with the ability
>> to run in place WITHOUT absolute addressing.
>>
>>
>>
>>
>> On Tue, Jun 5, 2018 at 6:58 AM, Ken Pettit > > wrote:
>>
>> Ahh, I see!  Okay, then put just a small DATA statement on the
>> first line:
>>
>> 65531 DATA a:ML code here
>> 65531 ML code here
>> 65531 and here...
>>
>> Then "10 READ A$" will give you the address of "a" in the DATA
>> statement, and it only consumes 3 bytes (DATA token, 'a' and ':'),
>> plus the PEEK magic to get access to the address.
>>
>> Ken
>>
>>
>>
>> On 6/5/18 3:53 AM, Stephen Adolph wrote:
>>
>> sorry I was thinking just to have the RAW ML in the line. no
>> Data, no string.
>>
>> 65531 m-98&"lkj3
>>
>> so long as you never execute this code line in BASIC, I
>> believe it is fine.  you just have to find the first byte of
>> code.
>>
>>
>>
>>
>
>

Re: [M100] Fwd: Reporting Breakthrough for "Run In Place" Operation -- Was Re: Remem : relocatable ML codes.

[John Gardner]

If a BASIC pgm with code embedded in a DATA statement loads

OK,  maybe embed a return instruction,  call the routine,  & see

what happens?

On 6/1/18, John R. Hogerhuis  wrote:
> Awesome. Thanks Steve, and Ken.
>

Re: [M100] compact embedded ML coding

[John Gardner]

...pop B...   6809?

Hi Willard -

70C20,  actually.   I'm not smart enough for 808X."8)

On 6/1/18, Stephen Adolph  wrote:
> Sure no problem.  Let me know what you need
>
> On Friday, June 1, 2018, Willard Goosey  wrote:
>
>> On Wed, 30 May 2018 14:48:11 -0400
>> Stephen Adolph  wrote:
>>
>> > I often want to embed ML into basic programs.  There are 2 ways that
>> > I use 1)  make a string of binary and assign it to a basic string
>> > variable.  (use VARPTR)
>> > 2)  include data statements that contain the ML binary, with some
>> > encoding, and use a routine to poke into memory
>> >
>> [...awesomeness deleted...]
>>
>> > Anyhow the net result is very compact with a minimal poke routine.  I
>> > compile my machine code into Intel HEX format, run a simple program to
>> > encode the data into sets of DATA statements, and copy the resulting
>> > text into a .DO file.
>>
>> Any chance I could include this with the M100SmallCLib? It might remove
>> one of the roadblocks to people actually using it (smallclib) for
>> something. ;-)
>>
>> Willard
>> --
>> Willard Goosey  goo...@sdc.org
>> Socorro, New Mexico, USA
>> I search my heart and find Cimmeria, land of Darkness and the Night.
>>   -- R.E. Howard
>>
>

Re: [M100] Fwd: Reporting Breakthrough for "Run In Place" Operation -- Was Re: Remem : relocatable ML codes.

[John Gardner]

Good stuff!

HP-LX docs call Run-In-Place code "XIP",  for Execute-In-Place.

Although RIP seems appropriate enough for my code...

On 6/1/18, Stephen Adolph  wrote:
> this is quite useful; it applies specifically to (a) running code that is
> buried in BASIC string variables and (b) running code that is buried in
> DATA structures, because in those cases you really don't know where the
> code is (easily), and the code can't adapt to being moved around (easily).
> Now it can.  Very useful!
>
> Regarding .DO files - the contents of the .DO file survives being loaded
> into M100 memory intact.  One has to avoid EOF and 0A.   One does not need
> quotes either.  So this is quite dense, and
>
>
> On Fri, Jun 1, 2018 at 3:15 AM, Ken Pettit  wrote:
>
>> Hi John,
>>
>> So based on Ron's research, the WHEREAMI function in ROM can be used as
>> another way to perform a relative branch without the need for a fixed
>> location in RAM:
>>
>> LXI   D, branch_offset   ; Calculated relative to the DAD D opcode
>> below
>> CALL  WHEREAMI   ; 31E9H or 3F3DH.  HL now contains address
>> of
>> DAD D opcode on next line
>> DAD   D  ; Perform relative address calculation
>> POP   D  ; Pop old HL value from Stack
>> PCHL ; Jump to new relative location
>>
>> And if you need a conditional relative jump, you can do:
>>
>> LXI  D, branch_offset; Calculated relative to the DAD D opcode
>> below
>> CALL WHEREAMI; 31E9H or 3F3DH.  HL now contains address
>> of
>> DAD D opcode on next line
>> DAD  D   ; Perform relative address calculation
>> POP  D   ; Pop old HL value from Stack
>> JZ (or JNZ, etc.) 0ED7H  ; Conditional jump to a PCHL opcode
>>
>> ; Fall though if condition not met
>>
>>
>> Ken
>>
>>
>> On 5/31/18 12:49 PM, John R. Hogerhuis wrote:
>>
>> Self-locating code.
>>
>> Ron Wiesen did some research a long time ago to figure out code in the
>> ROM
>> that could tell you where you are calling from.
>>
>> This is a critical part of code that can efficiently relocate itself to
>> run-in-place or at a specific location.
>>
>> -- John.
>>
>> -- Forwarded message --
>> From: Ron Wiesen 
>> Date: Thu, Nov 9, 2006 at 2:25 AM
>> Subject: Reporting Breakthrough for "Run In Place" Operation -- Was Re:
>> Remem : relocatable ML codes.
>> To: Model 100 Listserve 
>>
>>
>> Previously I wrote:
>> > But your "relocatable ML codes" message has reminded me of some
>> > progress
>> I
>> > recently made on a mission that was placed on the "back burner" a long
>> time
>> > ago.  So I'll review my mission notes and report my progress to this
>> list.
>> >
>> > The mission was to develop the means for software, operating in a M10x
>> > or
>> > M200 laptop, to discovered the memory address of "Where I am Now".
>> > I've
>> > found four methods to do it, tested all four of them, and believe I've
>> > determined which is the "best" method of the four.  Having the means to
>> > ascertain "Where I am Now" is a long sought after breakthrough.  It's
>> > something that's essential in obtaining a substantial improvement in
>> > the
>> > "Run In Place" operation of binary objects; the improvement eliminates
>> need
>> > for the separate utility that launches said binary objects.  "Run In
>> Place"
>> > operation of binary objects avoids need for a HIMEM area and avoids the
>> > double-consumption penalty that ordinary invocation of binary objects.
>>
>> The "Self-Locate" snippet shown below is my report, which details the
>> "best"
>> method of the four methods that I found and tested.  Details are given
>> for
>> both the Model 10x laptop (CALL 31E9H and JMP 14EDH) and for the Model
>> 200
>> laptop (CALL 3F3DH and JMP 1604H).
>>
>> = Self-Locate -- major milestone for run-in-place laptop executables
>> =
>> WHEREAMI:   EQU  $
>> CALL 31E9H   ;XTHL PCHL stacks HL, HL=rtn. Model 10x.
>> ;   CALL 3F3DH   ;XTHL PCHL stacks HL, HL=rtn. Model 200.
>> IAMHERE:EQU $;I am HERE at this discovered return address
>>  ;which now is in HL
>> PUSH D
>> PUSH B
>> PUSH PSW
>> ;All reg content stacked. JMP 14EDH is a handy unstack exit.
>> JMP 14EDH;Pops PSW,B,D,H and then RET exit. Model
>> 10x.
>> ;   JMP 1604H;Pops PSW,B,D,H and then RET exit. Model
>> 200.
>>
>> Once it's discovered "Where I am Now" then inspection of "Where I was
>> Before" is done.  The difference is the needed adjustment of wordAdrs.
>> Note, if difference is 0, adjustment isn't needed and time is saved --
>> often the case for code held within BASIC program files.
>>
>> Via link-lists, locales of wordAdrs are found.  Each is adjusted
>> according to the adjustment difference.  If there are locales for
>> byteAdrs (unlikely), they have their own link-lists and also 

Re: [M100] compact embedded ML coding

[John Gardner]

...Reljmp.pdf...

Nice.  Thanks.

On 5/31/18, John Gardner  wrote:
> Hi John -
>
> I'm thinking about Ken's idea of having code embedded in BASIC
>
> jumping to code embedded in a DO file -  Sounds workable,  even
>
> reasonable with a big routine,  or a number of smaller routines.
>
> On 5/31/18, John R. Hogerhuis  wrote:
>> On Thu, May 31, 2018 at 12:15 PM, John Gardner  wrote:
>>
>>> Your code can figure out it's execution address  with something like:
>>>
>>>  call  @Boo
>>> Boo   pop B
>>>  pop A
>>>
>>> Boo's address is now in register pair A,B...
>>>
>>
>> But you kind of already know since that code would have to be relocated
>> to
>> function.
>>
>> -- John.
>>
>

Re: [M100] compact embedded ML coding

[John Gardner]

Hi John -

I'm thinking about Ken's idea of having code embedded in BASIC

jumping to code embedded in a DO file -  Sounds workable,  even

reasonable with a big routine,  or a number of smaller routines.

On 5/31/18, John R. Hogerhuis  wrote:
> On Thu, May 31, 2018 at 12:15 PM, John Gardner  wrote:
>
>> Your code can figure out it's execution address  with something like:
>>
>>  call  @Boo
>> Boo   pop B
>>  pop A
>>
>> Boo's address is now in register pair A,B...
>>
>
> But you kind of already know since that code would have to be relocated to
> function.
>
> -- John.
>

Re: [M100] compact embedded ML coding

[John Gardner]

Your code can figure out it's execution address  with something like:

 call  @Boo
Boo   pop B
 pop A

Boo's address is now in register pair A,B...

 ...

Re: [M100] compact embedded ML coding

[John Gardner]

Hi Steve -

My original scheme (for TI-74) was to make the 1st pgm line

the DATA statement,  in the form:  100  DATA ### ... ###

The "#" character are simply placeholders,  up to 80 chars,

the max length of a DATA statement in TI-74 BASIC.


A TI-74 "main" pgm always starts at HIRAM;  individual elements

of the DATA statement will alway be at a fixed offset from HIRAM,

thus at a known address.  One then opens the DEBUG monotor &

replaces the placeholders with the desired code.  To run the code

BASIC executes CALL EXEC(the desired execution ADDR).


Once the placeholders have been replaced with code,  the pgm can

be saved to PC as a text file (".b74",  in TI74 parlance),  or as an

executable (".pgm"),  and the DATA statement willl survive in situ.


Note that READing the DATA sttement is not necessary - I wonder if

READs are a factor in having to offset non-printing chars on the MTs?


I'm about to move,  & my 8201a's are already packed...  Another thing;

I saw a Ron Wiesen pgm once where it seemed he'd embedded machine

code in BASIC,  but that was long ago,  & memory is unreliable...

On 5/31/18, Ken Pettit  wrote:
> Hi Steve,
>
> Search through BASIC lines?  Nah, don't do that!  Put a dummy DATA
> statement and then your ML code:
>
> 10 DATA "a", "encoded ML"
>
> Then do a READ D$.  The BASIC ROM will perform the search and update
> address FBB8H (on M100/T102) with the address where READ will start it's
> search next.  Just use that variable as your starting point. Of course
> you still have to avoid opcode and operands in the low region of the
> ASCII table.
>
> Ken
>
> On 5/31/18 4:49 AM, Stephen Adolph wrote:
>> John I think a scheme like that could work, however you'd need to
>> eliminate all codes under 32decimal.  To run in place, you lose the
>> ability to encode/decode the problematic characters.
>>
>> finding the DATA statements in RAM can be done but it is a bit of
>> work.  I think you'd have to start from the directory table and trace
>> out the line by line starting addresses from there.
>>
>> On Wed, May 30, 2018 at 3:15 PM, John Gardner > <mailto:gof...@gmail.com>> wrote:
>>
>> Or,  for really evil results,  you can execute your embedded code
>>
>> in place - I think.  I have'nt tried this on a MT,  but it works a
>> treat
>>
>> on TI CC-40's & TI-74's,  8-bitters of a similar vintage.  Of course
>>
>> you have to keep track of where your code is in memory...
>>
>> I actually wrote a tool once (in QB) that would take a .lst file and
>>
>> turn the opcodes into DATA statements,  with offsets & jumps in
>>
>> the right places;  a TI-BASIC DATA statement length is 80 Bytes
>>
>> max, not 255,  so more than one is sometimes needed,  & there's
>>
>> some overhead in the jumps,  but an EXEC statement is pretty fast...
>>
>> Too much fun..."8)
>>
>>  ...
>>
>>
>> On 5/30/18, Stephen Adolph > <mailto:twospru...@gmail.com>> wrote:
>> > I often want to embed ML into basic programs. There are 2 ways
>> that I use
>> > 1)  make a string of binary and assign it to a basic string
>> variable.  (use
>> > VARPTR)
>> > 2)  include data statements that contain the ML binary, with
>> some encoding,
>> > and use a routine to poke into memory
>> >
>> > regarding (2)
>> > I've seen 2 methods
>> > 1) encode data as decimal numbers
>> > ex.  Data 125, 34, 56 etc
>> >
>> > 2) encode data as hex characters
>> > ex. Data C9F501 etc
>> >
>> > Neither of these are really optimal because they expand the size
>> of the
>> > code by 2 -3 x
>> >
>> > I've come up with an alternative to this which I'm now using.
>> The raw
>> > binary, with some code changes, can be directly embedded in data
>> > statements, in quotes.
>> >
>> > ex. Data "$%#(Lop" etc
>> >
>> > gotchas:
>> > 1)  all binary codes <=32 must be mapped to special sequences to
>> avoid
>> > problems with BASIC
>> > 2)  the " character has to be mapped to a different sequence
>> otherwise you
>> > confuse BASIC
>> >
>> > I use the "/" as a special symbol to mean "special sequence" and
>> I map all
>> > characters <=32, + " + / by adding 64d to each character.
>> >
>> > Ex. if the code 0Dh is encountered in the binary, it would get
>> transformed
>> > to "/" + chr$(13+64).
>> >
>> > Decoding is straightforward - look for / and subtract 64 from
>> the next
>> > character.
>> >
>> > Anyhow the net result is very compact with a minimal poke
>> routine.  I
>> > compile my machine code into Intel HEX format, run a simple
>> program to
>> > encode the data into sets of DATA statements, and copy the
>> resulting text
>> > into a .DO file.
>> >
>>
>>
>
>

Re: [M100] compact embedded ML coding

[John Gardner]

Or,  for really evil results,  you can execute your embedded code

in place - I think.  I have'nt tried this on a MT,  but it works a treat

on TI CC-40's & TI-74's,  8-bitters of a similar vintage.  Of course

you have to keep track of where your code is in memory...

I actually wrote a tool once (in QB) that would take a .lst file and

turn the opcodes into DATA statements,  with offsets & jumps in

the right places;  a TI-BASIC DATA statement length is 80 Bytes

max, not 255,  so more than one is sometimes needed,  & there's

some overhead in the jumps,  but an EXEC statement is pretty fast...

Too much fun..."8)

 ...


On 5/30/18, Stephen Adolph  wrote:
> I often want to embed ML into basic programs.  There are 2 ways that I use
> 1)  make a string of binary and assign it to a basic string variable.  (use
> VARPTR)
> 2)  include data statements that contain the ML binary, with some encoding,
> and use a routine to poke into memory
>
> regarding (2)
> I've seen 2 methods
> 1) encode data as decimal numbers
> ex.  Data 125, 34, 56 etc
>
> 2) encode data as hex characters
> ex. Data C9F501 etc
>
> Neither of these are really optimal because they expand the size of the
> code by 2 -3 x
>
> I've come up with an alternative to this which I'm now using.  The raw
> binary, with some code changes, can be directly embedded in data
> statements, in quotes.
>
> ex. Data "$%#(Lop" etc
>
> gotchas:
> 1)  all binary codes <=32 must be mapped to special sequences to avoid
> problems with BASIC
> 2)  the " character has to be mapped to a different sequence otherwise you
> confuse BASIC
>
> I use the "/" as a special symbol to mean "special sequence" and I map all
> characters <=32, + " + / by adding 64d to each character.
>
> Ex. if the code 0Dh is encountered in the binary, it would get transformed
> to "/" + chr$(13+64).
>
> Decoding is straightforward - look for / and subtract 64 from the next
> character.
>
> Anyhow the net result is very compact with a minimal poke routine.  I
> compile my machine code into Intel HEX format, run a simple program to
> encode the data into sets of DATA statements, and copy the resulting text
> into a .DO file.
>

Re: [M100] TPDD Utility Disk

[John Gardner]

Is Catweasel still around?

On 5/30/18, Mike Stein  wrote:
> In general it's not the drive but the controller that controls whether the
> format is FM or MFM. Many PC controllers can do both FM and/or MFM no
> problem; in fact, some formats use both on the same disk.
>
> I don't see any fundamental reason why you couldn't read/write a TPDD disk
> on a 'standard' PC drive but I don't have a drive or disks to try.
>
> m
>   - Original Message -
>   From: Stephen Adolph
>   To: m...@bitchin100.com
>   Sent: Tuesday, May 29, 2018 7:28 PM
>   Subject: Re: [M100] TPDD Utility Disk
>
>
>   Only an fm drive can make a tppd disc.  Mfm can't
>Do It.
>
>
>https://en.m.wikipedia.org/wiki/Modified_Frequency_Modulation
>
>
>
>
>   Translation...a standard 3.5 drive can't work.  But the idea of a program
> to make a boot disc is possible provided you have a good Tpdd.
>
>
>
>
>
>   On Tuesday, May 29, 2018, Kevin Becker  wrote:
>
> Unless the pictures on eBay are wrong, mine is definitely a TPDD.
>
>
>
>
>
> On May 29, 2018, at 7:01 PM, Brian White  wrote:
>
>
>   If what you have is a TPDD-2 and not a TPDD, I can supply a copy for
> TPDD-2. Send me an address off-list and I'll mail it tomorrow.
>
>
>
>   Conversely I would like a copy for TPDD myself if anyone is willing to
> either make me one, or trust me with mailing me theirs and I'll mail it back
> after making a copy myself.
>
>
>   From what I've been able to tell, although people have tried and
> failed for 30 years, it actually *should* be physically possible to generate
> a new disk purely from a download, as long as you have a real drive and a
> working special cable. After all, the included floppy dos + backup.ba does
> it, and the drive is controlled entirely by mere serial communication which
> anything can do.
>
>
>   A little progress has been made recently wrt recording the entire
> serial conversation during a backup, but it still has not yet gone all the
> way to being able to generate a disk from scratch from a download.
>   I think the tools are there to at least work on it and eventually get
> there. So if you want an interesting project that hasn't already been solve
> at least 7 different times over the decades, yet looks within reach, there
> it is. :)
>
>
>   You absolutely need a working TPDD or TPDD-2 drive to make these
> though, even if you use a modern pc to control it. It's not just a matter of
> an odd number of tracks or sectors or other formatting. The raw magnetic
> format is FM instead of MFM which all pc drives & drive controllers use. No
> amount of special software can overcome that!
>
>
>
>
>
>   On Tue, May 29, 2018 at 4:58 PM, Kevin Becker 
> wrote:
>
> A little deeper googling is leading me to believe there is a special
> floppy_sys file on the utility disk that nobody has figured out how to
> recreate.  I'll try it anyway when it arrives but If that ends up being the
> case, then I wonder if there is anyone on the list who would be willing to
> make my a utility disk.  I'd be happy to send a blank disk and a
> self-addressed stamped envelope.
>
>
>
>
>
>
> On Tue, May 29, 2018 at 4:38 PM, Tom Dison 
> wrote:
>
>   Ah that's a good question, is like to know also.
>
>
>   On Tue, May 29, 2018 at 3:29 PM Kevin Becker
>  wrote:
>
> I don’t mean with a PC. I should already be able to use the
> drive via TS-DOS so I’m assuming I can just copy floppy.co to my M102 using
> desklink and then save it to the TPDD. I’m just wondering if that is good
> enough or if there is some special boot sector magic necessary.
>
> On May 29, 2018, at 3:55 PM, Tom Dison 
> wrote:
>
>
>   I don't believe you can create one with a PC floppy
> controller. I'd buy a copy off of someone is I could. For now, I'm planning
> on using the python library on Linux box connected to the drive to create
> the disk. I'd much rather just have the floppy.
>
>
>   On Tue, May 29, 2018 at 2:31 PM Kevin Becker
>  wrote:
>
> I've been watching eBay on and off for a TPDD or TPDD2
> complete with cable at a reasonable price for what feels like forever.  I
> finally pulled the trigger on one today but doesn't include the utility
> diskette.
>
>
> I already have a REX with TS-DOS and I know how to bootstrap
> TEENY if necessary, but I'd like to have a utility disk with floppy.co just
> for the fun of it.  I believe I found floppy.co in an archive on the Club100
> site.  Is there anything special about the utility disk or can I just save
> floppy.co to any formatted disk and then be able to use it to bootstrap
> floppy.co later?
>   --
>
>   Faith without Works is Dead...
>
>   --
>
>   Faith without Works is Dead...
>
>
>
>
>
>
>   --
>
>   bkw
>

Re: [M100] SPAM-LOW: Re: New member - question on 'half' alive Model 100

[John Gardner]

You're not going to find a supercap that'll

a)  Keep RAM alive as long as a healthy NiCd will,  and

2)  Fit inside the case.  Or inside your trunk,  probably...

But what you can do is

1)  Use Eneloop "Low Self-Discharge" AAs,  which if your RAM
 is healthy (not drawing much stand-by current)  will keep memory
 alive for many years,  fully charged.

b)  Use a 3 or 5F supercap,  which will keep healthy RAM alive for
 weeks;  plenty of time to recharge or replace your Eneloops.

Why?  Eneloops don't leak.  Supercaps don't leak.  NiCds do.



On 5/13/18, Jeffrey Birt  wrote:
> Update…
>
>
>
> It was the RAM module. After thinking about it after Fugu’s email the other
> day it occurred to me I had done a capture of the standard RAM bank select
> lines (and I happened to dave it) and after looking at it again it looked
> fine. This evening I pulled the standard RAM module out, split apart a 30
> pin DIP socket to make two 15 pin SIPs and plugged in of the option RAMs.
> AND…nothing. Sigh…
>
>
>
> Then I noticed I had not plugged the ROM back in after cleaning the flux
> from the board. So, the ROM was installed, and STRL-BRK done on power up
> and…It’s ALIVE! Bwa-ha-ha-ha! It’s ALIVE!
>
>
>
> I tried reflowing the original standard RAM module and it still did not
> work. I could ohm out each line to each individual RAM chip and maybe get
> lucky and find one open trace, but I would guess that a bad RAM chip is more
> likely. I’ll look into making some more RAM module or buying a few, for now
> I have 16K.
>
>
>
> As luck would have it the second M100 I bought from across the state arrived
> yesterday, I still have not opened it yet. It is supposed to work, got it
> from the original owner who seemed like a nice guy. A grand total of $61
> including shipping. Now I’ll put together an order for enough caps to finish
> recapping the first M100 and re-cap the 2nd one while I’m at it. I also need
> to try and calculate a super-cap size that will at least match the original
> NiCad battery.
>
>
>
> Thanks again everyone (especially Fugu) for your help.
>
>
>
> Jeff
>
>
>
>
>
> From: M100  On Behalf Of Fugu ME100
> Sent: Thursday, May 10, 2018 10:06 AM
> To: m...@bitchin100.com
> Subject: Re: [M100] SPAM-LOW: Re: New member - question on 'half' alive
> Model 100
>
>
>
> The address could be stuck internally on the RAM so the address line would
> appear OK externally.  The fact the ROM runs correctly with the shared
> Address line would indicate the address lines are generally OK.  It could be
> floating on the module as you suggest,  look to see if there is any
> corrosion on the module and the pins to the module are in good condition.
> Perhaps try reflowing each of the module pins to make sure there are no dry
> joints?
>
>
>
> I am currently looking into producing some sort of test harness for the
> model T however the lack of socket for the 8085 makes it hard to add in a
> test fixture.  Even trying to tri-state the 8085 appears difficult as it
> does not tri-state the ALE, all the other lines are OK.  Another option
> would be to try and monitor what it does with something that plugs into the
> RAM socket.  That way at least there would be a trace showing the bus
> activity.   Being able to single step the 8085 might be another option with
> a known ROM in the socket.
>
>
>
>

Re: [M100] Estate Sale: Big Load of Computer Stuff

[John Gardner]

Such a deal...   "8)

 ...


On 5/11/18, Diggy Dude  wrote:
> Too much to inventory, huh? As in he wants you to pay $9000 for a load of
> stuff without even knowing what's in it?
>
> - Jim
>
> On Thu, May 10, 2018 at 5:57 PM, Anthony Coghlan 
> wrote:
>
>> I’ll have to use this as leverage for my wife to appreciate how
>> relatively
>> frugal and selective I’ve been in my ancient computer acquisitions over
>> time, and how much it could “potentially” be worth...
>>
>> There are some interesting pieces in the lot, ranging from the humble but
>> ingenious Sinclair ZX-81 to what looked like an Apple Lisa, but the
>> seller
>> would be wise to part it out.  That will be a lot of work (no pun
>> intended)
>> but much more likely to sell.
>>
>> Best wishes,
>> Anthony
>>
>>
>>
>> On Thursday, May 10, 2018, Greg Swallow  wrote:
>>
>>> Amen John. He'll be paying taxes on that load before he ever sells it
>>> untested and all at once.
>>>
>>> GregS <><
>>>
>>> - Original Message -
>>> From: "John R. Hogerhuis" 
>>> To: m...@bitchin100.com
>>> Sent: Thursday, May 10, 2018 3:35:50 PM
>>> Subject: Re: [M100] Estate Sale: Big Load of Computer Stuff
>>>
>>> Haha.
>>>
>>> I have piles of computers junk too... it ain't worth $9,000.
>>>
>>> "Too much to inventory"
>>>
>>> -- John.
>>>
>>
>

Re: [M100] SPAM-LOW: Re: New member - question on 'half' alive Model 100

[John Gardner]

Jeff - You might try contacting Saleae directly.  They're pretty responsive,

the times I've had questions...

Re: [M100] SPAM-LOW: Re: New member - question on 'half' alive Model 100

[John Gardner]

...the memory battery only protects the RAM when changing the AA’s...

That's why I recommend using Eneloops along with a supercap. The

very low self-discharge of the Eneloops could conceivably keep RAM

alive  the supercap charged for years.

 ...


On 5/6/18, Jeffrey Birt  wrote:
> I just peeked at the CE signals (on M4) for the RAM (only std RAM module is
> installed). All /CE signals toggle but it is not consistent from reset to
> reset. I guess I should have checked they were getting to the RAM as well.
> I
> looked and at the input signal sot M4 and they all toggle happily after
> reset as well.
>
>
>
> One thing that has been bothering me is the /RD* timing when reading from
> the ROM. Take a look at the screen capture from my LA here:
>
>
>
> https://1drv.ms/u/s!AtH4vpaZnzX7j8BykM3nU_zsOHq5iA
>
>
>
> Channel 7 here is the /RD* signal and is being used as a clock for the
> simple parallel decoder. Notice that as /RD* goes low the data line state
> is
> just changing. I would expect the data to already be valid here.well.
> Thinking again that would not make sense. The 80C85 would set /RD and would
> have to give the ROM a chance to preset the data to the data bus and then
> read it on the falling edge of the next clock. So, the issue I have here is
> that the simple parallel decoder is not looking at the falling edge of the
> next clock but rather the falling edge of the /RD*.
>
>
>
> O, back to the RAM. I do see all the /CE signals but as I said what I see
> is
> not consistent with each reset. Sometimes the M100 seems to keep running
> for
> just over a second before stopping and while it does this I see quite a lot
> of activity on the RAM /CE lines (some more than others).
>
>
>
> One other ting I did today was to lift the anode of D11 (diode which
> prevents the memory battery from back feeding the whole machine) and
> soldered in a 3.6V lithium primary cell. This did no good of course, but it
> will keep what ever content of RAM consistent at least. Once I get the M100
> running I'll take some current measurements so see what is drawn from the
> memory battery when the AA's are not present. The way it looks the memory
> battery only protects the RAM when changing the AA's. By knowing what is
> drawn from the battery I hope to size a suitable super cap replacement.
>
>
>
> I guess for further work I can check that the signals from M4 are getting
> to
> the RAM module and check that it seems to output data. After that I am
> stuck
> again. If I can resolve the issue with the LA software so it will decode
> the
> collected parallel data correctly I might have a better chance of knowing
> how far it gets in the boot process. I'm wondering if it gets to a point
> where it tried to talk to some I/O device which causes a problem.
>
>
>
> Thanks again for your help!
>
>
>
> Jeff
>
>
>
> From: M100  On Behalf Of Fugu ME100
> Sent: Sunday, May 6, 2018 2:11 AM
> To: m...@bitchin100.com
> Subject: Re: [M100] SPAM-LOW: Re: New member - question on 'half' alive
> Model 100
>
>
>
> I would say your CPU looks good :)  The ROM seems to be working as are all
> the buffers and ROM decoding, the code is executing correctly to the point
> of failure.  The IO is still a possible source of error but as there are
> multiple accesses  it looks like it performs the operations correctly.
>
>
>
> Did you check the CE- on the RAM module?  Just after that IN op RAM
> accesses
> start to happen.  Without the NiCd the RAM might always start up with
> garbage which could cause some oddness.
>
>
>
> Interrupts are disabled so that should not cause problems.
>
>
>
> Looks like the RAM is the next target to investigate.
>
>
>
>

Re: [M100] SmallC-85 library 0.0.6 upload

[John Gardner]

If you can lay hands on one of the Small-C books by Hendrix

it'll give you an idea of the limitations.

On 5/6/18, Stephen Adolph  wrote:
> Wow, you did a lot of work here Willard.
> Nice stuff.
>
> I wonder how close smallC is to BDS-C?
> I know that BDS-C does not compile things that other C compilers would
> handle.
>
> On Sun, May 6, 2018 at 2:24 PM, Stephen Adolph 
> wrote:
>
>> Willard,
>> wanted to revive this thread.
>> So, if one wanted to write some C I take it that you write andcompile
>> outside of M100 on a windows box, but you get a .CO program that can run
>> on
>> M100?
>>
>> thx
>> Steve
>>
>> On Thu, Jul 13, 2017 at 4:18 PM, Willard Goosey  wrote:
>>
>>> Wow, it's been a month?!? Sorry guys RAM files are complicated...
>>>
>>> Anyway, my Model 100 library for SmallC-85 is now at version 0.0.6. Get
>>> the goodies at my homepage at
>>> http://www.sdc.org/~goosey/m100/m100smallc0.0.6.zip or from my
>>> "personal library" at club100.org in "Willard Goosey" -> "linux cross
>>> development"
>>>
>>> Don't be scared, there are windows versions of the compiler and
>>> assembler too
>>>
>>> All the wrapper functions for the ROM routines handling ASCII files
>>> in RAM have been verified, and (I believe) documented correctly. RAM
>>> files are complicated and if you get them wrong it's a quick trip to a
>>> Cold Start.
>>>
>>>
>>> Write C, and grow strong
>>> Willard
>>> --
>>> Willard Goosey  goo...@sdc.org
>>> Socorro, New Mexico, USA
>>> I search my heart and find Cimmeria, land of Darkness and the Night.
>>>   -- R.E. Howard
>>>
>>
>>
>

Re: [M100] New user, AA battery leakage

[John Gardner]

I did'nt change anything.  Note,  however,  that the 8201a is similar

but not identical to the 100/102.  It's probably worth comparing the

schematics before doing the modification.  Kurt,  IIRC,  had some

issues with dropping a supercap into a 200...

On 4/30/18, Jeffrey Birt <bir...@soigeneris.com> wrote:
> Did you need to replace any part of the charging circuitry? I suspect not as
> it was the NiCad was only a 50mah part and if it was charge as C/10 then any
> super cap could handle the 5ma with no issues (I'm guessing).
>
> Jeff
>
> -Original Message-
> From: M100 <m100-boun...@lists.bitchin100.com> On Behalf Of John Gardner
> Sent: Monday, April 30, 2018 4:50 PM
> To: m...@bitchin100.com
> Subject: Re: [M100] New user, AA battery leakage
>
> I replaced my two 8201a NiCds with supercaps 6-7 years ago.
>
> It just works,  so far.
>
>
>
>

Re: [M100] New user, AA battery leakage

[John Gardner]

I replaced my two 8201a NiCds with supercaps 6-7 years ago.

It just works,  so far.

Re: [M100] Power Adapter Questions

[John Gardner]

IME 6 VDC (8201a) works fine.

 ...


On 3/16/18, Mike Stein  wrote:
> I think it would depend on the adapter type; I would measure the *actual*
> voltage of both adapters, both unplugged and plugged in with the computer
> turned on.
>
> They do have regulators, in fact they have complete regulated switching
> power supplies. I really wouldn't recommend using the 8.5V supply instead of
> the 6V; extra voltage is usually dissipated in heat, which could possibly
> cause a problem with extended use.
>
> How about just colour-coding the connectors and jacks?
>
> m
>   - Original Message -
>   From: Kurt McCullum
>   To: Model 100 Discussion
>   Sent: Friday, March 16, 2018 11:52 AM
>   Subject: [M100] Power Adapter Questions
>
>
>A quick power question for those who may be able to answer this question.
> On my NEC 8201 the AC power adapter is rated for 8.5 volts. The AC power
> adapter for my 100/102/200/TPDD2 is 6v. I have both on my desk but get them
> mixed up at times even though I try not to. The units seem happy with either
> voltage. So I'm wondering if there is a risk of damage when I accidentally
> put the 8.5v plug in my 200 or 102. Do they have an internal regulator that
> prevents damage?
>
>
>   And one other question. I am getting ready to make the modification to my
> 200 which allows it to have rechargeable batteries rather than regular AA
> cells. This is an option which the service manual refers to. It involves
> soldering two small jumpers. Will I need to run a higher voltage to charge
> these batteries or is 6v enough?
>
>
>   Kurt

Re: [M100] Power Adapter Questions

[John Gardner]

I've used rechargeable NiMH (Eneloops) in 8201a packs

for many years.  In practice,  I have'nt noticed a downside

to plug-in cells,  & there is one distinct advantage - It allows

use of a purpose-built Eneloop charger (Maha C9000).

 ...


On 3/16/18, Kurt McCullum  wrote:
>  A quick power question for those who may be able to answer this question.
> On my NEC 8201 the AC power adapter is rated for 8.5 volts. The AC power
> adapter for my 100/102/200/TPDD2 is 6v. I have both on my desk but get them
> mixed up at times even though I try not to. The units seem happy with either
> voltage. So I'm wondering if there is a risk of damage when I accidentally
> put the 8.5v plug in my 200 or 102. Do they have an internal regulator that
> prevents damage?
> And one other question. I am getting ready to make the modification to my
> 200 which allows it to have rechargeable batteries rather than regular AA
> cells. This is an option which the service manual refers to.
> It involves soldering two small jumpers. Will I need to run a higher voltage
> to charge these batteries or is 6v enough?
> Kurt

Re: [M100] batteries...

[John Gardner]

Most manufacturers advise against trickle-charging NiMH

 ...
 .

On 3/12/18, George Michael Rimakis  wrote:
> The thing about NiMH, is the level of trickle charge that they can tolerate
> is a bit less than NiCD. Might not be good in the long run.
>
> On Fri, Mar 9, 2018 at 5:00 PM, Jim Anderson  wrote:
>
>> > -Original Message-
>> >
>> > This brings up an interesting point.  Having just replaced my NiCad I
>> > think I'm going to use my label maker to leave a note about when it was
>> > replaced under the battery door.
>>
>> I like to do this anyway (and not just with m100s), because I find myself
>> struggling to remember later which machines have which things replaced,
>> and
>> when they were done...
>>
>>
>>
>>
>>
>>
>>
>> jim
>>
>

Re: [M100] Need a M102 keyswitch

[John Gardner]

Pure speculation,  but I wonder if ultrasonic cleaning of balky

switches would do any good?

 ...


On 1/26/18, Jim Anderson  wrote:
>> -Original Message-
>>
>> My keyswitch has been restored to service.  I carefully scraped (with my
>> fingernail) the surface of the graphite pad to expose a new layer, and
>> that seems to have worked.  Thanks to all for advice.
>
> Just as a general question, since there was some good advice on this thread
> on restoring the normal keyswitches: I had a problem with the F8 key on my
> 'best' M100 (its only remaining problem was the F8 key).  I couldn't see any
> non-destructive way of taking the tiny F-key switches apart, so I ended up
> desoldering it and swapping it with the 'LABEL' keyswitch.  (I was going to
> steal a keyswitch from one of the parts machines, but their switches have a
> different click feel and I didn't want my best machine to have a different
> feel on the F8 compared to the other function keys.)
>
> The switch undoubtedly has filth inside and/or the conductive pad needs
> cleaning, but without a way of getting the switch apart that knowledge
> doesn't help me.  The swap was a satisfactory solution for me because the
> key works intermittently (requires a firm press, and sometimes makes contact
> multiple times during a single press, which is annoying when trying to quit
> just one level out of something, like in UR-2 or Sardine).  It's fine as
> 'LABEL' because I don't often use that key, and there is very little
> consequence to multiple presses of 'LABEL' versus any of the other keys in
> that row - just keep hitting it until the toggling stops in the state you
> wanted. :)
>
>
>
>
>
>
>
> jim
>

Re: [M100] gps

[John Gardner]

Simply getting the Time from GPS can be pretty useful...

 ...


On 1/22/18, Mike Stein  wrote:
> That might be me; we did have some discussions about the protocol etc. way
> back when and I did use the M100 with a Delorme Tripmate to log my trips for
> a while; fun and some interesting data, but not terribly useful in the end.
>
> I can't find any notes or programs at a fast look but it wasn't very
> complicated; just a matter of parsing the data stream into its various
> fields.
>
> I'll have another look around for anything from those days.
>
> m
>
> - Original Message -
> From: "Peter Vollan" 
> To: 
> Sent: Sunday, January 21, 2018 6:03 PM
> Subject: [M100] gps
>
>
>>A while back, years ago probably, someone detailed how they used a GPS
>> unit with a serial connection to their Model 100. I went as far as
>> acquiring the GPS unit and the connector for it to splice into a
>> cable, then the project got stalled. Anyone know where I could find
>> this info?
>

Re: [M100] Assembly Development on the 100

[John Gardner]

Well,  there's this:  ftp://ftp.whtech.com/club100/rom/cleurom2.txt

I use the 8210a version of this - It works ok.

http://www.club100.org/library/librom.html

On 1/9/18, Chris Kmiec  wrote:
> What's the best solution for assembler on the Tandy 100/102? Is there a ROM
> add-on with one, or a software I can download? Thanks!
>

Re: [M100] DVI Operation

[John Gardner]

Did'nt know I had a whitelist...   :)   Thanks,  I'll look into it.

 ...


On 1/9/18, John R. Hogerhuis <jho...@pobox.com> wrote:
> On Tue, Jan 9, 2018 at 3:10 PM, John Gardner <gof...@gmail.com> wrote:
>
>> Msgs from some members of the several lists I monitor regularly
>>
>> end up in my (gmail) spam folder - No idea why...
>>
>>  ...
>>
>
> Seems to be Yahoo, I think maybe add these specific users to your
> whitelist?
>
> -- John.
>

Re: [M100] DVI Operation

[John Gardner]

Msgs from some members of the several lists I monitor regularly

end up in my (gmail) spam folder - No idea why...

 ...


On 1/9/18, you got me  wrote:
> wouldn't you need the code that's on the ROM chips?
>
> 
> From: M100  on behalf of Jim Anderson
> 
> Sent: Thursday, January 4, 2018 9:38:21 PM
> To: m...@bitchin100.com
> Subject: Re: [M100] DVI Operation
>
>
> FWIW, I’ve also (I have now noticed) had a lot of Jan’s messages go into
> spam on my end (and I’m not using gmail).
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> jim
>
>
>
> From: M100 [mailto:m100-boun...@lists.bitchin100.com] On Behalf Of Brian
> White
> Sent: Thursday, January 04, 2018 12:35
> To: m...@bitchin100.com
> Subject: Re: [M100] DVI Operation
>
>
>
> Possibly the reason you feel ignored is your first post was sent to spam in
> gmail.
>
>
>
> I didn't see it until today.
>
>
>
> Gmail sticks this supremely helpful message on it:
>
>
>
> "Why is this message in Spam? It's from an address in the
> yahoo.com domain but has failed
> yahoo.com's required tests for authentication."
>
>
>
> I don't know what it *really* means, and I don't know if there is anything
> you can do about it on the client side, or if it's some misconfiguration in
> the mail list or if there is even anything actually wrong and it's actually
> gmail in error. It happens to a number of posts though.
>
>
>
> --
>
> bkw
>
>
>
> On Jan 4, 2018 4:04 AM, "VANDEN BOSSCHE JAN"
> > wrote:
>
> A guy walks in to the doctor's office.
>
> He says:
>
> "Doctor, I have the impression that people are constantly ignoring me."
>
> The doctor says:
>
> "NEXT!"
>
>
>
> Greetings from the TyRannoSaurus
>
> Jan-80   |\  _,,,--,,_
>
> @ work  / ,`.-'`'   ._  \-;;,
>
>|,4-  ) )_.;.(  `'-'
>
>   <---''(_/._)--'(_\_)
>
>
>
> From: M100
> [mailto:m100-boun...@lists.bitchin100.com]
> On Behalf Of Jan Vanden Bossche
> Sent: dinsdag 2 januari 2018 14:53
> To: m...@bitchin100.com
> Subject: [M100] DVI Operation
>
>
>
> [..]
>
>
>
> Could anybody with a DVI perform the following test:
>
> - start the DVI & the monitor
>
> - start the Model T without the DOS
>
> - in BASIC, type SCREEN 1,1
>
> Does the DVI react ?
>
>
>
> If it does, I have my answer. Next thing to do, is start scanning codes with
> a Raspberry Pi hooked up to the I/O bus of the Model T.
>
>
>
> Greetings from the TyRannoSaurus
> Jan-80
>
>
>
> 
>
> From: Brian White >
> To: m...@bitchin100.com
> Sent: Wednesday, 27 December 2017, 21:56
> Subject: Re: [M100] Rex ram/rom
>
> [..]
>
> Video expansion? Do you mean you want a Disk/Video Interface?
>
>
>
> The DVI uses the system bus.
>
> [..]
>
> [Image removed by sender.] Rejoignez-nous sur Facebook - Volg ons op
> Facebook
>
> DISCLAIMER
>
> Pensez à l’environnement, n’imprimez cette page et ses annexes que si c’est
> nécessaire. Ce message électronique, y compris ses annexes, est confidentiel
> et réservé à l’attention de son destinataire. Si vous n’êtes pas le
> destinataire de ce message, merci de le détruire et d’en informer
> l’expéditeur. Toute divulgation, copie ou utilisation de ce mail est dans ce
> cas interdite. La sécurité et l’exactitude des transmissions de messages
> électroniques ne peuvent être garanties.
>
> Denk aan het milieu; druk deze pagina en de bijlagen alleen af als het nodig
> is. Dit e-mailbericht (inclusief zijn bijlagen) is vertrouwelijk en is
> uitsluitend bestemd voor de geadresseerde. Als dit bericht niet voor u
> bestemd is, wordt u verzocht het te wissen en de afzender te informeren. Het
> is in dat geval niet toegestaan dit bericht te verspreiden, te kopiëren of
> te gebruiken. We kunnen niet garanderen dat de gegevensoverdracht via het
> internet veilig en nauwkeurig is.
>
>   ­­
>

Re: [M100] supercap

[John Gardner]

I've got a 3F supercap (from Mouser,  IIRC) in one of my 8201a's,

and a 5F in the other.

Not sure how long they'll keep RAM alive -  Weeks,  at least,  IME.

My MO is to use Eneloops in the battery pack,  which again IME,

don't leak,  & will keep RAM alive for years - The supercap picks

up the load when the Eneloops are removed for recharging.

Been doing this for 6 years now - Seems to work,  so far.

FWIW,  the Eneloops are over 10 years old now,  & still hanging

in there...   YMMV,  of course.

   Jack



On 1/4/18, Fugu ME100  wrote:
> Used this one previously:
> https://www.jameco.com/z/NHB60H3A2H-Evergreen-Battery-Nimh-3-6Volt80Mah-2-Pins-Std-14-16Hrs-8Ma-6Hrs-16Ma_2137473.html
>
> Need the 2pin version. They also have a 3pin version which will not fit the
> Ts.
>
> From: M100
> >
> on behalf of Tom Hoppe >
> Reply-To: >
> Date: Thursday, January 4, 2018 at 5:55 PM
> To: >
> Subject: Re: [M100] supercap
>
> While on the subject, where is a good place to obtain a replacement
> nicd/nimh for the M100? I have a supercap in mine just because they are easy
> to find (I think mine came from Amazon).
>
> Tom
>
>
> On Thu, Jan 4, 2018 at 12:48 PM, Fugu ME100
> > wrote:
> I agree I replace all mine with NiMH they are a) easy to get (at the moment)
> and b) are a direct fit into the old spot.
>
> As someone said it is nice to remove the AAs and come back later and be at
> the same point.  Although if I store a unit for a long time I turn off the
> backup too.
>
> From: M100
> >
> on behalf of Brian White >
> Reply-To: >
> Date: Thursday, January 4, 2018 at 2:42 PM
> To: >
> Subject: Re: [M100] supercap
>
> I'm not asking why replace the old battery. I'm asking why use a cap if it
> will have the same disadvantages plus an extra disadvantage of only
> delivering a fraction of the run time?
>
> I replace all mine with new nimh batteries.
>
> I could see dropping to a few hours or days of sleep time if you gain the
> advantage of a part that might last even longer than 30 years and there's
> nothing to leak and corrode even if it does fail some day. Then you are
> making the unit safe for indefinite long term forget about it storage.
>
> But an electrolytic cap makes no sense to me at all.
>
> --
> bkw
>
> On Jan 4, 2018 3:20 PM, "Peter Vollan"
> > wrote:
> IMHO you should check them for correct voltage and replace them as
> necessary. If allowed to discharge, they may corrode and damage the
> PCB. I think the feeling around here is that the correct supercap may
> be better than the nicad battery, as well as the fact that the nicads
> are getting hard to find.
>
>
> On 4 January 2018 at 02:16, VANDEN BOSSCHE JAN
> > wrote:
>>
>> I have some 10+ Model Ts, 100, 102 ,200 ,O.M-10 ,N.8201. But so far, I
>> have never changed the NiCd (?) battery in any of my machines.
>>
>> Now, should I be worried? Most of the machines I have are simply in
>> storage. (cold & dry) Typically, I launch 1 or 2 machines (always the same
>> ones) maybe once every 2-3 months. So, they don't get much usage.
>>
>> How can I tell that the backup-battery is going on the machines that I
>> use?
>> And those I don't use, are they safe?
>>
>> The caps that can replace the batteries, are they indistructible, or will
>> they leak, explode, desintegrate, ... too ?
>>
>> Greetings from the TyRannoSaurus
>> Jan-80 "
>> @ work( / \ )
>> --.ooo--(_)--ooo.---
>>
>>> -Original Message-
>>>
>>> Would this be suitable for a model 100?
>>> https://vetco.net/products/super-capacitor-10-956-f-5-5-
>>> volts?taxon_id=1892
>>
>> The primary problem with this one is the lead spacing is too close - it's
>> 5mm but the original battery is about 3/4 of an inch long with the pins at
>> each end (approximately 19mm, although I haven't precisely measured the
>> hole spacing on the PCB).  If the cap had longer leads or if the spacing
>> were close to 19mm you could bend them to fit.
>>
>> It would be really handy to find a cap in this form factor which would
>> just drop into the existing holes, although the diameter might 

Re: [M100] diagnose

[John Gardner]

If you're convinced it's stuck in a loop,  removing all power (including

the NiCd) for a time should fix that



On 12/14/17, Mauro Pintus  wrote:
> Thank you Fugu and Brian for the feedback.
>
> Yes I tried the beep BASIC test with no luck and also the cold start (the
> M10 and the M100 are almost identical...).
>
> I made few other measurements trying to replicate what Brian is doing and
> for sure the unit is in a loop...
>
> In the linked google photo album I added another picture (the first one)
> showing the ROM CS (Pin 20 yellow trace) and the IO/M of the main processor
> (Pin 34 blue trace)
> https://photos.app.goo.gl/8YSbaAxZBuXu5rjC2
>
> As you can see at the beginning of the repeted sequence, I get only 5 pulses
> on the IO/M
>
> The strange thing is that there is so little activity on the RAM CEx (chip
> enable), like nothing is loaded.
>
> Finally I measured also the CSx (chip select) on the LCD connector and none
> are moving, confirming that on the LCD nothing can be displayed.
>
> Mauro
>
>
>
>
> On Dec 13, 2017, at 7:01 AM, Fugu ME100 wrote:
>
>> Vee at –4.9V is good.
>>
>> You may have already looked at these options, so apologies if you have…
>>
>> The repetitive nature of the ROM CS cycling could be the CPU in a software
>> loop waiting for keyboard input.   Have you tried the BEEP test from BASIC
>> to see if the motherboard is actually running?
>>
>> Have you tried a cold start?  On the M100 press ctrl+pause while powering
>> on, not sure about the M10.  It could be the memory is corrupted with the
>> loss of backup power.  Always a good idea when first powering after
>> switching off/on the backup power..
>>
>>
>> From: M100  on behalf of Mauro Pintus
>> 
>> Reply-To: 
>> Date: Tuesday, December 12, 2017 at 5:24 PM
>> To: 
>> Subject: Re: [M100] diagnose
>>
>> Hi,
>>   I have a not working Olivetti M10 and a Rigol DS1104Z oscilloscope, so I
>> made few measurement to try to help Brian and in the mean time try to
>> troubleshoot my unit.
>>
>> My unit was working properly and stopped as soon as I flipped the NiCd
>> battery switch off while the unit was ON (done by mistake with the cover
>> open).
>> Now the screen turn on but I can regulate just the contrast and no text
>> appear on the screen.
>> I also made a small arduino circuit to test the LCD alone, and I'm able to
>> write text on it, so the LCD should be fine.
>>
>> BTW I think Brian is using way too long ground leads on the oscilloscope
>> probe.
>> I made my measurement clipping the alligator clip to the metal case of the
>> main crystal that in the M10 is grounded with a pice of bare wire.
>> Is your scope grounded? I can see in one of your pictures the usual US
>> plug with only 2 terminals...
>>
>> Here are some screenshots of my measurements.
>>
>> https://photos.app.goo.gl/8YSbaAxZBuXu5rjC2
>>
>> Pictures:
>> 1) CLK pin 37 of the 8085
>> 2) Pin 7 of the 8085
>> 3-4) CS Pin 20 of the ROM it seems to cycle over and over
>> 5) Reset * at power on
>>
>> VEE is 4.9V
>> V across the battery is 4.02 when the unit is on and 3.9 when off
>>
>> Tomorrow I'll continue hoping Brian or some of you can confirm/compare
>> some of my measurements.
>> Have a nice day
>> Ciao
>>   Mauro
>>
>> NOTE: I think I will measure all the pins on the system bus so anyone with
>> an oscilloscope can do the same without opening the unit case...
>>
>>
>>
>>
>>
>> On Dec 11, 2017, at 9:28 AM, Fugu ME100 wrote:
>>
>>> Ah the “special tool” requirement always hated to see that in any
>>> step…..
>>>
>>> What did the –5V measure on the meter?  If it is not within spec neither
>>> the LCD or buzzer will work.
>>>
>>> From: M100  on behalf of Brian White
>>> 
>>> Reply-To: 
>>> Date: Sunday, December 10, 2017 at 11:30 PM
>>> To: 
>>> Subject: Re: [M100] Fwd: Re: diagnose
>>>
>>> Thanks for that tip.
>>>
>>> And oh like some GM repair manuals where replacing an entire transmission
>>> might be 11 steps, but one of them is to use the $12,000 machine no one
>>> outside of the factory has ever even seen.
>>>
>>>
>>> On Dec 8, 2017 1:38 PM, "Fugu ME100"  wrote:
>>> It might be better to use the CLK (37) output as a reference if it is
>>> needed.  The CLK is derived from the X1,X2 XTAL inputs and should not be
>>> impacted by the loading of the scope probes.
>>>
>>> The M100 reference manual is quite good for troubleshooting some parts,
>>> although it does have a few broad instructions like “Check All IC’s”.
>>> :-)
>>>
>>> From: M100  on behalf of Brian White
>>> 
>>> Reply-To: 
>>> Date: Friday, December 8, 2017 at 9:55 AM
>>> To: 
>>> Subject: Re: [M100] Fwd: Re: diagnose
>>>
>>> I noticed something a couple days ago. 

Re: [M100] Tandy 102 Text question

[John Gardner]

There's something to be said for bit-banging...   "8)

On 11/29/17, Ron Lauzon  wrote:
> I located the pin numbers for the Mega's serial ports.  It looks like
> Serial1 and Serial2 conflicted with the SD card shield.  But I did get
> communication on Serial3.
> Unfortunately, it has the same problem.  Fails after the same number
> of chars sent.
>
> So not much of an improvement.  But at least I got rid of the
> SoftwareSerial library from my project.
>
> I broke out the RS-232 shifters that supports DSR/DTR and set them up
> to loopback on the RS-232 side, but I couldn't get them to work.
> I have a couple of things I need to check, but I think those shifters
> simply don't work.
>
>
>
> On Tue, Nov 28, 2017 at 6:45 PM, Bob Pigford  wrote:
>> Ron,
>> On one of my Arduino projects I finally gave up on SoftwareSerial on an
>> Uno and went to a Mega so I could have several real serial ports.  As I
>> recall, there are a total of 4 available (don't remember the pin nos.).
>> Something like ...
>>  Serial.
>>  Serial1.
>>  Serial2.
>>  Serial3.
>>
>> Example for the first 2 hardware ports on a Mega:
>> void setup() {
>>   // initialize both serial ports:
>>   Serial.begin(9600);
>>   Serial1.begin(9600);
>> }
>> Thereafter I had no serial issues.  I realize that you have probably
>> already tried this, but I offer this small thing from my experience.
>> Good Luck,
>> Bob
>>
>>
>> -Original Message-
>> From: M100 [mailto:m100-boun...@lists.bitchin100.com] On Behalf Of Ron
>> Lauzon
>> Sent: Tuesday, November 28, 2017 5:53 PM
>> To: m...@bitchin100.com
>> Subject: Re: [M100] Tandy 102 Text question
>>
>> I'm using pins 62 and 63.  I am using an Arduino Mega (left over from a
>> previous project that needed more memory and the standard Arduino Uno).
>> Those are were the only available pins that would support the
>> RS-232 shifter.
>>
>> I'm making the assumption based on the fact that the Arduino is faster.
>> But it's just an assumption.  But I did do a SAVE "COM:98N1E"
>> in my testing and more than 80 bytes were sent to the Arduino.
>>
>> For debugging right now, all characters that enter the Arduino are echoed
>> out the USB/Serial.  So I can see everything that arrives on the serial
>> connection.
>>
>>
>> On Tue, Nov 28, 2017 at 5:46 PM, Fugu ME100  wrote:
>>> Which pins are you using for the software serial port?  It should be
>>> able to run up to at least 57600bps on the Ardruino.
>>>
>>> How do you know the 102 stops sending?   Could the Arduino stop
>>> receiving?
>>>
>>>
>>> I assume at the moment you are just reading in on the Software Serial
>>> port and passing it out on the USB port to make sure everything works
>>> OK?
>>>
>>> On 28/11/17, 2:07 PM, "M100 on behalf of Ron Lauzon"
>>> 
>>> wrote:
>>>
Here's the setup I'm going to talk about:
Tandy 102, serial cable to my Arduino with an RS-232 shifter.  I'm
using the SoftwareSerial library to interface the RS-232 shifter to
the Arduino via the Arduino's TX/RX pins - as opposed to using the USB
cable.

Software-wise, this is pretty simple.  I'm just writing a text file in
the Text app and saving it to COM:98N1E

Here's my frustration.  No matter what I do, the 102 stops sending
after about 80 bytes.

The only way I could get it to work was to reduce the speed to 300 BPS
(and, of course, saving to COM:38N1E).

Keep in mind that this is the 102 sending to the Arduino.  I find it
difficult to believe that the Arduino couldn't keep up.  And when I
tried other BPS, it stopped in exactly the same place: at 80 bytes.

The 102 never showed an error message.  Everything looked like it
worked fine on that end.  But the rest of the text file never appeared
on the Arduino side.

The Arduino set up doesn't support hardware flow control.  So I
thought that enableing XON/XOFF would make sure that the 102 didn't do
that (No, I didn't see any XON/XOFF characters on the Arduino side
either).


Is there some sort of strangeness in the 102 that turns some sort of
hardware flow-control on for speeds > 300 BPS?  Or did I miss setting
something?

If there was a problem with one side keeping up, I expected to see
dropped characters, not communications just stopping after 80 bytes.


--
Ron Lauzon - rlauzon at acm dot org
   Homepage:
https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwebpages.
charter.net%2Frlauzon%2F=02%7C01%7Cb4me100%40hotmail.com%7C1da1d8
f1ef
344c75fb9108d536ac9c19%7C84df9e7fe9f640afb435%7C1%7C0%7C63
6475
037326050935=s6klg5s%2Bx65YTwdo%2Ba2WAWUb%2FJrU6SzRhRuIb8QbeC8%3
D
served=0
   Weblog:
https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fronsa
part

Re: [M100] new project

[John Gardner]

Yup.  If you have a clock,  you know what time it is.

If you have more than one clock,  you don't...   :)

 ...


On 10/31/17, Peter Vollan  wrote:
> Let me sure that I understand: however correctly you set the time on
> your Model 100, it will "drift off", because it cannot keep correct
> time?
>
>
> On 26 October 2017 at 12:58, John R. Hogerhuis  wrote:
>>
>>
>> On Thu, Oct 26, 2017 at 12:22 PM, Brian Brindle 
>> wrote:
>>>
>>> Hey John,
>>>
>>> To move RAM images around I"m using REX, creating a backup of the RAM
>>> image and saving it to "disk" or in this case Mcomm or my NADS. I like
>>> Mcomm
>>> because the directory it saves everything in on the phone is
>>> automatically
>>> backed up (by another application) to dropbox right now. Then I load
>>> that
>>> image in VirtualT on the PC.
>>>
>>
>> Ah. Well, I did write a program to sync time with NADSBox.
>>
>> http://bitchin100.com/wiki/index.php?title=Synchronize_Time_with_your_NADS
>>
>> -- John.
>

Re: [M100] ROM call: MAKFIL (2239h) help plz

[John Gardner]

Thanks.

On 10/25/17, John R. Hogerhuis <jho...@pobox.com> wrote:
> On Wed, Oct 25, 2017 at 2:48 PM, John Gardner <gof...@gmail.com> wrote:
>
>> Thanks,  John.  Any particular file you have in mind?  I don't see
>>
>>
> I guess "technical reference" and "technical notes" are the relevant stuff.
>
> -- John.
>

Re: [M100] ROM call: MAKFIL (2239h) help plz

[John Gardner]

AOBTW,  that site went about 15 years without an update - Looks different

now,  so I'm guessing the Band is taking the year off...

On 10/25/17, John Gardner <gof...@gmail.com> wrote:
> Thanks,  John.  Any particular file you have in mind?  I don't see
>
> a "NEC Programmers Reference".
>
>
>
> On 10/25/17, John R. Hogerhuis <jho...@pobox.com> wrote:
>> On Wed, Oct 25, 2017 at 2:17 PM, John Gardner <gof...@gmail.com> wrote:
>>
>>> "NEC Programmers  Reference"?
>>>
>>> OK - I'll bite...
>>>
>>>
>> http://www.web8201.net/default.asp?content=tech.asp
>>
>> -- John.
>>
>

Re: [M100] ROM call: MAKFIL (2239h) help plz

[John Gardner]

Thanks,  John.  Any particular file you have in mind?  I don't see

a "NEC Programmers Reference".



On 10/25/17, John R. Hogerhuis <jho...@pobox.com> wrote:
> On Wed, Oct 25, 2017 at 2:17 PM, John Gardner <gof...@gmail.com> wrote:
>
>> "NEC Programmers  Reference"?
>>
>> OK - I'll bite...
>>
>>
> http://www.web8201.net/default.asp?content=tech.asp
>
> -- John.
>

Re: [M100] ROM call: MAKFIL (2239h) help plz

[John Gardner]

"NEC Programmers  Reference"?

OK - I'll bite...



On 10/25/17, Stephen Adolph  wrote:
> Boy I wish we could all agree on variable names in M100!
>
> here is my assessment of what you've done-
>
> 1)  you are using the wrong starting location.  Think you need to use the
> ASCTAB (DOSTART?) location which is the lowest first byte of .DO file data.
> 2)  you need to ensure your new directory entry gets the correct
> (incorrect) address , meaning you need to trick LNKFIL (DIROK?) to order
> the file names correctly.  in this case ASCTAB-1. in this way the current
> directory entry, that points to ASCTAB, will be ordered and linked
> correctly.
>
> make sense?
> and I agree with John, without the NEC reference I would never have gotten
> REX to work.
>
>
> On Wed, Oct 25, 2017 at 4:59 PM, Stephen Adolph 
> wrote:
>
>>
>>
>> Here is some code to look at.
>> do you run LNKFIL afterwards? you must!
>>
>> note you must ensure the address of the new file name in the ram
>> directory
>> is 1 less than the actual starting location to ensure LNKFIL orders the
>> file names correctly.
>>
>>
>>
>> ramfile_copy_DO:; new directory entry address in TEMP3
>> ; source directory entry at input buffer
>>
>> ; ASCTAB-1 start of new file in directory entry
>> ; make xx byte hole at ASCTAB, xx is file length incl
>> EOF
>> ; copy data to hole
>> ; LNKFIL
>>
>> lhldBINTAB; hl points to injection point
>> shldTEMP3; store injection point in TEMP3
>> dcxh
>> shldTEMP1; start address for new directory entry in
>> TEMP1
>>
>> callramcopy_makehole; make the hole
>> callramfile_copy_file; copy the data into the hole
>> jmprammenu_loop0; done
>>
>> ;---
>> 
>> ramcopy_makehole:
>>
>> lhld TEMP4; get length of file
>> pushh; on stack
>>
>>   
>>
>> popb; length of file in bc
>>
>> lhldTEMP3; hl is injection point
>>
>> rst6
>> .dwMAKHOL; make hole BC long at HL, adjusting
>> pointers
>>
>> ; MAKHOL adjusts BINTAB, VARTAB, ARYTAB
>> ; MAKHOL does not adjust ASCTAB, needed by LNKFIL
>>
>>
>> jcramfile_copy_fail4; jump here if not enough space
>>
>> ret
>>
>>
>> ;---
>> 
>> ramfile_copy_file:; copy the data into the hole
>>
>> ; TEMP2 new directory entry address
>> ; INPUT_BUFFER source directory entry, points to
>> source file
>> ; TEMP3 injection point of new file
>> ; TEMP1 start address for directory entry
>> ; TEMP4 size
>> ; TEMP5 source data (system file)
>>
>> lhldTEMP4
>> movb,h
>> movc,l; get size in BC
>>
>> lhldTEMP3; target in hl
>> xchg; target in de
>>
>> ldaDSTATE
>> ani1000b
>> jzramfile_copy_file_1
>> ; use when in ram file mode
>> lhldINPUT_BUFFER+1d
>> callfix_hl_mode; correct hl for lower block
>>
>> ; hl source, de target
>> callramfile_copy_block; copy block
>> jmpramfile_copy_file_2
>>
>> ramfile_copy_file_1:; use when copying system files
>> lhldTEMP5; hl = source
>> ; hl source, de target
>> xchg; de source hl target
>> callMOVEB_D_H; mov bc bytes from de to hl
>>
>> ramfile_copy_file_2:
>>
>> lhldTEMP2; TEMP2 holds pointer for new directory
>> entry
>> inxh
>> xchg
>> lhldTEMP1; start address for directory entry in hl
>> shlx; store new start of file into new directory
>> entry
>>
>> rst6
>> .dwLNKFIL; fix up directory
>>
>>
>> ret
>>
>>
>> On Wed, Oct 25, 2017 at 4:40 PM, Stephen Adolph 
>> wrote:
>>
>>> willard, would commented assembly help?
>>> I have this working in REX Manager...
>>>
>>>
>>> On Wed, Oct 25, 2017 at 4:20 PM, Willard Goosey  wrote:
>>>
 So, there is this (from Mike Nugent's RAM-ROM file)

 ;2239H - Insert entry into directory.
 ; Entry:
 ;   HL - Points to empty directory slot
 ;   DE - Contains address of file in RAM
 ;A - Attribute (80h=.BA, C0h=.DO, A0h=.CO, etc.)
 ; Note: Routine gets filename from FC93H, where it must be
 ;   stored,padded with spaces, no delimiter.
 ; Exit: DE - Unchanged

 And I have the 

Re: [M100] Who wants a REX? Gauging interest

[John Gardner]

Hi Brian.

I'm also struggling with diminished eyesight - Not to mention the

onset of senescence...  Clip-on loupes for eyeglasses help.  Also

have had some luck reflowing single-sided SMD boards on kitchen

stove "glass" burners.  YMMV,  naturally...

 ...


On 10/9/17, Brian Brindle  wrote:
> I took advantage of the 3 day weekend and worked on my boards. Stupidly I
> started them in a temporary location rather than the "bench" and scrapped
> the 1st board with a stupid cutting mistake after I had it already
> populated.
>
> I have built many things in my lifetime but this project is somehow special
> and has been a journey in self discovery. I have learned so much about
> myself. First, I am a very angry man. Second, I am apparently blind now
> requiring more magnification and light than I thought ever possible. Third,
> I suffer from some weird form of aphasia that only lets me figure out that
> what I'm vigilantly checking and double checking is completely backwards
> when it's impossible to fix. Finally, always go with what you know. I tried
> several of the new fandangled methods for SMT soldering that seemed less
> complicated but ultimately what worked is my old methods of doing things
> that I thought were inferior. Trust your gut.
>
> Anyway, I too have some cad/stellated boards on the way to test and have a
> pretty good process for cutting/shaping the existing ones. I've also
> determined that hot air is the way to go for assembling these things but
> still I can only crank out about one an hour. I'm using some solder paste
> and one of these guys:
> https://www.amazon.com/WEP-858D-Soldering-Station-Suitable/dp/B0055B6NGE
>
> I got some epoxy (to hold the flash on) and plan to try the hot skillet
> method later this week. If I can do several boards at once I may be willing
> to both share my setup and help with production of these things if
> necessary.
>
> More to come in the next few days.
>
> Brian
>
>
> On Mon, Oct 9, 2017 at 8:46 AM, Josh Malone  wrote:
>
>> I'm shooting to produce them at the same $60 price that club100 sold
>> them previously.
>>
>> As a status update, I'm expecting delivery of the castellated board
>> test this week. Assuming I can validate this modification to the PCB
>> design, I think the pre-castellated board from OSH Park will be the
>> way to go. Still hoping to announce a small board run sometime this
>> month. We'll see.
>>
>> -Josh
>>
>> On Mon, Oct 9, 2017 at 4:42 AM, James Zeun  wrote:
>> > I've little experience in this area, but a friend of mine makes
>> > hardware
>> for
>> > the ZX Spectrum, Timex computer to those in the states. I know he ended
>> up
>> > out sourcing work to China as it was cheaper then populating 30+ boards
>> by
>> > hand. I don't believe his IDE adapter was anymore complicated then the
>> > REX,not sure if he had to flash chips.
>> >
>> > If the decision is to solder them ourselves, I'll put my hand up and
>> offer
>> > to help out. My soldering isn't too ropey, probably not as good as some
>> of
>> > the chaps on here :-)
>> >
>> > How much is an assembled REX? I already own one, but wouldn't mind
>> having a
>> > spare.
>> >
>> >
>> >
>> > On 9 Oct 2017 6:31 a.m., "ray gordon"  wrote:
>> >>
>> >> Hi,
>> >>
>> >> I hav'nt been monitoring the list for a couple weeks, but I'm
>> >> certainly
>> >> interested in several rexes
>> >>
>> >>
>> >>
>> >>
>> >> 
>> >> From: M100  on behalf of Jim
>> Anderson
>> >> 
>> >> Sent: Thursday, October 5, 2017 7:01 PM
>> >> To: m...@bitchin100.com
>> >> Subject: Re: [M100] Who wants a REX? Gauging interest
>> >>
>> >> > -Original Message-
>> >> >
>> >> > You don't need any tpdd device, you just need any modern pc and a
>> >> > usb
>> >> > serial cable and some free software.
>> >>
>> >> Sorry, by 'TPDD device' I meant TPDD emulators as well, not just the
>> >> actual Tandy drives or NADSBox or whatnot.  I guess I should have said
>> 'some
>> >> kind of TPDD-compatible device'.
>> >>
>> >> > The only problem would be if the cpld programming is not the same
>> >> > for
>> >> > 100 vs 200. If not, then it would probably not be possible to take a
>> 100
>> >> > rex and re-flash it to a 200 rex using only a 200.
>> >>
>> >> It's the same CPLD code.  AFAIK re-flashing a 100 REX with 200
>> >> firmware
>> in
>> >> a 200 ought to work the same way as re-flashing a 4.8 REX to 4.9...
>> >>
>> >> > I have a 200, but I don't remember if Stephen has made the 200
>> >> > version
>> >> > firmware available yet.
>> >>
>> >> Yes, it's available.  (So is the NEC firmware.)
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> jim
>>
>

Re: [M100] BASIC Integer Division Question

[John Gardner]

As part of the random number generator subroutine,  why not print the

returned values & ask your student if A/B is a valid operation?



On 9/20/17, Roger Mullins <km4...@gmail.com> wrote:
> LOL it happens I guess; I'm close to that many years removed from having to
> deal with most of this stuff myself.
>
> Anyhow, I don't think I described my predicament as clearly as I should
> have.  My focus is less on having the computer do the math (although it has
> to in order to check the answer given), and more on not presenting an
> unnecessarily difficult problem to the kiddo.  Here's the general idea.
>
> 1) GOSUB to send back two random integers, A and B
> 2) Print 'What is A divided by B?'
> 3) Input quotient (C)
> 4) Input remainder (D)
> 5) GOSUB to check the answers - correct if C = A\B and D=(A mod B)
>
> What I'm trying to figure out is where to insert the test between steps 1
> and 2 to make sure that the program doesn't spit out "What is 5 divided by
> 12" or "What is 8 divided by 0".
>
> On Wed, Sep 20, 2017 at 11:35 AM, John Gardner <gof...@gmail.com> wrote:
>
>> Yep,  I screwed it up - The Remainder is what's left of the Dividend.
>>
>> Anyway,  have fun - My 9-year-old daughter is nearly 40. Good times...
>>
>> On 9/20/17, John Gardner <gof...@gmail.com> wrote:
>> > Or simply subtract the Divisor from the Dividend until the Dividend
>> >
>> >  is less than the Divisor - The index of the loop is the
>> >
>> > Quotient,  & the Remainder is what's left of the Quotient.
>> >
>> > I hope I did'nt screw that up - 3rd grade was about 60 years ago...
>> >
>> >:)
>> >
>> > On 9/20/17, John R. Hogerhuis <jho...@pobox.com> wrote:
>> >> I guess for division your random numbers are the divisor and the
>> >> result
>> >> of
>> >> the division.
>> >>
>> >> Multiply them together to get what you are to divide.
>> >>
>> >> -- John.
>> >>
>> >
>>
>

Re: [M100] BASIC Integer Division Question

[John Gardner]

Yep,  I screwed it up - The Remainder is what's left of the Dividend.

Anyway,  have fun - My 9-year-old daughter is nearly 40. Good times...

On 9/20/17, John Gardner <gof...@gmail.com> wrote:
> Or simply subtract the Divisor from the Dividend until the Dividend
>
>  is less than the Divisor - The index of the loop is the
>
> Quotient,  & the Remainder is what's left of the Quotient.
>
> I hope I did'nt screw that up - 3rd grade was about 60 years ago...
>
>:)
>
> On 9/20/17, John R. Hogerhuis <jho...@pobox.com> wrote:
>> I guess for division your random numbers are the divisor and the result
>> of
>> the division.
>>
>> Multiply them together to get what you are to divide.
>>
>> -- John.
>>
>

Re: [M100] BASIC Integer Division Question

[John Gardner]

Or simply subtract the Divisor from the Dividend until the Dividend

 is less than the Divisor - The index of the loop is the

Quotient,  & the Remainder is what's left of the Quotient.

I hope I did'nt screw that up - 3rd grade was about 60 years ago...

   :)

On 9/20/17, John R. Hogerhuis  wrote:
> I guess for division your random numbers are the divisor and the result of
> the division.
>
> Multiply them together to get what you are to divide.
>
> -- John.
>

Re: [M100] Inaugural Tandy Assembly in Chillicothe, Ohio 7-8 October 2017 -- who is going?

[John Gardner]

 !  Good luck,  Philip...

On 9/8/17, Philip Avery  wrote:
> Me, me! I'm making the trip from New Zealand. But I won't be the
> furthest travelled, one is coming from Australia.
> If all goes well between now & then in my development dept, I'll be
> bringing my remem-powered T102 to demonstrate CP/M on a real machine.
> I'm also into Model III & 4, so look forward to meeting the podcasters &
> other guys I've met online.
>
> Philip
>
> On 9/09/2017 6:19 AM, John W. Linville wrote:
>> Who is excited about Tandy Assembly? It will be here in less than 30
>> days? All Tandy-branded (and related) machines are welcome!
>>
>> http://www.tandyassembly.com/
>>
>> See you in Chillicothe!
>>
>> John
>
>

Re: [M100] Another eBay Alert

[John Gardner]

...Careful there, Mr. Gardner...

Sad to say,  I remember manual typewriters all too well.

I finally got into the Selectric income bracket when the

Air Force bought me one...   "8(

On 9/5/17, Roger Mullins <km4...@gmail.com> wrote:
> I wasn't even thinking of those newfangled Selectrics... I figure those
> kids were already OK with a 'return' key.  I was thinking more along the
> lines of the manual (literal) carriage return crowd.
>
> On Tue, Sep 5, 2017 at 5:07 PM, John Graf <j...@grafs.us> wrote:
>
>> Careful there, Mr. Gardner, with the age related dig
>>
>> Oh, and what was it we were talking about anyway? <Grin!>
>>
>>
>> On Sep 5, 2017, at 3:35 PM, John Gardner <gof...@gmail.com> wrote:
>>
>> Oh well - If you're old enough to remember this stuff,
>>
>> you're probably too old...   "8(
>>
>>
>

Re: [M100] Another eBay Alert

[John Gardner]

I could'nt remember the key color scheme(s) on the Selectrics,

if any;  a quick look through the images Boodle pulls up did'nt

turn up multi-color key schemes,  but I could swear I've seen

some...  Oh well - If you're old enough to remember this stuff,

you're probably too old...   "8(

On 9/5/17, Roger Mullins  wrote:
> I wonder if it was to make the transition easier for folks switching over
> from typewriters?  (That's purely conjecture on my part).
>
> On Tue, Sep 5, 2017 at 2:43 PM, Kim Holviala  wrote:
>
>> On 05 Sep 2017, at 21:09, John Graf  wrote:
>> >
>> > Why is the return key different color than the rest of the keys? Is it
>> not original, or were return keys different color in the “older” days?
>>
>> In the Good Old Days(tm) the Return/Enter key was usually colored
>> diferently. I don't know why, it was never really discussed in the 80's -
>> that's just how it was.
>>
>>
>> - Kim
>>
>>
>>
>

Re: [M100] Figtronix Main ROM adapter

[John Gardner]

...You could make a board where the chip is soldered on, and that
would fit in the original socket.  The problem then is, that chip
would not be re-programmable very easily, because the combined
chip-on-adapter creates a non-standard pinout that a programmer
doesn't support...

A pgming adapter sounds doable - And cheap...




On 8/23/17, Brian White  wrote:
> The problem is that the new adapter is too tall for the available space, if
> it's plugged in to the original socket.
>
> The reason it's too tall is because of the plcc socket. Through-hole style
> plcc sockets are pretty tall.
>
> The way that adapter works, you lose the ability to plug the original rom
> back in, but but the new rom is removable and rewriteable without any
> further special adapters. You just pop the bare chip out and it pops into a
> standard reader, with an adapter too, but a standard one that comes with
> the reader just to adapte the physical form, notrearrange pins into a
> special pinout.
>
> There are lots of possible work-arounds, but they all have some kind of
> down-side just like desoldering the original socket is a down-side.
>
> You could make a board where the chip is soldered on, and that would fit in
> the original socket.
>
> The problem then is, that chip would not be re-programmable very easily,
> because the combined chip-on-adapter creates a non-standard pinout that a
> programmer doesn't support.
>
> You would have to make a "reverse adapter" to ever reprogram later, or get
> a test-clip that clips righ onto the chip on the board.
>
> I *think* it should bebpossible to make an adapter that plugs in to the
> original dip socket and still has a plcc socket itself, by using a surface
> mount plcc socket instead of a throu-hole one. There is a figtronix option
> rom board that uses that. I have made a few and they work. But the
> down-side in *that* case is that a low profile surface mount plcc socket
> can only be soldered with an oven or hot air and paste. It's MUCH simpler
> to solder the through-hole kind for the average hobbyist. I have managed
> it, and did it using a cheap $20 hot air gun instead of a $60-$500 "real"
> hot air soldering station, but it was tricky and finnicky and not reliably
> reproduceable. I also botched it several times and had to keep starting
> over. (heat it all up enough to come off, clean off all solder, and start
> over very carefully applying new paste and flux and trying lay the socket
> in exactly the right position...)
>
> No mmatter which way you turn, there is either one problem, or some other
> problem.
>
> Mike Stein has a board that uses a full dip chip, and can plug in to the
> original socket, but I don't think it can accomodate a socket to make the
> new, standard 27C256 removable for reprogramming and still all fit in the
> case. If it can, that would be the way to go. Otherwise it's just one of
> many equally good-with-a-problem options.
>
> Remember, this is all only for M100's that have the original non-standard
> pinout main rom. Some late M100's and all T102's don't have any problem and
> don't need any adapter.
>
> --
> bkw
>
> On Aug 23, 2017 5:18 PM, "Gary Weber"  wrote:
>
>> Hello all,
>>
>> I have a question for anyone out there who has created a main ROM adapter
>> for their Model 100, using these parts and following these instructions:
>> http://tandy.wiki/FigTronix#Model_100_Main_ROM_27C256_PLCC_Adapter
>>
>> My question has to do with this statement:
>>"Unfortunately, using this adapter requires desoldering the original
>> socket from the motherboard. It IS possible to do this, without damaging
>> either the motherboard or even the old socket, with flux, solder wick,
>> and
>> patience."
>>
>> I'm a little confused as to why the original socket would have to be
>> de-soldered.  Can't this adapter just be plugged into an empty CPU
>> socket?
>> Or is it the case that the M100 case can't close again because of
>> something
>> so high in that socket pressing against the keyboard circuit-board?
>>
>> Thanks for the info!
>>
>>
>> --
>> Gary Weber
>> g...@web8201.com
>>
>

Re: [M100] Bar Code Reader

[John Gardner]

...I've been slowly introducing my daughters (7 and 9) to BASIC.

Nice!   "8)

If you're not careful,  those kids will learn how to think...

 ...




On 8/18/17, Roger Mullins <km4...@gmail.com> wrote:
> Fun ideas! My daughter has a Frozen book that has tiny code squares of some
> sort (not QR, but not bar either) that's sort of interactive with a
> scanning wand that came with it.  I had no idea there was even such a
> 'thing' as a barcode gaming scene, so I'll definitely look into that.  And
> I love the idea of geocaching, if only because we'd be walking around the
> park with our M100's. :-)
>
> You know (alert: rambling aside ahead), I downloaded the scanned BCR manual
> and was reading it last night.  What I love about our computers is the
> forced economy when it comes to programming.  I was never a big time
> programmer by any stretch, but I remember having to really take the time to
> map stuff out and try to make it as efficient as possible because memory
> constraints dictated it.  The inventory program that's listed in the BCR
> book doesn't do a whole lot, but I couldn't help but wonder what it would
> look like 'today' by the time you had to import this library over here and
> incorporate that driver from over there, etc.  I'm glad programming in
> general has reached a much larger audience nowadays with all the IDEs and
> bells and whistles and modules and stuff, but there's a minimalist beauty
> in a lot of the 'old school' code that I think a lot of people miss.  I've
> been slowly introducing my daughters (7 and 9) to BASIC.  They recognize
> that it's a whole lot easier to pick up their tablet, tap something, and
> play whatever high-def game they want, but it seems like they also can't
> help being a little impressed when they're watching me tinker with
> something and I show them the listing and they see what a few lines of code
> can accomplish.
>
> On Fri, Aug 18, 2017 at 10:31 AM, Kurt McCullum <kurt.mccul...@att.net>
> wrote:
>
>> As luck would have it, I found the files on my key chain USB drive.
>>
>> BCR Files
>> <http://www.club100.org/memfiles/index.php?=0==Kurt%20McCullum/Bar%20Code%20Reader>
>>
>>
>>
>> Kurt
>>
>>
>> On Friday, August 18, 2017 7:26 AM, Kurt McCullum <kurt.mccul...@att.net>
>> wrote:
>>
>>
>> I've got those programs Willard. I'll try to upload them today.
>>
>>
>> On Friday, August 18, 2017 12:45 AM, Willard Goosey <goo...@sdc.org>
>> wrote:
>>
>>
>> On Thu, 17 Aug 2017 12:35:28 -0500
>> John Gardner <gof...@gmail.com> wrote:
>>
>> > Once upon a time PC mags had bar code pgm listings.  Getting
>> > that going again might be fun...  "8)
>> >
>> Speaking of... the "TandyCode" BCR driver was a seperate software
>> package and does not seem to have made it onto the Net. I speak
>> specifically of :26-3847 TandyCode
>>
>> There was also 26-3846 Bar Code Reader that either supported more bar
>> code formats or expanded on the existing drivers?
>>
>> Anyway, you know the drill. If anybody has this software, please upload
>> so it can be preserved.
>>
>> Willard
>> --
>> Willard Goosey  goo...@sdc.org
>> Socorro, New Mexico, USA
>> I search my heart and find Cimmeria, land of Darkness and the Night.
>>   -- R.E. Howard
>>
>>
>>
>>
>>
>

Re: [M100] Bar Code Reader

[John Gardner]

Once upon a time PC mags had bar code pgm listings.  Getting

that going again might be fun...   "8)

 ...


On 8/17/17, Roger Mullins  wrote:
> Very excited - I picked up a bar code reader on eBay this morning via Buy
> It Now while I was waiting for the drop-off line to clear at my kid's
> school!  I've been wanting one to play around with for a while now but I've
> kept getting out-bid.  It's just the wand itself, no software or book, so
> I'm going to download the scanned manual and follow the discussion thread
> here from a few weeks ago about setting it up.
>
> I'm curious to know - any of you have one set up, using it for anything
> practical?  I'm looking forward just to the challenge of getting it up and
> running, but I'm also brainstorming ways to actually put it to use.  I
> don't really have anything I need to inventory. :-)
>
> I'm also awaiting delivery of my replacement M100 (also from eBay) as I
> never got the screen/boot-up issue figured out on mine and I was worried I
> would end up putting more into diagnostics than it would cost to just pick
> up a 'new' machine.  Plus it's always good to have an in-house supply of
> parts.  It should be here by the weekend.
>