PPCGeeks Forums HTC Arrive HTC HD2 HTC Thunderbolt HTC Touch Pro 2 HTC Evo 4G HTC Evo 3D Samsung Galaxy S II Motorola Droid X Apple iPhone Blackberry
Go Back   PPCGeeks > Windows Mobile > WM HTC Devices > HTC Touch Pro 2
Register Community Search

Notices


Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 01-04-2010, 05:13 PM
ziggy471's Avatar
Geek with a Gun
Offline
Pocket PC: Thunderbolt
Carrier: Verizon
Threadstarter
Location: NoVA
 
Join Date: Oct 2009
Posts: 744
Reputation: 6575
ziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the community
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Fix/Workaround for 2016 Issue

I've found the function that's causing the issue, or at least I think I have. The subroutine in RILPHONE.dll that accesses the reg key is at 0x100722C8, and it is only called by 2 other routines, 0x10075080+1C8 and 0x10076A40+45C. Both of those functions read the SystemTime, then run the folowing code starting at loc_10075270:
CMP R0, #1
BNE loc_10075270
ADD R0, SP, #0x34+SystemTime ; lpSystemTime
BL GetSystemTime
ADD R1, SP, #0x34+SystemTime ; void *
MOV R2, #0x10 ; size_t
ADD R0, R5, #0x54 ; void *
BL memcpy
B loc_10075280
loc_10075270
R3, R7, #0x400
ADD R0, R3, #0xD9
ADD R1, R5, #0x54
BL sub_100744C8
LDR R3, [R4,#4]
ORR R3, R3, #0x40
STR R3, [R4,#4]
loc_1007528C ; CODE XREF: sub_10075080+1B0j
ADD SP, SP, #0x10
LDMFD SP!, {R4-R11,LR}
BX LR
sub_100744C8 is dealing with TimeZoneInformation and FileTimes and converting SystemTime to FileTime. Filetime is how MAPI stores it's datetime.

Well, at least we know where the issue is now, maybe someone at HTC has found the same thing and patched it.



Z

Last edited by ziggy471; 01-04-2010 at 05:16 PM.
Reply With Quote
This post has been thanked 3 times.
  #2 (permalink)  
Old 01-04-2010, 05:16 PM
Scientific's Avatar
GTX Team Member
Offline
Pocket PC: Epic! (Evo and TP2 on standby)
Carrier: Sprint
Location: SF Bay Area/Washington D.C.
 
Join Date: May 2008
Posts: 890
Reputation: 3715
Scientific is still contributing even after becoming a VIPScientific is still contributing even after becoming a VIPScientific is still contributing even after becoming a VIPScientific is still contributing even after becoming a VIPScientific is still contributing even after becoming a VIPScientific is still contributing even after becoming a VIPScientific is still contributing even after becoming a VIPScientific is still contributing even after becoming a VIPScientific is still contributing even after becoming a VIPScientific is still contributing even after becoming a VIPScientific is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Fix/Workaround for 2016 Issue

Quote:
Originally Posted by ziggy471 View Post
I've found the function that's causing the issue, or at least I think I have. The subroutine in RILPHONE.dll that accesses the reg key is at 0x100722C8, and it is only called by 2 other routines, 0x10075080+1C8 and 0x10076A40+45C. Both of those functions read the SystemTime, then run the folowing code starting at loc_10075270:
CMP R0, #1
BNE loc_10075270
ADD R0, SP, #0x34+SystemTime ; lpSystemTime
BL GetSystemTime
ADD R1, SP, #0x34+SystemTime ; void *
MOV R2, #0x10 ; size_t
ADD R0, R5, #0x54 ; void *
BL memcpy
B loc_10075280
loc_10075270
R3, R7, #0x400
ADD R0, R3, #0xD9
ADD R1, R5, #0x54
BL sub_100744C8
LDR R3, [R4,#4]
ORR R3, R3, #0x40
STR R3, [R4,#4]
loc_1007528C ; CODE XREF: sub_10075080+1B0j
ADD SP, SP, #0x10
LDMFD SP!, {R4-R11,LR}
BX LR
sub_100744C8 is dealing with TimeZoneInformation and FileTimes and converting SystemTime to FileTime.

Well, at least we know where the issue is now, maybe someone at HTC has found the same thing and patched it.



Z
You're spending WAY too much time on this issue Zig! lol
Reply With Quote
  #3 (permalink)  
Old 01-04-2010, 05:20 PM
ziggy471's Avatar
Geek with a Gun
Offline
Pocket PC: Thunderbolt
Carrier: Verizon
Threadstarter
Location: NoVA
 
Join Date: Oct 2009
Posts: 744
Reputation: 6575
ziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the communityziggy471 is a trusted member of the community
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Fix/Workaround for 2016 Issue

Quote:
Originally Posted by Scientific View Post
You're spending WAY too much time on this issue Zig! lol
I got really bored imaging laptops today, sorry.......

Remember what I said in IRC, I Can't let the machines win. Hey maybe I should rename myself to John Conner.



Z
Reply With Quote
This post has been thanked 1 times.
Reply

  PPCGeeks > Windows Mobile > WM HTC Devices > HTC Touch Pro 2

Tags
2016 y2k


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


All times are GMT -4. The time now is 08:10 AM.


Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.6.0
©2012 - PPCGeeks.com