Incorrect Temp folder on PA 2009 Pro
-
can you please try with PA 2010 Beta 1 Preview? If you are Pro user, you should have gotten it in email.
thanks,
-
Checked with PA 2010 :(.
Same bug.
PA loading “TMP” variable on starting “POWERARC.EXE”. When I changed variable after starting PA, temp folder not changed.
The worst of it is that: PA 2009 checked destination, if it exist, by creating file with zero length on it. PA 2010 not check this :(. -
wait - so problem is that you changed destination after load of PA?
It works if you restart?
-
or do you mean that it doesnt save the change?
-
backup is now different from PA, so you have to exit PA for the settings to be saved.
-
So…
PA2010 installed over PA2009.
Before start PA 2010:
“TMP” from WinXP set to “%USERPROFILE%\Local Settings\Temp” by default.
“Temp Location” from PA 2009 set to “I:*”.
1. Start PA2010, Check “Temp Location”, same - “**I:*”. Close PA2010.
For ZIP.
2. Start PA2010. Click Backup>….pbs. Check settings , everything is OK. Click “Do Backup”.
3. Check temp file while PA working. Created in “TMP” location = “%USERPROFILE%\Local Settings\Temp**”.
4. Close PA 2010!!. Change “TMP” to “I:\temp”. Repeat step 2.
5. Check temp file while PA working. Created in NEW “TMP” location = “I:\temp”. !!
6. Close Backup window!!. PA not closed.
7. Change “TMP” to “D:\temp”. Click Backup>….pbs. Check settings, everything is OK. Click “Do Backup”.
8. Check temp file while PA working. Created in OLD “TMP” location = “I:\temp”. !!For 7ZIP – no temp file, checked.
-
So the problem is that in Backup “Temp” location is not used the same as defined in Configuration of main Pa WIndow (Options -> Configuation -> Folder)?
If this is your problem, it will be fixed in next release.
-
Yes!
I can’t change it.
Because on all my clients with WinXP, “C:” is formatted with FAT32 / it is easily fight with viruses /. And I can’t create backup:(. -
Ok. Sorry for inconvinience that caused to you. We always suggest not to use beta for work environment, but new beta will come really soon, and hopefully solve the issue.
-
please check with official beta 1, and let us know if this has been fixed… thank you!
