UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
Hi.
Either using 1.075 and 1.076beta3 version, with multi session processing, when i proceed to integration tab, this error occurs.
Any help or solution, please?
Thanks
Andrea
I think it means your working directory is in a place which is read-only, so APP is unable to use it for processing. Could you try by changing the working directory to a place where you're sure you can read and write files?
@vincent-mod
Since i started evaluating APP trial i set that directory as default; where every astro .fits files are saved (it's a dedicated SSD HDD partition) and no problem at all: APP opens and saves always every files in that directory. But this happens only when i use a single sequence of frames, single session. When i want to process a multi session frames, until normalize tool everything works fine: when i click integrate it happens as shown in the attached screenshots.
I changed the directory, as vincent suggested, and everything worked flawlessy as usual: it's another SDD HDD partition.
So i wonder: why the usual directory works for a single session process? And APP doesn't like that usual directory for a multi session process? The 2 SDD HDD partitions are both in NTFS and created by the same program (Aomei Partition)..
Thanks Vincent for your help: now, anyway, i'm able to do multi session processing
Last edit/ Update: even if i'm the unique pc administrator, every time i wanted to move or copy a file into that partition it asked me a popup with "administrator permissions must be provided...": i had to give every permissions to everyone. After that, i'm able to move/copy/write files into that partition....And eventually, obviously APP now works...
Hi @ippiu & @vincent-mod,
The problem here is that the partition is not permanently mounted by the OS. If you configure the mount points to be permanently mounted, then all should work okay.
So once you start processing, the partition will be mounted and all seems to work okay. But when APP arrives at the integration stage, the Operating System no longer had a valid mountpoint. That is what the warning is about 😉
Kind regards,
Mabula
