| From: | Bill Eaves |
| Date: | 12 Mar 2001 at 12:43:49 |
| Subject: | Re: WarpOS requester. |
Hello Dave and all those who responded.
Maybe BPPCFix is the way to go. I was hoping there would be a simpler
solution like WarpOS getting on with its termination without putting up the
requester. Straight after boot up I won't be running any PowerUp software
so I'd be happy with it just to get on with the termination itself.
On 12-Mar-01, Dave Naylor wrote:
> 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.
I remember seeing that, it looked quite impressive but Ilike to hit the
switch and leave my Miggy to get on with loading without too much manual
interaction. That's why I want rid of the WarpOS requester ;-)
> When I boot into WarpOS I have this line right at the top of SS, even
> before setpatch:-
> BPPCFix install reboot >NIL:
Is it possible to have this *without* a reboot. I run Setpatch with its no
reboot option. The miggy takes long enough to start up these das without
having to have reboots :-(
> 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...
Goodness, you must have a lot of patience. I yearn for the days when you
switched on a computer and could start typing almost instantly.
> 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. :)
I tend to switch off items I am not using and that includes the Miggy so any
increase in boot time even when cold is a nuisance.
Also there are those times when a crash forces you to do a cold reboot which
gives a lengthy bootup every time :-(
> Further down the SS where the OS makes it assigns, I've added this:-
>> NIL: LIBS: SYS:LibsWARP ADD
> If I boot into PowerUP the there's no BPPCFix line, and the assign go
> elsewhere, I.e.
>> 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.
I can see the sense in that, it makes sense. Aren't the Powerup libs in the
Blizzard ROM though ?
> 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...
I have heard there were problems with TurboPrint's PPC support under WOS.
Does this newer version fix that too ?
Regards,
Bill.
Still wondering if this PPC stuff is all it was cracked up to be ;)
------------------------ 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/