Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: x56h34 on January 29, 2004, 06:37:43 AM
-
-
Check which version of Fblit you have!
(have you tested and older version?)
I run that also , but have found that certain other software (deleted) seems to dislike it...
I would try disabling all but one and `test` it to see how stable you system is...then add another, say WBCtrl, ....etc...
Good luck,
testing, testing, testing...
-
This is how I have my system setup:
Startup-sequence:
(Placed after Resident Assign REMOVE, and before C:LoadWB)
C:FBlit ;version 3.73
C:SystemPatch NOUTIL QUIET ;version 2.2
C:WBCtrl IMT=ICONFAST ;version 1.7
And then, my Prefs setting :
SYS:Prefs/Workbench...Images in Other Memory
I use SystemPatch instead of FText...FBlit is left at default settings (haven't used FBlitGUI to modify anything)
Hope that help...stability here is excellent...no lock-ups or crashes...
-
Make sure to run FText after FBlit. Run WBCTRL at the
end of your startup, right before the LOADWB line is
a good idea.
WBCTRL IMT=ICONFAST
and after that:
LoadWB SIMPLEGELS
Then go to your Workbench prefs in sys:prefs, and set
it up to store images in "fastram". That should speed
things up a bit, whilst not using much chipram for
on-screen icon display.
You may also want to try and run FBlit in "exclude"
mode...this will exclude from promotion only the tasks
which you specify in the FBlit prefs. That way you can
be sure that pretty much anything ran on your WB will
be promoted (IBrowse runs much better this way f.e).
--edit--
And as Rob72 pointed out, SystemPatch is a great
replacement for FText and BlazeWCP, among other
things.
-
Thanks for the replies guys. It seems that Rob72's suggestion about the placement of FBlit was a good idea. In my setup it was placed according to the guide, however once I've put all 3 after Resident Assign REMOVE, the system seems to run fine now. :-)
Seems like the best place to put it, at the end of the SS file, so that other stuff doesn't get corrupted.
Once again, thanks to all replies, and especially Che's...I mean Rob72's! ;-)