As I understand things you need to put the c:morelibspace *before* setpatch. and append REBOOT - the caps are needed, I don't think reboot will work(?) - to it if you are running 3.1. Having said (typed?) that it don't work for me.
I have a number of patches running on my OS3.9 install, so I am guessing there is a conflict. At present all I know is that it fails to get as far as a boot picture I have, all I get is a black screen with the dick drives (DF0:) clicking away. If I take the boot picture out of startup sequence I get no further. I have the following patches;
fblit, ftext, BlazeWCP,WBAllocFast
Could someone who has this working please post their startup-sequence?
As I understand things you need to put the c:morelibspace *before* setpatch. and append REBOOT - the caps are needed, I don't think reboot will work(?) - to it if you are running 3.1. Having said (typed?) that it don't work for me.
I have a number of patches running on my OS3.9 install, so I am guessing there is a conflict. At present all I know is that it fails to get as far as a boot picture I have, all I get is a black screen with the dick drives (DF0:) clicking away. If I take the boot picture out of startup sequence I get no further. I have the following patches;
fblit, ftext, BlazeWCP,WBAllocFast
Could someone who has this working please post their startup-sequence?
Many thanks
J.
Hi,
I use a 3.9 and I almost don't have any patches (mcp) otherwise it is "clean". I disabled birdie, and VisualPrefs.
You see my floppy is also clicking... I mean the system start booting but than... just floppy is clicking. Black screen. When I cancel a c:morelibspace system start (even when I leave a Afa_os_loader?!)
Than I can start the Afa prefs.
I use a newest Mediator drivers... and Voodoo.
System is really "clean".
HELP.
BTW. "In the past" I used a Afa3.95 (3.96) I don't remember... I installed even png icons... ehh I will try "go back" and try again 3.9x. Soon.
The AfA_OS code itself increases the OS3.9 performance. The eye candy is an optional feature.
What exactly increases performance in AFA_OS? The TrueType fonts with or without antialiasing? The skins? The support for PNG icons? All of these DEcreases performance. Most importantly, even if you disable all the eye-candy, the AFA_OS task itself eats CPU cycles even when everything idles. Launch scout to see it by yourself. The only thing that increases performance afaik, is a single patch in the graphics.library which replaces IconBeFast and makes icon rendering faster. Of cource, PNG icons will still be slower. Correct me if i said something inaccurate.
What exactly increases performance in AFA_OS? The TrueType fonts with or without antialiasing? The skins? The support for PNG icons? All of these DEcreases performance.
Correct.
Quote:
Most importantly, even if you disable all the eye-candy, the AFA_OS task itself eats CPU cycles even when everything idles. Launch scout to see it by yourself.
I can't see any activity except the Scout itself and LimpidClock eating almost 10%.
Quote:
The only thing that increases performance afaik, is a single patch in the graphics.library which replaces IconBeFast and makes icon rendering faster.
Correct but besides that there are several optimized libraries in AfA_OS_Libs folder that replaces the original system functions. All I can say is that my system is more responsive with AfA_OS installed. Bernd, the author of AfA_OS, would give you more precise answer, though.