From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,546b2e2a44f83809 X-Google-Attributes: gid103376,public From: jerry@jvdsys.nextjk.stuyts.nl (Jerry van Dijk) Subject: Re: Gnat For use at Question Date: 1996/07/11 Message-ID: #1/1 X-Deja-AN: 167939159 references: <4s2eb5$qt6@masala.cc.uh.edu> organization: JerryWare HQ, Haarlem, Holland newsgroups: comp.lang.ada Date: 1996-07-11T00:00:00+00:00 List-Id: Spasmo (cosc19z5@Bayou.UH.EDU) wrote: : Gnat305S for DOS ^^^ Note the DOS! : I'm trying to create an array at an absolute memory location Sounds reasonable, but: : Some_Array : String(1..4000); : for Some_Array use at 16#bbbbb#; apart from the syntax problems already mentioned by Bob, if this address is in conventional memory (< 1 Mb, say accessing the screen memory :-) it it not possible to address it this way, due to the way the djgpp protected mode system works. The way to do this safely is to use the djgpp far pointer package or any of the other two less safe methods outlined in the djgpp FAQ. If you are feeling really adventures *and* know for sure that your program will only be run with the CWSDPMI or other DMPI v1.0 provider, it is possible to do this using the dpmi_map_conventional_memory... functions. But, warning: the CWSDPMI dpmi_get_capabilities call is not always as reliable as it should be! If I guessed right but the above doesn't make sense, email me. Regards, Jerry. -- ----------------------------------------------------------------------- -- Jerry van Dijk -- e-mail: jerry@jvdsys.nextjk.stuyts.nl -- -- Banking Consultant -- Member Team-Ada -- -- Ordina Finance BV -- Located at Haarlem, The Netherlands --