@eddie0360
Interesting-er and interestingly, to state the obvious. Out of pure cussedness i've dl'ed the D2335090 file, expecting that it's probably a version of the medium sized D3080060, with less compression to let the 8x5 series cope with it. That's the problem you see, the fw just isn't up to the task of dealing with the larger compressed jcv files, or so it would seem reading between the lines of the usual 'weasel words' concocted by the corporate lawyers:
The end result of which is, to put it your words: "... it slows it down like crazy and keeps freezing ...", but it wouldn't do to say that outright, would it, if you're the ones responsible for foisting cr*p onto your unsuspecting customers.
Now, the curious thing is that comparing the two files, D2335090 @ ~708MB and D3060060 @ ~757MB, using my modded 1300 on the route from the centre of New York City (Holland Tunnel/Hudson-->West) and 'shuffling off' to Buffalo there are 15 jv's on each file, over about 700km (370 odd miles to the non-metric among us). Maybe their assertion that 'Once you have completed this process, your device will contain the complete Junction View data base' is actually true. So there goes the lower compression theory, maybe. 'Coz that's only one route. if you've got the file, try it out and see if it runs slow or makes your 855 play ice-maiden like with the D3060060. Perhaps the large file has been messed around with in some other way to get the inadequate 8x5 series to cope with it. If it does run ok though, why the heck don't they just offer it to 8x5 owners via WebUdater anyway upfront instead of offering them the small one and then making them 'find' this one?



Likes: 







Bookmarks