| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
I need to access video memory/device driver for VMS on a VAXstation
3100 (the same for ULTRIX on VS3100 and DS3100 would be nice too)
directly and bypass DECwindows - is there any documentation or examples
of the interface like there was for the UIS Video Device Driver?
Mike
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1701.1 | FK::FRED | So sue me. | Mon Nov 13 1989 23:03 | 9 | |
You *are* kidding. Right?
There *is* no access to the hardware except for the server. The only
way to access the hardware is to shut down DECwindows, allocate the
device (like the server) and if it's a dragon... read the VCB02 manual
because *you* are going to have to do it *all*. About the only thing
that will be done for you is vsynch and queued input packets.
| |||||
| 1701.2 | DECWIN::FISHER | Burns Fisher 381-1466, ZKO3-4/W23 | Tue Nov 14 1989 17:44 | 12 | |
If you want to BYPASS DECwindows, that is not use it at all, you might be better off using UIS. There you get the DOP interface which will give you some help. If you use the DECwindows device drivers, you will have to do a lot more work. This is because there is a lot more code in the server and a lot less in the drivers than was the case with UIS. If you really mean that you want to send some direct hardware commands while DECwindows is still running, forget it. There is FAR too much interaction between the server and the hardware for this to work. Multi-thread access to the hardware doesn't work. Sorry. Burns | |||||
| 1701.3 | XUI::VANNOY | Jake VanNoy | Wed Nov 15 1989 14:01 | 12 | |
I'm surprised Burns didn't ask these questions, so I will... Why do you think you want to go around DECwindows? What are you trying to accomplish? Does whatever you're doing need to be integrated with DECwindows? Often times when people know WHY you want to do somthing, the answer is different than HOW you do something particular (or peculiar, as in the case of "going around" DECwindows). jake | |||||