In a message of 01-Nov-99 Sealey, M. wrote:
>> Following the last instruction in the installation script, it even
>> says to do a flush avail.
> Which is in NO WAY guaranteed to work. There is no written word
> ANYWHERE that says an Avail Flush command will flush *ALL* libraries
> from memory.
Well, according to the AmigaDOS Manual, then an "Avail flush" will indeed
"cause all unused libraries and devices to be expunged from memory".
So, if you know what you are doing it should be sufficient.
>> If you have no other programs...read vapor programs, running at that
>> point avail flush should flush ALL unused libraries. ( so even if
>> you just used the last version of voyager, and the library was still
>> in memory, it should be flushed.
> Not always possible, if a library needs to hold a resource (maybe if
> it's patched a library, or is waiting on data from an external app)
> then it can 'refuse' to be expunged.
If this is the case you can hardly call it "unused", and therefore they
naturally can't be expunged. Martin is fully correct, that an "Avail flush"
ought to expunge all unused libraries and device. On the other hand I
think his bashing of Chris was a bit inappropriate, because as you say then
you can't always be 100% certain a library is unused and will be expunged,
so a reboot is definitely the next step if a flush of unused libraries
didn't solve such a library problem.
> It's ***OBVIOUS*** that you should reboot. It's the ****ONLY**** way
> to ensure that all libraries are flushed from memory.
Yes, but very often not necessary if you know what you are doing.
As I said above, if you know what you are doing, then a simple flush of
unused libraries will most often be more than sufficient - I very rarely
reboot when installing new versions of applications. But you need to know
what you are working with and which libraries to flush. The natural steps
would be 1) close old Voyager and flush; 2) if new Voyager still doesn't
work, then close all Vapor applications and flush; 3) if new Voyager still
doesn't work, then close all MUI applications and flush; and 4) if new
Voyager still doesn't work, then reboot. If this still doesn't solve the
problem, then it is perhaps time to start complaining on the mailing list,
but certainly not before.
Uffe Holst
____________________________________________________________
Voyager Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
