Read post # 34, on same page
Read post # 34, on same page
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. Click Here To Register...] or [Only registered and activated users can see links. Click Here To Register...]
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
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 !
Quote:
Originally Posted by krzysxxx [Only registered and activated users can see links. Click Here To Register...]
Hello,
I have found this WNRO topic a little late, but Thank you very much for your work :)
I have an Asus A696 for about 15 years now.
It seems to be alive again with this driver.
Also, I have had to switch back the SIRF3 chip into "SIRF" Mode with SirfTech (I have had set it in "NMEA" protocol since many years, and the driver was not working).
For those who would like to set their SIRF3 chip, I have attached the software and the .reg file for A696 with COM9 for the Index port value.
BUT be warning: This can brick the chip ! And there is no way to fix that.
[Only registered and activated users can see links. Click Here To Register...]
:)