Is there anything that ordinary user can do about that, i.e. opening file manually and saving it? Is it possible with cookies?
Other nuisance is caching fonts every time i open Odyssey, is it due to the same issue as with cookies?
In that case I shall be using SFS2 instead
I already expressed my opinion in a private email.
EDIT: With reference to item 2 in your post: I used Snoopy to check what IO functions Odyssey is using. It's using unbuffered AmigaDOS 'Read' and 'Write' commands for cookies so I don't think there's any flushing to be done.
Radek wrote:Is there anything that ordinary user can do about that, i.e. opening file manually and saving it? Is it possible with cookies?
Other nuisance is caching fonts every time i open Odyssey, is it due to the same issue as with cookies?
broadblues wrote:Close the program down before rebooting.
tonyw wrote:Thanks to xenic's help, I can now confirm the behaviour. It is caused by the fact that NGFS "writes behind" its meta data. File data is written immediately, but meta data (eg the file header, containing the file size) is not updated until the next write or the file is closed.
tonyw wrote:No, the partition data is only written once, during Format, and it's the time/date of the Format. If some program shows the boot time, it's not coming from there.
xenic wrote:tonyw wrote:No, the partition data is only written once, during Format, and it's the time/date of the Format. If some program shows the boot time, it's not coming from there.
Not sure where daveyw got his date but on my system 'Ranger' shows the creation time/date for SFS2 partitions and the boot time for NGFilesystem partitions. Maybe Ranger just needs an update.
tonyw wrote:Yeah, so it does. Don't worry about the BZ, I'll find out why and fix it.
Return to Platform: AmigaOne X5000
Users browsing this forum: No registered users and 2 guests