Quote:
Originally Posted by natemcnutty
Unfortunately, I also have 0x14 on that paddress. Did you disassemble a wince driver for that address?
Code:
HaRET(12)# pdump 0x00081034 128
00081034 | 00000014 efffffff fff7ffdf ffffbfff | ................
00081044 | fffefffb fffffdff ffffffff fffdffff | ................
00081054 | ffffff7f 00000000 52455354 55aaaa55 | ........TSERU..U
00081064 | 58899885 00480052 0044004f 00300035 | ...XR.H.O.D.5.0.
00081074 | 00300030 00000030 ffffffff ffffffff | 0.0.0...........
00081084 | ffffffff 5349424b 52454749 ffffffff | ....KBISIGER....
00081094 | ffffffff 3fffff00 fdfffffd ffffbfff | .......?........
000810a4 | 00000000 4e534543 00001000 00000080 | ....CESN........
|
Had Cotulla take a look at the dlls and he got the address. We verified because it matches the wince kernel log.
If you dump the kernel log from wince during boot you will see g_currentpaneltype=20. So we know 0x14 is what most of us use.