-
Configuration:
Powerarchiver 2021 20.00.73
Windows 10 Education 10.0.19042 Build 19042When extracting gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz , Powerarchiver wrongly thinks some .exe files have a length of zero:
98773b3b-65c0-48fa-8cd4-d081b2e0adee-image.png
Once extracted:
D:\Temp\Powerarchiver\gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf\bin>dir *.exe Volume in drive D is DATA Volume Serial Number is 0E12-BCA2 Directory of D:\Temp\Powerarchiver\gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf\bin 2020-11-20 07:10 PM 1,391,599 arm-none-linux-gnueabihf-addr2line.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ar.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-as.exe 2020-11-20 07:41 PM 3,030,119 arm-none-linux-gnueabihf-c++.exe 2020-11-20 07:10 PM 1,389,293 arm-none-linux-gnueabihf-c++filt.exe 2020-11-20 07:41 PM 3,027,513 arm-none-linux-gnueabihf-cpp.exe 2020-11-20 07:10 PM 4,040,503 arm-none-linux-gnueabihf-dwp.exe 2020-11-20 07:10 PM 391,769 arm-none-linux-gnueabihf-elfedit.exe 2020-11-20 07:41 PM 0 arm-none-linux-gnueabihf-g++.exe 2020-11-20 07:41 PM 3,026,926 arm-none-linux-gnueabihf-gcc-10.2.1.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-ar.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-nm.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-ranlib.exe 2020-11-20 07:41 PM 0 arm-none-linux-gnueabihf-gcc.exe 2020-11-20 07:41 PM 2,165,533 arm-none-linux-gnueabihf-gcov-dump.exe 2020-11-20 07:41 PM 2,343,605 arm-none-linux-gnueabihf-gcov-tool.exe 2020-11-20 07:41 PM 2,450,233 arm-none-linux-gnueabihf-gcov.exe 2020-11-20 07:54 PM 9,605,899 arm-none-linux-gnueabihf-gdb.exe 2020-11-20 07:41 PM 3,028,997 arm-none-linux-gnueabihf-gfortran.exe 2020-11-20 07:10 PM 1,412,943 arm-none-linux-gnueabihf-gprof.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.bfd.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.gold.exe 2020-11-20 07:41 PM 25,546,567 arm-none-linux-gnueabihf-lto-dump.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-nm.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-objcopy.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-objdump.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ranlib.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-readelf.exe 2020-11-20 07:10 PM 1,393,083 arm-none-linux-gnueabihf-size.exe 2020-11-20 07:10 PM 1,392,464 arm-none-linux-gnueabihf-strings.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-strip.exe 32 File(s) 67,465,867 bytes 0 Dir(s) 1,002,422,431,744 bytes freeWhen the same archive is being extracted from a git bash session (after having installed git 2.30.1 for Windows 64 bit version from git-scm.com), the .exe files are extracted as expected:
xz -k -d gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz tar xf gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar cd gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf/bin ll *.exe -rwxr-xr-x 1 User 197121 1391599 Nov 20 19:10 arm-none-linux-gnueabihf-addr2line.exe* -rwxr-xr-x 2 User 197121 1421598 Nov 20 19:10 arm-none-linux-gnueabihf-ar.exe* -rwxr-xr-x 2 User 197121 2028927 Nov 20 19:10 arm-none-linux-gnueabihf-as.exe* -rwxr-xr-x 2 User 197121 3030119 Nov 20 19:41 arm-none-linux-gnueabihf-c++.exe* -rwxr-xr-x 1 User 197121 1389293 Nov 20 19:10 arm-none-linux-gnueabihf-c++filt.exe* -rwxr-xr-x 1 User 197121 3027513 Nov 20 19:41 arm-none-linux-gnueabihf-cpp.exe* -rwxr-xr-x 1 User 197121 4040503 Nov 20 19:10 arm-none-linux-gnueabihf-dwp.exe* -rwxr-xr-x 1 User 197121 391769 Nov 20 19:10 arm-none-linux-gnueabihf-elfedit.exe* -rwxr-xr-x 2 User 197121 3030119 Nov 20 19:41 arm-none-linux-gnueabihf-g++.exe* -rwxr-xr-x 2 User 197121 3026926 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-10.2.1.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-ar.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-nm.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-ranlib.exe* -rwxr-xr-x 2 User 197121 3026926 Nov 20 19:41 arm-none-linux-gnueabihf-gcc.exe* -rwxr-xr-x 1 User 197121 2165533 Nov 20 19:41 arm-none-linux-gnueabihf-gcov-dump.exe* -rwxr-xr-x 1 User 197121 2343605 Nov 20 19:41 arm-none-linux-gnueabihf-gcov-tool.exe* -rwxr-xr-x 1 User 197121 2450233 Nov 20 19:41 arm-none-linux-gnueabihf-gcov.exe* -rwxr-xr-x 1 User 197121 9605899 Nov 20 19:54 arm-none-linux-gnueabihf-gdb.exe* -rwxr-xr-x 1 User 197121 3028997 Nov 20 19:41 arm-none-linux-gnueabihf-gfortran.exe* -rwxr-xr-x 1 User 197121 1412943 Nov 20 19:10 arm-none-linux-gnueabihf-gprof.exe* -rwxr-xr-x 4 User 197121 2572182 Nov 20 19:10 arm-none-linux-gnueabihf-ld.bfd.exe* -rwxr-xr-x 4 User 197121 2572182 Nov 20 19:10 arm-none-linux-gnueabihf-ld.exe* -rwxr-xr-x 2 User 197121 4550029 Nov 20 19:10 arm-none-linux-gnueabihf-ld.gold.exe* -rwxr-xr-x 1 User 197121 25546567 Nov 20 19:41 arm-none-linux-gnueabihf-lto-dump.exe* -rwxr-xr-x 2 User 197121 1404945 Nov 20 19:10 arm-none-linux-gnueabihf-nm.exe* -rwxr-xr-x 2 User 197121 1531656 Nov 20 19:10 arm-none-linux-gnueabihf-objcopy.exe* -rwxr-xr-x 2 User 197121 1991350 Nov 20 19:10 arm-none-linux-gnueabihf-objdump.exe* -rwxr-xr-x 2 User 197121 1421598 Nov 20 19:10 arm-none-linux-gnueabihf-ranlib.exe* -rwxr-xr-x 2 User 197121 1163376 Nov 20 19:10 arm-none-linux-gnueabihf-readelf.exe* -rwxr-xr-x 1 User 197121 1393083 Nov 20 19:10 arm-none-linux-gnueabihf-size.exe* -rwxr-xr-x 1 User 197121 1392464 Nov 20 19:10 arm-none-linux-gnueabihf-strings.exe* -rwxr-xr-x 2 User 197121 1531656 Nov 20 19:10 arm-none-linux-gnueabihf-strip.exe*The same archive file does extract properly under a native Linux Ubuntu 20.04 system, or under Windows 10 using the WSL2 Linux subsystem using xz and tar.
-
Hi I recently bought PowerArchiver and found some bugs and issues that I hit testing some of the features out.
If you are doing a backup and on the compression options screen its default is compression format is PA with no option to change disk spanning. If you change to 7-zip you can change disk spanning. If you change the disk spanning then move back to PA format the field for disk spanning disables but the option stays set to what you changed it to. When you do a backup it will use PA with files spanning but PowerArchiver says that its not a valid format when you open it. If PA can’t really do file spanning then this screen is allowing it.
I have attached an image where the progress bar is in the middle of the CD/DVD/BD Tools screen.
alt text
I have a 7-Zip file I created using the backup tools doing an increment backup. It opens and extracts just fine but if you using the Test option PowerArchiver locks up. Link to file: Backup-2021-02-05-20-35-36 TEST LOCKUP.7z
On any Zip/PA/7-Zip process the pause and cancel buttons do not work. You have to hard kill the entire application to get out.
-
There would be many of us with Intel Processors.
and they have their own optimized zlib algorithm, which can result in more efficiency if used combined with their hardware processor.
Reference:
https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/zlib-compression-whitepaper-copy.pdfCan we get the same Functionality Under Hardware Acceleration Feature?
Zlib is not the only feature that intel has included with their processor, there’s many, which if combined can result in efficient and better compression ratios.
-
Hi,
After the batch archiving is complete, and if I click on whitespace of the PA app, I get this error.
PA Batch.png
I did check for ongoing process and ensured no archives were corrupt, It seems like activity did complete successfully but the error is shown for no reason, and only after clicking the whitespace.
Please see if this can be removed.
-
I’m using the Kaspersky Total Security.
I have configured PA as exclusion as followed:
PA Exclusion.png
and also is set us trusted application
PA Trusted Application.png
Scenario:
My Antivirus likes to scan for everything, and it’s safeguarding behavior is to prevent the access to the file until the file is properly scanned for.
The issue:
PA when losses the access to file, it is stuck, consumes Resources, and never completes the process or throws any error
Recommendation:
PAStarter should also work as PAMonitor:
There should be a monitoring process, at least if I’m using queuing feature, that should check for never ending compression processes and terminate them so the queue can be little bit automated.Also,
There should be multiple attempts at retrying if PA loses access to or is denied, instead of having to see process was stuck for longer duration.Or, better, save the parameters I used for keeping the files in compression, and automatically restart the whole compression process after termination the same, of same folders and files set, this should happen in case if compression was stuck.
-
If you use Queue Feature, you are not saving on space, you are just squeezing less.
Here’s explaination:
https://youtu.be/XcxG2wxyink
I did test the same on multiple files, and of different types.
It does have large difference for each large file you are trying to squeeze.
Folders with multiple files, just have no benefits if you use Queue Feature
-
Hello!
I am using the portable version of PA2021. After switching from build 58 to 73 I have problems with the color-scheme:
While 58 behaves like expected and showed everything in light or dark colors according to the settings, 73 always shows the lower part of the window in dark colors, no matter whether I select automatic, light or dark.
This happens on a clean installation of 73 as well as on an update from build 58. I have attached two images generated on the same machine at the same time with the same settings. The upper shows build 73, the lower 58. Is it a bug or some changed setting I miss?
Thanks for help!
A.BorquePA2021_73.png PA2021_58.png
-
Hello,
PowerArchiver Command Line 7 support file greater than 2 Go ?
Thanks
-
If you have tabbed archive browsing(reuse same window for all archive opening)
and if you open two archives, and right click on older one to view properties it will only show of the recent archive that was opened, on all tabs/archivesupgraded to 20.0.73
-
Hi.
I currently own the PowerArchiver Select - lifetime free upgrades and support for PowerArchiver Toolbox English license.
This license is active on 1 device. Does the license allow me to activate PowerArchiver on a second device that I own? Or do I need a separate license for that?
Thank you ! :)
-
Hello!
While the installable version of PA 2021 has already received two updates and is at version 20.0.73 the portable version still remains at the initially released build 58. Are there plans to update that version, too?
Thanks for a reply! -
I’ve been dealing with an intermittent explorer.exe crash for 5-6 years now. It happens randomly and will usually occur multiple times within a single session of an hour or two on my machine when manipulating files through Windows Explorer. explorer.exe is the only thing that ever crashes, so it’s not hardware IMO. I’ve done all hardware diagnostics and RAM is good. I’ve even swapped out motherboards with different brand and even the exact same one and it still crashes. sfc /scannow indicates system files are fine. I’ve done multiple reinstalls of the OS with no positive results. This crashing has happened on Windows 7 64-bit and Windows 10 64-bit. It seemed to get more frequent with Windows 10 after upgrading last year. I’ve also been using PowerArchiver throughout that time period (upgrading over time with new releases). I recently disabled all non-Microsoft extensions via ShellExView and saw no crashes for about 10 days, which is really unusual. I turned back them all back on after 10 days and saw another explorer.exe crash within the hour. So I disabled all 32-bit extensions and saw another crash. Following that I disabled all the PowerArchiver shell extensions and haven’t seen a crash after a day of heavy usage manipulating files within Windows Explorer, which doesn’t happen for me. The crash dumps I’ve captured don’t seem to indicate PowerArchiver is involved but I have a hunch it has something do with PowerArchiver shell extensions. The system even feels smoother with the PA extensions disabled. Windows 10 reliability monitor always has the same type of problem:
Description Faulting Application Path: C:\WINDOWS\explorer.exe Problem signature Problem Event Name: BEX64 Application Name: explorer.exe Application Version: 10.0.17134.165 Application Timestamp: 4031a9f8 Fault Module Name: StackHash_e78e Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: PCH_8D_FROM_ntdll+0x000000000009AA54 Exception Code: c0000005 Exception Data: 0000000000000008 OS Version: 10.0.17134.2.0.0.256.48 Locale ID: 1033 Additional Information 1: e78e Additional Information 2: e78e327659b46c9a0c6916396b253cbf Additional Information 3: cebf Additional Information 4: cebf952c5db535ae7880488aafce55d9 Extra information about the problem Bucket ID: 1a57e4e784fbc735c231c68bd88581a9 (1311047270476906921)I know this is a very nebulous explanation but is there any way to link this up to PA shell extensions as the cause? I can provide the crash dumps and additional information if necessary.
-
When you select “Deflate (.zip, compatible)” as the method, it still converts the archive to a ZIPX format.
-
Would like to see uha archives supported compression as well as extraction. I use this all the time and it is a very good compression format
-
In windows 10 you can right-click and select send to and the compressed zipped folder and the zip folder will contain the name of the last selected file.
Does PowerArchiver have a similar function?
Tom
-
Converting an archive to .zip (using both the “Deflate (.zip, compatible)” and “Store” compression methods) always creates a .zipx file instead.
pa-convert-zip-1.jpg
pa-convert-zip-2.jpgUsing the “Store” method sometimes creates a .zip file; I have seen it happen just now, but I cannot reproduce it.
-
patchbeam a waste of time never updated with latest version
-
I have just installed 2021, but seems to have similar issues to 2019. If you move the app between differen monitors (with different resolutions) the app does not automatically adjust accordingly, so on one monitor I have the app is too big for the screen, whereas on another monitor it only takes up a small fraction of the screen.
This was worse with 2019, where the fonts were totally screwed up, making the app unusable. This seems better in 2021, but still not working properly. -
Hi! I came across an issue when I tried to uninstall PowerArch 2013. I got an error “The specified account already exists” which broke the process. I got the same error when I tried to install the current version, without uninstalling the previous one.
So I can’t uninstall and I can’t install PowerArchiver. Any suggestions? OS Windows 8.1 x64.Dariusz
-
Good morning,
I have been using all compression programs for over 20 years, I have always found Winrar very easy to use when I create a self-extracting archive, even 7-zip is simple, “right click” and “create self-extracting archive”, because on powerarchiver it must be like this confused ?
It doesn’t just create the archive, it opens a page where I have to select the file again, what kind of archive, which folder to create it, etc … you should learn from your competitors how to make life easier!
External cd/dvd drive not working properly with PA Burner
-
I can confirm a freezing issue with PA’s internal burner. I tried it last night…with no data on the disc. I selected just 2 mg of data for burning…and proceeded with burning onto DVD. It stops at 93% and my disk drive light continually flashes. I had to manually stop the PABurnTools process in TaskManager. Then to get my DVD rom drive back…I had to disable the power supply.
I’m thankful it was an external DVD drive that I used instead of the internal one - as otherwise I would have been forced to reboot the computer just to get the DVD out of the drive.
So as of right now…and today is August 11th, 2009 - I see no official response on the problem. We need an update on the DVD burning issue otherwise this feature is non existent now…at least for me. I have to go back to XPCD Burner for now.
-
I can confirm a freezing issue with PA’s internal burner. I tried it last night…with no data on the disc. I selected just 2 mg of data for burning…and proceeded with burning onto DVD. It stops at 93% and my disk drive light continually flashes. I had to manually stop the PABurnTools process in TaskManager. Then to get my DVD rom drive back…I had to disable the power supply.
I’m thankful it was an external DVD drive that I used instead of the internal one - as otherwise I would have been forced to reboot the computer just to get the DVD out of the drive.
So as of right now…and today is August 11th, 2009 - I see no official response on the problem. We need an update on the DVD burning issue otherwise this feature is non existent now…at least for me. I have to go back to XPCD Burner for now.
there will be an update to the burner, but it doesnt not guarantee that your specific issue will be fixed, as it is probably specific to the drive you used.
Can you please try using your internal drive and see if it works.
-
you should also open an ticket with suppor at conexware dot com. That way we can get more specific info if/when needed.
thanks
-
there will be an update to the burner, but it doesnt not guarantee that your specific issue will be fixed, as it is probably specific to the drive you used.
Can you please try using your internal drive and see if it works.
I’m not going to do this because if the freezing issue can be duplicated on my internal drive…I won’t be able to get the disc out if the lights flash like they did with the external drive. I’d be forced to literally reboot the computer.
As there appears to be an update coming to “fix” this issue…I’ll wait for that before deciding on what to do. In the meantime…I’ll stick to USB flash drives.
-
I’m not going to do this because if the freezing issue can be duplicated on my internal drive…I won’t be able to get the disc out if the lights flash like they did with the external drive. I’d be forced to literally reboot the computer.
As there appears to be an update coming to “fix” this issue…I’ll wait for that before deciding on what to do. In the meantime…I’ll stick to USB flash drives.
as i said, it is generic update, i doubt it will fix your specific problem. Every cd/dvd drive has little hole near the loading tray into which you can insert an clip to manually eject the drive.
-
as i said, it is generic update, i doubt it will fix your specific problem. Every cd/dvd drive has little hole near the loading tray into which you can insert an clip to manually eject the drive.
Not if the drive lights are flashing…I think.
Edit: just a thought…is there consensus that it could be antivirus programs causing the freezing issues? I’ve been hearing about antivirus problems…and I’m wondering if the freezing could be a result of the antivirus software blocking the burning process on PABurnTools?
-
Not if the drive lights are flashing…I think.
Edit: just a thought…is there consensus that it could be antivirus programs causing the freezing issues? I’ve been hearing about antivirus problems…and I’m wondering if the freezing could be a result of the antivirus software blocking the burning process on PABurnTools?
nobody knows until you test it out :). AV’s could cause all kinds of troubles.
Poke that little hole with a clip and it will eject the drive always, its fully manual control (made so it works if your drive breaks or you are out of power)…
-
You mentioned the coming update will be generic. Is it customary to only say updates are generic…or can you issue change logs to alert users what has been fixed, etc?
-
You mentioned the coming update will be generic. Is it customary to only say updates are generic…or can you issue change logs to alert users what has been fixed, etc?
we wont know if your issue is fixed if you dont want to test it, it would be impossible to do without your cooperation.
-
I have more information and this part is interesting so listen carefully. I was able to “try” burning using my external DVD rom drive previously. It froze PA2010.
Now…I just tried to duplicate what happened before…but now PA2010 doesn’t even see my external DVD rom drive anymore. Instead…it only “sees” my internal one.
Just to be sure I wasn’t having a “hardware not found” issue in Windows XP…I did a search to see what was recognized on my system. Windows XP correctly lists my external DVD rom drive as visible. But PowerArchiver 2010 could no longer see it. So…just to be sure…I fired up my opensource CD burning software and did a check using that program.
I did a quick test burn on it and it was quickly able to see and read the same 2 mg of files I wanted for a test burn on a CD-RW disc. Took less than 30 seconds. It read it fine.
So…it appears to be a problem with Power Archiver 2010 not being able to read external CD/DVD rom drives plugged into USB ports. This is as far as I can go to narrowing down the problem currently with PowerArchiver 2010 on my system with the burning freezing issue.
Edit: more information -
1. PowerArchiver is “seeing” external DVD drive correctly in list view. But when I open the burner dialog box to select files for inclusion for a burning session…it’s only seeing the internal DVD rom drive in the drop down list. Another thing…when I put a CD/DVD into my external drive…the list view changes from seeing a DVD RAM drive…to a CD rom drive?! When I selected the CD ROM drive…it froze PowerArchiver and I had to do the three finger salute to regain control of my system.
Conclusion: this is definitely a Power Archiver 2010 issue. If my opensource software can read and burn files correctly while Power Archiver 2010 can’t even see my drive correctly then something is wrong.
-
I have more information and this part is interesting so listen carefully. I was able to “try” burning using my external DVD rom drive previously. It froze PA2010.
Now…I just tried to duplicate what happened before…but now PA2010 doesn’t even see my external DVD rom drive anymore. Instead…it only “sees” my internal one.
Just to be sure I wasn’t having a “hardware not found” issue in Windows XP…I did a search to see what was recognized on my system. Windows XP correctly lists my external DVD rom drive as visible. But PowerArchiver 2010 could no longer see it. So…just to be sure…I fired up my opensource CD burning software and did a check using that program.
I did a quick test burn on it and it was quickly able to see and read the same 2 mg of files I wanted for a test burn on a CD-RW disc. Took less than 30 seconds. It read it fine.
So…it appears to be a problem with Power Archiver 2010 not being able to read external CD/DVD rom drives plugged into USB ports. This is as far as I can go to narrowing down the problem currently with PowerArchiver 2010 on my system with the burning freezing issue.
Edit: more information -
1. PowerArchiver is “seeing” external DVD drive correctly in list view. But when I open the burner dialog box to select files for inclusion for a burning session…it’s only seeing the internal DVD rom drive in the drop down list. Another thing…when I put a CD/DVD into my external drive…the list view changes from seeing a DVD RAM drive…to a CD rom drive?! When I selected the CD ROM drive…it froze PowerArchiver and I had to do the three finger salute to regain control of my system.
Conclusion: this is definitely a Power Archiver 2010 issue. If my opensource software can read and burn files correctly while Power Archiver 2010 can’t even see my drive correctly then something is wrong.
my head hurts now :)
Were you previously burning files via PowerArchiver to your external dvd drive or not? (when it crashed at 93%).
Also, when you say in list view, you mean in explorer view in PowerArchiver or where exactly? Where did you exactly select CD ROM drive and PowerArchiver froze?
thanks :)
-
I was trying and still am trying to burn files onto my external DVD rom drive connected to the USB port. Just to be clear…
1. My opensource software burner can read and burn files correctly onto the external DVD drive perfectly.
2. Power Archiver 2010 CANNOT read or see the external DVD drive when I hit the Burn button and the drop down list ONLY shows the internal DVD burner.
3. PowerArchiver 2010 can ONLY see the external drive listed correctly in Explorer mode/List view mode. It’s in effect…able to see it but can’t use it for burning jobs. But the internal DVD drive is readable and recognized for burning jobs.
My problem is why can PowerArchiver ONLY read my internal drive correctly for burning jobs…but is ALSO able to see I have ANOTHER DVD rom drive on the USB port…but I can’t use THAT one for burning jobs. Keep in mind…my opensource software package can see BOTH drives and can burn jobs on the external drive. Power Archiver 2010 can’t burn on the external drive…even though it lists it in Explorer view/list mode.
-
explorer view has apsolutly nothing to do with burner, it is just an wrapper over standard windows controls which show drives available on your computer. What happened with PowerArchiver freezing when trying to read that external drive from post above?
PowerArchiver has apsolutly nothing to do with your other burning software which may be working perfectly. So lets get that out of the way please.
Now, when it comes to the PA Burner and your external drive. Did it EVER recognize the drive? Or did it simply not work ever?
-
explorer view has apsolutly nothing to do with burner, it is just an wrapper over standard windows controls which show drives available on your computer. What happened with PowerArchiver freezing when trying to read that external drive from post above?
PowerArchiver has apsolutly nothing to do with your other burning software which may be working perfectly. So lets get that out of the way please.
Now, when it comes to the PA Burner and your external drive. Did it EVER recognize the drive? Or did it simply not work ever?
It briefly recognized the external drive the first time I used it when I tried the first burning job. After the first burning job didn’t work…it no longer reads the drive for CD/DVD jobs.
-
ok great, we will start from there :).
We will have an internal build with new burning engine within few days and we will let you know via this thread where to download it.There are million possible issues when it comes to cd/dvd/bd burners, they are all slightly different and there are 3 different interfaces we can use to burn files, this all contributes to the issues with specific burners. We do have very extensive logging support just for this.
thank you,
-
ok great, we will start from there :).
We will have an internal build with new burning engine within few days and we will let you know via this thread where to download it.There are million possible issues when it comes to cd/dvd/bd burners, they are all slightly different and there are 3 different interfaces we can use to burn files, this all contributes to the issues with specific burners. We do have very extensive logging support just for this.
thank you,
I have good news. I did a Windows XP reboot and now PowerArchiver 2010 can see and read the external DVD drive correctly. Whew! That was close.
Now comes the hard part…narrowing down why the freezing happens.
Here’s an interesting question…
1. Do I put the DVD/CD in the external drive BEFORE hitting the Burn button on PA2010 when I need to run a burn job? Would this help prevent PA2010 from “skipping” to reading the drive contents more accurately?
-
I have good news. I did a Windows XP reboot and now PowerArchiver 2010 can see and read the external DVD drive correctly. Whew! That was close.
Now comes the hard part…narrowing down why the freezing happens.
:-)
I pretty much figured out that was the case (needed an reboot).
You do need to try to burn to internal drive, that will narrow down issue to the external drive (vs everything else).
-
:-)
I pretty much figured out that was the case (needed an reboot).
You do need to try to burn to internal drive, that will narrow down issue to the external drive (vs everything else).
Ugh! I was hoping to save the internal DVD drive for only emergency situations like reinstalling the OS. I’ve become paranoid about this because if one uses the internal DVD drive to the point of exhaustion you’d be forced to bring in your box to having it serviced to install a new one. This just inconveniences your time to do this.
I’ll try burning a DVD using the internal one.
-
I’ve attached a screenshot showing PA2010 successfully did a test burn on my internal DVD drive. So…that part has been removed from consideration.
-
Uh…fellas? I’m still waiting for the build to fix the burner freezing issue. Although I’m able to burn using my internal DVD drive…doens’t mean this problem is fixed. I have an external DVD burner that I’d like to use for primary burning jobs.
-
Uh…fellas? I’m still waiting for the build to fix the burner freezing issue. Although I’m able to burn using my internal DVD drive…doens’t mean this problem is fixed. I have an external DVD burner that I’d like to use for primary burning jobs.
there is no magic wand we wave around here to fix issues. Be patient, and you will be informed via this forum thread when we have new build.
thank you!
-
there is no magic wand we wave around here to fix issues. Be patient, and you will be informed via this forum thread when we have new build.
thank you!
Just thought I’d give you some eyebrow raising information about my further “adventures” in DVD burning using my external drive.
I decided to double check just to make sure that there is something wrong with the burner software in PA2010.
Well, I have good news…look at the screenshot. It says PA2010 successfully burned and VERIFIED 200 mg of data to my external DVD drive. But…
I double checked using Directory Opus 9 to verify the contents of the newly “burned and verified” DVD I just put through PA2010. Guess what? There was absolutely NOTHING on the disc. Zero. Nada. I used the defaults in PA2010 and it went through the motions to read and “verify” my data and said my session was completed successfully. That’s what the screen grab shows in the attached photo. But when I checked to make sure it was true…there wasn’t anything there.
When I hit the close button to the dialog box saying the burn session had completed? It froze PA2010 and I had to give it the three finger salute to close the application.
-
You mean it froze PA Burner right? As those are two separate applications actually, closing PA Burner has nothing to do with PA 2010 itself.
Seems like session info was not recorded properly in that case. We will know more once new burner is ready.
thanks
-
Hi,
please check following release:
http://dl.powerarchiver.com/2010/powarc1160rc1.exeand let us know how it works now.
thanks!
-
It briefly recognized the external drive the first time I used it when I tried the first burning job. After the first burning job didn’t work…it no longer reads the drive for CD/DVD jobs.
I just wanted to confirm I a similar issue with v11.50.61
I got to 98% in the burning process, then gave an error (dont recall what it said). Ejected the disk and from that point failed to recognize any blank disk inserted.
The OS also wouldnt recognize when a blank disk was inserted. Reboot didnt fix it. I had to unplug the drive, boot up into Windows, then plug the drive back in. Now the OS can see the drive and I can burn from the shell. Havent tried it again in PA.
The file I was burning was a 1 GB ISO image. Vista Business x86 SP1. The drive is a Toshiba H653A.
-
Hi,
please check following release:
http://dl.powerarchiver.com/2010/powarc1160rc1.exeand let us know how it works now.
thanks!
So far so good on my end. I need to test it on my external tomorrow before giving it a full thumbs up.
-
did you check with your external drive? We just added support for another burning method (SPTD) in PA 2010, in latest preview version. It is actually faster (20% in our tests it might be different) and lets multiple devices use burner at same time (which is problem with other burning methods).
It is automatically installed once you get latest PAVD update… let us know how it works.
-
I just installed the PA 2010 (latest build) today. I’ll test it to see if this works on my external burner.
-
I just installed the PA 2010 (latest build) today. I’ll test it to see if this works on my external burner.
make sure you also install latest PAVD…
-
Something is wrong…I get an error dialog box saying “wrong Starburn.dll file”. What’s going on? And what is this PAVD thing you’re referring to?
-
Something is wrong…I get an error dialog box saying “wrong Starburn.dll file”. What’s going on? And what is this PAVD thing you’re referring to?
hm, check the dates on files:
PABURNTOOLS.EXE
Starburn.dllin your PA folder. They should be 7.9.2009 and 13.08.2009 respectivly.
-
hm, check the dates on files:
PABURNTOOLS.EXE
Starburn.dllin your PA folder. They should be 7.9.2009 and 13.08.2009 respectivly.
Actually I’m reading
PABURNTOOLS.EXE as 8.9.2009
Starburn.dll as 13.08.2009So in conclusion…I think I’m using an even more updated version of PABURNTOOLS.EXE while Starburn.dll appears incorrect…because it’s not updated for the PaBurnTools.exe date. This is probably why I’m getting the error message when I hit the option VD button.
-
Actually I’m reading
PABURNTOOLS.EXE as 8.9.2009
Starburn.dll as 13.08.2009So in conclusion…I think I’m using an even more updated version of PABURNTOOLS.EXE while Starburn.dll appears incorrect…because it’s not updated for the PaBurnTools.exe date. This is probably why I’m getting the error message when I hit the option VD button.
when exactly do you get the error message?
-
-
Only when I select the Virtual Drive button.
thats is fine, i thought you were getting it in burner because thats what we were talking about previously :)… just do the Web Update via Help, and you will get latest VD drivers which i talked about :-).
