OPS will be updated now! request your modifications!

OPS will be updated now! request your modifications!
okay, i'm fed up with the lag! i ran home on break and burned a copy of microsoft visual studio 6.0 enterprise, and installed it here on the xp machine i'm downloading the ops source tree and will commit all the updates that i can find on here. if there is anything that you want or need, say it now! EDIT: well, i committed what i saw, so now i'm beating my head against the wall with massdugg/lockfree for 53.18. i dub this thread for ops modifications and requests, so i know what direction we need to go.

w00t! Ops needs w4r3z music 8)

add the fawkes message and build burningman into it?

Second for burningman, maybe make it automatic and on the fly, regardless of FW version (no more "help I can't unlock!!!" threads).

Second for burningman, maybe make it automatic and on the fly, regardless of FW version (no more "help I can't unlock!!!" threads). well, last time we tried something like that, pd stepped down hard, and the version immediately after that removed the cronus code. not touching this until i have a consensus from other members on the board.

ops upgrade
I made a version that with the newest challenge 09 camcorders you could write the default challenge/response keys back into the camcorder. There was a limit of the 04 keys. Easy fix, but it would be nice to have it in a general release...

Re: ops upgrade
I made a version that with the newest challenge 09 camcorders you could write the default challenge/response keys back into the camcorder. There was a limit of the 04 keys. Easy fix, but it would be nice to have it in a general release... what do you mean, by resetting the camcorder key to the LAMSSMAL key? if that's it, i already took care of it.

Add lockfree and massdugg (start with just 53.14) - I am willing to review and -*test*-('"). This should only require minor changes to the snippets I provided at: forumer.com/viewtopic.php?p=43405#43405" target="_blank">http://camerahacks.10.forumer.com/viewtopic.php?p=43405#43405

massdugg and lockfree would be good. i can imagine a permanent unlock button and a working enable mass storage button.

well, last time we tried something like that, pd stepped down hard, and the version immediately after that removed the cronus code. not touching this until i have a consensus from other members on the board. I still think BurningMan is potentially a legal "hot potato"... so I don't see how this board could support building that logic into Ops and still remain neutral. And, PD keeps changing the C2R mechanisms. So... I would recommend that you isolate the C2R mechanism out of Ops and into a separate DLL. In fact, PV2Tools could be re-written to call the same DLL. I expect that this forum would support distributing Ops with a "baseline" C2R DLL that handles safe cases (i.e. reset camera key, original camera key, etc.) Then, others could develop and distribute a different version of the same DLL that could convert more challenge types. This approach would keep the legal code (ops) separate from questionable code (CronusKey, BurningMan, etc.) The legal code could be fully supported and discussed here.

Maybe add a command-line switch that would enable a child-proof mode so that my niece and nephew could use the cameras without me worrying about them fiddling with "bad" things. Basically: open/unlock, download, shutdown. Just a thought.

couldnt you use the family friendly ops

1. Add "Create New Folder" selection to Download All Movies 2. Add a label that displays the Camcorder's Date and Time so we can synch the corders times only if needed Thanx for Updating Ops Tinhorn

i dunno how hard this would be to implement, but a built-in option to change screens/sounds would be nice! the hard part would prob be scanning the files to make sure it doesn't screw up the camcorder, or maybe just a big 'ol sign that says USE AT OWN RISK, or something. on another note, i've been out of things since about oct, where did this burningman tool come from, its not based on PD code like cronus, is it? if its not, then why would PD get upset about implementing it?

Nobody (well... none of us :?) knows where Burningman came from. The person who announced it here used a well disguised IP address... Cronus never "used" PD code - it was written using a standard, publicly known encryption algorithm. The algorithm and key length were learned from looking at code that PD posted on the Internet. Burningman code looks like the PD code that led to Cronus.

View Full Version: OPS will be updated now! request your modifications!