Hi Jan,
For some reason, all emails from you (and a couple of others on the
list) end up in my SPAM folder.
Okay, trying to understand the "twisted" question. :) Could part of
... um .. TDock ... umm ... DVI ... umm ... what? :)
The TDock code REPLACES the DVI code and basically provides the same
function, so I don't think so. The DVI plugs into the System bus and
adds display hooks that write to specific ports on the 8085 I/O Port
interface. TDock hooks to the LPT port and adds display hooks that
encode the data and send it to the LPT I/O port.
To have a "screen-receptor" that diverts or "replicates" the output
going to a physically connected DVI, I believe you would have to fully
disassemble and patch the DVI "hooks" that run on the Model T.
If you are instead meaning could the TDock code be used to send screen
data to something that isn't TDock or DVI, but instead some other
generic screen-receptor, then YES. The TDock code has a bunch of hooks
but the lowest level function call is "Write this byte to the screen",
and it is an ASM routine that is only about 12 opcodes long. So you
could simply change that one routine and you would be displaying to
something other than TDock.
Ken
On 9/14/18 12:12 AM, Jan Vanden Bossche wrote:
Ken,
To come back to the question of the OP: could (part of?) the
technology/programming of TDOCK you already developed be used to
emulate the behaviour of the Model T when connected to a DVI, in
regard to screen output only? That way, we could build
"screen-receptors" of different types, that could interprete the
control codes and display the Model T display that would normally go
to the DVI.
(I know the above sounds twisted, I hope it's understandable)
Greetings from the TyRannoSaurus
Jan-80
------------------------------------------------------------------------
*From:* Ken Pettit <[email protected]>
*To:* [email protected]
*Sent:* Friday, 14 September 2018, 1:27
*Subject:* Re: [M100] DVI or modern equivalent
All,
Attached are three files TDOCK.CO file for M100/M102 and CCHART.DO /
CCHART.BA. The TDOCK.CO file is the binary output of the code I was
writing for the DVI replacement solution called TDock. VirtualT 1.7
emulates TDock.
Load this to the emulation and from BASIC exectute:
clear 256,62400
loadm"tdock.co"
This will load TDOCK to address 62400 in high RAM but will not install
the TDock / DVI "hooks". To install the hooks and thus activate TDock,
issue
call 62400,1
This will print the TDock copyright screen
Once the TDock hooks are installed, from BASIC you can get an 80 x 25
screen by issuing:
screen 1
width 80
Go back to the regular screen mode with "screen 0". Note that the 80x25
window is EXPERIMENTAL ... it has no options for resizing, the menu
items on the top are non-functional, and if you close it while you are
in active "screen 1" mode (i.e. the cursor is on the emulated DVI
screen), VirtualT WILL crash.
To "uninstall" the TDock hooks, issue
screen 0
call 62400,2
no notification given, but "screen 1" should no longe work.
The CCHART.BA / CCHART.DO files (one tokenizd BASIC, the other TEXT) are
an example application that draws a color chart on the emulated DVI
screen. You must first go into BASIC and issue the commands: "screen1"
and "width 80" before this BASIC program will work. Hit CTRL-C to exit
out.
Ken
On 9/13/18 3:05 PM, Greg Swallow wrote:
> How is it enabled/activated?
>
> God Bless,
>
> GregS <><
>
> ----- Original Message -----
> From: "Ken Pettit" <[email protected] <mailto:[email protected]>>
> To: [email protected] <mailto:[email protected]>
> Sent: Thursday, September 13, 2018 12:27:58 PM
> Subject: Re: [M100] DVI or modern equivalent
>
> VirtualT 1.7 supports DVI mode :)
>
> Ken
>
>
