| From: | Frank Wille |
| Date: | 25 Feb 2001 at 19:04:31 |
| Subject: | Re: Can use Yam again, but only with snoopdos... |
Jesper Wilhelmsson wrote:
> >> I read somewhere that loadlib was a more system friendly way of
> >> putting the correct version of ppc.library in memory than different
> >> patches etc.
> >
> > Better use PPCInstall. LoadLib will not increase the OpenCnt of the
> > library, so it might get removed from memory on the next memo- ry
> > flush.
>
> I found where I read it: In your README-file in the ppclibemu-package:
>
> "Please remove PPCInstall from your startup-sequence. You will get the
> same effect by using "loadlib path:ppc.library", but don't place the
> call before "C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ" !"
>
> Never read the readme's ;-)
I changed my mind. I always used LoadLib and had no problems. But
now I found a few ones where it's better to use a utility which
really opens the library, instead of only loading it into memory.
> So where do I find ppcinstall?
Part of PowerUp. Or take Sebastian Jedruszkiewicz's ppcInstall-
clone (I forgot the name). The next ppclibemu release will come
with an own utility, which is a bit more flexible.
I hate it to have to put ppc.library into LIBS: to be able to
use PPCInstall, so I never used it.
> My current status is: I have reinstalled MUI and removed all datatypes,
> no difference. After trying mostly everything I have came to the
> conclution that Yam (and the other programs) work if I:
>
> * Remove bppcfix from startup-sequence (which results in a milion
> 'Warning blah, blah, Terminate / Cancel'-messages where I press cancel)
> OR
Then you have original PowerUp running, and WarpOS tries to ter-
minate it! Ouch! ;)
This is definitely no solution!
> * Run snoopdos first... (what?!) The only thing that have to be
> monitored is the LoadSeg-calls (since it's one of them that goes
> wrong...) Once I have started Yam once, I can close it and SnoopDos and
> then run all programs without problems.
>
> So now my question is: What is Snoopdos doing that obviously heals all
> broken parts of the system?
I have no idea.
> I wonder if this may be related to that picture.datatype bug that
> existed once. What version of picture.datatype and ilbm.datatype are
> safe to use?
Check all your datatypes for PowerUp versions! Eliminate them all
and replace them with M68k or WOS-versions.
I'm using this picture datatype:
picture.datatype 44.19 (01.10.99)
Maybe you should avoid the OS3.9 one. I heard about some problems.