Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!julius.cs.uiuc.edu!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!ub!uhura.cc.rochester.edu!rochester!kodak!uupsi!sunic!liuida!micja
From: micja@IDA.LiU.SE (Michael Jansson)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: GOMF-req.library
Message-ID: <1991Jan10.131643.13987@ida.liu.se>
Date: 10 Jan 91 13:16:43 GMT
References: <4385@mindlink.UUCP>
Sender: news@ida.liu.se (News Subsystem)
Organization: CIS Dept, Univ of Linkoping, Sweden
Lines: 27

In article <4385@mindlink.UUCP> a447@mindlink.UUCP (Colin Fox) writes:
>Someone posted a message about GOMF saying that req.library's file requester
>trashes a low-memory-vector. THIS DOES NOT HAPPEN. It is a known problem with
>GOMF, not req.library.
>
>This point has been brought up before and explained before.
>
>As far as to what a low-memory vector is (the poster asked), all system
>vectors, such as exception and interrupt vectors, are stored in low memory. You
>naturally don't want these stomped.
>
>To reliably check low-memory violations, use Enforcer (you need an MMU to use
>Enforcer - either a 68020 + 68851 or a 68030). This has been done with
>req.library and it passes ok.

Well, I'm using the enforcer, CED, an older version of req.library (it
came with Manx 5.0a) and NOT GOMF and I get memory hits whenever I bring
up the file requster. I vote on that both GOMF and the older version of
req.library is not quite nice to the system.


--
##########################################################
#   Michael Jansson             |   \_/
#   Internet: mij@IDA.LIU.SE    |    V                   _|_
#   UUCP: uunet!liuida!mij      |    |    Absolut Software|
#   BITNET: mij@SELIUIDA        |   ~~~