More on CED/GOMF
9 messages in this thread
I can shed some more light on the subject. Apparently, the low memory trashing
only occurs if you have CED in a 640×200 evironment. I run in a 640×400
interlace environment and have NO problems. I demoed the program at a local
user group on a system that runs GOMF3.0 with low memory checking enabled and
the problem came up. I also run GOMF3.0 with low memory checking and haven't
had a problem in the 640×400 mode. The minute I switch to 640×200 and open a
requester, the GOMF warning comes up.
Also, it was noticed that if you quit CED after the low vectors were trashed
and clicked on a disk icon, the system GURU's.
Hope this information helps. Many of the people who I showed CEDPro 2.0 to
said they'd either buy or upgrade once this is fixed.
As for me, I'm enjoying CEDPro 2.0!
Does this happen with ANY requester or just the file requester?
Thanks – this should help a great deal.
This may be unrelated, but I have seen memwatch catch low memory writes
on CED regularly when I open the file requeter in a low-memory situation.
Memory location $00000078 is be overwritten with $00089810. Similarly, the
next time I select an icon from workbench the system guru's. I'm using CED
Pro, along with GOMF (no low-memory checking), machii, interlaced WB, 1.3.2, to
be completely reproducable, i.e., it happens anytime I try to open the file
requester with little memory to spare.
“with little memory to spare.''
Noone said this before. This could be significant. How much is little?
When I do this on purpose I bring it down to less than 20k. I've never
had it happen to me on purpose in more than 50k. The times it has surprised me
I haven't been keepin track of just how much memory was free.
I still can't get this to occur. Exactly how can I get it to happen?
Also, again GOMF is present. Have you gotten memwatch to act when GOMF is NOT
running at all?
Nope. GOMF seems to be a major part of the problem. It seems that when
I haven't sufficient memory to open a file requester and try anyway, with GOMF
I get a lowmem stomp, without GOMF I get a clean failure.
(By the way, I brought this up on BIX, too, so your not suddenly being flooded
with a bunch of unrelated problems 😉
I just don't know about this GOMF interaction. I can open requesters all day
long in 640 by 200 mode and not see any changes taking place to low memory. I
do not have GOMF so am physically looking at memory using a debugger. Perhaps
it is a problem with GOMF? Dunno – but we'll keep looking.
pk