NEW File shows in camera Tree index - HIBERNTE.BIN -
This is strange .. I didn't see it before, but now a new file seems to have been written to the PV2 RED 27 called HIBERNTE.BIN I could have sworn it wasn't there before , or called something else. It may have replaced the PDSCRTCH.BIN cause I don't see it anymore. it's almost the same size as the FIRMWARE.BIN file but just around 1k less I'm going to check my last saved Image to see what it was like before, but has anyone seen the HIBERNTE.BIN file too? before i get all WOW about it ... maybe it's really nothing new. :oops: BTW-just so we're clear on this, the FIRMWARE.BIN file IS still there.

Nobody has really looked into the hibernate file in any detail AFAIK. Interesting that you mention that it's close to firmware size. That leads me to think that it's probably a "live" copy of the firmware. (which would save all of the variables needed to save state during a hibernation) It's not like the pv2 actually needs a hibernate, but it's probably inherited that code from it's other commercial camera siblings, like the ff2, ff3, etc., which share very similar firmwares.

OK.. I looked at both before and after Image files Original CVS unlocked, and the one I have NOW. the CVS Unlocked one was right after I got the camera, with the ONLY mod done to unlock it, and no files changed other to use the UNlock FIRMWARE button of the TOOL utility. That one has the HIBERNTE.BIN file :oops: but it also has two more that the one I have NOW doesn't have... CAMCALIB.BIN ----- 1024 bytes and PDSCRTCS.BIN ------ 24 bytes all I did was change the screens for the shutdown and splash, and all but two of the TIF's with the spiderCAM collection from one of the other sites, REALLY COOL TIF's BTW :D SO... are these missing ones important, ? ... does it tell you anything important? should I just forget about it and go about my monkey business?

shootME, You have more reading to do. Some detail about camcalib file: forumer.com/viewtopic.php?t=387" target="_blank">http://camerahacks.10.forumer.com/viewtopic.php?t=387 If one follows legal hack step by step you will still have factory color calibration file.

I still have the original calib file from the original UnLocked FLASH Image. should i re-up it to the camera? If it makes the pictures better, I wonder how it was removed in the first place, I know I didn't take it out. :P :roll: :P

The only reason to put it back now would be if you were going to have it processed by CVS. There is no other known software that reads the calib files. I suggest saving it just incase a developer figures out how to use it (maybe VB6 Freak can add it to his next release). The format command deletes files not in a special firmware list. I think BillW indicated he was going to include a work around in version 14.

Ahhh.. that's what I needed to know ... Thing is I don't remember using the Format command. :? and I just tried to re-up it to the flash and it won't go in. I even tried to inject it into my saved modded image, using WinImage, and re-up the entire 16 MEG file, and when i looked, it wasn't there anymore. so, I'm thinking a work around is needed in the TOOL progie :wink: :lol: it doesn't seen to want to re-install some original files... unless I'm doing it wrong... I clicked on the top folder in the TREE list, then pressed the UPLOAD FILE button in the TOOL (v2.13) , chose the file , pressed OK, and it said it uploaded it OK, but when I re-listed the TREE, it wasn't there. Is this the BUG in the TOOL you speak of :?:

No, not a bug in the tool - it's a bug in the camera's format command (or a feature, depending on your perspective). Normally it saves system files, but camcalib.bin isn't in the list of system files in the firmware, so it doesn't get saved. I haven't added any cabcalib.bin saving code yet, since it's not really an important file anyway. I doubt anyone will reverse engineer at this point, since that application that actually creates and uses it is independant of the camera and the normal SMaL drivers.

OK.. thanks for the insight. I was thinking I did something wrong. still ... it's odd how it was deleted in the first place, if my original FLASH Image has it when i first saved it to hard drive, using the Download FLASH button, and now it won't put it back... Silly Camera. as long as it's not needed to convert from the RAW to BMP, that's OK. One more question, shouldn't the TWAIN32 Driver ask me what I want the file to be taken off the camera as? .. like JPG or BMP, or whatever it has! I looked into the TWAIN32 file, with a HEX editor, and saw it has the JPG routines in there, as well as support for many companies using this same camera & driver, so, what's up with that. Or is it my application I'm using that isn't fully utilizing this TWAIN32 file.? (Corel Photo-Paint's Acquire Routine) also, I tried taking off the file using the built-in Windows XP "Scanners & Cameras" Capture routine, and it seems to add a bit MORE contrast to the Picture when it puts it to the Hard Drive as the BMP, and the Corel one makes it a bit lighter. I know the WinXP one isn't using the TWAIN32, and is instead using the WIA driver. is there a way to direct WinXP's capture to use the TWAIN32, and why is WinXP's capture look better and bolder (more contrast)

Well here's a bit of strangeness for ya'll I tried putting the config into a different folder, and it worked... The DCIM folder took it without a problem, BUT,... it wasn't there in the original FLASH Image ... (BTW-the PDSCRTCS.BIN went there too without a problem) In the original, the CONFIG was above the FIRMWARE.BIN file., in the first folder on top (the ROOT) but the PDSCRTCS.BIN was always in the DCIM folder . so... why CONFIG doesn't want to go back there anymore is any bodies guess. Maybe it's supposed to go into the DCIM folder, since the RAWS are there too... but if that's so , why not be there from the start.? :?: :!: :?: :? Hmmmmm :!: OH ... and to ... Create987 ... I determined the HIBERNTE.BIN was there even in the original IMAGE, I was wrong in the first post here, as I mentioned it with a " :oops: " too... :roll: :lol: edited ... OK .. I just checked something out ... WinImage lists it differently than the TOOL utility when you list the Directory TREE... WinImage shows it as; Root \ \ DCIM ...\ .....\ .......RAW on the left part of the screen and on the right side, all the files are listed under the DCIM Folder, (when it's NOT opened) BUT on the TREE listing within the TOOL... it shows it as it should be, where the FIRMWARE.BIN is within the ROOT, and most likely the CONFIG & SCRATCH BIN files were in the proper place of DCIM all the while, and i didn't notice until they vanished and the WinImage window Confused me. :roll: :idea: :!:

OK .. I just had to clarify this again .... I was right from the beginning... the CALIB file WAS in the ROOT directory , i was mis-reading WinImage TREE The Scratch file was in the DCIM folder though. IT seems they were both taken out when I used the twain32 driver to reset the pix counter in the camera... that's how it deleted it without me knowing. :roll: :oops: anywho ... if anyone cares anyway. :roll: :wink: :P :lol: BTW-anyone know WHY this happens? :?: :idea: