Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 5 of 5 FirstFirst ... 345
Results 41 to 43 of 43
  1. #41
    iGO Enthusiast GPS Week Number Rollover (WNRO) JUST Findings, Fixes, and Frustrations
    GPS Week Number Rollover (WNRO) JUST Findings, Fixes, and FrustrationsGPS Week Number Rollover (WNRO) JUST Findings, Fixes, and FrustrationsGPS Week Number Rollover (WNRO) JUST Findings, Fixes, and FrustrationsGPS Week Number Rollover (WNRO) JUST Findings, Fixes, and FrustrationsGPS Week Number Rollover (WNRO) JUST Findings, Fixes, and FrustrationsGPS Week Number Rollover (WNRO) JUST Findings, Fixes, and FrustrationsGPS Week Number Rollover (WNRO) JUST Findings, Fixes, and Frustrations
    Boki_Srb's Avatar
    Join Date
    Jun 2014
    Location
    Niš
    Age
    50
    Posts
    5,313
    Rep Power
    3524

    Default

    Read post # 34, on same page
    Before asking a question, know it's already discussed here and at 99.9% is not unique. Use search.
    NO ONE IS A SEER, READ (click on): [Only registered and activated users can see links. ] <- Click!
    [Only registered and activated users can see links. ] <- Click!

    Spoiler: obs
    Many questions become very arduous, a lot of time chewed deja vu...Since we have lost all the year of work and effort, many people have no will to answer the same questions again. Me neither. Use a search, please.

  2.    Advertissements


  3. #42
    Junior Member
    Join Date
    Jul 2015
    Location
    Poland
    Posts
    1
    Rep Power
    0

    Default

    Hi, i've made WNRO fix for my WM2003-WM6.5 devices. I'am using IGO with Toshiba TG01 and WNRO is pain in the ass: all logs has wrong date inside, log files has wrong date, night/day is at wrong time...
    So i made simple 'on the fly' gps protocol translator. It is driver for COM port. After installation it creates new COM port to which your program should connect. Configuration included inside cab creates COM6 and reads from COM7 (my TG01 configuration). After installation you should set proper values for your system in registry key HKLM\Drivers\Builtin\WNROFIX. The value 'SourcePort' contains number of port where you have original gps source, the value 'Index' is number of new port. It should be 'free' number to not collide with existing COM ports.
    Link: [Only registered and activated users can see links. ] or [Only registered and activated users can see links. ]
    I've tested this with WM2003, WM6.1, WM6.5 and some additional software like port splitter, gps logger, external gps mouse via BT, and it looks like it simply works.
    regards Krzysiek

  4. #43
    Junior Member
    Join Date
    Mar 2015
    Location
    World
    Posts
    1
    Rep Power
    0

    Default

    After a lot of research, I didn't think I could find a solution to my problem until I found this post. I have an HTC TYTN2 WM6.0 phone and WNRO was really a pain in the ass with Tomtom! Permanent notification error messages, hour 0.00, automatic date change to year 2000, navigation impossible and phone memory saturation. So I installed the magic program WNRO fix from Krzysiek, configured the ports in the registry key (for me 'SourcePort' = 4 and 'Index' = 1) and set Tomtom to use the GPS of port 1, and then miracle Tomtom works perfectly again as before the bug!
    Huge thanks to krzysxxx for the WINRO fix he made for mobile phones with WM6 !! It's perfect !
    Last edited by Boki_Srb; 17th August 2020 at 07:19 AM. Reason: removed unnecessary quote

 

 

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •