od hybca v 06 led 2011 20:28
Ahoj šikovní kluci,
dostala se mi do ruky výše uvedená navi. V interní paměti jsou nainstalovány origo mapy.
Má to i slot na microSD, kde se pokouším dostat iGO8 a unlock.
Jenže stále mi nejde ani to, abych otevřel unlock. Stále mi nabíhají orig. soft s int. paměti.
V int. paměti je nainstalován pcmfg.ini, kde jsem se pokoušel různě přepsat Navigatorexepath, ale samozřejmě určitě špatně.
Buď navi napíše setup error, please check setup, nebo naskočí orig. soft. A to zkouším pouze ten unlock. Věřím, že dál si již poradím, ale momentálně je na sto-pro problém mezi klávesnicí a židlí.
Zkuste mi prosím poradit. Díky. Jěště přikládám originál pcmfg.ini:
[ProcessManager]
;Configuration file for rescue system control
;use logfile (0=dont log, 1=normal log, 2=log with size limitNAVIGON g=0
;Path to write Log file
Logpath=\MN Settings\RESY.log
;Path to write Log file backup (if size restriction is active)
Logpath2=\MN Settings\RESY_backup.log
;max size of the logfile in bytes
Maxlogfilesize=1000
;Path to executable (of MN7)
Navigatorexepath = .\NAVIGON\navigon.exe
;what to do at Process exit/crash 0=nothing 1=restart 2=reboot
;(avoid restart because of problems with open filehandles!)
Crashrecovery=2
;Path for route target file which ist written from MN7
Rescuedatapath=\MN Settings\NavigationRoute.resy
;Path to private status file of resy procmanager
StatusFilePath=\MN Settings\ProcManStatus.resy
;How to check for new RESY file 1=length only , 2=no check - use countdowntimer
Checkmode=1
;how many restarts with same RESY file
Maxrestarts=3
;Show message box if exe could not be started
ExeStartFailureMessagebox=1
;countdown timer settings (only used in countdown timer check algorithm)
;the route target file is deleted when the countdowntimer is zero
;start value of the countdowntimer - this is also the maximum value
LeakyBucketStart=10
;each crash and restart decreases this value from the countdowntimer
LeakyBucketDecrease=5
;!!but: the timer value is *increased* every minute by one during normal operation!
;Check application thread table
UseThreadMonitor=0
;Maxmum of missing thread table updates (in sequence) until reboot request
MaxCounterUpdateFailures=10
;Create an (smothing) average of watchdog failures over all table updates
AverageFailureCountSmoothing=5
;Maximal accepted average smoothed failure value until reboot request
MaxAverageFailureLimit=4.0
;How many simultaneous thread watchdog failures are required for a reboot request
MaxPeakFailureLimit=6
;Exit this monitor if application terminates with exit code zero (0=no, 1=yes)
CancelOnExitCodeZero=1
Navi: Made in China