Pentax Firmware Hack site

pingflood · 08-07-2009, 08:54 AM

What does that do, give you infinite lives?

WheresWaldo · 08-07-2009, 10:23 AM

Just a point of clarification. I had to post this at DPR since some did not understand that some of the MODSET commands are sticky.

Once debug is enabled it stays enabled until you disable it. It survives power cycles and does not need to be reloaded each time.

I just tested scripting and it works the same way, once enabled it works every time without re-enabling it. So all you need to do is load the MODSET file one time enabling scripting, then any card that has a AUTORUN.xxx file on it will run at start up without use of the MENU button. Try it yourself it does not appear to change any other functionality other than allowing a short BASIC script to run at camera boot.

tr13 · 08-07-2009, 10:34 AM

Thanks for clarification for ordinary users.
We also must expiriment with BASIC if we could make it background task (USING WAIT, INTERVAL, etc). Most probably it is not possible at this time.

I finished disassembling functions at second TBR (CPU Firmware).
We don't have any text at CPU part, so it is quite hard to understand functionality.
But we are now at exactly same state were last attempt by Rule 34 and other guys was abandoned. :-)

PNTXFTW12 · 08-07-2009, 10:49 AM

Rule 34...wut?

tr13 · 08-07-2009, 10:55 AM

Originally posted by PNTXFTW12

Rule 34...wut?

Just guy at DPReview who did some hacking efforts in 2007. Some others helped, but without any meaningful progress. I have his quotes and links at my site.

falconeye · 08-07-2009, 05:31 PM

Originally posted by tr13

Just buy Hiew license in this case!
P.S. Nasty humor again :-)

So, I now purchased the Hiew license!

@tr13, the license file is underway and I'll keep you informed by PM.

@everybody else, find another option to donate

falconeye · 08-07-2009, 05:41 PM

Originally posted by tr13

You could try DISABLEBLC.
ALso try to write [DISABLEBLC] like im previous file.

My guess why it didn't work:

The function isn't called NR within firmware at all. I guess, it is either "DFS" or "Bulb Dark", judging from strings found so far:

DFS Offset
[Bulb Dark Interval Time (ms)]
[Bulb Dark Last Time (ms)]
[Bulb Dark Time (ms)]

darky_mtp · 08-07-2009, 05:58 PM

Dark Frame Substraction ?

falconeye · 08-07-2009, 06:03 PM

Originally posted by darky_mtp

Dark Frame Substraction ?

darky_mtp, welcome to the forum! Enjoy your time.

Yes, DFS is the standard abbr. for dark frame substraction. Why I wondered if the "long exposure NR" found in the Pentax menu may be called differently in the depths of the firmware, like in dfs or bulb dark.

darky_mtp · 08-07-2009, 06:10 PM

COLOR 4; Use red for print command.
ALLCLR; Clear the screen. What about CLS ?
PAUSE; Wait a key.
I failed to use WHILE,IF.

Class A · 08-07-2009, 07:56 PM

Originally posted by WheresWaldo

I just tested scripting and it works the same way, once enabled it works every time without re-enabling it.

This means you could a different script at each for your SD cards that will make them identify them themselves once you start the camera. No need to check the card slot anymore in case you have some many as to get potentially confused which one you are using at the moment.

Perhaps the keyboard commands could be used to establish start up macros, e.g., for resetting the camera to some customs settings?

Class A · 08-07-2009, 08:06 PM

Originally posted by falconeye

My guess why it didn't work:

What do you think about the possibility that DISABLEBLC could mean "disable black level correction/compensation" ?

tr13 · 08-07-2009, 08:31 PM

Originally posted by falconeye

So, I now purchased the Hiew license!

@tr13, the license file is underway and I'll keep you informed by PM.

@everybody else, find another option to donate

Thanks! As I use free hiew version at this time, just because it is best tool for a task. At least, I work with it, let me remember, like from 1989 :-)

tr13 · 08-07-2009, 08:38 PM

Originally posted by Class A

This means you could a different script at each for your SD cards that will make them identify them themselves once you start the camera. No need to check the card slot anymore in case you have some many as to get potentially confused which one you are using at the moment.

Perhaps the keyboard commands could be used to establish start up macros, e.g., for resetting the camera to some customs settings?

Thanks for good idea. We must try previously provided extra commands.
May be WAIT 4WU will work? :-)
We also must check BASIC and other script languages documentation to provide users fully correct usage syntax.

We completely forget about Cam-Control_V2.dll so if anyone with x86 asm knowledge could help he could use free IDA version to look at functions of this DLL and their usage in service software we have.
As I understand tethering is possible on all cameras via "CamGetJPGMainMemArea", "CamGetRAWMemArea" and similar functions.

tr13 · 08-07-2009, 10:46 PM

Some info about GX20 v1.01 and MODSET and AUTORUN functions.

MODSET works with turning on with open or closed (!) SD door (without any buttons).
You must not have AUTORUN.xx for MODSET to work :-)

All commands seems to work.

[VLENS_CTRL] displays VLENS CONTROL on screen and do not react to keys I tried. We must find key combination that toggles SDM On/off and PZ On/Off. As they are in the same assembler function :-)

[OPEN_DEBUG_MENU] Opens large debug menu on startup there you can make all functions. Like dumping your lens ROM. :-)
Especially interesting is AF PINT DISP as it displays some displacements.

----------------------------
AUTORUN works on every camera start, and in case of synax error it hangs sometimes :-)

Extra info, you could use FILEOUT "STRING" to write STRING to CHKDAT.xxx file. String will be appended to end of file.

WAIT without parameters causes syntax error.
With any parameter it wait indefinetely. Parameter may be TaskID.

You could also note that interpreter runs in his own thread, at least AF and metering works perfectly :-)

08-07-2009, 05:31 PM	#171
falconeye Veteran Member Join Date: Jan 2008 Location: Munich, Alps, Germany Photos: Gallery Posts: 6,871	Originally posted by tr13 Just buy Hiew license in this case! P.S. Nasty humor again :-) *So, I now purchased the Hiew license!* @tr13, the license file is underway and I'll keep you informed by PM. @everybody else, find another option to donate Last edited by falconeye; 08-07-2009 at 05:42 PM.

08-07-2009, 08:38 PM	#179
tr13 Veteran Member Join Date: Jul 2009 Location: Russia Posts: 343 Original Poster	Originally posted by Class A This means you could a different script at each for your SD cards that will make them identify them themselves once you start the camera. No need to check the card slot anymore in case you have some many as to get potentially confused which one you are using at the moment. Perhaps the keyboard commands could be used to establish start up macros, e.g., for resetting the camera to some customs settings? Thanks for good idea. We must try previously provided extra commands. May be WAIT 4WU will work? :-) We also must check BASIC and other script languages documentation to provide users fully correct usage syntax. We completely forget about Cam-Control_V2.dll so if anyone with x86 asm knowledge could help he could use free IDA version to look at functions of this DLL and their usage in service software we have. As I understand tethering is possible on all cameras via "CamGetJPGMainMemArea", "CamGetRAWMemArea" and similar functions. Last edited by tr13; 08-07-2009 at 08:57 PM.

08-07-2009, 10:46 PM	#180
tr13 Veteran Member Join Date: Jul 2009 Location: Russia Posts: 343 Original Poster	Some info about GX20 v1.01 and MODSET and AUTORUN functions. MODSET works with turning on with open or closed (!) SD door (without any buttons). You must not have AUTORUN.xx for MODSET to work :-) All commands seems to work. [VLENS_CTRL] displays VLENS CONTROL on screen and do not react to keys I tried. We must find key combination that toggles SDM On/off and PZ On/Off. As they are in the same assembler function :-) [OPEN_DEBUG_MENU] Opens large debug menu on startup there you can make all functions. Like dumping your lens ROM. :-) Especially interesting is AF PINT DISP as it displays some displacements. ---------------------------- AUTORUN works on every camera start, and in case of synax error it hangs sometimes :-) Extra info, you could use FILEOUT "STRING" to write STRING to CHKDAT.xxx file. String will be appended to end of file. WAIT without parameters causes syntax error. With any parameter it wait indefinetely. Parameter may be TaskID. You could also note that interpreter runs in his own thread, at least AF and metering works perfectly :-) Last edited by tr13; 08-07-2009 at 11:34 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
DFS hack	eccentricphotography	Pentax DSLR Discussion	24	10-12-2010 11:08 AM
Yet another hack job -- OM to PK ??	RioRico	Pentax SLR Lens Discussion	15	10-07-2010 07:49 AM
K20D Firmware Ver - Pentax Web Site Ver?	ChipB	Pentax DSLR Discussion	2	02-23-2010 04:14 PM
Teleconverter hack?	Raptorman	Pentax SLR Lens Discussion	4	01-20-2010 03:51 AM
News Site News and Site Suggestions hidden from guests	Adam	Site Suggestions and Help	0	11-30-2009 12:38 AM

08-07-2009, 08:54 AM	#166
pingflood Veteran Member Join Date: Jun 2008 Location: Borås, Sweden Photos: Gallery Posts: 3,169	What does that do, give you infinite lives?

08-07-2009, 10:23 AM	#167
WheresWaldo Veteran Member Join Date: Sep 2006 Location: North Carolina Photos: Gallery Posts: 498	Just a point of clarification. I had to post this at DPR since some did not understand that some of the MODSET commands are sticky. Once debug is enabled it stays enabled until you disable it. It survives power cycles and does not need to be reloaded each time. I just tested scripting and it works the same way, once enabled it works every time without re-enabling it. So all you need to do is load the MODSET file one time enabling scripting, then any card that has a AUTORUN.xxx file on it will run at start up without use of the MENU button. Try it yourself it does not appear to change any other functionality other than allowing a short BASIC script to run at camera boot.

08-07-2009, 10:34 AM	#168
tr13 Veteran Member Join Date: Jul 2009 Location: Russia Posts: 343 Original Poster	Thanks for clarification for ordinary users. We also must expiriment with BASIC if we could make it background task (USING WAIT, INTERVAL, etc). Most probably it is not possible at this time. I finished disassembling functions at second TBR (CPU Firmware). We don't have any text at CPU part, so it is quite hard to understand functionality. But we are now at exactly same state were last attempt by Rule 34 and other guys was abandoned. :-)

08-07-2009, 10:49 AM	#169
PNTXFTW12 Senior Member Join Date: Oct 2008 Location: Vaughan, Ontario Photos: Gallery Posts: 269	Rule 34...wut?

08-07-2009, 10:55 AM	#170
tr13 Veteran Member Join Date: Jul 2009 Location: Russia Posts: 343 Original Poster	Originally posted by PNTXFTW12 Rule 34...wut? Just guy at DPReview who did some hacking efforts in 2007. Some others helped, but without any meaningful progress. I have his quotes and links at my site.

08-07-2009, 05:41 PM	#172
falconeye Veteran Member Join Date: Jan 2008 Location: Munich, Alps, Germany Photos: Gallery Posts: 6,871	Originally posted by tr13 You could try DISABLEBLC. ALso try to write [DISABLEBLC] like im previous file. My guess why it didn't work: The function isn't called NR within firmware at all. I guess, it is either "DFS" or "Bulb Dark", judging from strings found so far: DFS Offset [Bulb Dark Interval Time (ms)] [Bulb Dark Last Time (ms)] [Bulb Dark Time (ms)]

08-07-2009, 05:58 PM	#173
darky_mtp New Member Join Date: Mar 2008 Posts: 19	Dark Frame Substraction ?

08-07-2009, 06:03 PM	#174
falconeye Veteran Member Join Date: Jan 2008 Location: Munich, Alps, Germany Photos: Gallery Posts: 6,871	Originally posted by darky_mtp Dark Frame Substraction ? darky_mtp, welcome to the forum! Enjoy your time. Yes, DFS is the standard abbr. for dark frame substraction. Why I wondered if the "long exposure NR" found in the Pentax menu may be called differently in the depths of the firmware, like in dfs or bulb dark.

08-07-2009, 06:10 PM	#175
darky_mtp New Member Join Date: Mar 2008 Posts: 19	COLOR 4; Use red for print command. ALLCLR; Clear the screen. What about CLS ? PAUSE; Wait a key. I failed to use WHILE,IF.

08-07-2009, 07:56 PM	#176
Class A Pentaxian Join Date: Aug 2008 Location: Wellington, New Zealand Posts: 11,251	Originally posted by WheresWaldo I just tested scripting and it works the same way, once enabled it works every time without re-enabling it. This means you could a different script at each for your SD cards that will make them identify them themselves once you start the camera. No need to check the card slot anymore in case you have some many as to get potentially confused which one you are using at the moment. Perhaps the keyboard commands could be used to establish start up macros, e.g., for resetting the camera to some customs settings?

08-07-2009, 08:06 PM	#177
Class A Pentaxian Join Date: Aug 2008 Location: Wellington, New Zealand Posts: 11,251	Originally posted by falconeye My guess why it didn't work: What do you think about the possibility that DISABLEBLC could mean "disable black level correction/compensation" ?

08-07-2009, 08:31 PM	#178
tr13 Veteran Member Join Date: Jul 2009 Location: Russia Posts: 343 Original Poster	Originally posted by falconeye *So, I now purchased the Hiew license!* @tr13, the license file is underway and I'll keep you informed by PM. @everybody else, find another option to donate Thanks! As I use free hiew version at this time, just because it is best tool for a task. At least, I work with it, let me remember, like from 1989 :-)