Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!cbmvax!rutgers!tut.cis.ohio-state.edu!bloom-beacon!spdcc!lexicon!trh
From: trh@lexicon.UUCP (Tom Hegg)
Newsgroups: comp.sys.amiga.tech
Subject: Need help with ....
Message-ID: <298@lexicon.UUCP>
Date: 6 Sep 88 19:01:31 GMT
Article-I.D.: lexicon.298
Reply-To: trh@lexicon.uucp (Tom Hegg)
Organization: Lexicon Inc. Waltham, MA
Lines: 69


I have a bunch of questions that I (and some friends not on the net)
have accumulated, hopefully of a technical enough nature for the
c.a.tech group.  Please email responses to me if not of general
interest.  Sorry if its long, but I'm desparate.

OK, here goes:

1) Lattice 4.0.  I've seen some discussion on the net about the compiler
defaulting to a 16-bit addressing mode, which was apparently not the
case in 3.10.  The '-B' flag isn't accepted by LC, but the documentation
states that the flag '-b0' will turn off base-relative addressing and
use absolute 32-bit addressing.  In fact, using the -b0 option DOES
result in a bigger program segment (which is I guess what you would
expect), but now BLINK gives an error (I think number 512 or 502)
in reference to the symbol _IntuitionBase.  Can anybody clear this up?

2) The above comes up in reference to a program we are working on that
does a lot of calls to AllocRemember().  This program used to run when
compiled under 3.10, but now it crashes after the Nth call to
AllocRemember().  For some reason, after a number of calls, AR()
returns NULL (even though there is plenty of memory); looking up the
chain of Remember structures, it occurs usually right after
allocating memory at a suspiciously low address (0x1980 or so).
(I have 1 Meg of FAST RAM, all allocs don't specify a preference
for CHIP, and all previous allocs DID allocate from FAST RAM.)
The nature of the crash is that the program completes, but
no commands can be executed from the shell (always returns with
"Command Not Found").  Changing the stack size, using CLI
instead of the Dillon CSH has no effect.  (Oh, this was using
the default addressing mode in the compiler, coz' remember I
couldn't get the -b0 option to link).

3)  Another Lattice 4.0 question:  the old version of ATOM
doesn't seem to work with the new compiler - I ran one of
my files through and ATOM returned with a message saying
there was an unknown hunk type.  Sorry can't be more exact,
I'm at work, the Amiga is at home.  Can the compiler really
be generating newer hunk types than the Amiga Tech Ref Manual
describes?

4)  Would like to find out the names for file system devices
currently running ("DF0:", "DH0:", "VD0:", etc.).  This is for
a file requester that hopefully has some smarts and gives you
buttons for names of devices you actually have.  Is there
any way to get this information from the operating system?
(Or maybe a better way to ask this: how does the INFO command
work?  - could someone point me to some PD code?)

5)  There was some talk a few months back I think about a
midi.library thingy that someone had written.  I looked,
but couldn't find it on the Fish disks at the local computer
store.  Anybody know where I might find it, and is source available?

6)  I don't know if anybody can help with this last one, but:
I have a program that fairly regularly adds and deletes lots
of gadgets in a non-resizable SMARTREFRESH window.
After a while, flipping between windows (with the
window-to-back gadgets) produces a rather annoying "rippling"
effect (as I guess long lists of ClipRect's are repainted, I dunno).
This happens really slowly (takes about a full second),
SOMETHING must be wrong, because it happens when flipping
between two full-sized windows, there is no reason to split it
up into all these tiny ClipRects.  Huh?


-- 
Tom Hegg
{ihnp4,harvard,linus,ima,bbn,m2c}!spdcc!lexicon!trh