Page 2 of 5

Re: UPDATE: DMCP-3.12 / DM42-3.12

Posted: Wed Jan 23, 2019 10:19 am
by grsbanks
mezoganet wrote:
Wed Jan 23, 2019 10:12 am
Hem, nothing special ! All went right and I can now display the date as DMY ;)
You could do before but it wasn't immediately obvious without reading the release notes. Pressing [∑+] would have done it :)
mezoganet wrote:
Wed Jan 23, 2019 10:12 am
Patrick, Tours, France
Je connais le coin ayant vécu 8 ans à Chinon :)

(I know the area having lived in Chinon for 8 years)

Re: UPDATE: DMCP-3.12 / DM42-3.12

Posted: Wed Jan 23, 2019 12:01 pm
by mezoganet
@grsbanks
(I know the area having lived in Chinon for 8 years)
Nice to ear from you...

In fact I live in Tours but I hope to go back soon in Brittany where I was born (even if Tours and Tourraine are nice places) and play as a retired guy with my DM42 fantastic toy !

Re: UPDATE: DMCP-3.12 / DM42-3.12

Posted: Wed Jan 23, 2019 1:45 pm
by Thomas Okken
grsbanks wrote:
Tue Jan 22, 2019 2:04 pm
Image
The copyright message still says 2018...

The same thing happened to me in the Windows build. Apparently I missed free42/windows/Free42.rc during my annual copyright year update ritual. Anyone have a clue why the MacOS grep would not find 2018 in that file, despite the fact that the MacOS file says it's plain text?

Re: UPDATE: DMCP-3.12 / DM42-3.12

Posted: Wed Jan 23, 2019 2:01 pm
by grsbanks
Thomas Okken wrote:
Wed Jan 23, 2019 1:45 pm
The copyright message still says 2018...
Good point. I think the annual copyright update ritual might have been skipped in this case because it was neither applied to Free42 nor DMCP. I'll get that changed for the next release.

Re: UPDATE: DMCP-3.12 / DM42-3.12

Posted: Wed Jan 23, 2019 3:10 pm
by revwillie
akaTB wrote:
Wed Jan 23, 2019 8:37 am
I am currently set @ PowerOFF mode = 1, showing the least current drain from the battery.
Thanks for the info. I'm getting old because I looked all through the setup menus several times and missed the power off mode setting. I was at mode 1, but I'm trying out mode 3.

I stopped hard fault resets by installing a fresh battery, but it does seem to be draining more quickly than I remember in the past. I'll fiddle with power modes for a couple of weeks and maybe finally solder the bridge connection I said I would many months ago... :lol:

Re: UPDATE: DMCP-3.12 / DM42-3.12

Posted: Wed Jan 23, 2019 7:08 pm
by zeno333
The DM42 is the best Scientific Calculator ever made...The original HP 42S is the 2nd best...

Re: UPDATE: DMCP-3.12 / DM42-3.12

Posted: Thu Jan 24, 2019 12:20 am
by H2X
grsbanks wrote:
Tue Jan 22, 2019 2:04 pm
Power-off mode

Offers several levels of power off with different components switched on/off. Useful for diagnosing excessive power consumption.
Which components need to be switched on when the calculator is switched off?

Re: UPDATE: DMCP-3.12 / DM42-3.12

Posted: Thu Jan 24, 2019 9:17 am
by H2X
H2X wrote:
Thu Jan 24, 2019 12:20 am
grsbanks wrote:
Tue Jan 22, 2019 2:04 pm
Power-off mode

Offers several levels of power off with different components switched on/off. Useful for diagnosing excessive power consumption.
Which components need to be switched on when the calculator is switched off?
I am actually having a bit of bother which seems related to power. Several months ago I updated my (beta) DM42, and it died after a few days. Replacing the battery helped for another few days, then it died again.

I then put the calculator away, forgot about it for a while, and then updated it a couple of weeks ago (to 3.11), but it still has the same problem. I suspected the batch of batteries I was using and bought a new one from a different brand. I installed it a couple of days ago, and guess what - today my calculator is dead.

Does this sound familiar to anyone?

Re: UPDATE: DMCP-3.12 / DM42-3.12

Posted: Thu Jan 24, 2019 9:49 am
by Thomas_ER
@H2X: Michael suggested to email him in those cases.

Re: UPDATE: DMCP-3.12 / DM42-3.12

Posted: Thu Jan 24, 2019 10:26 am
by akaTB
H2X wrote:
Thu Jan 24, 2019 9:17 am
Does this sound familiar to anyone?
Yep, same here.

As already suggested, please contact David for this kind of problems.
From what I now know I'd suggest to upgrade to 3.12 since now it should recognise the hardware it runs on and adapt to the correct setting.

But, again, contact David, please.