Path: utzoo!attcan!uunet!husc6!cmcl2!nrl-cmf!ames!umd5!umbc3!alex From: alex@umbc3.UMD.EDU (Alex S. Crain) Newsgroups: comp.sys.att Subject: Re: UNIX PC Graphics Questions Summary: Graphics answers & keyboard questions Message-ID: <989@umbc3.UMD.EDU> Date: 17 May 88 09:51:55 GMT References: <2271@inco.UUCP> <267@uncle.UUCP> <700@naucse.UUCP> Reply-To: alex@umbc3.UMD.EDU (Alex S. Crain) Organization: University of Maryland, Baltimore County Lines: 30 In article <700@naucse.UUCP> rrr@naucse.UUCP (Bob Rose ) writes: >In article <267@uncle.UUCP>, jbm@uncle.UUCP (John B. Milton) writes: >> In article <2271@inco.UUCP> todd@inco.UUCP (Todd O'Connell) writes: >> > [Is there any way to directly access screen memory?] > >> The UNIXpc screen memory is located at $420000, and the only way to access >> that area of memory would be through a loadable driver. This kind of access >> would screw up the window manager's view of things. > >What about opening `/dev/mem' for reading and writing. >Note, I'm note responsible if you miss the screen and hit >the drive controller crashing your hard disk. It is easier to load a device driver that to do io to /dev/mem, and /dev/mem carries ALL of the dangers of device drivers. Be warned that playing with device drivers can do more damage than simply crashing the machine, a friend of mine thinks that he wrote over the partition table on his hard drive, ther wasn't enough left to be sure. If you want to play with this, PLEASE know what you are doing. On this train of thought though, Does anyone know how works the keyboard controller? and does the mouse do its work through the controller registers, or is that different? If one of the folks with a hardware manual could breifly explain it, I would be most appreciative. For those interesed in poking the video memory, look in -- :alex. nerwin!alex@umbc3.umd.edu alex@umbc3.umd.edu