Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!uwvax!uwmacc!hobbes!root From: root@hobbes.UUCP (John Plocher) Newsgroups: comp.unix.questions Subject: Microport shmcreate Message-ID: <115@hobbes.UUCP> Date: Sun, 10-May-87 07:33:16 EDT Article-I.D.: hobbes.115 Posted: Sun May 10 07:33:16 1987 Date-Received: Wed, 13-May-87 00:45:02 EDT References: <93@upas.UUCP> Reply-To: root@hobbes.UUCP (John Plocher) Followup-To: comp.unix.questions Distribution: world Organization: U of Wisconsin - Madison Spanish Department Lines: 43 This is a topic which has broad interest (there are lots of Microport users out there) so I am posting this instead of mailing. I'm glad to see that I'm not the only one having problems with this! +---- Robert White writes the following in article <93@upas.UUCP> ---- | | Greetings. I have a problem with the shmcreate facility of | Microport Unix 2.2 when attempting to use shared memory to access | the Hercules bit mapped graphics memory. | | extern char *shmat(); | shmid = shmget (0xb8000,32768,0); /* shmid is an int, large model */ Problem 1: shmid = shmget ((key_t)0xb8000,32768,0); ^^^^^^^ the key parameter is not an int, but a long | shmaddr = shmat (shmid, (char *) 0); /* shmaddr is a large model pntr */ Problem 2: shmaddr = shmat (shmid, (char *) 0, 0); ^^^ Bug in MicroPort manual, need a flag here to tell shmat to give read/write permission to this memory. | | However, in all cases, shmget returns -1 and errno gets set to | ENOENT. What am I doing wrong? | | Robert White, Graphics Information Inc. +---- Problem 3: The Microport SV/AT release 2.2 (and before) version of shmcreate is BROKEN. It doesn't attach the segment created to the proper physical memory location. I got bit by this last week... No work-around, call tech support and bug them about getting a fix to this program. -- John Plocher UUCP: !uwvax!uwmacc!hobbes!plocher ============== Internet: plocher%hobbes.UUCP@uwvax.WISC.EDU FidoNet: 121/0 BITNET: uwvax!uwmacc!hobbes!plocher@psuvax1