M102 ROM Locations:
'1' (change to a '2'): 5A53h - PRINT CHR$(PEEK(23123))
'9' (change to a '0'): 5A56h - PRINT CHR$(PEEK(23126))
Ken
On 11/29/18 1:45 PM, Kurt McCullum wrote:
Off the top of my head I don't know the exact locations of the two
bytes that need to be changed. On all of
Off the top of my head I don't know the exact locations of the two bytes
that need to be changed. On all of them, the 1 and 9 need to be changed
to 2 and 0. I've done it on my NEC and 200 models. The ROM images with
Virtual-T have all been patched. And virtual-T can disassemble any of
the ROMs for
Related; what are the bytes that need to be patched in the rom for the
102? I can't find the info online anywhere.
~~ related; is there a disassembly dump of the M102's rom?
On Wed, Nov 28, 2018 at 10:09 PM Scott Lawrence wrote:
> right, or 1900, but that wasn't the point of what i was
Is there a simple way in basic to just send everything that goes to
the display to a file as well?
That's probably similar to the NEC 8201a with the Japanese keyboard. The
layout is different on the one I have when compared to a US keyboard.
Unfortunately mine is a dead unit so I can't pull the rom code.
Kurt
On Thu, Nov 29, 2018, at 4:23 AM, Stephen Adolph wrote:
> yah, I'll post it when
All,
In the spirit of John's message about connections: I'm going to be in
Raleigh, NC on Monday evening. Any Model T-ers in that area interested
in grabbing dinner or hanging out? Extended area is okay, too - I
don't mind a bit of a drive.
-Josh
M10 keyboard supports 4x47 unique keys for symbols.. 188 max.
M100 keyboard supports 6x44 unique keys for symbols .. 224 of which are
assigned. 89 standard keys, 73 graph keys and 61 code keys
the mapping for M10 Graph keys to M100 Graph keys is something to think
through. I don't know how
based on that, perhaps it is better to modify T102 ROM to accept the M10
keyboard.
The keyboards are quite different, and there are 47 keys on M10 vs 44 on
T102 that are mapped to characters.
On Thu, Nov 29, 2018 at 5:30 AM VANDEN BOSSCHE JAN <
jan.vandenboss...@vivaqua.be> wrote:
> The M-10
thanks for that info!
On Thu, Nov 29, 2018 at 6:18 AM Georg Käter <
georg.kae...@gk-engineering-services.de> wrote:
> The KB map in M100/102 ROM starts @ 0x7BF1 in total 264 bytes and is
> organized in 6 blocks
> 44 byte each with the following order
> 1. key
> 2. SHIFT key
> 3. GRAPH key
> 4.
yah, I'll post it when done.
not there yet.
M10 is a complicated keyboard system. Plus there are reduced characters
relative to M100 - there is no CODE key.
So Graph and Shift-Graph have to be remapped.
I have to decide whats easier - to modify the T102 driver to work with the
M10 keyboard, or
The KB map in M100/102 ROM starts @ 0x7BF1 in total 264 bytes and is organized
in 6 blocks
44 byte each with the following order
1. key
2. SHIFT key
3. GRAPH key
4. GRAPH-SHIFT key
5. CODE key
6. CODE-SHIFT key
I?ve tried modifications to localize KB to German in VirtualT and it works. So
a ROM
The M-10 came with several localized keyboards: UK, FR and GE that worked
natively. When you wanted to have a FR keyboard on a Model 100, you had to
change the keys AND load an option ROM to activate it. (That's why I stuck with
QWERTY) The build-in driver of the M-10 in ROM might be what's
12 matches
Mail list logo
