Vincent Rivière, 25.01.2013 22:49:59:
Hello.I notice that when FreeMiNT is running, I can't rename C:\MINT to something else, because the C:\MINT\1-18-CUR\XAAES directory is locked.I suspect it is because of the XaAES log file. Is this the expected behaviour?
1. This file is opened, written to and closed again. It is unlikely the reason for a lock. It suffices that any active process has it's cwd there to inhibit renaming the parent-directory, which is likely the case. The bootlog can be removed at any time and will be written from 0. I have added in the debug-kernel an output that tells who is this process.
BTW, would it be possible to disable the creation of xa_boot.log? It is useless for normal users, and may slow down the boot process on real hardware. Of course, one could manually enable it if he has trouble.
Unnoticeable.I run XaAES from another directory which is on ext2, because I often had a corrupted drive C:, which I guess was because of the bootlog (not an XaAES-bug, but a FAT-fs-bug).
-- Helmut Karlowski