More on CED/GOMF
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!