Re: [M100] New member

[Peter Vollan]

I am using the Model 100 that my father used to take on business
trips, so I have been in this for awhile.

Also have a TI-99/4A and an Amiga 500.

On Mon, 30 Mar 2020 at 17:13, Greg Swallow  wrote:
>
> Welcome aboard. Am sure you'll find in -- not only entertaining, but a great 
> source of help.
>
> God Bless,
> GregS <><
>
> TRS M100 (7), M102, Nec 8201a
> Apple PowerMac G5x2 (MorphOS/OSx 10.5.8), iBook G4 (MorphOS)
> Micro P4 (2) servers openSuse (13.x)
> Toshiba Portege M200 (Centrino 2GHz) openSuse 15.1 Tumbleweed
> Dell inspirion 530 (Core2Duo) openSuse (15.1) Tumbleweed
> HP Pavilion (Core2Quad) Windows 7
>
>
> Mar 30, 2020 4:20:27 PM me :
>
> >
> > Hello folks,
> >
> > I'm a new member of the community and awaiting the delivery of my first T. 
> > I'm a huge fan of retro computing and, while my main computer is a modern 
> > system, many of my hobby pursuits relate to retro systems.
> >
> > I have a C64 as well as a mini, the incoming T, a vectrex, PS2, gamecube, 
> > and an avid user of BBS systems. I also use quite a bit of gopher, hosting 
> > my own phlog and navigating around gophersphere. My gopher hole address is: 
> > gopher://gcpp.world
> >
> > Currently, a project I'm on involves the creation of a fresh BBS door game 
> > that will be in the universe of Star Trek. I'm having loads of fun.
> >
> > You can see me on IRC as calcmandan on freenode, dalnet, airlock, undernet, 
> > quakenet, hackint, oftc, pine, and gamesurge. Long live mozilla's IRC, 
> > retired end of February.
> >
> > Selected newsgroups I peruse/post are: a.o.l.ubuntu, a.gopher, a.s.pipes, 
> > a.astronomy, s.physics, s.p.relativity, r.a.piloting, a.o.linux, 
> > r.f.cooking, c.i.gopher, a.ascii-art, c.b.cbm, c.s.tandy
> >
> > I'm also known on fidonet, scinet, etc as calcmandan.
> >
> > I hope to make some friends here. I attempted to get my face pic on the 
> > website, but the email address posted on the page is undeliverable.
> >
> > Daniel from Sacramento, CA
> >
> >
>
>

Re: [M100] M102 add Rexx (w/ switch)

[Mike Stein]

- Original Message - 
From: Brian White 
To: m...@bitchin100.com 
Sent: Tuesday, March 31, 2020 8:57 AM
Subject: Re: [M100] M102 add Rexx (w/ switch)

> M100 main rom is socketed so those are simpler, except for the fact that for 
> M100, you need some form of pinout adapter and can't just stick a 27C256 in 
> the socket, which you can do with a T102.
---
Might be worth mentioning that as in Greg's collection this only applies to 
M100s older than ~October 1983 (serial no.s starting with 310 or 311); later 
models can use the same standard 27C256 or equivalent as the T102 or 200.

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

I was just thinking if you use the BUILDIT script you just need a framework
4.5 or higher.

On Tue, Mar 31, 2020, 6:00 PM Ken Pettit  wrote:

> Hey John,
>
> I'm trying to compile LaddieAlpha on Ubuntu 14.04 using mono-mcs. Have
> you ever tried this before?  I'm getting a bunch of compile errors, but
> have never programmed in C# before so don't really know if syntax like
> "s?.Close()" is legal or not.
>
> Ken
>
> On 3/31/20 5:34 PM, John R. Hogerhuis wrote:
> > I had similar issues randomly when starting NEWDOS / LaddieAlpha.
> >
> > When it happened, what worked is to break out of NEWDOS (sometimes
> > takes a hitting reset button), go into TELCOM, stat 981ND, term, F8
> > Bye, CALL NEWDOS again.
> >
> > The BASIC launcher I wrote has a similar effect since it opens the COM
> > port and sends the ATDT command. Since you're not doing that, maybe
> > you could just OPEN the com port at the 98N1D settings and then close
> > it, without having written anything.
> >
> > Ken says he disabled the DTR/DSR checking in NEWDOS which would be my
> > first guess for getting stuck at DISK mode, so my feeling is that the
> > autobauding is involved, and going back into TELCOM resets the port
> > settings.
> >
> > It's weird.
> >
> > If you want a debug version of LaddieAlpha I can share one and we can
> > see all the I/O serial traffic.
> >
> > -- John.
>
>

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

On Tue, Mar 31, 2020 at 6:00 PM Ken Pettit  wrote:

> Hey John,
>
> I'm trying to compile LaddieAlpha on Ubuntu 14.04 using mono-mcs. Have
> you ever tried this before?  I'm getting a bunch of compile errors, but
> have never programmed in C# before so don't really know if syntax like
> "s?.Close()" is legal or not.
>
> Ken
>
>
I used to only build with Linux. Lately I've been building with Visual
Studio.

It's legal but those are C# 7'isms. I guess I added those in recently.

You may need Visual Studio at the moment.

Or I can build it for you.

-- John.

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

> John:
> If you want a debug version of LaddieAlpha I can share one and we can see all 
> the I/O serial traffic

Happy to try it with a debug build and produce some logs.

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

On Mar 31, 2020, at 5:22 PM, Ken Pettit  wrote:
> 
> So when you say NEWDOS hangs, is this after hitting F4, for instance, to get 
> a DISK listing?  If the server wasn't responding, then I would expect NEWDOS 
> to simply print the "DRIVE NOT READY" error message.  Makes me think NEWDOS 
> is receiving *something*, but doesn't like what is returned and is getting 
> lost or

The behavior is that F4 clears the screen, prints the reverse text banner, 
doesn't RX or TX anything (or so little my RX/TX LEDs don't catch it), and does 
nothing.

Re: [M100] WiModem TPDD

[Ken Pettit]

Hey John,

I'm trying to compile LaddieAlpha on Ubuntu 14.04 using mono-mcs. Have 
you ever tried this before?  I'm getting a bunch of compile errors, but 
have never programmed in C# before so don't really know if syntax like 
"s?.Close()" is legal or not.


Ken

On 3/31/20 5:34 PM, John R. Hogerhuis wrote:

I had similar issues randomly when starting NEWDOS / LaddieAlpha.

When it happened, what worked is to break out of NEWDOS (sometimes 
takes a hitting reset button), go into TELCOM, stat 981ND, term, F8 
Bye, CALL NEWDOS again.


The BASIC launcher I wrote has a similar effect since it opens the COM 
port and sends the ATDT command. Since you're not doing that, maybe 
you could just OPEN the com port at the 98N1D settings and then close 
it, without having written anything.


Ken says he disabled the DTR/DSR checking in NEWDOS which would be my 
first guess for getting stuck at DISK mode, so my feeling is that the 
autobauding is involved, and going back into TELCOM resets the port 
settings.


It's weird.

If you want a debug version of LaddieAlpha I can share one and we can 
see all the I/O serial traffic.


-- John.

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

I had similar issues randomly when starting NEWDOS / LaddieAlpha.

When it happened, what worked is to break out of NEWDOS (sometimes takes a
hitting reset button), go into TELCOM, stat 981ND, term, F8 Bye, CALL
NEWDOS again.

The BASIC launcher I wrote has a similar effect since it opens the COM port
and sends the ATDT command. Since you're not doing that, maybe you could
just OPEN the com port at the 98N1D settings and then close it, without
having written anything.

Ken says he disabled the DTR/DSR checking in NEWDOS which would be my first
guess for getting stuck at DISK mode, so my feeling is that the autobauding
is involved, and going back into TELCOM resets the port settings.

It's weird.

If you want a debug version of LaddieAlpha I can share one and we can see
all the I/O serial traffic.

-- John.

Re: [M100] WiModem TPDD

[Ken Pettit]

So when you say NEWDOS hangs, is this after hitting F4, for instance, to 
get a DISK listing?  If the server wasn't responding, then I would 
expect NEWDOS to simply print the "DRIVE NOT READY" error message.  
Makes me think NEWDOS is receiving *something*, but doesn't like what is 
returned and is getting lost or something.


On 3/31/20 3:31 PM, Joshua O'Keefe wrote:

Happy to be a part of that effort in any way I can be of service.

I also tried Kurt's SARDOS-D with delay inbuilt, and it complains of disk not 
ready after a short burst of I/O.  Switching to any of the non-delayed ROMs 
restores functionality once LaddieAlpha is bounced.

The WiModem isn't here yet, so I can't tell you if any of this is reproducible 
via network.  I had just been hoping to pick one ROM loadout for both wired and 
wireless usage, so I've been experimenting with NEWDOS and other delay ROMs on 
a wired connection.




On Mar 31, 2020, at 3:04 PM, Ken Pettit  wrote:

Sounds like we (I) need to create a debug version of NEWDOS to figure out 
where it is getting lost or something.

Ken


On 3/31/20 2:56 PM, Joshua O'Keefe wrote:
Great idea!  Let me go try that...

Doing this caused it to work once! I went to go fish some RAM files out of a 
Rex backup and upon returning to NEWDOS: hang again.

Cold resetting and re-re-loading to REX didn't restore the functionality, nor 
did restarting my TPDD emulator.

The fact that it works once suggests there's some kind of state change 
somewhere along the line, but I'm not clear where.  I've tried resetting the 
state of LaddieAlpha (which was the only persistent thing between attempts)  at 
each step, but it doesn't change the story.

If I can get it back into "work once" mode I'll try to see if the causal action 
is invoking rexmgr, which is common to all these tries.


On Mar 31, 2020, at 2:17 PM, Ken Pettit  wrote:

Maybe try re-programming NEWDOS to your REX?

Ken


On 3/31/20 2:03 PM, Joshua O'Keefe wrote:

On Mar 31, 2020, at 1:55 PM, Ken Pettit  wrote:
 Try resetting everything and then running NEWDOS first instead of TS-DOS.

Alas, no joy on this approach either, with either LaddieAlpha or dlplus running 
at the other end.  Flipping to a vanilla rom (Or one of Kurt's ROMs) after 
resetting (warm or cold) works fine, so whatever's not quite right with my rig 
it's only NEWDOS that doesn't like it, whether NEWDOS goes first or second.  
I'm mystified here.

I've long since lost my RS-232 breakout box (by a good couple of decades), so 
the diagnostic information I can offer is only circumstantial at this point.

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

Happy to do a packet capture once this all moves to IP.  Of course, it may also 
just work.  At this point it's pure wired RS-232 -> USB with the unexpected 
behavior but I can try to do Unix Fanciness to cap what's happening on the tty 
if that helps.  I'd love to be able to just switch to NEWDOS as my daily driver 
and have it handle both wired and my eventual wireless connectivity.

To recap:

Working serial connection works with all un-delayed ROMs just the way you 
expect it to. (Vanilla TSDOS, SARDOS, Ultimate Rom bootstrapping to DOS100.CO)

Same serial connection works once and only once with NEWDOS on first boot; 
merely exiting to menu and coming back is enough to make it stop working, and 
invoking it with no delay solves nothing.

Serial connection works not at all with SARDOS-delayed, first or subsequent 
start, presumably because the delay is hard coded?

I want to try a fresh build of LaddieAlpha, because it does seem to wedge up 
after being used by NEWDOS, but I can't get it to compile.  Something about 
TPDD.cs causes an internal compiler error with the versions of Mono I have on 
hand.

> On Mar 31, 2020, at 3:40 PM, Stephen Adolph  wrote:
> 
> 
> I think what would be good is to get wireshark running somewhere in that IP 
> link.
> Ideally we should see a single packet carrying the request and a single 
> packet carrying the response.
> I don't know that this is necessary for good comms, but I have a feeling it 
> helps.
> 
> Joshua, are you familiar with Wireshark?  you should be able to see packets 
> ingressing and egressing from the USB port IP address.
> ..steve
> 
>> On Tue, Mar 31, 2020 at 6:32 PM Joshua O'Keefe  
>> wrote:
>> Happy to be a part of that effort in any way I can be of service.
>> 

Re: [M100] WiModem TPDD

[Stephen Adolph]

I think what would be good is to get wireshark running somewhere in that IP
link.
Ideally we should see a single packet carrying the request and a single
packet carrying the response.
I don't know that this is necessary for good comms, but I have a feeling it
helps.

Joshua, are you familiar with Wireshark?  you should be able to see packets
ingressing and egressing from the USB port IP address.
..steve

On Tue, Mar 31, 2020 at 6:32 PM Joshua O'Keefe 
wrote:

> Happy to be a part of that effort in any way I can be of service.
>
>

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

Happy to be a part of that effort in any way I can be of service.

I also tried Kurt's SARDOS-D with delay inbuilt, and it complains of disk not 
ready after a short burst of I/O.  Switching to any of the non-delayed ROMs 
restores functionality once LaddieAlpha is bounced.

The WiModem isn't here yet, so I can't tell you if any of this is reproducible 
via network.  I had just been hoping to pick one ROM loadout for both wired and 
wireless usage, so I've been experimenting with NEWDOS and other delay ROMs on 
a wired connection.



> On Mar 31, 2020, at 3:04 PM, Ken Pettit  wrote:
> 
> Sounds like we (I) need to create a debug version of NEWDOS to figure out 
> where it is getting lost or something.
> 
> Ken
> 
>> On 3/31/20 2:56 PM, Joshua O'Keefe wrote:
>> Great idea!  Let me go try that...
>> 
>> Doing this caused it to work once! I went to go fish some RAM files out of a 
>> Rex backup and upon returning to NEWDOS: hang again.
>> 
>> Cold resetting and re-re-loading to REX didn't restore the functionality, 
>> nor did restarting my TPDD emulator.
>> 
>> The fact that it works once suggests there's some kind of state change 
>> somewhere along the line, but I'm not clear where.  I've tried resetting the 
>> state of LaddieAlpha (which was the only persistent thing between attempts)  
>> at each step, but it doesn't change the story.
>> 
>> If I can get it back into "work once" mode I'll try to see if the causal 
>> action is invoking rexmgr, which is common to all these tries.
>> 
 On Mar 31, 2020, at 2:17 PM, Ken Pettit  wrote:
>>> 
>>> Maybe try re-programming NEWDOS to your REX?
>>> 
>>> Ken
>>> 
 On 3/31/20 2:03 PM, Joshua O'Keefe wrote:
> On Mar 31, 2020, at 1:55 PM, Ken Pettit  wrote:
>  Try resetting everything and then running NEWDOS first instead of 
> TS-DOS.
 Alas, no joy on this approach either, with either LaddieAlpha or dlplus 
 running at the other end.  Flipping to a vanilla rom (Or one of Kurt's 
 ROMs) after resetting (warm or cold) works fine, so whatever's not quite 
 right with my rig it's only NEWDOS that doesn't like it, whether NEWDOS 
 goes first or second.  I'm mystified here.
 
 I've long since lost my RS-232 breakout box (by a good couple of decades), 
 so the diagnostic information I can offer is only circumstantial at this 
 point.
> 

Re: [M100] WiModem TPDD

[Ken Pettit]

Sounds like we (I) need to create a debug version of NEWDOS to figure 
out where it is getting lost or something.


Ken

On 3/31/20 2:56 PM, Joshua O'Keefe wrote:

Great idea!  Let me go try that...

Doing this caused it to work once! I went to go fish some RAM files out of a 
Rex backup and upon returning to NEWDOS: hang again.

Cold resetting and re-re-loading to REX didn't restore the functionality, nor 
did restarting my TPDD emulator.

The fact that it works once suggests there's some kind of state change 
somewhere along the line, but I'm not clear where.  I've tried resetting the 
state of LaddieAlpha (which was the only persistent thing between attempts)  at 
each step, but it doesn't change the story.

If I can get it back into "work once" mode I'll try to see if the causal action 
is invoking rexmgr, which is common to all these tries.


On Mar 31, 2020, at 2:17 PM, Ken Pettit  wrote:

Maybe try re-programming NEWDOS to your REX?

Ken


On 3/31/20 2:03 PM, Joshua O'Keefe wrote:

On Mar 31, 2020, at 1:55 PM, Ken Pettit  wrote:
 Try resetting everything and then running NEWDOS first instead of TS-DOS.

Alas, no joy on this approach either, with either LaddieAlpha or dlplus running 
at the other end.  Flipping to a vanilla rom (Or one of Kurt's ROMs) after 
resetting (warm or cold) works fine, so whatever's not quite right with my rig 
it's only NEWDOS that doesn't like it, whether NEWDOS goes first or second.  
I'm mystified here.

I've long since lost my RS-232 breakout box (by a good couple of decades), so 
the diagnostic information I can offer is only circumstantial at this point.

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

Great idea!  Let me go try that...

Doing this caused it to work once! I went to go fish some RAM files out of a 
Rex backup and upon returning to NEWDOS: hang again.

Cold resetting and re-re-loading to REX didn't restore the functionality, nor 
did restarting my TPDD emulator.

The fact that it works once suggests there's some kind of state change 
somewhere along the line, but I'm not clear where.  I've tried resetting the 
state of LaddieAlpha (which was the only persistent thing between attempts)  at 
each step, but it doesn't change the story.

If I can get it back into "work once" mode I'll try to see if the causal action 
is invoking rexmgr, which is common to all these tries.

> On Mar 31, 2020, at 2:17 PM, Ken Pettit  wrote:
> 
> Maybe try re-programming NEWDOS to your REX?
> 
> Ken
> 
>> On 3/31/20 2:03 PM, Joshua O'Keefe wrote:
>>> On Mar 31, 2020, at 1:55 PM, Ken Pettit  wrote:
>>>  Try resetting everything and then running NEWDOS first instead of TS-DOS.
>> Alas, no joy on this approach either, with either LaddieAlpha or dlplus 
>> running at the other end.  Flipping to a vanilla rom (Or one of Kurt's ROMs) 
>> after resetting (warm or cold) works fine, so whatever's not quite right 
>> with my rig it's only NEWDOS that doesn't like it, whether NEWDOS goes first 
>> or second.  I'm mystified here.
>> 
>> I've long since lost my RS-232 breakout box (by a good couple of decades), 
>> so the diagnostic information I can offer is only circumstantial at this 
>> point.
> 

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

On Mar 31, 2020, at 1:55 PM, Ken Pettit  wrote:
> 
>  Try resetting everything and then running NEWDOS first instead of TS-DOS.

Alas, no joy on this approach either, with either LaddieAlpha or dlplus running 
at the other end.  Flipping to a vanilla rom (Or one of Kurt's ROMs) after 
resetting (warm or cold) works fine, so whatever's not quite right with my rig 
it's only NEWDOS that doesn't like it, whether NEWDOS goes first or second.  
I'm mystified here.

I've long since lost my RS-232 breakout box (by a good couple of decades), so 
the diagnostic information I can offer is only circumstantial at this point.

Re: [M100] M102 add Rexx (w/ switch)

[Greg Swallow]

I have seven M100 with new Sys Roms. All have the Y2K fix and serial number 
entered over "Microsoft (C)." Two have a straight in 27c256 and four have a 
modified Mike Stein adapter board. Need to build one more adapter for last M100.

I have the M102 that got messed -- probably because I did not use Chip Quick 
like I had before on three other M102s. Seems my memory is going with my eyes.

I have the new M102 rom already so mayse I'll get to Fry's for a Chip Quick kit 
and go from there. Using the Rex is looking to be more trouble than it's worth 
for this M102. As I plan on it being on my DVI. rex is more useful for me when 
I use it in a system outside the house.

God bless,

GregS <><

Mar 31, 2020 5:57:43 AM Brian White :

> I think I'm with Steve. For 102, you have to desolder a whole dip-28, which 
> as you discovered can be tricky, and for what benefit? The only modified rom 
> that currently exists is a couple bytes changed for a mostly cosmetic y2k 
> fix. 
> 
> Are you planning on hacking on the main rom? I would love that. 
> 
> M100 main rom is socketed so those are simpler, except for the fact that for 
> M100, you need some form of pinout adapter and can't just stick a 27C256 in 
> the socket, which you can do with a T102.
> 
> 
> The rex main rom feature is cool but not really all that critical. The 
> biggest value of rex is the on-board option rom library, which gets you a 
> TPDD client (TS-DOS) without any annoying bootstrap install procedure after 
> every hard reset, and the on-board backup/restore.
> 
> 
> If you want to take another crack at desoldering a T102 main rom, I suggest 
> using ChipQuick or SRA FastChip low temp desoldering alloy, some flux paste, 
> and some solder wick. And watch some youtube videos about how to use it. This 
> is the safest, least drama way to do it and least likely to damage anything. 
> The iron doesn't have to be so hot that you burn up the epoxy holding the 
> traces to the board. And the chip basically falls out, no yanking or working. 
> Use the wick to really clean up the special alloy good before going to 
> install the socket. Vacuum desolderers can work but it takes more practice 
> and patience to get each individual leg fully un-stuck from it's hole.
> 
> --
> bkw
> 
> 
> 
> 
> 
> On Tue, Mar 31, 2020, 7:51 AM Greg Swallow < gswal...@mchsi.com > wrote:
> 
> 
> > With the troubles I'm having with my sight, I don't want to make a mess of 
> > another removal/replace on a M102. I figured clipping the CS and adding a 
> > switch would better. Otherwise, I would prefer adding a "socket" et al.
> > 
> > Thanks,
> > 
> > GregS <><
> > 
> > 
> > Mar 31, 2020 4:16:17 AM Stephen Adolph < twospru...@gmail.com >:
> > 
> > > I must say - what is the end objective? What ROM other than T102 ROM do 
> > > you want as the main ROM?
> > > REX provides y2k fix...
> > > You can probably tell but I am not really a fan anymore of using REX to 
> > > replace the main rom. In my experience it has had little benefit and much 
> > > pain.
> > >
> > >
> > >
> > > On Tue, Mar 31, 2020 at 6:05 AM Greg Swallow < gswal...@mchsi.com > wrote:
> > >
> > >
> > > > I have mucked the M102 up removing the system ROM and installing a 
> > > > socket. Believe I broke a trace somewhere, but am unable to track it 
> > > > down due eye sight (near and far sighted with progressive glasses on 
> > > > eyes that see 5 of everything) that even my magnifier hasn't helped.
> > > >
> > > > Picked up another M102 for the motherboard. My Rex doesn't have a wire 
> > > > to connect it to CS on the system ROM. Am seeking to acquire as much 
> > > > info as I can before I clip the ROM on the new M102.
> > > >
> > > > Figured Rex would be a safer way for me to go at this point. I'll check 
> > > > out the links and see where I can go.
> > > >
> > > > Thanks,
> > > >
> > > > GregS <><
> > > >
> > > > Mar 31, 2020 12:21:38 AM Brian White < b.kenyo...@gmail.com >:
> > > >
> > > > > From this, I don't have any idea what you actually tried or what 
> > > > > exactly happened.
> > > > >
> > > > > You could try
> > > > >
> > > > >
> > > > > http://tandy.wiki/FlexROM_102 
> > > > >
> > > > >
> > > > > It's designed exactly to facilitate switching back to an internal rom 
> > > > > after clising up the case si you can add or remove a REX at will 
> > > > > after that.
> > > > >
> > > > >
> > > > > Some more detailed directions about loading the rom images onto the 
> > > > > rex are on the directions for the M100 version of the same board
> > > > >
> > > > >
> > > > > http://tandy.wiki/FlexROM_100 
> > > > >
> > > > >
> > > > > The 102 (and some late model 100's) are different from the early 
> > > > > 100's (most 100s? I'm not sure about the numbers or percentages) So, 
> > > > > look at that page for the siftware directions but use the 102 board 
> > > > > in a 102.
> > > > >
> > > > >
> > > > > Or, you don't need to actually order and build that board. You could 
> > > > > also just use that as some 

Re: [M100] WiModem TPDD

[Ken Pettit]

Try resetting everything and then running NEWDOS first instead of TS-DOS.

Ken

On 3/31/20 1:52 PM, Joshua O'Keefe wrote:

Thanks Ken!

I've reset everything on the wired end (including replugging the USB 
device to get a nice clean slate) and cold reset again just to see 
where things lie.

Cold reset then:
Plain TSDOS rom: works as expected
Switch to NEWDOS: hang at the DISK banner
CALL63013,1,1: same story
Switch back to vanilla ROM: works as expected

There's definitely something somewhere in my setup that NEWDOS doesn't 
like (although it worked once!) but I'm not clear what it is at this 
point.




On Mar 31, 2020, at 1:39 PM, Ken Pettit  wrote:

 Hi Joshua,

Well, a cold reset will fix any issue with the M100 side of the 
equation.  NEWDOS has no way of saving contextual information through 
a cold boot.  The only information it saves is within the "TS-DOS" 
menu launcher (which is actually a BASIC program with no .BA 
extension).  A cold boot would wipe this out, reseting to ground zero.


This would tend to indicate there is some issue with the "wired" end, 
whatever that is (I believe Steve already asked about that).


I guess you could try calling NEWDOS and specifically telling it not 
to use any delay to see if that makes any difference:


CALL 63012,1,1

Ken

On 3/31/20 1:24 PM, Joshua O'Keefe wrote:

Hi Ken,

In anticipation of my WiModem coming in I've decided to experiment 
with NEWDOS 5.05 while using my wired connection.  I got it to come 
up on the DISK screen both with and without a delay, but the next 
time I went back into TS-DOS all disk operations would hang.  Now 
I've even gone so far as to cold reset, and I still can't get a DISK 
screen to come up past the banner line. It just sits at the banner 
with no I/O attempted (from watching my serial LEDs) no matter what 
delay is set or disabled.


I'm not sure how to troubleshoot this.  As far as I can tell, NEWDOS 
is the only pure TSDOS ROM out there with the shift down fix -- 
although it's also in Kurt's SARDOS, but not his M100 TSDOS+Delay 
ROM -- so it's an obvious choice for me as an end user who does a 
bit of roaming around on the DISK screen.  If I can get it working 
again!


Any pointer where I should be looking to get it making I/O again? 
 This is just a plain old null modem connection that works just 
dandy with other ROMs, so I'm surprised to run into issues with NEWDOS.



On Mar 29, 2020, at 10:52 AM, Ken Pettit  wrote:

 Hey Gang,

It's amazing how much I have forgotten since 2014!

With NEWDOS 5.05, using the F7 Cfg option from within NEWDOS, you 
can enable and set the delay factor using a UI I had added.  This 
will not only change the delay factor for TPDD accesses, but also 
updates the "TS-DOS" MENU item with the selected delay.  So by 
simply choosing TS-DOS from MENU, it will configure for the 
selected delay factor, it it is enabled.


If you want to set IP address in WiModem232, you probably still 
need the shortcut BA that John detailed.


Ken

On 3/29/20 1:19 AM, John R. Hogerhuis wrote:



On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson > wrote:


Is NEWDOS a ROM we can install on Rex, or is it a COM file?


NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).

http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05 



-- John.

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

Thanks Ken!

I've reset everything on the wired end (including replugging the USB device to 
get a nice clean slate) and cold reset again just to see where things lie.  
Cold reset then:
Plain TSDOS rom: works as expected
Switch to NEWDOS: hang at the DISK banner
CALL63013,1,1: same story
Switch back to vanilla ROM: works as expected

There's definitely something somewhere in my setup that NEWDOS doesn't like 
(although it worked once!) but I'm not clear what it is at this point.


> On Mar 31, 2020, at 1:39 PM, Ken Pettit  wrote:
> 
>  Hi Joshua,
> 
> Well, a cold reset will fix any issue with the M100 side of the equation.  
> NEWDOS has no way of saving contextual information through a cold boot.  The 
> only information it saves is within the "TS-DOS" menu launcher (which is 
> actually a BASIC program with no .BA extension).  A cold boot would wipe this 
> out, reseting to ground zero.  
> 
> This would tend to indicate there is some issue with the "wired" end, 
> whatever that is (I believe Steve already asked about that).
> 
> I guess you could try calling NEWDOS and specifically telling it not to use 
> any delay to see if that makes any difference:
> 
> CALL 63012,1,1
> 
> Ken
> 
> On 3/31/20 1:24 PM, Joshua O'Keefe wrote:
>> Hi Ken,
>> 
>> In anticipation of my WiModem coming in I've decided to experiment with 
>> NEWDOS 5.05 while using my wired connection.  I got it to come up on the 
>> DISK screen both with and without a delay, but the next time I went back 
>> into TS-DOS all disk operations would hang.  Now I've even gone so far as to 
>> cold reset, and I still can't get a DISK screen to come up past the banner 
>> line. It just sits at the banner with no I/O attempted (from watching my 
>> serial LEDs) no matter what delay is set or disabled.
>> 
>> I'm not sure how to troubleshoot this.  As far as I can tell, NEWDOS is the 
>> only pure TSDOS ROM out there with the shift down fix -- although it's also 
>> in Kurt's SARDOS, but not his M100 TSDOS+Delay ROM -- so it's an obvious 
>> choice for me as an end user who does a bit of roaming around on the DISK 
>> screen.  If I can get it working again!
>> 
>> Any pointer where I should be looking to get it making I/O again?  This is 
>> just a plain old null modem connection that works just dandy with other 
>> ROMs, so I'm surprised to run into issues with NEWDOS.
>> 
>>> On Mar 29, 2020, at 10:52 AM, Ken Pettit  wrote:
>>> 
>>>  Hey Gang,
>>> 
>>> It's amazing how much I have forgotten since 2014!  
>>> 
>>> With NEWDOS 5.05, using the F7 Cfg option from within NEWDOS, you can 
>>> enable and set the delay factor using a UI I had added.  This will not only 
>>> change the delay factor for TPDD accesses, but also updates the "TS-DOS" 
>>> MENU item with the selected delay.  So by simply choosing TS-DOS from MENU, 
>>> it will configure for the selected delay factor, it it is enabled.
>>> 
>>> If you want to set IP address in WiModem232, you probably still need the 
>>> shortcut BA that John detailed.
>>> 
>>> Ken
>>> 
>>> On 3/29/20 1:19 AM, John R. Hogerhuis wrote:
 
 
 On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson  wrote:
> Is NEWDOS a ROM we can install on Rex, or is it a COM file?
> 
 
 NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).
 
 http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05
   
 
 -- John. 
>>> 
> 

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

The wired system is what I've been using all along: 
102 - gender - 25-9 - StarTech USB (with internal null) - /dev/ttyUSB0 - 
LaddieAlpha (or dlplus)

I can switch ROMs back to any other, and the connection lights right back up 
again, but something I'm doing isn't quite right for NEWDOS.  It works great 
with everything except NEWDOS, which hangs on DISK no matter the state.  In 
fact, the hang occurs even if I leave the cable off entirely, as though it's 
maybe a DTR/DSR thing?  Neither RX or TX LEDs flicker at all, so it doesn't 
seem to get even that far.

Resident commands hang similarly.



> On Mar 31, 2020, at 1:29 PM, Stephen Adolph  wrote:
> 
> 
> Can you describe the wired system?  M100 -RS232-??
> 
> 
>> On Tue, Mar 31, 2020 at 4:25 PM Joshua O'Keefe  
>> wrote:
>> Hi Ken,
>> 
>> In anticipation of my WiModem coming in I've decided to experiment with 
>> NEWDOS 5.05 while using my wired connection.  I got it to come up on the 
>> DISK screen both with and without a delay, but the next time I went back 
>> into TS-DOS all disk operations would hang.  Now I've even gone so far as to 
>> cold reset, and I still can't get a DISK screen to come up past the banner 
>> line. It just sits at the banner with no I/O attempted (from watching my 
>> serial LEDs) no matter what delay is set or disabled.
>> 
>> I'm not sure how to troubleshoot this.  As far as I can tell, NEWDOS is the 
>> only pure TSDOS ROM out there with the shift down fix -- although it's also 
>> in Kurt's SARDOS, but not his M100 TSDOS+Delay ROM -- so it's an obvious 
>> choice for me as an end user who does a bit of roaming around on the DISK 
>> screen.  If I can get it working again!
>> 
>> Any pointer where I should be looking to get it making I/O again?  This is 
>> just a plain old null modem connection that works just dandy with other 
>> ROMs, so I'm surprised to run into issues with NEWDOS.
>> 
 On Mar 29, 2020, at 10:52 AM, Ken Pettit  wrote:
 
>>>  Hey Gang,
>>> 
>>> It's amazing how much I have forgotten since 2014!  
>>> 
>>> With NEWDOS 5.05, using the F7 Cfg option from within NEWDOS, you can 
>>> enable and set the delay factor using a UI I had added.  This will not only 
>>> change the delay factor for TPDD accesses, but also updates the "TS-DOS" 
>>> MENU item with the selected delay.  So by simply choosing TS-DOS from MENU, 
>>> it will configure for the selected delay factor, it it is enabled.
>>> 
>>> If you want to set IP address in WiModem232, you probably still need the 
>>> shortcut BA that John detailed.
>>> 
>>> Ken
>>> 
>>> On 3/29/20 1:19 AM, John R. Hogerhuis wrote:
 
 
 On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson  wrote:
> Is NEWDOS a ROM we can install on Rex, or is it a COM file?
> 
 
 NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).
 
 http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05
   
 
 -- John. 
>>> 

Re: [M100] WiModem TPDD

[Ken Pettit]

Hi Joshua,

Well, a cold reset will fix any issue with the M100 side of the 
equation.  NEWDOS has no way of saving contextual information through a 
cold boot.  The only information it saves is within the "TS-DOS" menu 
launcher (which is actually a BASIC program with no .BA extension).  A 
cold boot would wipe this out, reseting to ground zero.


This would tend to indicate there is some issue with the "wired" end, 
whatever that is (I believe Steve already asked about that).


I guess you could try calling NEWDOS and specifically telling it not to 
use any delay to see if that makes any difference:


CALL 63012,1,1

Ken

On 3/31/20 1:24 PM, Joshua O'Keefe wrote:

Hi Ken,

In anticipation of my WiModem coming in I've decided to experiment 
with NEWDOS 5.05 while using my wired connection.  I got it to come up 
on the DISK screen both with and without a delay, but the next time I 
went back into TS-DOS all disk operations would hang.  Now I've even 
gone so far as to cold reset, and I still can't get a DISK screen to 
come up past the banner line. It just sits at the banner with no I/O 
attempted (from watching my serial LEDs) no matter what delay is set 
or disabled.


I'm not sure how to troubleshoot this.  As far as I can tell, NEWDOS 
is the only pure TSDOS ROM out there with the shift down fix -- 
although it's also in Kurt's SARDOS, but not his M100 TSDOS+Delay ROM 
-- so it's an obvious choice for me as an end user who does a bit of 
roaming around on the DISK screen.  If I can get it working again!


Any pointer where I should be looking to get it making I/O again? 
 This is just a plain old null modem connection that works just dandy 
with other ROMs, so I'm surprised to run into issues with NEWDOS.



On Mar 29, 2020, at 10:52 AM, Ken Pettit  wrote:

 Hey Gang,

It's amazing how much I have forgotten since 2014!

With NEWDOS 5.05, using the F7 Cfg option from within NEWDOS, you can 
enable and set the delay factor using a UI I had added.  This will 
not only change the delay factor for TPDD accesses, but also updates 
the "TS-DOS" MENU item with the selected delay.  So by simply 
choosing TS-DOS from MENU, it will configure for the selected delay 
factor, it it is enabled.


If you want to set IP address in WiModem232, you probably still need 
the shortcut BA that John detailed.


Ken

On 3/29/20 1:19 AM, John R. Hogerhuis wrote:



On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson > wrote:


Is NEWDOS a ROM we can install on Rex, or is it a COM file?


NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).

http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05 



-- John.

Re: [M100] Warning: Not a(n) M100 but a PC-2 question.

[Jesse Huyett]

Thanks all for the recommendations and links. Looking forward to getting
this all up and running.
Esp appreciated as working from home/ stir-crazy due to mostly stuck inside.

Next on the project list does deal with my T102/ DVI so promises I'll keep
topics relevant to the group next time.

Again thanks.
Regards,
Jesse

On Tue, Mar 31, 2020 at 3:53 PM Philip Avery  wrote:

> Thanks Ron, that's good to know.
>
> Philip
>
> On 1/04/2020 8:07 am, Ron Lauzon wrote:
>
> The batteries only give the extra "oomph" to run the solenoids when
> printing.
>
> But it's possible that the printer is reporting batteries too low.
>
> Note that you can use a more powerful AC adapter to power the
> printer/PC-2.  I have a 2A one for my set up.  Then you don't need the
> batteries at all.
>
> --
> Weblog: http://ronsapartment.blogspot.com/
>
> TRS-80 Pocket Computer 2 - TRS-80 Pocket Computer 4 - TRS-80 Model 100/102
> - Tandy 1100FD - Commodore 64 - TRS-80 Model 4P
> RC2014 (Mini and Pro) - Altair-Duino with TI Silent 700 - VT320
> terminal/Raspberry Pi 0
> Some people like to work on old cars.  But old computers are cheaper and
> don't require a big garage.
>
>
>
> Mar 31, 2020, 14:58 by pav...@xtra.co.nz:
>
> I have one of those. The printer needs the batteries to function. They
> provide current sinking beyond what the wall wart does.
>
> Philip
>
> On 1/04/2020 5:04 am, Jesse Huyett wrote:
>
> Hello All,
> Asking here having seen some other handhelds come up, and this seems to be
> a welcoming group for all things Tandy. Feel free to point me elsewhere,
> tell me otherwise, or state where I can stick this thing.
>
> Pocet Computer 2 with the Printer/ Cassette Interface.
> I passed the first "CHECK 6" error having realized no power was getting
> through due to a bad Cadmium battery.
> Removed and now getting the pleasant sound of a printer going through the
> self check...
> https://www.youtube.com/watch?v=oncEeFjXthA
> Still ends up on CHECK 6 though.
> Definitely getting power, doesn't seem jammed, ...  Is anyone familiar
> with the startup process and know what I should look for next?
>
> Regards,
> Jesse
>
>
>
>

Re: [M100] WiModem TPDD

[Stephen Adolph]

Can you describe the wired system?  M100 -RS232-??


On Tue, Mar 31, 2020 at 4:25 PM Joshua O'Keefe 
wrote:

> Hi Ken,
>
> In anticipation of my WiModem coming in I've decided to experiment with
> NEWDOS 5.05 while using my wired connection.  I got it to come up on the
> DISK screen both with and without a delay, but the next time I went back
> into TS-DOS all disk operations would hang.  Now I've even gone so far as
> to cold reset, and I still can't get a DISK screen to come up past the
> banner line. It just sits at the banner with no I/O attempted (from
> watching my serial LEDs) no matter what delay is set or disabled.
>
> I'm not sure how to troubleshoot this.  As far as I can tell, NEWDOS is
> the only pure TSDOS ROM out there with the shift down fix -- although it's
> also in Kurt's SARDOS, but not his M100 TSDOS+Delay ROM -- so it's an
> obvious choice for me as an end user who does a bit of roaming around on
> the DISK screen.  If I can get it working again!
>
> Any pointer where I should be looking to get it making I/O again?  This is
> just a plain old null modem connection that works just dandy with other
> ROMs, so I'm surprised to run into issues with NEWDOS.
>
> On Mar 29, 2020, at 10:52 AM, Ken Pettit  wrote:
>
>  Hey Gang,
>
> It's amazing how much I have forgotten since 2014!
>
> With NEWDOS 5.05, using the F7 Cfg option from within NEWDOS, you can
> enable and set the delay factor using a UI I had added.  This will not only
> change the delay factor for TPDD accesses, but also updates the "TS-DOS"
> MENU item with the selected delay.  So by simply choosing TS-DOS from MENU,
> it will configure for the selected delay factor, it it is enabled.
>
> If you want to set IP address in WiModem232, you probably still need the
> shortcut BA that John detailed.
>
> Ken
>
> On 3/29/20 1:19 AM, John R. Hogerhuis wrote:
>
>
>
> On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson  wrote:
>
>> Is NEWDOS a ROM we can install on Rex, or is it a COM file?
>>
>>
> NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).
>
>
> http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05
>
>
> -- John.
>
>
>

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

Hi Ken,

In anticipation of my WiModem coming in I've decided to experiment with NEWDOS 
5.05 while using my wired connection.  I got it to come up on the DISK screen 
both with and without a delay, but the next time I went back into TS-DOS all 
disk operations would hang.  Now I've even gone so far as to cold reset, and I 
still can't get a DISK screen to come up past the banner line. It just sits at 
the banner with no I/O attempted (from watching my serial LEDs) no matter what 
delay is set or disabled.

I'm not sure how to troubleshoot this.  As far as I can tell, NEWDOS is the 
only pure TSDOS ROM out there with the shift down fix -- although it's also in 
Kurt's SARDOS, but not his M100 TSDOS+Delay ROM -- so it's an obvious choice 
for me as an end user who does a bit of roaming around on the DISK screen.  If 
I can get it working again!

Any pointer where I should be looking to get it making I/O again?  This is just 
a plain old null modem connection that works just dandy with other ROMs, so I'm 
surprised to run into issues with NEWDOS.

> On Mar 29, 2020, at 10:52 AM, Ken Pettit  wrote:
> 
>  Hey Gang,
> 
> It's amazing how much I have forgotten since 2014!  
> 
> With NEWDOS 5.05, using the F7 Cfg option from within NEWDOS, you can enable 
> and set the delay factor using a UI I had added.  This will not only change 
> the delay factor for TPDD accesses, but also updates the "TS-DOS" MENU item 
> with the selected delay.  So by simply choosing TS-DOS from MENU, it will 
> configure for the selected delay factor, it it is enabled.
> 
> If you want to set IP address in WiModem232, you probably still need the 
> shortcut BA that John detailed.
> 
> Ken
> 
> On 3/29/20 1:19 AM, John R. Hogerhuis wrote:
>> 
>> 
>> On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson  wrote:
>>> Is NEWDOS a ROM we can install on Rex, or is it a COM file?
>>> 
>> 
>> NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).
>> 
>> http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05
>>   
>> 
>> -- John. 
> 

Re: [M100] Warning: Not a(n) M100 but a PC-2 question.

[Philip Avery]

Thanks Ron, that's good to know.

Philip

On 1/04/2020 8:07 am, Ron Lauzon wrote:
The batteries only give the extra "oomph" to run the solenoids when 
printing.


But it's possible that the printer is reporting batteries too low.

Note that you can use a more powerful AC adapter to power the 
printer/PC-2.  I have a 2A one for my set up.  Then you don't need the 
batteries at all.


--
Weblog: http://ronsapartment.blogspot.com/

TRS-80 Pocket Computer 2 - TRS-80 Pocket Computer 4 - TRS-80 Model 
100/102 - Tandy 1100FD - Commodore 64 - TRS-80 Model 4P
RC2014 (Mini and Pro) - Altair-Duino with TI Silent 700 - VT320 
terminal/Raspberry Pi 0
Some people like to work on old cars.  But old computers are cheaper 
and don't require a big garage.




Mar 31, 2020, 14:58 by pav...@xtra.co.nz:

I have one of those. The printer needs the batteries to function.
They provide current sinking beyond what the wall wart does.

Philip

On 1/04/2020 5:04 am, Jesse Huyett wrote:

Hello All,
Asking here having seen some other handhelds come up, and this
seems to be a welcoming group for all things Tandy. Feel free
to point me elsewhere, tell me otherwise, or state where I can
stick this thing.

Pocet Computer 2 with the Printer/ Cassette Interface.
I passed the first "CHECK 6" error having realized no power
was getting through due to a bad Cadmium battery.
Removed and now getting the pleasant sound of a printer going
through the self check...
https://www.youtube.com/watch?v=oncEeFjXthA
Still ends up on CHECK 6 though.
Definitely getting power, doesn't seem jammed, ...  Is anyone
familiar with the startup process and know what I should look
for next?

Regards,
Jesse

Re: [M100] Warning: Not a(n) M100 but a PC-2 question.

[Brian K. White]

Pens and gears: http://tandy.wiki/CGP-115
--
bkw

On 3/31/20 3:04 PM, Jesse Huyett wrote:

Hello Phillip,
Thanks much for the response.
Good to know. I thought this could be removed without any loss in 
functionality. I am using a bench supply which pushes more amps than the 
wall wart if it matters.
I plan on building a pack for this anyway and will definitely see if 
this helps.


It was also recommended that gears rotating the pens may need replaced. 
Googling now for a source.


Thanks again and Regards,
Jesse

On Tue, Mar 31, 2020 at 2:58 PM Philip Avery > wrote:


I have one of those. The printer needs the batteries to function. They
provide current sinking beyond what the wall wart does.

Philip

On 1/04/2020 5:04 am, Jesse Huyett wrote:
 > Hello All,
 > Asking here having seen some other handhelds come up, and this seems
 > to be a welcoming group for all things Tandy. Feel free to point me
 > elsewhere, tell me otherwise, or state where I can stick this thing.
 >
 > Pocet Computer 2 with the Printer/ Cassette Interface.
 > I passed the first "CHECK 6" error having realized no power was
 > getting through due to a bad Cadmium battery.
 > Removed and now getting the pleasant sound of a printer going
through
 > the self check...
 > https://www.youtube.com/watch?v=oncEeFjXthA
 > Still ends up on CHECK 6 though.
 > Definitely getting power, doesn't seem jammed, ...  Is anyone
familiar
 > with the startup process and know what I should look for next?
 >
 > Regards,
 > Jesse




--
bkw

Re: [M100] Warning: Not a(n) M100 but a PC-2 question.

[Ron Lauzon]

The batteries only give the extra "oomph" to run the solenoids when printing.

But it's possible that the printer is reporting batteries too low.

Note that you can use a more powerful AC adapter to power the printer/PC-2.  I 
have a 2A one for my set up.  Then you don't need the batteries at all.

-- 
Weblog: http://ronsapartment.blogspot.com/

TRS-80 Pocket Computer 2 - TRS-80 Pocket Computer 4 - TRS-80 Model 100/102 - 
Tandy 1100FD - Commodore 64 - TRS-80 Model 4P
RC2014 (Mini and Pro) - Altair-Duino with TI Silent 700 - VT320 
terminal/Raspberry Pi 0
Some people like to work on old cars.  But old computers are cheaper and don't 
require a big garage.



Mar 31, 2020, 14:58 by pav...@xtra.co.nz:

> I have one of those. The printer needs the batteries to function. They 
> provide current sinking beyond what the wall wart does.
>
> Philip
>
> On 1/04/2020 5:04 am, Jesse Huyett wrote:
>
>> Hello All,
>> Asking here having seen some other handhelds come up, and this seems to be a 
>> welcoming group for all things Tandy. Feel free to point me elsewhere, tell 
>> me otherwise, or state where I can stick this thing.
>>
>> Pocet Computer 2 with the Printer/ Cassette Interface.
>> I passed the first "CHECK 6" error having realized no power was getting 
>> through due to a bad Cadmium battery.
>> Removed and now getting the pleasant sound of a printer going through the 
>> self check...
>> https://www.youtube.com/watch?v=oncEeFjXthA
>> Still ends up on CHECK 6 though.
>> Definitely getting power, doesn't seem jammed, ...  Is anyone familiar with 
>> the startup process and know what I should look for next?
>>
>> Regards,
>> Jesse
>>

Re: [M100] Warning: Not a(n) M100 but a PC-2 question.

[Jesse Huyett]

Hello Phillip,
Thanks much for the response.
Good to know. I thought this could be removed without any loss in
functionality. I am using a bench supply which pushes more amps than the
wall wart if it matters.
I plan on building a pack for this anyway and will definitely see if this
helps.

It was also recommended that gears rotating the pens may need replaced.
Googling now for a source.

Thanks again and Regards,
Jesse

On Tue, Mar 31, 2020 at 2:58 PM Philip Avery  wrote:

> I have one of those. The printer needs the batteries to function. They
> provide current sinking beyond what the wall wart does.
>
> Philip
>
> On 1/04/2020 5:04 am, Jesse Huyett wrote:
> > Hello All,
> > Asking here having seen some other handhelds come up, and this seems
> > to be a welcoming group for all things Tandy. Feel free to point me
> > elsewhere, tell me otherwise, or state where I can stick this thing.
> >
> > Pocet Computer 2 with the Printer/ Cassette Interface.
> > I passed the first "CHECK 6" error having realized no power was
> > getting through due to a bad Cadmium battery.
> > Removed and now getting the pleasant sound of a printer going through
> > the self check...
> > https://www.youtube.com/watch?v=oncEeFjXthA
> > Still ends up on CHECK 6 though.
> > Definitely getting power, doesn't seem jammed, ...  Is anyone familiar
> > with the startup process and know what I should look for next?
> >
> > Regards,
> > Jesse
>
>

Re: [M100] Warning: Not a(n) M100 but a PC-2 question.

[Philip Avery]

I have one of those. The printer needs the batteries to function. They 
provide current sinking beyond what the wall wart does.


Philip

On 1/04/2020 5:04 am, Jesse Huyett wrote:

Hello All,
Asking here having seen some other handhelds come up, and this seems 
to be a welcoming group for all things Tandy. Feel free to point me 
elsewhere, tell me otherwise, or state where I can stick this thing.


Pocet Computer 2 with the Printer/ Cassette Interface.
I passed the first "CHECK 6" error having realized no power was 
getting through due to a bad Cadmium battery.
Removed and now getting the pleasant sound of a printer going through 
the self check...

https://www.youtube.com/watch?v=oncEeFjXthA
Still ends up on CHECK 6 though.
Definitely getting power, doesn't seem jammed, ...  Is anyone familiar 
with the startup process and know what I should look for next?


Regards,
Jesse

[M100] Warning: Not a(n) M100 but a PC-2 question.

[Jesse Huyett]

Hello All,
Asking here having seen some other handhelds come up, and this seems to be
a welcoming group for all things Tandy. Feel free to point me elsewhere,
tell me otherwise, or state where I can stick this thing.

Pocet Computer 2 with the Printer/ Cassette Interface.
I passed the first "CHECK 6" error having realized no power was getting
through due to a bad Cadmium battery.
Removed and now getting the pleasant sound of a printer going through the
self check...
https://www.youtube.com/watch?v=oncEeFjXthA
Still ends up on CHECK 6 though.
Definitely getting power, doesn't seem jammed, ...  Is anyone familiar with
the startup process and know what I should look for next?

Regards,
Jesse

Re: [M100] Building VirtualT

[Tom Dison]

Love it!

On Tue, Mar 31, 2020 at 07:29 Ken Pettit  wrote:

>
> On 3/26/20 7:00 PM, John R. Hogerhuis wrote:
> >
> >
> >
> > Don't ask, don't tell :-)
> >
> > sprintf at least is inherently dangerous and should never be used.
> > Should always use snprintf so you're committing to a certain buffer size.
>
> Yep.  But then again, almost all of this code was written over 10 year
> ago.  Did they even have snprintf then! ;)
>
> Heck, programmer's have it easy these days ... they get 1's *and* 0's.
> When I was a kid, we only had 0's!
>
> Ken
>
> --
Faith without Works is Dead...

Re: [M100] M102 add Rexx (w/ switch)

[Brian White]

I think I'm with Steve. For 102, you have to desolder a whole dip-28, which
as you discovered can be tricky, and for what benefit? The only modified
rom that currently exists is a couple bytes changed for a mostly cosmetic
y2k fix.

Are you planning on hacking on the main rom? I would love that.

M100 main rom is socketed so those are simpler, except for the fact that
for M100, you need some form of pinout adapter and can't just stick a
27C256 in the socket, which you can do with a T102.

The rex main rom feature is cool but not really all that critical. The
biggest value of rex is the on-board option rom library, which gets you a
TPDD client (TS-DOS) without any annoying bootstrap install procedure after
every hard reset, and the on-board backup/restore.

If you want to take another crack at desoldering a T102 main rom, I suggest
using ChipQuick or SRA FastChip low temp desoldering alloy, some flux
paste, and some solder wick. And watch some youtube videos about how to use
it. This is the safest, least drama way to do it and least likely to damage
anything. The iron doesn't have to be so hot that you burn up the epoxy
holding the traces to the board. And the chip basically falls out, no
yanking or working. Use the wick to really clean up the special alloy good
before going to install the socket. Vacuum desolderers can work but it
takes more practice and patience to get each individual leg fully un-stuck
from it's hole.

-- 
bkw

On Tue, Mar 31, 2020, 7:51 AM Greg Swallow  wrote:

> With the troubles I'm having with my sight, I don't want to make a mess of
> another removal/replace on a M102. I figured clipping the CS and adding a
> switch would better. Otherwise, I would prefer adding a "socket" et al.
>
> Thanks,
>
> GregS <><
>
>
> Mar 31, 2020 4:16:17 AM Stephen Adolph :
>
> > I must say - what is the end objective? What ROM other than T102 ROM do
> you want as the main ROM?
> > REX provides y2k fix...
> > You can probably tell but I am not really a fan anymore of using REX to
> replace the main rom. In my experience it has had little benefit and much
> pain.
> >
> >
> >
> > On Tue, Mar 31, 2020 at 6:05 AM Greg Swallow < gswal...@mchsi.com >
> wrote:
> >
> >
> > > I have mucked the M102 up removing the system ROM and installing a
> socket. Believe I broke a trace somewhere, but am unable to track it down
> due eye sight (near and far sighted with progressive glasses on eyes that
> see 5 of everything) that even my magnifier hasn't helped.
> > >
> > > Picked up another M102 for the motherboard. My Rex doesn't have a wire
> to connect it to CS on the system ROM. Am seeking to acquire as much info
> as I can before I clip the ROM on the new M102.
> > >
> > > Figured Rex would be a safer way for me to go at this point. I'll
> check out the links and see where I can go.
> > >
> > > Thanks,
> > >
> > > GregS <><
> > >
> > > Mar 31, 2020 12:21:38 AM Brian White < b.kenyo...@gmail.com >:
> > >
> > > > From this, I don't have any idea what you actually tried or what
> exactly happened.
> > > >
> > > > You could try
> > > >
> > > >
> > > > http://tandy.wiki/FlexROM_102
> > > >
> > > >
> > > > It's designed exactly to facilitate switching back to an internal
> rom after clising up the case si you can add or remove a REX at will after
> that.
> > > >
> > > >
> > > > Some more detailed directions about loading the rom images onto the
> rex are on the directions for the M100 version of the same board
> > > >
> > > >
> > > > http://tandy.wiki/FlexROM_100
> > > >
> > > >
> > > > The 102 (and some late model 100's) are different from the early
> 100's (most 100s? I'm not sure about the numbers or percentages) So, look
> at that page for the siftware directions but use the 102 board in a 102.
> > > >
> > > >
> > > > Or, you don't need to actually order and build that board. You could
> also just use that as some additional reference material for how to load
> and use the rom images. I come at the same process, and I come at
> documentation of the same thing from a slightly different angle, so by
> following two different docs for the same thing maybe some fuzzy parts
> might clear up.
> > > >
> > > >
> > > > Honestly I found Stevens original docs for the rex main rom feature
> on bitchin100 (linkred from the pages above) are pretty good and explicit.
> Just follow them exactly, and if there is some step that you don't know
> what it means, ask for clarification about it in detail.
> > > >
> > > >
> > > > The entire process is 500 details, but from this description I can't
> tell which one(s) tripped you up. It could be anything. So just try going
> from the top, and do not proceed past the very first word that you aren't
> 100% sure about. Just stop and ask what does x mean, even if it's right in
> the first sentence. Then we can probably make the docs better by expanding
> on whatever wasn't clear enough.
> > > >
> > > >
> > > > --
> > > > bkw
> > > >
> > > >
> > > >
> > > > On Mon, Mar 30, 2020, 7:18 PM Greg Swallow 

Re: [M100] M102 add Rexx (w/ switch)

[Greg Swallow]

With the troubles I'm having with my sight, I don't want to make a mess of 
another removal/replace on a M102. I figured clipping the CS and adding a 
switch would better. Otherwise, I would prefer adding a "socket" et al.

Thanks,

GregS <><


Mar 31, 2020 4:16:17 AM Stephen Adolph :

> I must say - what is the end objective? What ROM other than T102 ROM do you 
> want as the main ROM?
> REX provides y2k fix...
> You can probably tell but I am not really a fan anymore of using REX to 
> replace the main rom. In my experience it has had little benefit and much 
> pain.
> 
> 
> 
> On Tue, Mar 31, 2020 at 6:05 AM Greg Swallow < gswal...@mchsi.com > wrote:
> 
> 
> > I have mucked the M102 up removing the system ROM and installing a socket. 
> > Believe I broke a trace somewhere, but am unable to track it down due eye 
> > sight (near and far sighted with progressive glasses on eyes that see 5 of 
> > everything) that even my magnifier hasn't helped.
> > 
> > Picked up another M102 for the motherboard. My Rex doesn't have a wire to 
> > connect it to CS on the system ROM. Am seeking to acquire as much info as I 
> > can before I clip the ROM on the new M102.
> > 
> > Figured Rex would be a safer way for me to go at this point. I'll check out 
> > the links and see where I can go.
> > 
> > Thanks,
> > 
> > GregS <><
> > 
> > Mar 31, 2020 12:21:38 AM Brian White < b.kenyo...@gmail.com >:
> > 
> > > From this, I don't have any idea what you actually tried or what exactly 
> > > happened.
> > >
> > > You could try
> > >
> > >
> > > http://tandy.wiki/FlexROM_102 
> > >
> > >
> > > It's designed exactly to facilitate switching back to an internal rom 
> > > after clising up the case si you can add or remove a REX at will after 
> > > that.
> > >
> > >
> > > Some more detailed directions about loading the rom images onto the rex 
> > > are on the directions for the M100 version of the same board
> > >
> > >
> > > http://tandy.wiki/FlexROM_100 
> > >
> > >
> > > The 102 (and some late model 100's) are different from the early 100's 
> > > (most 100s? I'm not sure about the numbers or percentages) So, look at 
> > > that page for the siftware directions but use the 102 board in a 102.
> > >
> > >
> > > Or, you don't need to actually order and build that board. You could also 
> > > just use that as some additional reference material for how to load and 
> > > use the rom images. I come at the same process, and I come at 
> > > documentation of the same thing from a slightly different angle, so by 
> > > following two different docs for the same thing maybe some fuzzy parts 
> > > might clear up.
> > >
> > >
> > > Honestly I found Stevens original docs for the rex main rom feature on 
> > > bitchin100 (linkred from the pages above) are pretty good and explicit. 
> > > Just follow them exactly, and if there is some step that you don't know 
> > > what it means, ask for clarification about it in detail.
> > >
> > >
> > > The entire process is 500 details, but from this description I can't tell 
> > > which one(s) tripped you up. It could be anything. So just try going from 
> > > the top, and do not proceed past the very first word that you aren't 100% 
> > > sure about. Just stop and ask what does x mean, even if it's right in the 
> > > first sentence. Then we can probably make the docs better by expanding on 
> > > whatever wasn't clear enough.
> > >
> > >
> > > --
> > > bkw
> > >
> > >
> > >
> > > On Mon, Mar 30, 2020, 7:18 PM Greg Swallow < gswal...@mchsi.com > wrote:
> > >
> > >
> > > > Still unable to get my M102 working w/ Sys ROM I burned. Another M102 
> > > > off eBay arrived today. Plan to use motherboard from this and put in my 
> > > > case.
> > > >
> > > > Figure on taking the Rexx I have in an M100 and put in in this M102; 
> > > > using the Sys image option. I have found descriptions of what to do, 
> > > > but no pictures or diagrams. Anybody have anything?
> > > >
> > > > Looking at a micro slide switch (SPDT) to select between original ROM 
> > > > or image just in case of bad image hang.
> > > >
> > > > Thanks,
> > > >
> > > > GregS <><
> > > >
> > > >
> > > >
> > >
> > >
> > 
> > 
> > 
> 
> 

Re: [M100] M102 add Rexx (w/ switch)

[Stephen Adolph]

I must say - what is the end objective?  What ROM other than T102 ROM do
you want as the main ROM?
REX provides y2k fix...
You can probably tell but I am not really a fan anymore of using REX to
replace the main rom.  In my experience it has had little benefit and much
pain.

On Tue, Mar 31, 2020 at 6:05 AM Greg Swallow  wrote:

> I have mucked the M102 up removing the system ROM and installing a socket.
> Believe I broke a trace somewhere, but am unable to track it down due eye
> sight (near and far sighted with progressive glasses on eyes that see 5 of
> everything) that even my magnifier hasn't helped.
>
> Picked up another M102 for the motherboard. My Rex doesn't have a wire to
> connect it to CS on the system ROM. Am seeking to acquire as much info as I
> can before I clip the ROM on the new M102.
>
> Figured Rex would be a safer way for me to go at this point. I'll check
> out the links and see where I can go.
>
> Thanks,
>
> GregS <><
>
> Mar 31, 2020 12:21:38 AM Brian White :
>
> > From this, I don't have any idea what you actually tried or what exactly
> happened.
> >
> > You could try
> >
> >
> > http://tandy.wiki/FlexROM_102
> >
> >
> > It's designed exactly to facilitate switching back to an internal rom
> after clising up the case si you can add or remove a REX at will after that.
> >
> >
> > Some more detailed directions about loading the rom images onto the rex
> are on the directions for the M100 version of the same board
> >
> >
> > http://tandy.wiki/FlexROM_100
> >
> >
> > The 102 (and some late model 100's) are different from the early 100's
> (most 100s? I'm not sure about the numbers or percentages) So, look at that
> page for the siftware directions but use the 102 board in a 102.
> >
> >
> > Or, you don't need to actually order and build that board. You could
> also just use that as some additional reference material for how to load
> and use the rom images. I come at the same process, and I come at
> documentation of the same thing from a slightly different angle, so by
> following two different docs for the same thing maybe some fuzzy parts
> might clear up.
> >
> >
> > Honestly I found Stevens original docs for the rex main rom feature on
> bitchin100 (linkred from the pages above) are pretty good and explicit.
> Just follow them exactly, and if there is some step that you don't know
> what it means, ask for clarification about it in detail.
> >
> >
> > The entire process is 500 details, but from this description I can't
> tell which one(s) tripped you up. It could be anything. So just try going
> from the top, and do not proceed past the very first word that you aren't
> 100% sure about. Just stop and ask what does x mean, even if it's right in
> the first sentence. Then we can probably make the docs better by expanding
> on whatever wasn't clear enough.
> >
> >
> > --
> > bkw
> >
> >
> >
> > On Mon, Mar 30, 2020, 7:18 PM Greg Swallow < gswal...@mchsi.com > wrote:
> >
> >
> > > Still unable to get my M102 working w/ Sys ROM I burned. Another M102
> off eBay arrived today. Plan to use motherboard from this and put in my
> case.
> > >
> > > Figure on taking the Rexx I have in an M100 and put in in this M102;
> using the Sys image option. I have found descriptions of what to do, but no
> pictures or diagrams. Anybody have anything?
> > >
> > > Looking at a micro slide switch (SPDT) to select between original ROM
> or image just in case of bad image hang.
> > >
> > > Thanks,
> > >
> > > GregS <><
> > >
> > >
> > >
> >
> >
>
>
>

Re: [M100] M102 add Rexx (w/ switch)

[Greg Swallow]

I have mucked the M102 up removing the system ROM and installing a socket. 
Believe I broke a trace somewhere, but am unable to track it down due eye sight 
(near and far sighted with progressive glasses on eyes that see 5 of 
everything) that even my magnifier hasn't helped.

Picked up another M102 for the motherboard. My Rex doesn't have a wire to 
connect it to CS on the system ROM. Am seeking to acquire as much info as I can 
before I clip the ROM on the new M102.

Figured Rex would be a safer way for me to go at this point. I'll check out the 
links and see where I can go.

Thanks,

GregS <><

Mar 31, 2020 12:21:38 AM Brian White :

> From this, I don't have any idea what you actually tried or what exactly 
> happened. 
> 
> You could try
> 
> 
> http://tandy.wiki/FlexROM_102 
> 
> 
> It's designed exactly to facilitate switching back to an internal rom after 
> clising up the case si you can add or remove a REX at will after that.
> 
> 
> Some more detailed directions about loading the rom images onto the rex are 
> on the directions for the M100 version of the same board
> 
> 
> http://tandy.wiki/FlexROM_100 
> 
> 
> The 102 (and some late model 100's) are different from the early 100's (most 
> 100s? I'm not sure about the numbers or percentages) So, look at that page 
> for the siftware directions but use the 102 board in a 102.
> 
> 
> Or, you don't need to actually order and build that board. You could also 
> just use that as some additional reference material for how to load and use 
> the rom images. I come at the same process, and I come at documentation of 
> the same thing from a slightly different angle, so by following two different 
> docs for the same thing maybe some fuzzy parts might clear up.
> 
> 
> Honestly I found Stevens original docs for the rex main rom feature on 
> bitchin100 (linkred from the pages above) are pretty good and explicit. Just 
> follow them exactly, and if there is some step that you don't know what it 
> means, ask for clarification about it in detail.
> 
> 
> The entire process is 500 details, but from this description I can't tell 
> which one(s) tripped you up. It could be anything. So just try going from the 
> top, and do not proceed past the very first word that you aren't 100% sure 
> about. Just stop and ask what does x mean, even if it's right in the first 
> sentence. Then we can probably make the docs better by expanding on whatever 
> wasn't clear enough.
> 
> 
> --
> bkw
> 
> 
> 
> On Mon, Mar 30, 2020, 7:18 PM Greg Swallow < gswal...@mchsi.com > wrote:
> 
> 
> > Still unable to get my M102 working w/ Sys ROM I burned. Another M102 off 
> > eBay arrived today. Plan to use motherboard from this and put in my case.
> > 
> > Figure on taking the Rexx I have in an M100 and put in in this M102; using 
> > the Sys image option. I have found descriptions of what to do, but no 
> > pictures or diagrams. Anybody have anything?
> > 
> > Looking at a micro slide switch (SPDT) to select between original ROM or 
> > image just in case of bad image hang.
> > 
> > Thanks,
> > 
> > GregS <><
> > 
> > 
> > 
> 
> 

Re: [M100] NEC 8201A Drawing a line

[Brian White]

web8201.net has been limping ever since Gary (is that right?) moved it to a
new server recently. Try at different times of day. It's been pretty
consistently slow, but sometimes better than others. Sometimes it appears
100% down, but other times it's merely slow. So, just try again later, try
at a few different times trough the whole 24h range, you'll probably get
lucky somewhere along the way, maybe in the day, maybe at night.

-- 
bkw

On Mon, Mar 30, 2020, 8:00 PM D10D3 Data  wrote:

> Thanks
>
> On Mon, Mar 30, 2020 at 7:50 PM Kurt McCullum  wrote:
>
>> Found it in an email I sent some time ago. File attached
>>
>> On Mon, Mar 30, 2020, at 4:38 PM, Kurt McCullum wrote:
>>
>> You need the line utility. It adds the hooks to line() in basic. It's on
>> the web8201.net site but it's down right now.
>>
>> I have it on another computer and I can send it to you later. Also, there
>> is a version of SARDOS (ver 1.71) that has the LINE code in the ROM.
>> Whenever you want to use it, a call to the rom loads it into the ALTLCD
>> memory space.
>>
>> Kurt
>>
>> On Mon, Mar 30, 2020, at 3:33 PM, D10D3 Data wrote:
>>
>> I'm trying to port a program I wrote on my M100 to run on my NEC 8201A.
>> My program draws a few lines, and this turns out to be a lot harder on
>> the 8201.
>>
>> It seems that NEC, in their infinite wisdom, removed the LINE() command
>> from NEC BASIC, so all I can do is plot individual pixels. My program only
>> draws a few lines, so even though it would be slower to draw lines pixel by
>> pixel I'd like to try it. Does anyone know of an example program that plots
>> lines this way? I'm trying to sort out the logic for a line drawing sub but
>> it's making my head spin.
>> -Jason
>>
>>
>>
>>

Re: [M100] M102 add Rexx (w/ switch)

[Brian White]

>From this, I don't have any idea what you actually tried or what exactly
happened.

You could try

http://tandy.wiki/FlexROM_102

It's designed exactly to facilitate switching back to an internal rom after
clising up the case si you can add or remove a REX at will after that.

Some more detailed directions about loading the rom images onto the rex are
on the directions for the M100 version of the same board

http://tandy.wiki/FlexROM_100

The 102 (and some late model 100's) are different from the early 100's
(most 100s? I'm not sure about the numbers or percentages) So, look at that
page for the siftware directions but use the 102 board in a 102.

Or, you don't need to actually order and build that board. You could also
just use that as some additional reference material for how to load and use
the rom images. I come at the same process, and I come at documentation of
the same thing from a slightly different angle, so by following two
different docs for the same thing maybe some fuzzy parts might clear up.

Honestly I found Stevens original docs for the rex main rom feature on
bitchin100 (linkred from the pages above) are pretty good and explicit.
Just follow them exactly, and if there is some step that you don't know
what it means, ask for clarification about it in detail.

The entire process is 500 details, but from this description I can't tell
which one(s) tripped you up. It could be anything. So just try going from
the top, and do not proceed past the very first word that you aren't 100%
sure about. Just stop and ask what does x mean, even if it's right in the
first sentence. Then we can probably make the docs better by expanding on
whatever wasn't clear enough.

-- 
bkw

On Mon, Mar 30, 2020, 7:18 PM Greg Swallow  wrote:

> Still unable to get my M102 working w/ Sys ROM I burned. Another M102 off
> eBay arrived today. Plan to use motherboard from this and put in my case.
>
> Figure on taking the Rexx I have in an M100 and put in in this M102; using
> the Sys image option. I have found descriptions of what to do, but no
> pictures or diagrams. Anybody have anything?
>
> Looking at a micro slide switch (SPDT) to select between original ROM or
> image just in case of bad image hang.
>
> Thanks,
>
> GregS <><
>
>
>