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, [email protected] 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 <[email protected]>
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
<[email protected]
> <mailto:[email protected]>> 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 <[email protected]
> <mailto:[email protected]>> 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
> [email protected] <mailto:[email protected]>
> (619)940-6311
>
>
>
> On Thu, Jan 28, 2021 at 4:09 PM Tom Wilson
<[email protected]
> <mailto:[email protected]>> 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
> [email protected] <mailto:[email protected]>
> (619)940-6311
>
>
>
> On Thu, Jan 28, 2021 at 1:53 PM Jim Anderson
> <[email protected] <mailto:[email protected]>>
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 X<char>X 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
