Open xela92 opened 5 years ago
Hi, @xela92, I'm sorry to hear you're having trouble.
Can you confirm what version of the pISO OS you're running? I haven't been able to reproduce this problem. The log file doesn't indicate any issues, which is a bit odd. When you say the interface crashes, do you see the "An error occured" screen? If so, you should have gotten a 'piso_debug.tar' file that would contain more info.
I suspect the issue is somehow related to case (in)sensitivity on NTFS. The folder should be called 'ISOS' (all caps). Can you try that and see if it resolves the problem?
Hi, I'm using latest OS version, 1.3.0. no errors showing up, the interface just freezes. I will try your tip and tell you if it works!
@ALSchwalm renaming ISOs to ISOS as of your suggestion, I could see ISO files with NTFS, and that's great (naming the folder 'ISOs', the ISO files wouldn't show).
I did some other tests and got to a conclusion. It's not related to the ISOs folder, it's related to Windows.
at first, I noticed that when it freezed, after a while (a minute more or less), pISO started working again (and the umount was done), and the issue happened only when I forgot to do unmount in Windows before doing it on pISO (I had issues with unmount process in Windows that took ages, so I started doing umount only on pISO, so I was able to notice this issue). It's related only to NTFS, with vFat for instance if I don't unmount from Windows, the unmount process is done from pISO correctly with no slow downs.
Also, no issues at all with Linux or MacOS, even with NTFS.
I don't know if there's something to do on pISO side to make it faster, but always doing unmount from Windows is a good workaround to this issue (and, of course, a good habit!)
Thanks for the help!
Hi there,
I found out a bug. If I create an NTFS drive, create an ISOs folder on it, put some ISO file inside, mount it and try to umount it, the interface crashes and I need to unplug and replug pISO to make it work again.
Tried to rename the ISOs folder, and the issue is gone. Renaming it again in "ISOs" (or if the directory name just starts with "ISOs"!!), the issue appears again. I'm attaching piso.log captured while crashing.