🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.amiga.tech
Article #9303

Re: Chip RAM

#9303
From: Lance Franklin
Date: Sat, 16 Jul 1988 05:28
37 lines
2453 bytes
In article <4270@cbmvax.UUCP> carolyn@cbmvax.UUCP (Carolyn Scheppner CATS) writes:
>So one other option would be to make some educated guesses about where
>some chip mem should be and use the TypeOfMem() function to check those
>addresses to see of they are CHIP ram.
This is the first time I've ever heard of the TypeOfMem() function, except
for a mention in a previous message.  I couldn't find it in the RKM or Sybex's
Amiga Proggers Manual, so I assumed it was some function in Lattice (I use
Manx) or some subroutine another programmer did.  I just now checked in the
Developer's Ref Guide and found it, evidently a part of the exec.library...
could you describe the function for me?  Or tell me where I can find a
description?
>
>Why do you need to know the highest CHIP address they have ????
>Wouldn't it be better to know how much CHIP ram they have FREE ??????
>
>That's easy - AvailMem(MEMF_CHIP)
>
I was looking to create a quick and easy function that would check a passed
address (and size) of a structure and pass me back the original address (if
the structure is already in CHIP ram, or allocate the space in CHIP ram, copy
the structure into it and pass me back its address, keeping track of the
CHIP ram allocated so I can free it at the program's exit.  TypeOfMem() sounds
like just what I need to test the structures present location.

> Oh I'm a numberjack and I'm OK, I code all night and I work all day...
I Code B-Trees, I wear a dress, suspenders and a bra...
On Wednesdays I go Shopping, buy cokes and more twinkies!


Lance


-- 
+------------------+ +------------------------------------------------------+
| Lance T Franklin | |  Now accepting suggestions for clever, humourous or  |
|    ltf@killer    | |  incredibly insightful .signature quote.  Send Now!  |
+------------------+ +------------------------------------------------------+
Technical Details
Message-ID: <4811@killer.UUCP>
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!convex!killer!ltf
References: <3150@polya.Stanford.EDU> <6428@well.UUCP> <2242@sugar.UUCP> <735@applix.UUCP> <11717@agate.BERKELEY.EDU> <2327@antique.UUCP> <737@applix.UUCP> <2333@antique.UUCP> <4790@killer.UUCP> <4266@cbmvax.UUCP> <4270@cbmvax.UUCP>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!convex!killer!ltf
From: ltf@killer.UUCP (Lance Franklin)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Chip RAM
Message-ID: <4811@killer.UUCP>
Date: 16 Jul 88 05:28:44 GMT
References: <3150@polya.Stanford.EDU> <6428@well.UUCP> <2242@sugar.UUCP> <735@applix.UUCP> <11717@agate.BERKELEY.EDU> <2327@antique.UUCP> <737@applix.UUCP> <2333@antique.UUCP> <4790@killer.UUCP> <4266@cbmvax.UUCP> <4270@cbmvax.UUCP>
Reply-To: ltf@killer.UUCP (Lance Franklin)
Organization: The Unix(R) Connection BBS, Dallas, Tx
Lines: 37