PV2Tool Releases

PV2Tool Releases
PV2Tool 2.15 is out, find it in the usual place. ( http://sourceforge.net/project/showfiles.php?group_id=134210&package_id=151762 ) The only notable change is support for file listing of larger flash cams. (-*test*-('")ed with binaryweaver's ubercam) Changelog Excerpt: Changes from 2.14 to 2.15 -Fixed all file routines to work with larger flash sizes. -Removed direntry-to-cluster-info mapping, and removed all code dependencies for that mechanism.

heheh, i just get the first quickinstaller for the pv2 out and the next version of pv2tool is out a couple days later

Has anyone, other than me, got warning boxes that pop up for every file when you download images? Using Libusb 1.8 and Pv2tool 2.15.

Has anyone, other than me, got warning boxes that pop up for every file when you download images? Using Libusb 1.8 and Pv2tool 2.15. i get that too, for images i use pv2fetch though, makes it easier

Has anyone, other than me, got warning boxes that pop up for every file when you download images? Using Libusb 1.8 and Pv2tool 2.15. i get that too, for images i use pv2fetch though, makes it easier I have also found that the preview TFT buttons are not working with the Pv2tool 2.15. I get "Failed to CD to /DCIM/RAW/ Trouble changing directories"

CamCam, I've fixed that in 2.16, which I'll release shortly. Zapped, are you sure because I can't replicate that. Are you selecting the TFT file you want to preview from the tree view?

Zapped, are you sure because I can't replicate that. Are you selecting the TFT file you want to preview from the tree view? Yes, I am selecting THMBNAIL.TFT in the DCIM/RAW directory. I did find that the TFTs I tried in the root directory display fine with 2.15 though. I also found that when uploading my modified firmware with 2.15 I tell it to fix the checksum and then download the firmware file and compare it with the firmware file uploaded and checksum fixed by 2.14. The files differ in the last two bytes of the file. In 2.15 however, if I "change" my pid (to what it already is), it must correctly fix the checksum because then it matches the 2.14 checksum fixed file.

Ah, I replicated it now. I'll fit in a fix before I release 2.16. The firmware has 2 checksum locations. At some point I realized that I fubared the first checksum calculation - it escaped my notice because the cameras don't actually use the first checksum location anyway. Being anal retentive, I went ahead and fixed the routine to be 100% correct in 2.15. The second checksum will be slightly different for 2.15+ patched firmwares because the first checksum is part of the byte range used to calculate the second checksum.

PV2Tool 2.16 is out. ( http://sourceforge.net/project/showfiles.php?group_id=134210&package_id=151762 ) No new functionality, just a few bugfixes. Changelog Excerpt: Changes from 2.15 to 2.16 -Removed debugging messagebox that was accidentally left in raw download routines. -Fixed TFT viewing for non-root directories.

I guess I'm the first to get the new PV2TOOL v0.16 :D the download counter on that site said zero(0) ... SO... I'm the first. :P Thanks for your efforts :wink:

PV2Tool 2.17 is out. ( http://sourceforge.net/project/showfiles.php?group_id=134210&package_id=151762 ) Changelog Excerpt: Changes from 2.16 to 2.17 -Added a "delete file" button. -Added a "transfer individual flash blocks" checkbox to the "Transfer Memory" dialog. (only useful if you have block errors and want to retrieve as much good flash as possible)

-Added a "transfer individual flash blocks" checkbox to the "Transfer Memory" dialog. is this the same as reading RAW Flash data?

No. I haven't had a chance to -*test*-('") out my theories WRT raw flash reading. Even if it works I'm not sure it will be able to be automated.

PV2Tool 2.19 is out. ( http://sourceforge.net/project/showfiles.php?group_id=134210&package_id=151762 ) Changelog Excerpt: Changes from 2.18 to 2.19 -Changed "Transfer Memory" bad block marker to "BADBLOCK" so the length would be a multiple of 8 -Added byte offset information for bad block reporting.

This is more of a feature request than anything else, but it would be nice if we had an NVRAM.DAT editor like the USP.BIN editor in Ops. This would, presumably, allow us to clear the R2R bit, edit the serial number, and change the C/R data at will. (or simply reset the key to the \"reset key\" ala Ops)

View Full Version: PV2Tool Releases