Re: [M100] Radio Shack trs80 Model 200 for sale

[Daniel L]

What a relief. I would've bought it to save if I weren't beyond budget this 
month.

On February 24, 2023 6:14:49 AM PST, Joshua O'Keefe  
wrote:
>> On Feb 24, 2023, at 5:57 AM, Randall Kindig  wrote:
>> 
>> I didn’t get a response either.
>
>After this thread revived (thanks b 9!) I received an off-list reply that it 
>had been sold.  Nice to hear it didn't wind up making that dump run after all.

[M100] Small changes to C0DE function in CloudT

[John R. Hogerhuis]

I made a couple of small changes to the C0DE helper in CloudT:

First, I disabled "spellcheck" so when you type assembly instructions it
won't underline them

Second for the "Raw" format where it emits code bytes directly, if the byte
is unprintable (less than ASCII 32), instead of missing characters it will
instead emit

"+CHR$(val)+"

where val is the decimal equivalent of the byte being emitted.

Which is probably what you want if you're choosing to emit unprintable
bytes to be part of a string.

The only thing to understand is that the content of

A$="BLAH"

is referenced directly as an immutable literal in the string symbol/object.
It takes a number of bytes of the string plus constant overhead.

A$="BLAH"+CHR$(2)

takes twice as much space, since it has to keep the immutable part "BLAH"
immutable since it is part of your program code. But then it allocates
string space to copy the immutable part to, then append the character.

Also, strings that are part of the string region and not literals in your
program can get moved by the garbage collector. It would be bad if you
stored ML code in a string, calculate its address and then jump to it, but
the code was moved by the garbage collector. If you think garbage
collection is a factor you need to take VARPTR of the string again and
recompute the entry point.

-- John.

Re: [M100] M100 LCD repair video and alternative use for unused screen RAM

[Philip Avery]

Yes, I have a list of jobs to do on M100 CP/M. Rest assured I'm still 
committed to all-things M100 CP/M.  My excuse is I was commissioned to 
do a vintage vehicle restoration which has soaked up all my spare time 
for the last 2-years. The good news is I'm almost complete & I expect 
within a few months to get my vintage computing time back & be able to 
resolve any M100 CP/M issues & add new features...


Philip

On 25/02/2023 6:59 am, Jim Anderson wrote:

-Original Message-

Did you ever finish whatever it was you still needed to do for rexcpm?

I don't remember what the problem was supposed to be by now, but I
remember to keep watching for some update to either cpmupd or to the
disk image every time I reload my rexcpm, and I only know that the files
haven't changed.

I guess for that matter the question should be "What was that problem
supposed to be again?"

Another chime in from someone who is still around but lurking :)

I didn't want to bring this up because I have my own unfinished project I feel 
guilty about, but I will answer the question.  (My unfinished thing is that I 
started on a project to improve the font used on the MVT100 board, and I made a 
minor improvement to readability of a few characters (6, 9, and Q, I believe) 
which Stephen started distributing with new boards, and then I embarked on a 
project to dramatically improve the rendering of the 80x24 mode font and also 
reproduce the original DVI font, and then I got stalled out partway through the 
character set when Life Happened :( but I do mean to get back to it, I promise)

The thing that I think you're remembering is that there isn't enough directory 
entries in the CP/M image for the 4MB REXCPM.  I discovered this because I was 
filling mine up and I'm only able to use a little more than half the capacity 
IIRC (it might have been more approaching 2/3 capacity).  Philip said he would 
need to re-make the image for 4MB with a greater number of directory entries, 
and that anyone who wanted to use it would of course have to export their 
files, load the new disk image, and re-import their files back.  (A pain to be 
sure, if you've filled it up like I have, but a pain I'm quite willing to 
undergo.)

Two other things I've been hoping for for quite some time, and I'm not sure how 
much of this was Philip's thing and how much was Stephen's thing and/or someone 
else's thing, but there was talk of new versions of import/export which would 
support 8.3 filenames instead of just 6.2 when used with a compatible TPDD 
emulator...

The second thing was 76800bps support when used with a compatible TPDD 
emulator.  I know there's a private version of this floating around somewhere 
because the REX backup/restore utility supports it, and I've been aching to 
make use of it.

Maybe if I get my project moving and released?  My internal guilt makes me not 
want to ask for these things because I have failed so far to deliver on my 
thing... :P







 jim

Re: [M100] DVI character set

[Kenneth Pettit]

Hey George,

When you execute SCREEN 0 or SCREEN 1, it sets a variable indicating the 
selected screen at the following addresses:


M100:  F638H
T200:   EF06H

This will be 0 for LCD or 1 for DVI.

Or you can look at the active ROWs, COLs addresses

M100:
   ROWS: F63Bh   will be 8 or 25
   COLS: F63Ch   will be 40 or 80

T200:
   ROWS: EF08H   will be 16 or 25
   COLS: EF09H   will be 40 or 80

I don't believe there is a copy of DVI contents in RAM anywhere. For an 
80x25 display, this would be 2000 bytes of data.


Ken

On 2/24/23 8:14 AM, grima...@gmail.com wrote:

Random questions.

1. Is there an easy way to identify from BASIC, a computer which is 
connected to a DVI.
2. Is there a range of memory that I can access from BASIC that 
mirrors the DVI screen contents?


Basically, I've updated Text Sweeper to properly ID the model 200 and 
check the right LCD memory locations, but now I am facing a similar 
issue with the DVI system.


-George

On Fri, Feb 24, 2023 at 11:04 AM Brian K. White  
wrote:


nuthin toit

On 2/24/23 09:27, Stephen Adolph wrote:
> Brian thanks again for posting the ROMs.
> They dropped directly into my new project unmodified!
>
> On Thu, Feb 23, 2023 at 8:36 PM Stephen Adolph
 > wrote:
>
>     I'm back at this.
>     In the emulator I am working on. Ow, I have to redo the
fonts.  I'm
>     free to use whatever I want.
>
>     So, which one of these fonts is actually used by the dvi? 
The 8x8
>     or the 7x8?
>
>
>
>     On Thursday, January 28, 2021, Tom Wilson      > wrote:
>
>         Ooh! There are actually two fonts in the 4K ROM
>
>         Here's the second one
>         image.png
>
>         This is the same font, but with only 7 bits used. I'm
betting
>         this is the same as the internal font on the M100
itself. Here's
>         one of the characters (255) for comparison:
>
>         Bank 0:
>         image.png
>
>         Bank 1:
>         image.png
>
>
>         Tom Wilson
> wilso...@gmail.com 
>         (619)940-6311
>
>
>
>         On Thu, Jan 28, 2021 at 4:09 PM Tom Wilson
         > wrote:
>
>             Hey, the file works with my Commodore font editor! 
=)  I'm
>             totally going to add this as an optional font in my
terminal
>             emulator.
>
>             image.png
>
>
>
>             Tom Wilson
> wilso...@gmail.com 
>             (619)940-6311
>
>
>
>             On Thu, Jan 28, 2021 at 1:53 PM Jim Anderson
>             mailto:jim.ander...@kpu.ca>>
wrote:
>
>                  > -Original Message-
>                  > If you're going to do that much, then I will grab
>                 some more pics with a
>                  > better camera and a tripod so my hand isn't
moving,
>                 and manual focus.
>                  > Maybe even a good straight-on centered shot
without
>                 glare from the room
>                  > lights. Maybe with manual controls I can get
a shot
>                 in the dark without
>                  > the text blooming.
>
>                 You know what, I realize that I went straight to
that
>                 screen photo image because I was looking for a clear
>                 image that had my XX pattern in 80-column
mode...
>                 and it's really not so blurry, but the capture in
>                 "Snapshot_20210127_233755.jpg" is sharper and
does have
>                 the full character set showing.  Even though they're
>                 flanked by square brackets I think I can work
with it.
>                 (the square brackets don't go to the full left
and right
>                 extent of the character cell, that's why I used X.)
>                 Don't worry about going to any trouble for a sharper
>                 screen photo.  For my cleanup/rescaling of the
original
>                 font I've been working off a handheld iphone
photo of my
>                 monitor.
>
>                 I also whipped something up to display the ROM
data as
>                 large block pixels for an absolute reference to the
>                 original intended shapes so I think I've got
everything
>                 I need (except time) :)
>
>
>
>
>
>
>
>                          jim
>

-- 
bkw

Re: [M100] C# terminal slooowwww

[John R. Hogerhuis]

On Fri, Feb 24, 2023 at 11:34 AM Kenneth Pettit  wrote:

> Hey Steve,
>
> I think the operative words in your email contributing to slowness are
> "windows machine"  (tee hee hee).  But seriously ... Windows? Do people
> still use Windows in 2023?  (Sorry, just can't help myself).
>
> Ken
>
>
Hey now, Windows NT is a real OS :-) I don't know why you'd want to pay for
a Windows license versus free Linux, but people seem to do it. Maybe they
need to run applications on it.

My license came with my laptop.

-- John.

Re: [M100] C# terminal slooowwww

[John R. Hogerhuis]

On Fri, Feb 24, 2023 at 11:34 AM John R. Hogerhuis  wrote:

>
> Yes. Sounds like something is broken or badly written. Some non-blocking
> loop.
>
> Generally a program waiting on terminal input has absolutely nothing to do
> but wait for the OS to wake it up with a character.
>
> -- John.
>


And "wait" is probably even the wrong term for it. The program would spend
most of its time blocked on a read call.

Now if the program is not a console app but a GUI app with a message loop,
that's a little different. But properly written CPU utilization should
still be low. Still blocks on dequeue.

-- John.

Re: [M100] C# terminal slooowwww

[Mike Stein]

MS-DOS Forever!!!

On Fri, Feb 24, 2023 at 2:34 PM Kenneth Pettit  wrote:

> Hey Steve,
>
> I think the operative words in your email contributing to slowness are
> "windows machine"  (tee hee hee).  But seriously ... Windows? Do people
> still use Windows in 2023?  (Sorry, just can't help myself).
>
> Ken
>
> On 2/24/23 11:15 AM, Stephen Adolph wrote:
> > Question for the crowd.
> >
> > I've got the mvt100 terminal in C# running well.  It is compiled in
> > Visual Studio.
> >
> > When I run in full screen mode, the cpu utikixlxation jumps to 50% and
> > the response of the terminal is visibly slow.
> >
> > I get that the screen updates take time, but really?  My windows
> > machine is less responsive than the little Pic based Geoff terminal.
> >
> > Is thisn indicative of bad code?
>
>

Re: [M100] C# terminal slooowwww

[John R. Hogerhuis]

On Fri, Feb 24, 2023 at 11:16 AM Stephen Adolph 
wrote:

> Question for the crowd.
>
> I've got the mvt100 terminal in C# running well.  It is compiled in Visual
> Studio.
>
> When I run in full screen mode, the cpu utikixlxation jumps to 50% and the
> response of the terminal is visibly slow.
>
> I get that the screen updates take time, but really?  My windows machine
> is less responsive than the little Pic based Geoff terminal.
>
> Is thisn indicative of bad code?
>

Yes. Sounds like something is broken or badly written. Some non-blocking
loop.

Generally a program waiting on terminal input has absolutely nothing to do
but wait for the OS to wake it up with a character.

-- John.

Re: [M100] C# terminal slooowwww

[Kenneth Pettit]

Hey Steve,

I think the operative words in your email contributing to slowness are 
"windows machine"  (tee hee hee).  But seriously ... Windows? Do people 
still use Windows in 2023?  (Sorry, just can't help myself).


Ken

On 2/24/23 11:15 AM, Stephen Adolph wrote:

Question for the crowd.

I've got the mvt100 terminal in C# running well.  It is compiled in 
Visual Studio.


When I run in full screen mode, the cpu utikixlxation jumps to 50% and 
the response of the terminal is visibly slow.


I get that the screen updates take time, but really?  My windows 
machine is less responsive than the little Pic based Geoff terminal.


Is thisn indicative of bad code?

[M100] C# terminal slooowwww

[Stephen Adolph]

Question for the crowd.

I've got the mvt100 terminal in C# running well.  It is compiled in Visual
Studio.

When I run in full screen mode, the cpu utikixlxation jumps to 50% and the
response of the terminal is visibly slow.

I get that the screen updates take time, but really?  My windows machine is
less responsive than the little Pic based Geoff terminal.

Is thisn indicative of bad code?

Re: [M100] M100 LCD repair video and alternative use for unused screen RAM

[Jim Anderson]

> -Original Message-
> 
> Did you ever finish whatever it was you still needed to do for rexcpm?
> 
> I don't remember what the problem was supposed to be by now, but I
> remember to keep watching for some update to either cpmupd or to the
> disk image every time I reload my rexcpm, and I only know that the files
> haven't changed.
> 
> I guess for that matter the question should be "What was that problem
> supposed to be again?"

Another chime in from someone who is still around but lurking :)

I didn't want to bring this up because I have my own unfinished project I feel 
guilty about, but I will answer the question.  (My unfinished thing is that I 
started on a project to improve the font used on the MVT100 board, and I made a 
minor improvement to readability of a few characters (6, 9, and Q, I believe) 
which Stephen started distributing with new boards, and then I embarked on a 
project to dramatically improve the rendering of the 80x24 mode font and also 
reproduce the original DVI font, and then I got stalled out partway through the 
character set when Life Happened :( but I do mean to get back to it, I promise)

The thing that I think you're remembering is that there isn't enough directory 
entries in the CP/M image for the 4MB REXCPM.  I discovered this because I was 
filling mine up and I'm only able to use a little more than half the capacity 
IIRC (it might have been more approaching 2/3 capacity).  Philip said he would 
need to re-make the image for 4MB with a greater number of directory entries, 
and that anyone who wanted to use it would of course have to export their 
files, load the new disk image, and re-import their files back.  (A pain to be 
sure, if you've filled it up like I have, but a pain I'm quite willing to 
undergo.)

Two other things I've been hoping for for quite some time, and I'm not sure how 
much of this was Philip's thing and how much was Stephen's thing and/or someone 
else's thing, but there was talk of new versions of import/export which would 
support 8.3 filenames instead of just 6.2 when used with a compatible TPDD 
emulator...

The second thing was 76800bps support when used with a compatible TPDD 
emulator.  I know there's a private version of this floating around somewhere 
because the REX backup/restore utility supports it, and I've been aching to 
make use of it.

Maybe if I get my project moving and released?  My internal guilt makes me not 
want to ask for these things because I have failed so far to deliver on my 
thing... :P







jim

Re: [M100] Super ROM for NEC

[John R. Hogerhuis]

rant on

It always surprises me that anyone would do an 8085 assembler or
disassembler and not implement the undocumented instructions. I mean
they're there, everyone knows about them, it has been decades, the
instructions were fully implemented and stable, they're not hard to find
and as you're coding you want to fill out your jump table, data structure,
or switch case right? Just for symmetry?

And a forensics or hacking tool... kinda no excuse. It has to work on real
world code as you find it or it's useless. And real programmers use the
undocumented instructions.

rant off

That said, ghidra sounds like an cool tool.

-- John.

On Fri, Feb 24, 2023 at 1:30 AM B 9  wrote:

> On Sun, Feb 19, 2023 at 12:34 PM Stephen Adolph 
> wrote:
>
>> Yah I'm not sure it is actually doable, in a reasonable amount of time
>> effort.
>> It is hard to separate data tables from code.
>>
>> I found one disassembler that was capable of labeling, and tracing code,
>> but it did not support undoc opcodes, so it wasn't a good disassembly to
>> use.
>>
>
> Have you tried Ghidra ? It lacks the 8085
> undocumented instructions, but it's open source and thus extensible. For
> example, someone added support for undocumented opcodes for the Z80
> .
> Someone else started an implementation for the 8085
>  back in
> 2020, but nobody has tested it yet to give the author feedback.
>
> —b9
>

Re: [M100] M100 LCD repair video and alternative use for unused screen RAM

[Mike Stein]

Well, you don't need it on a T200 ;-)

The challenge was putting a 9x9 grid on an 8-line screen

BTW, he's also the guy who did most of the firmware for the CP/M port.



On Fri, Feb 24, 2023 at 2:41 AM B 9  wrote:

> On Sun, Feb 19, 2023 at 4:06 PM Mike Stein  wrote:
>
>> You might also get inspired by Philip Avery's Sudoku program in his
>> Club100 upload folder.
>>
>
> Unfortunately, it doesn't work at all on my Tandy 200. (I tried both
> version 3.1 and 4.1).
>
> Maybe he'll publish the source...
>>
>
> That'd be nice. Is he still around? It looks like he has a few nifty
> utilities (like the HW scrolling demo) which are worth archiving somewhere,
> if he's willing to release the source.
>
> —b9
>

Re: [M100] DVI character set

[grima...@gmail.com]

Random questions.

1. Is there an easy way to identify from BASIC, a computer which is
connected to a DVI.
2. Is there a range of memory that I can access from BASIC that mirrors the
DVI screen contents?

Basically, I've updated Text Sweeper to properly ID the model 200 and check
the right LCD memory locations, but now I am facing a similar issue with
the DVI system.

-George

On Fri, Feb 24, 2023 at 11:04 AM Brian K. White 
wrote:

> nuthin toit
>
> On 2/24/23 09:27, Stephen Adolph wrote:
> > Brian thanks again for posting the ROMs.
> > They dropped directly into my new project unmodified!
> >
> > On Thu, Feb 23, 2023 at 8:36 PM Stephen Adolph  > > wrote:
> >
> > I'm back at this.
> > In the emulator I am working on. Ow, I have to redo the fonts.  I'm
> > free to use whatever I want.
> >
> > So, which one of these fonts is actually used by the dvi?  The 8x8
> > or the 7x8?
> >
> >
> >
> > On Thursday, January 28, 2021, Tom Wilson  > > wrote:
> >
> > Ooh! There are actually two fonts in the 4K ROM
> >
> > Here's the second one
> > image.png
> >
> > This is the same font, but with only 7 bits used. I'm betting
> > this is the same as the internal font on the M100 itself. Here's
> > one of the characters (255) for comparison:
> >
> > Bank 0:
> > image.png
> >
> > Bank 1:
> > image.png
> >
> >
> > Tom Wilson
> > wilso...@gmail.com 
> > (619)940-6311
> >
> >
> >
> > On Thu, Jan 28, 2021 at 4:09 PM Tom Wilson  > > wrote:
> >
> > Hey, the file works with my Commodore font editor!  =)  I'm
> > totally going to add this as an optional font in my terminal
> > emulator.
> >
> > image.png
> >
> >
> >
> > Tom Wilson
> > wilso...@gmail.com 
> > (619)940-6311
> >
> >
> >
> > On Thu, Jan 28, 2021 at 1:53 PM Jim Anderson
> > mailto:jim.ander...@kpu.ca>> wrote:
> >
> >  > -Original Message-
> >  > If you're going to do that much, then I will grab
> > some more pics with a
> >  > better camera and a tripod so my hand isn't moving,
> > and manual focus.
> >  > Maybe even a good straight-on centered shot without
> > glare from the room
> >  > lights. Maybe with manual controls I can get a shot
> > in the dark without
> >  > the text blooming.
> >
> > You know what, I realize that I went straight to that
> > screen photo image because I was looking for a clear
> > image that had my XX pattern in 80-column mode...
> > and it's really not so blurry, but the capture in
> > "Snapshot_20210127_233755.jpg" is sharper and does have
> > the full character set showing.  Even though they're
> > flanked by square brackets I think I can work with it.
> > (the square brackets don't go to the full left and right
> > extent of the character cell, that's why I used X.)
> > Don't worry about going to any trouble for a sharper
> > screen photo.  For my cleanup/rescaling of the original
> > font I've been working off a handheld iphone photo of my
> > monitor.
> >
> > I also whipped something up to display the ROM data as
> > large block pixels for an absolute reference to the
> > original intended shapes so I think I've got everything
> > I need (except time) :)
> >
> >
> >
> >
> >
> >
> >
> >  jim
> >
>
> --
> bkw
>
>

Re: [M100] DVI character set

[Brian K. White]

nuthin toit

On 2/24/23 09:27, Stephen Adolph wrote:

Brian thanks again for posting the ROMs.
They dropped directly into my new project unmodified!

On Thu, Feb 23, 2023 at 8:36 PM Stephen Adolph > wrote:


I'm back at this.
In the emulator I am working on. Ow, I have to redo the fonts.  I'm
free to use whatever I want.

So, which one of these fonts is actually used by the dvi?  The 8x8
or the 7x8?



On Thursday, January 28, 2021, Tom Wilson mailto:wilso...@gmail.com>> wrote:

Ooh! There are actually two fonts in the 4K ROM

Here's the second one
image.png

This is the same font, but with only 7 bits used. I'm betting
this is the same as the internal font on the M100 itself. Here's
one of the characters (255) for comparison:

Bank 0:
image.png

Bank 1:
image.png


Tom Wilson
wilso...@gmail.com 
(619)940-6311



On Thu, Jan 28, 2021 at 4:09 PM Tom Wilson mailto:wilso...@gmail.com>> wrote:

Hey, the file works with my Commodore font editor!  =)  I'm
totally going to add this as an optional font in my terminal
emulator.

image.png



Tom Wilson
wilso...@gmail.com 
(619)940-6311



On Thu, Jan 28, 2021 at 1:53 PM Jim Anderson
mailto:jim.ander...@kpu.ca>> wrote:

 > -Original Message-
 > If you're going to do that much, then I will grab
some more pics with a
 > better camera and a tripod so my hand isn't moving,
and manual focus.
 > Maybe even a good straight-on centered shot without
glare from the room
 > lights. Maybe with manual controls I can get a shot
in the dark without
 > the text blooming.

You know what, I realize that I went straight to that
screen photo image because I was looking for a clear
image that had my XX pattern in 80-column mode...
and it's really not so blurry, but the capture in
"Snapshot_20210127_233755.jpg" is sharper and does have
the full character set showing.  Even though they're
flanked by square brackets I think I can work with it. 
(the square brackets don't go to the full left and right
extent of the character cell, that's why I used X.) 
Don't worry about going to any trouble for a sharper

screen photo.  For my cleanup/rescaling of the original
font I've been working off a handheld iphone photo of my
monitor.

I also whipped something up to display the ROM data as
large block pixels for an absolute reference to the
original intended shapes so I think I've got everything
I need (except time) :)







         jim



--
bkw

Re: [M100] M100 LCD repair video and alternative use for unused screen RAM

[Brian K. White]

Did you ever finish whatever it was you still needed to do for rexcpm?

I don't remember what the problem was supposed to be by now, but I 
remember to keep watching for some update to either cpmupd or to the 
disk image every time I reload my rexcpm, and I only know that the files 
haven't changed.


I guess for that matter the question should be "What was that problem 
supposed to be again?"


--
bkw

On 2/24/23 04:17, Philip Avery wrote:
Yes, I'm still around. I've uploaded to the Personal Library on 
Club100.org the source for Sudoku display - SUDISP.DO. I don't know how 
much use this would be for you as all I was doing was displaying a 9x9 
grid on the M100/T102 8-line display. I just rolled my own font for 
digits 1-9.


I've also uploaded the source for HW scroll demo - scroll.asm

Philip

On 24/02/2023 8:40 pm, B 9 wrote:

On Sun, Feb 19, 2023 at 4:06 PM Mike Stein  wrote:

You might also get inspired by Philip Avery's Sudoku program in
his Club100 upload folder.


Unfortunately, it doesn't work at all on my Tandy 200. (I tried both 
version 3.1 and 4.1).


Maybe he'll publish the source...


That'd be nice. Is he still around? It looks like he has a few nifty 
utilities (like the HW scrolling demo) which are worth archiving 
somewhere, if he's willing to release the source.


—b9




--
bkw

Re: [M100] RexCPM install

[Brian K. White]

I recently got dlplus working under cygwin and msys2, but I had to make 
changes to support it, it didn't work out of the box.
Were you using github.com/bkw777/dlplus or the zip file on bitchin100? 
It just worked or did you have to do anything to make it work?


I need to change the name of my fork. "dlplus" really still refers to 
John's version from the zip file on bitchin100.
And mine has deviated so far by now that it's no longer even very 
similar either inside or out.
And, I never liked that it was called dl-anything in the first place. 
DeskLink is Travelling Software's name, and so the original "dl for 
unix" and John's continuation "dlplus" should just not have been 
dl-anything in the first place, just like I should not call it 
LaddiePlus now.

But I don't know what.

dl2 makes the most sense if I didn't care about the "dl" part. It says 
what it is and what to expect correctly and succinctly.


vpdd ? virtual pdd,   meh
ndl ? new desklink or not desklink as you prefer,  meh
pddserver - just to needle Steve ;)
tpddd - tandy portable disk drive daemon , even I don't hate people that 
much

pdde ? maybe
fb100ulator - nailed it

--
bkw

On 10/16/22 17:33, Ben Wiley Sittler wrote:
I regularly use dlplus from a Cygwin command-line shell interface in 
Windows too, but I realize that's not everyone's cup of tea


On Sun, Oct 16, 2022, 14:29 Brian K. White  wrote:

On 10/16/22 14:17, Stephen Adolph wrote:
> Hi Robert, couple of comments.
>
> 1) test your REXCPM.  you can always test it yourself and see if
you
> have a hardware problem
> https://bitchin100.com/wiki/index.php?title=REXCPM
> 
> read up on how to load and run REXCPM.
> I would not do this if you are happy with the REX# part of the
install.
> In fact if that is working, likely no hardware problem.
> There is only one memory chip and it is used for both REX# and CPM.
>
> 2)  Philip's routines more or less rely on LaddieAlpha to
operate.  I
> would recommend you use LaddieAlpha as the TPDD client.

Laddie is a server not a client. You confuse things by insisting on
using the wrong terminology in what are supposed to be reference
documents.

I routinely use dlplus to reload rexcpm. But that's only available
from
linux or mac. In fact thanks to the fact that you have packaged up
rxcini as a loader.do it makes it super convenient to use the
bootstrapper to directly run rxcini in one shot. Same for REX#.
Thanks
much for that.

You can get that same convenience from Windows with a combination of
tsend.ps1 and laddie. Basically:
tsend.ps1 rxcini.DO ;laddiealpha.exe laddie-options-I-don't-remember
all one commandline.

github.com/bkw777/tsend.ps1 

For Robert, I would make sure you're following the points about
clearing
ram before trying to run cpmupd, and definitely use tpdd to copy
cpmupd
to the machine in case you're not.

I think you'll have to list out all the actual steps you're
performing
when you say doesn't work because "it works for me". But it doesn't
always work the first time just from memory.

The directions are somehow confusing to read and get the bullet
points
that matter. Even though I've done it several times and have tried to
write down my own more direct version, I still end up having to
pull up
the bitchin100 pages and refer to some points after it doesn't
work the
first time just from memory. Usually I forget one of the two times
you
should issue a clear statement.

> This is because the files are binary files with a .BK extension.
> Also, make sure you load and run CPMUPD.CO 
> after you
> power off, power on.  This is to ensure you are in the default
RAM config.

There you go, exactly the kind of step I skip or forget the
importance of.

But when I go back to the wiki page and don't skip anything, it
always
works.

-- 
bkw

Re: [M100] DVI character set

[Stephen Adolph]

Brian thanks again for posting the ROMs.
They dropped directly into my new project unmodified!

On Thu, Feb 23, 2023 at 8:36 PM Stephen Adolph  wrote:

> I'm back at this.
> In the emulator I am working on. Ow, I have to redo the fonts.  I'm free
> to use whatever I want.
>
> So, which one of these fonts is actually used by the dvi?  The 8x8 or the
> 7x8?
>
>
>
> On Thursday, January 28, 2021, Tom Wilson  wrote:
>
>> Ooh! There are actually two fonts in the 4K ROM
>>
>> Here's the second one
>> [image: image.png]
>>
>> This is the same font, but with only 7 bits used. I'm betting this is the
>> same as the internal font on the M100 itself. Here's one of the characters
>> (255) for comparison:
>>
>> Bank 0:
>> [image: image.png]
>>
>> Bank 1:
>> [image: image.png]
>>
>>
>> Tom Wilson
>> wilso...@gmail.com
>> (619)940-6311
>>
>>
>>
>> On Thu, Jan 28, 2021 at 4:09 PM Tom Wilson  wrote:
>>
>>> Hey, the file works with my Commodore font editor!  =)  I'm totally
>>> going to add this as an optional font in my terminal emulator.
>>>
>>> [image: image.png]
>>>
>>>
>>>
>>> Tom Wilson
>>> wilso...@gmail.com
>>> (619)940-6311
>>>
>>>
>>>
>>> On Thu, Jan 28, 2021 at 1:53 PM Jim Anderson 
>>> wrote:
>>>
 > -Original Message-
 > If you're going to do that much, then I will grab some more pics with
 a
 > better camera and a tripod so my hand isn't moving, and manual focus.
 > Maybe even a good straight-on centered shot without glare from the
 room
 > lights. Maybe with manual controls I can get a shot in the dark
 without
 > the text blooming.

 You know what, I realize that I went straight to that screen photo
 image because I was looking for a clear image that had my XX pattern
 in 80-column mode... and it's really not so blurry, but the capture in
 "Snapshot_20210127_233755.jpg" is sharper and does have the full character
 set showing.  Even though they're flanked by square brackets I think I can
 work with it.  (the square brackets don't go to the full left and right
 extent of the character cell, that's why I used X.)  Don't worry about
 going to any trouble for a sharper screen photo.  For my cleanup/rescaling
 of the original font I've been working off a handheld iphone photo of my
 monitor.

 I also whipped something up to display the ROM data as large block
 pixels for an absolute reference to the original intended shapes so I think
 I've got everything I need (except time) :)







 jim

>>>

Re: [M100] Radio Shack trs80 Model 200 for sale

[Joshua O'Keefe]

> On Feb 24, 2023, at 5:57 AM, Randall Kindig  wrote:
> 
> I didn’t get a response either.

After this thread revived (thanks b 9!) I received an off-list reply that it 
had been sold.  Nice to hear it didn't wind up making that dump run after all.

Re: [M100] Radio Shack trs80 Model 200 for sale

[Randall Kindig]

I didn’t get a response either.

> On Feb 24, 2023, at 7:53 AM, Joshua O'Keefe  wrote:
> 
> Alas, no response.  I assume the poor thing went into the trash.
> 
>> On Feb 23, 2023, at 11:44 PM, B 9  wrote:
>> 
>> Did Kevin ever respond to your offer? 
>> 
>> —b9
>> 
>> On Sun, Feb 19, 2023 at 10:45 AM Joshua O'Keefe > > wrote:
>> Hello Kevin.
>> Would you accept €150 for packing and shipping of the computer to the USA?

Re: [M100] M100 LCD repair video and alternative use for unused screen RAM

[grima...@gmail.com]

>
> Is the plan for TSWEEPER to eventually take advantage of the larger
> playing field on the Tandy 200 (and other Model Ts)?
>
Well, I think that definitely would be a great feature, although it's not
something I've started thinking about yet. If I were to go that route, I'd
potentially also want to support the DVI, as it has a very large display to
take advantage of. (and I have one)

Nice. That works much better. I suggest having F8 exit to the Menu since
> that is more typical.
>
> By the way, when the game is over, the screen still says "Exit to
> BASIC [F8]". However, F8 doesn't work at that point.
>
> Also, if one hits "Y" to play again, it takes them to the title screen
> instead of directly playing the game again.
>
I'll look into these for the next version. Should be simple to fix.

 The only change I think would make a huge difference for most people would
> be automatically flagging squares when a player presses space bar on a
> number and it is obvious that all the remaining squares must be flagged.

This one I'm not so sure about. Aside from it not being a feature of
Minesweeper I am not familiar with in other implementations, it potentially
creates some ambiguity for the user about what happens when you click a
number cell. I'd like to think about this one more.

-George


On Fri, Feb 24, 2023 at 4:33 AM B 9  wrote:

> Thanks, Philip. It could be useful for showing digits (and flags) for
> minesweeper! Also, it might be possible to port Sudoku to the Tandy 200.
>
> —b9
>
> On Fri, Feb 24, 2023 at 1:18 AM Philip Avery  wrote:
>
>> Yes, I'm still around. I've uploaded to the Personal Library on
>> Club100.org the source for Sudoku display - SUDISP.DO. I don't know how
>> much use this would be for you as all I was doing was displaying a 9x9 grid
>> on the M100/T102 8-line display. I just rolled my own font for digits 1-9.
>>
>> I've also uploaded the source for HW scroll demo - scroll.asm
>>
>> Philip
>>
>> On 24/02/2023 8:40 pm, B 9 wrote:
>>
>> On Sun, Feb 19, 2023 at 4:06 PM Mike Stein  wrote:
>>
>>> You might also get inspired by Philip Avery's Sudoku program in his
>>> Club100 upload folder.
>>>
>>
>> Unfortunately, it doesn't work at all on my Tandy 200. (I tried both
>> version 3.1 and 4.1).
>>
>> Maybe he'll publish the source...
>>>
>>
>> That'd be nice. Is he still around? It looks like he has a few nifty
>> utilities (like the HW scrolling demo) which are worth archiving somewhere,
>> if he's willing to release the source.
>>
>> —b9
>>
>>
>>

Re: [M100] Radio Shack trs80 Model 200 for sale

[Joshua O'Keefe]

Alas, no response.  I assume the poor thing went into the trash.On Feb 23, 2023, at 11:44 PM, B 9  wrote:Did Kevin ever respond to your offer? —b9On Sun, Feb 19, 2023 at 10:45 AM Joshua O'Keefe  wrote:Hello Kevin.Would you accept €150 for packing and shipping of the computer to the USA?

[M100] NEC PC-8221A Printer Manual?

[Gary Weber]

I actually ended up with a couple of these little portable thermal printers
over the years.  What I have always lacked, though, is a manual for it.

Does anyone out there have a manual?  Kurt, I know you ended up with one
brand new in the box back in 2019, did it have a manual?

I appreciate any info,

-- 
Gary Weber
g...@web8201.com

Re: [M100] M100 LCD repair video and alternative use for unused screen RAM

[B 9]

Thanks, Philip. It could be useful for showing digits (and flags) for
minesweeper! Also, it might be possible to port Sudoku to the Tandy 200.

—b9

On Fri, Feb 24, 2023 at 1:18 AM Philip Avery  wrote:

> Yes, I'm still around. I've uploaded to the Personal Library on
> Club100.org the source for Sudoku display - SUDISP.DO. I don't know how
> much use this would be for you as all I was doing was displaying a 9x9 grid
> on the M100/T102 8-line display. I just rolled my own font for digits 1-9.
>
> I've also uploaded the source for HW scroll demo - scroll.asm
>
> Philip
>
> On 24/02/2023 8:40 pm, B 9 wrote:
>
> On Sun, Feb 19, 2023 at 4:06 PM Mike Stein  wrote:
>
>> You might also get inspired by Philip Avery's Sudoku program in his
>> Club100 upload folder.
>>
>
> Unfortunately, it doesn't work at all on my Tandy 200. (I tried both
> version 3.1 and 4.1).
>
> Maybe he'll publish the source...
>>
>
> That'd be nice. Is he still around? It looks like he has a few nifty
> utilities (like the HW scrolling demo) which are worth archiving somewhere,
> if he's willing to release the source.
>
> —b9
>
>
>

Re: [M100] Super ROM for NEC

[B 9]

On Sun, Feb 19, 2023 at 12:34 PM Stephen Adolph 
wrote:

> Yah I'm not sure it is actually doable, in a reasonable amount of time
> effort.
> It is hard to separate data tables from code.
>
> I found one disassembler that was capable of labeling, and tracing code,
> but it did not support undoc opcodes, so it wasn't a good disassembly to
> use.
>

Have you tried Ghidra ? It lacks the 8085
undocumented instructions, but it's open source and thus extensible. For
example, someone added support for undocumented opcodes for the Z80
.
Someone else started an implementation for the 8085
 back in
2020, but nobody has tested it yet to give the author feedback.

—b9

Re: [M100] M100 LCD repair video and alternative use for unused screen RAM

[Philip Avery]

Yes, I'm still around. I've uploaded to the Personal Library on 
Club100.org the source for Sudoku display - SUDISP.DO. I don't know how 
much use this would be for you as all I was doing was displaying a 9x9 
grid on the M100/T102 8-line display. I just rolled my own font for 
digits 1-9.


I've also uploaded the source for HW scroll demo - scroll.asm

Philip

On 24/02/2023 8:40 pm, B 9 wrote:

On Sun, Feb 19, 2023 at 4:06 PM Mike Stein  wrote:

You might also get inspired by Philip Avery's Sudoku program in
his Club100 upload folder.


Unfortunately, it doesn't work at all on my Tandy 200. (I tried both 
version 3.1 and 4.1).


Maybe he'll publish the source...


That'd be nice. Is he still around? It looks like he has a few nifty 
utilities (like the HW scrolling demo) which are worth archiving 
somewhere, if he's willing to release the source.


—b9