| From: | Dave Naylor |
| Date: | 12 Mar 2001 at 10:21:53 |
| Subject: | Re: WarpOS requester. |
Hiya Bill
On 11-Mar-01, you wrote about "[amigactive] WarpOS requester."
>BE However, now I have installed OS3.9 on a new partition and the requester
>BE comes up as soon as I boot. This is no doubt due to the new fat binary
>BE picture.datatype (which of course did not manifest this behaviour on my
>BE now defunct 060 machine). I obviously want to keep the PPC datatype
>BE which with WarpJPEG is amazingly quick. What I dont want is this damned
>BE requester everytime I boot up. I am sure the answer must be buried
>BE somewhere in the WarpOS docs but can someone please tell me ASAP how to
>BE disable this annoying requester. I don't need to be told I cannot run
>BE PowerPC stuff anymore, I know that already.
If you recall from alt.WoA I have a number of different startup-sequences
from which I can choose at boot up. My system defaults to WarpOS but once
every blue moon I can boot into a PowerUP enviroment. A thing called
BootMan manages the startups.
When I boot into WarpOS I have this line right at the top of SS, even before
setpatch:-
BPPCFix install reboot >NIL:
BPPCFix will reset your macine, once, after OS 3.9 has done it on cold
boots. So we are looking at booting properly at the third time of asking
after switching on, but if like me your machine stays on all day, it makes
no difference and allows me to put the kettle on in the morning. :)
Further down the SS where the OS makes it assigns, I've added this:-
Assign >NIL: LIBS: SYS:LibsWARP ADD
If I boot into PowerUP the there's no BPPCFix line, and the assign go
elsewhere, I.e.
Assign >NIL: LIBS: SYS:LibsPOWER ADD
So the libs for PowerUP and WarpUP live in their own lib dir and not the
main one, and therefore when I boot into either Warp or Power, neither can
see each others libs etc.
The lib for PowerUP stuff under WarpOS (ppclibemu --> ppc.library) obviously
lives in the WarpOS dir.
Incidentally. I found a new version of ppclibemu today, a new release.
This one includes an env var that allows Candy Factory Pro to run under
WarpOS. It would consistantly fail before and was one of the few programs
that absolutely needed me to boot into PowerUP. Seemingly no longer
thoough, although I did manage to get it to crash earlier, but I was being
quite vigourous whilst testing :)
Cheerio
O Dave Naylor [ All your base are belong to us ]
<|> [ This boy has broken down ]
|---| ICQ 16742766 [ http://www.chipsngravy.co.uk ]
------------------------ Yahoo! Groups Sponsor ---------------------~-~>
Make good on the promise you made at graduation to keep
in touch. Classmates.com has over 14 million registered
high school alumni--chances are you'll find your friends!
http://us.click.yahoo.com/l3joGB/DMUCAA/4ihDAA/d8AVlB/TM
---------------------------------------------------------------------_->
Quote carefully and read all ADMIN:README mails
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/