#ADI Kit and newer High-C
4 messages in this thread
In my installation of metaware, in subdirectory \v1x, there are two batch
files: fixadi.bat and fixads.bat. I don't know why they wouldn't be in yours
as well.
As for your other questions, I don't believe I saw the beginning of this
thread, and so have little data about what is happening or what you are trying
to do. So tell me about the TERMINATE that doesn't show up, and about the EDIT
packet where you want a pointer to the video buffer.
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.
Gus: I've been following your thread and oticed that you are using a Bandit
box. How do you like it, and how do you have it configured?
Chris
P.S. I'm looking at getting one and I've wanted to talk to somebody that has
actually used one.
Okay, Gus; I understand now.
The PTERM packet should be working if you are using Studio 2.01, as far as I
know (haven't checked to be sure, though). There was a bug in 2.00 where that
packet wasn't being sent out, and it made certain kinds of drivers impossible,
as you are discovering. I'm getting confirmation as to whether or not this bug
was _really_ fixed.
As for getting a pointer to the video buffer, I'm still checking on this one,
but it appears that supplying a pointer to the buffer would be up to the video
driver, not up to studio. I also have doubts about using TEE to tap into
raster data. But as I say, I'm still checking.