However, my vfs didn't get corrupt. After the access violation, the HFS gui still loaded but showed an empty vfs which is what I was expecting as the vfs didn't load completely. I then exited HFS normally and re-loaded HFS again without cancelling. My original vfs loaded without error.
Maybe this is related to the
Auto-save VFS on Exit -function. I have always had it Enabled.
Here's in what happens here in more detail:
- Auto-Save
Enabled, I hit
Enter or
Space (keyboard) during the automatic .vfs loading
=> Access violation
==> The .vfs file reduces from 62kB to 1kB
===> Empty list in HFS
- Auto-Save
Disabled, I hit
Enter or
Space (keyboard) during the automatic .vfs loading
=> The .vfs loads perfectly
==> Nothing missing from the list
- Auto-Save
Enabled or
Disabled, I click
Cancel (with mouse) during the automatic .vfs loading
=> The .vfs loads perfectly
==> Nothing missing from the list ...no matter how fast I try to click it
- Trying to load the 1kB (corrupted) vfs
=> Access violation
==> Empty list
I also get
random Access violations when loading working vfs files but those don't seem to affect anything...Some times it just gives Access violation, sometimes not...but always loads up the vfs perfectly. But still all this seems a bit trivial to me..I don't think I happen to press Enter during the load too many times...and if I do, I'll just load the backup vfs I have there waiting.
