New PV2tool?
Bill - have you had a chance to look at pv2tool lately?

Shamefully, no. I have one with some small fixes in it that I put in a while back... don't have the changelog here with me now. Any particular feature you're looking for? Perhaps the "expert mode<>" checkbox?

Oh yeah. Hadn't gotten to those yet. I'll take a look and see what I can do tomorrow about the PID changer and expert mode. I think I can bang those out in short order. Vanity serial requires for me to write some real nvram.dat handling routines, which I'm not super enthused about, so that may wait... er... a while. :P

Just a quick update on this: The code is mostly done. Just gotta do a bit of modification to the patching engine and a bit of QA before I shove it out the door... probably a day or two before it sees the light of day.

Hey, is there any way to add error correction / ignoring? My camera's flash had some bad spots (as you might remember), and when downloading RAWS in pv2tool, sometimes they freeze randomly! I have to re-connect and try the transfer again. Then it works. Is there any way for pv2tool to be more tolerant of errors?

PV2 Tool Mod Request
I think all the work on this project has been great! I do have one hopefully small suggestion. For those of us that use Irfanview for downloading the images, is there a way to change the drivers or the tool so that we do not have to use the libusb 1.10 pv2 drivers so that pv2tool can unlock the camera, and then have to switch to anotehr driver, such as the fox2 to download images with irfanview? What INF modifications or other changes would be needed to have a simgle driver that makes pv2 tool work, and Irfanview? Thanks!

marshallh, there's not a whole lot to do for flash errors during file downloads. The pv2 has its own high level file handling functions built on top of the low-level flash routines, and they're the one's I'm using for file downloads. There isn't a whole lot to tweak there. It's odd that unplugging and replugging works. I'd expect flash errors to behave pretty consistantly. If they are flash errors, they should go away after a format. chiusano, you can avoid having to switch to pv2tool by permanently unlocking your firmware. See the "unlock FIRMWARE" button on pv2tool. After that's successful, you'll never have to launch pv2tool again to retrieve images from Irfanview.

BillW, The only times that PV2tool is needs are 1. when unlocking a new camera for the first time, and 2. when changing splash scrrens of the pic limit. Since all my relatives and freidns come to me when they want their camera tweaked, it means that I am switching between drivers regularly. It woudl just be nice, is all. I think what you have done is great!

Ah... I mistakenly thought that you didn't understand that a cam could be permanently unlocked. My fault. There's 2 ways to accomplish what you're looking at: 1) Use different drivers for both of your USB ports. Ie. one for libusb, and the other for foxz2/ff2. Then when you need to switch, you just need to move the cable from port to port. 2) Check out binaryweaver's site: http://camerahacking.mine.nu/phils/demanufacturing/pv2/ and choose the "software/drivers" from the links on the left. Then follow the "driverx" information link. It describes a combined libusb/foxz2 .inf file that allowed people to use both foxz2 and libusb at the same time. I didn't use that method myself, so I can't personally do more than point you in that direction. Hope that helps!

I have tried that che-ez INF mod, and it worked well under libusb1.8.0 for irfanview and pv2tool. However, in order to use the CVS camcorder, I had to switch to libusb1.10.1, which means that I am back to switiching drivers depending on if I wish to use irfanview or PV2tool. Of course, SUCR won't work under libusb1.10.1 That is one reason that I earlier inquired about merging the SUCR, PV2tool, and OPS so that all could work under a common libusb version.

No luck with using a different driver for each USB port? Drnm4ea is heading the charge for a combined app, but like all of us he has little free time, so initial progress will likely be slow. Once he gets the API carved out and the SUCR code in place, the code to contol the pv2 and the saturn should be integrated fairly quickly. Note that this will be a download tool - he doesn't have any intent to duplicate the settings/hacking type stuff AFAIK.

BillW No luck with the different driver for different USB ports. Must be a quirk of my HP media center PC, with all of its HP device recognition stuff, puls windows xp MCE. So, perhaps I will have to live with switching drivers to use PV2 tool. If SUCR is ported for use with libusb1.10.1, all my relatives with the old dakota cam and the newer cams will be happy. Thanks Again.

Driver Hell goes away if anyone can reverse engineer FF3 mass storage device mode!

A delete file button would be handy