I promise to do a video when I get my serial-VGA board going. It will
give a clean 80 x 24 display whereas XP Hyperterm gives some clutter.
Philip
On 26/01/2020 6:34 pm, Chris Fezzler wrote:
Video please!
On Saturday, January 25, 2020, 10:46:20 PM EST, Philip Avery
wrote:
It's about
Video please!
On Saturday, January 25, 2020, 10:46:20 PM EST, Philip Avery
wrote:
It's about time I chimed in here with my side of deal - which is producing a
CP/M operating system for M100. This works with Steve's REXCPM board and is a
RAM-based system instead of floppy disks, so
I did not do the E1SE thing, I assume it is an artifact of scanning
On Sat, 25 Jan 2020 at 10:26, Mike Stein wrote:
>
> What Brian said!
>
> Also, like many things, context matters; perhaps those variables are used
> elsewhere and they do need to be initialized. Even if not, 'habits' like
>
That will work with M100 CP/M. Same CP/M command (Stat) will redirect
'screen' output to the printer port if you like.
In fact you can redirect keyboard input from the serial as well, so you
can just use the M100 as a processor if you want.
Philip
On 26/01/2020 5:05 pm, John R. Hogerhuis
Yeah this does look interesting. Somewhat offtopic, I just switched my
work laptop from a MacBook to a Dell running Windows (for now) which
only has USB C ports. I could use a dongle to convert my old USB A to
serial cable but ordered a new USB-C to DB9 converter to keep things
simple. I also
Another possibility for display redirection is using the printer port. I've
connected my printer port to a parallel to serial converter and then that
can go to a PC or something else running a serial terminal.
Then you keep the serial port free for bidirectional communication.
But you need a
Mike Stein pointed me to this device: http://geoffg.net/terminal.html
which I have bought, but have yet to assemble & use. Up to now I have
just been using a XP box with Hyperterm to give 80 x 24.
Philip
On 26/01/2020 4:52 pm, Kevin Becker wrote:
I've been eagerly awaiting the REXCPM just for
I've been eagerly awaiting the REXCPM just for something to tinker
with. I've never really used CPM before and thought this would be a
good opportunity. But I wasn't aware of the serial terminal
possibilties. This sounds amazing.
I also had never realized there were simple serial to VGA options
It's about time I chimed in here with my side of deal - which is
producing a CP/M operating system for M100. This works with Steve's
REXCPM board and is a RAM-based system instead of floppy disks, so no
DVI necessary, just a REXCPM board. We have CP/M fully up & running on
real M100s and have
Very cool! Looking forward to it!
On Sat, Jan 25, 2020 at 9:16 PM Stephen Adolph wrote:
> As we get closer to having it fully baked and ready, we will be more
> vocal, visible with info online etc.
> Looking forward to getting it out the door. Cpm has been a long time
> coming!
>
> On
As we get closer to having it fully baked and ready, we will be more vocal,
visible with info online etc.
Looking forward to getting it out the door. Cpm has been a long time
coming!
On Saturday, January 25, 2020, r cs wrote:
>>> Also, be advised Steve is getting close to releasing a new
Very interested
On Sat, Jan 25, 2020 at 7:34 PM r cs wrote:
> > Also, be advised Steve is getting close to releasing a new REX with the
> incredible feature that it can let the M100 run CP/M as well as still being
> everything a normal REX is, for sale not diy
>
> On Sat, Jan 25, 2020 at 12:36
>> Also, be advised Steve is getting close to releasing a new REX with
the incredible feature that it can let the M100 run CP/M as well as still
being everything a normal REX is, for sale not diy
This sounds awesome! Where can we read more and follow it closely to get in
line when it goes on
> Also, be advised Steve is getting close to releasing a new REX with the
incredible feature that it can let the M100 run CP/M as well as still being
everything a normal REX is, for sale not diy
On Sat, Jan 25, 2020 at 12:36 PM Brian White wrote:
> It's the same parts except for the pcb.
>
>
On 1/25/20 4:49 PM, Charles Hudson wrote:
Last year, in my youthful enthusiasm, I also contacted emesystems and
obtained the original Gerbers for the MOMBO expansion card, from which I
had made a few boards. It seems I have the 27C256 EPROM as well.
If anyone is interested I can post them.
Last year, in my youthful enthusiasm, I also contacted emesystems and
obtained the original Gerbers for the MOMBO expansion card, from which I
had made a few boards. It seems I have the 27C256 EPROM as well.
If anyone is interested I can post them. Brian, please don't delete the
wiki yet.
-CH-
Hi,
In order to get CPM working on M100 you need 3 things. 1. All ram mode
and 2. Something to act as a disk drive with sector access 3. CPM custom
tailored to suit with applications.
I've been able to make a new REX that provides all the hardware needed,
using RAM as a disk drive. REXCPM has
I debated bothering preserving that original rex build page. I guess you
just vindicated the decision to keep it around at least off to the side.
You can still use the new page for the flashing directions. I tried to
flesh out and clarify the xilinx software stuff and the tpdd stuff. That is
all
Thanks Ian and Brian for your responses. As I have the parts I will build
with what I have.
CP/M on the 100 sounds like fun but not on top of my wish list. Maybe for
later; I have a box full of other kits to build first.
-CH-
On Sat, Jan 25, 2020 at 11:51 AM Tom Dison wrote:
> Having worked on “enterprise” software for 20 years I have seen worse - in
> production!
>
>
With a comment above it that says
// DO NOT REMOVE!
No reason given .
-- John
On Sat, Jan 25, 2020 at 7:37 AM Stefano Bodrato
wrote:
> I was able to edit the ROM and alter the M100 ROM already but there's a
> surprising code portion at $725E which is probably unmovable:
>
>
Yeah there are a few spots like that which rely on entering the middle of
an instruction to change
Same idea in BASIC with your example of a catchall goto. That requires that
you reach the catchall goto. That requires more details to have gone
according to plan, that you only branched away in ways you intended, that
you never branched away without having set some valid value, and only after
On Sat, Jan 25, 2020, 2:49 PM Peter Vollan wrote:
> The way one solves that is by having the CASE statements and then a
> GOTO catchall for whatever does not get caught. I think you know this.
>
I think I apparently know that and a few other things besides. You seem to
have missed the essence
Having worked on “enterprise” software for 20 years I have seen worse - in
production!
On Sat, Jan 25, 2020 at 1:49 PM Peter Vollan wrote:
> The way one solves that is by having the CASE statements and then a
> GOTO catchall for whatever does not get caught. I think you know this.
>
> On Sat,
The way one solves that is by having the CASE statements and then a
GOTO catchall for whatever does not get caught. I think you know this.
On Sat, 25 Jan 2020 at 07:49, Brian K. White wrote:
>
> Sometimes another explanation for a seemingly no-op line is, given that
> it's impossible for a human
I don't think it does anything with dvi but I have no special knowledge.
I'm sure full docs that answer all questions are just one of the many
things he's still working on.
On Sat, Jan 25, 2020, 1:46 PM Ian Eure wrote:
> Hot damn. Does it work on a regular M100, or does it need DVI?
>
> On
This was a program written by a hobbyist in the 80's, right? Probably
developed on some 8-bit micro (the best kind!).
I think we can forgive this person for barely knowing how to write good
code. I'm guessing he was just thrilled to get it working and published.
On Sat, Jan 25, 2020 at 12:26 PM
Hot damn. Does it work on a regular M100, or does it need DVI?
On January 25, 2020 9:36:30 AM PST, Brian White wrote:
>It's the same parts except for the pcb.
>
>The new pcb makes it much easier and safer to program the xilinx. I
>suggest, it's worth the couple bucks and couple weeks to get the
What Brian said!
Also, like many things, context matters; perhaps those variables are used
elsewhere and they do need to be initialized. Even if not, 'habits' like
explicitly initializing variables are often considered and taught as 'good
programming practice'.
Personally I wouldn't write it
It's the same parts except for the pcb.
The new pcb makes it much easier and safer to program the xilinx. I
suggest, it's worth the couple bucks and couple weeks to get the new pcb.
Also, be advised Steve is getting close to releasing a new REX with the
incredible feature that it can let the
http://tandy.wiki/Building_a_REX
These are the "new" instructions that are based on a later revision of the
board and designed to use a 3d printed carrier. I've never built one of
these. The original instructions are linked to from this page.
I highly recommend a bevel tip and MG chemicals flux
Last year I resolved to build a REX expansion unit. I obtained the
necessary parts and had boards made but that's as far as I got due to
family issues. With the waters now settled I find that my documentation
for the project has been lost, probably due to a crash and upgrades to
Windows 10.
Sometimes another explanation for a seemingly no-op line is, given that
it's impossible for a human to avoid forming habits, doing things by
habit, one can choose consciously to adopt habits that will more-often
work. Like always initialize your variables, or always set them to the
most likely
I'm still studying the ROM to have a good information source for z88dk.
I think I'm close to get a common source which will assemble to a byte-exact
rom image of either the M100 and the KC85. The M10 is close to the Kyocera, so
it will follow soon.
I was able to edit the ROM and alter the M100
34 matches
Mail list logo
