ADI Kit and newer High-C
05-Jun-93 02:57:33
Sb: #45372-ADI Kit and newer High-C
Fm: Gus Grubba 70673,1605
To: PhilD [ADESK] 71650,2154
Oops, sorry. I thought you knew what I was talking about. This thread is going
on for while between me and Nik and, I thought, he had given you the scoop…
First of all, I'm writing a couple of VTPADI drivers for a couple of different
machines. The first one was for the SONY laser disk recorder. I have written a
(dos) driver for the Bandit box and I would like, now, to port it to an ADI.
The problem with the TERMINATE packet is that I never get one. I placed a trap
at the entry point dumping all incoming packets out to the COM port and I never
saw the TERMINATE packet comming through. I need to have a couple of interrupt
handlers and I have to be notified when I'm out so I can return the interrupt
vectors to their rightful owners. The Out/In Shell work just fine (as just
about everything else).
The thing about the EDIT packet, the system (standard VTPADI) assumes the VTR,
or what have yoy, is "seeing" the image from the frame buffer. So it only sends
an edit command. In the case of the Bandit, I need to download the image buffer
through the SCSI port. I have to have access to the image buffer. It's just a
pointer and I'm sure is there somewhere as it is given to the display drivers.
As I said earlier, I could hack through TEE and grab the pointer from the
Rendering device but, what happens if the thing is being rendered to a NULL
device? Too messy.