|
Replies:
6
-
Pages:
1
-
Last Post:
11 Apr 23, 23:13
Last Post By: davidekholm
|
Threads:
[
Previous
|
Next
]
|
|
Posts:
31
Registered:
8-Dec-2019
|
|
|
|
Update 30.2 once again corrupted album creation
Posted:
5 Apr 23, 22:15
|
|
|
|
|
|
I just installed jAlbum 30.2 on Windows 11 after version 30.1 worked fine. Unfortunately, I am again experiencing inaccessible folders and files. Fix this as it gets very tiring.
|
|
|
Posts:
8,492
Registered:
31-Jan-2006
|
|
|
|
Re: Update 30.2 once again corrupted album creation
Posted:
5 Apr 23, 22:41
in response to: HPSmallegoor
|
|
|
|
This looks like a Windows file permission problem, having nothing to do with jAlbum.
Have you tried telling Windows to run jAlbum as "Administrator?"
|
|
|
Posts:
31
Registered:
8-Dec-2019
|
|
|
|
Re: Update 30.2 once again corrupted album creation
Posted:
6 Apr 23, 22:27
in response to: JeffTucker
|
|
|
|
Over the years I have installed many versions of jAlbum. Many versions don't change the behavior of (corrupt) album creation, but it happens every now and then. Version 30.1 was fine, but version 30.2 gave me the error again. All I did was generate an album in 30.1, run the 30.2 installer, and then it started complaining about lifeboat.zip again. So it is your installer who changes something. I'm a software guy myself and have installed hundreds of programs over the years and this never happens, just jAlbum. I love jAlbum and will continue to use it, but blaming the user for this is a bit unfriendly as I've only run your installer. Now I have figured out what the solution is myself, but it would be nice if you knew this too. I simply moved lifeboat.zip to another location and then the album generation works again by recreating another accessible file.
|
|
|
Posts:
8,492
Registered:
31-Jan-2006
|
|
|
|
Re: Update 30.2 once again corrupted album creation
Posted:
6 Apr 23, 23:25
in response to: HPSmallegoor
|
|
|
|
I'm not blaming the user. I was just suggesting a possible solution to a problem that is unfamiliar.
Glad you found a solution, but it's a strange one. I don't understand why simply moving the lifeboat file would cure an "access denied" problem. Perhaps David can shed some light on this. Album creation shouldn't be trying to read the lifeboat file - it should just delete it and generate a new one.
ETA: BTW, it's not "my installer." I am not an employee of jAlbum. I have no control over the application or its installer scripts.
|
|
|
Posts:
1
Registered:
14-Oct-2017
|
|
|
|
Re: Update 30.2 once again corrupted album creation
Posted:
7 Apr 23, 20:07
in response to: JeffTucker
|
|
|
|
I tried to run jAlbum as Administrator, I moved the project to another location on my computer. But always on creation an error comes up:
java.io.FileNotFoundException: {mypath}\album\res\android-chrome-192x192.png (Zugriff verweigert)
The file is there and there is no lock on it.
My OS is Windows 10 Professional.
Please fix this!
Edit: I've found a solution for me that works:
Move the res folder to another location.
Load project
Make album ->no errors
After that a new res folder has been created in place of the removed and it contains less files than the old one!
Edited by: abenus on 7 Apr 2023, 20:38
|
|
|
Posts:
8,492
Registered:
31-Jan-2006
|
|
|
|
Re: Update 30.2 once again corrupted album creation
Posted:
7 Apr 23, 21:00
in response to: abenus
|
|
|
|
I've seen those error messages in the console, but I've never been able to create a test case to reproduce it, which is what's needed to fix it. To be clear, this has never actually prevented album creation - in my case, it's always been a harmless console message.
Even easier than moving the res folder is simply to open the output directory and delete it. There's never any harm in that - album creation recreates the res folder, with all of the files that it needs.
|
|
|
Posts:
4,000
Registered:
18-Oct-2002
|
|
|
|
Re: Update 30.2 once again corrupted album creation
Posted:
11 Apr 23, 23:13
in response to: HPSmallegoor
|
|
|
|
The only possibly relating change we made to v30.2 was to update the software certificate to a higher grade. Can you install v30.1 alongside (to another target folder) and see if it behaves better? This should hopefully isolate whether it really is the v30.2 update that causes trouble (as opposed to changed requirements on recently installed software for instance)
|
|
|
|
Legend
|
|
Forum admins
|
|
Helpful Answer
|
|
Correct Answer
|
|
