Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ogicse!orstcs!usenet!
From: daye@jacobs.cs.orst.edu (Garion)
Newsgroups: comp.sys.apple2
Subject: Hyper C: aux memory for anchored variables
Message-ID: <1991Jan15.052420.23406@usenet@scion.CS.ORST.EDU>
Date: 15 Jan 91 05:24:20 GMT
Sender: @usenet@scion.CS.ORST.EDU
Organization: Oregon State University, CS Dept.
Lines: 31
Nntp-Posting-Host: jacobs.cs.orst.edu

I really need to know the following:

	1. How does hyper c react when aux memory is freed (the ram
	   disk is disabled)?
	2. If I can free aux memory, can I store anchored variables
	   there?
	3. No one I've asked knows, but what does error 0x0a from the
	   hyper c assembler mean?  I got a brief reference to its
	   name from Andy, but I don't know what it means or what
	   to do about it.  I figure it probably is a memory overflow
	   or something, because I have a root segment of a program
	   I am working on that is about 10+K of nothing but variables.
	   I had to do this to make the variables available to all overlays
	   and so forth.

I guess it should be obvious that this aux memory is needed to store that
10K of variables so I can have room to actually run the program...a few
variables are 24x80 arrays, but I can probably eliminate at least on of
those.

Anyone have any ideas?  Maybe storing into a disk file for reference, but
I'm not experienced enough with C to do any kind of complex disk I/O stuff,
and I definitely get frustrated easily. 

Advanced thanks to all whom may reply to the e-mail address both at the
top *AND* the bottom of this article!
--
|  Internet-----           | 'I'll have to teach you a few of my spells.  I    |
|  daye@jacobs.cs.orst.edu |  have one..a fireball..let's see, how did that    |
|  daye@nyssa.cs.orst.edu  |  go..?' - If you don't know, you don't need to    |
         My opinions are my own.  I have opinions, therefore I am....