Since I asked the original question about CP/M emulation I thought I should
share what I had been using to prompt it:
This emulator has BDOS integration directly to the filesystem (no
getunix/putunix because it just sees the host directory):
https://github.com/jhallen/cpm
It seems to work
Exactly, altering the drive tables of the Linux emulator should enable
execution of an M100 CP/M image I would think. Conversely, massaging the
image to suit what the emulator expects might be the way to go. You'd
need to be conversant with "CP/M Alteration Guide" - it contains all
info
keeping my experiment rolling ;)
I just received the "high speed rated" NSC800, supporting 4MHz.
Now, I did successfully run the 2.5 MHz rated part at 5MHz, so I will be
interested to see if the 4MHz part is really any faster in the M100.
as usual, I will report back.
On Fri, Nov 6, 2020 at
G'day Philip,
Yep, I've read through that section several times in an attempt to
reconfigure the drive parameters on the Kaypro to support a larger disk
on the SD card reader. But that one is currently beyond me. :-)
That's why I was so happy when you built a 3.5Mb drive on REXCPM. And
I'll
with teraterm I had to specify 8 bit transfer. frustrating till i figured
that out!
On Thu, Nov 12, 2020 at 4:37 PM Desi Villaescusa wrote:
> I've also found the terminal software can make a difference for me...
> I wasn't haveing great luck with Putty or Teraterm at all... (First
> things I
I've also found the terminal software can make a difference for me...
I wasn't haveing great luck with Putty or Teraterm at all... (First things I tried with my Win10 laptop)
So I pulled out an old CD and copied Hyperterm to my Wn10 machine, and that worked great (as it used to when I used
Hello,
When I looked at this, I saw that it was based on the z80 code written by Parag
Patel that I had been using. It compiled for me without any issues, and uses
the same image structure (for the A-Hdrive) as the one I had been using, so it
could open the cpm disk images I had already
Windows 10. And btw, my desktop computer has an actual serial port, the 9
pin kind, so I'm not using any kind of DB9/25-to-USB device or anything.
On Thu, Nov 12, 2020 at 8:30 PM MikeS wrote:
> Just curious: Which version of Windows were you using for this?
>
> m
>
> - Original Message
Just curious: Which version of Windows were you using for this?
m
- Original Message -
From: Russell Flowers
To: m...@bitchin100.com
Sent: Wednesday, November 11, 2020 9:24 PM
Subject: Re: [M100] Simple communication, M100 -> com1: ... can download from
PC, but can't upload
> -Original Message-
> It was written ages ago by someone named Pareg Patel. I lost contact
> with him after a while but I recently found the source on github:
> [...]
> Just for a lark, I tried to compile just now and while it gave some
> errors, it did produce a useable binary (gcc
I wonder if you changed the drive geometry info in CP/M to match the M100
definition, if it would work?
On Thu, Nov 12, 2020 at 9:02 AM Jim Anderson wrote:
> (On a lark, I also tried taking my REXCPM backup file and dropping it in
> place of the emulator's A: virtual disk file but as I
> -Original Message-
> I wonder if you changed the drive geometry info in CP/M to match the
> M100 definition, if it would work?
Probably - the readme says A: and B: emulate the 'ST-506 5Mb 5" 5Mb drive' and
any other drives (C: and down) emulate 'traditional 8" 256k drives'.
I have no
Perhaps Philip can comment when he sees this.
The tool I wrote to do backups, isn't purely a binary dump of the disk
contents.
It could be, though.
What RXCUTL does (by memory here... ;) ) is there is a first byte providing
the block #, followed by 16k of block data. (or 32k, not sure now).
Hello,
That's interesting because my 'ancient code' compiles and even works with
putunix and getunix. But when I looked at what was on github and what I have,
there are differences. As you stated, if I took out the -DPOSIX_TTY from the
Makefile, the github source compiled for me, and I could
14 matches
Mail list logo
