Large JCV (CNNANT_201910)

 
--
Phil in Mentor, Ohio -- Garmin Nuvi 1450
Page 1>>

Will be Available Shortly...

Already contacted nandyesc earlier tonight, and he's already graciously agreed to sharing his file again with the POI Factory community. He'll be downloading it shortly...

Great

I need it also.

Large JCV (CNNANT_201910)

https://mega.nz/#!0cpDwRaL!OFiWzx9Ksqnv5g54m8SjwcgE4mV4moAsyYdvoo7ft94


Password: [our benefactor's moniker]
Size: 830 MiB (870,803,526 bytes)
MD5: 683d15f3d30266c1f6e4760f37f0f89c

Much thanks to nandyesc for sharing his file! If it wasn't for his magnanimous gesture, we all would simply be stuck with our abridged versions.

850395 KB?

tli wrote:

https://mega.nz/#!0cpDwRaL!OFiWzx9Ksqnv5g54m8SjwcgE4mV4moAsyYdvoo7ft94


Password: [our benefactor's moniker]
Size: 830 MiB (870,803,526 bytes)
MD5: 683d15f3d30266c1f6e4760f37f0f89c

Much thanks to nandyesc for sharing his file! If it wasn't for his magnanimous gesture, we all would simply be stuck with our abridged versions.

tli, my file has a size of 850M: 850,395 KB. That sound about right?

Phil

--
Phil in Mentor, Ohio -- Garmin Nuvi 1450

Thank you nandyesc for

Thank you nandyesc for sharing

--
Ginpi

Thanks nandyesc

I(we)really appreciate you posting the large JCV file for us guys who need it. Thanks again.

No luck

I downloaded the zip file. When I attempted to move the jcv file it says it's password protected. The password supplied doesn't work here.

Hint

Password is not tli. Our benefactor is nandyesc.

--
Garmin nüvi 3597LMTHD, 3760 LMT, & 255LMT, - "Those who wish for fairness without first protecting freedom will end up with neither freedom nor fairness." - Milton Friedman

Thanks!

selfruler wrote:

Password is not tli. Our benefactor is nandyesc.

I didn't connect it.

Verify Downloaded File Integrity

plunder wrote:

tli, my file has a size of 850M: 850,395 KB. That sound about right?

Phil

Phil, close enough... wink More importantly, the MD5 checksum should be verified, so to provide a reasonable confidence that the file was not corrupted during download and/or extraction. For those unfamiliar, here's a simple online MD5 calculator and verifier tool (program/app download and install unnecessary):

http://onlinemd5.com/

Copy-and-paste the provided MD5 value into the 'Compare with:' field, this value should match the automatically calculated MD5 in the 'File checksum:' field. This webpage also displays the file size in bytes which should match the provided file size in bytes. If both file attributes match, then your downloaded and extracted file was successful.

Say wha'?

tli, I'm old and don't know nuthin' about any MD5 stuff. I'm going to try it and if it doesn't work I'll download the file again. I didn't see anything that indicated a problem so I'm assuming that everything's kosher.

Phil

--
Phil in Mentor, Ohio -- Garmin Nuvi 1450

@ Tli

Even though I don't personally use the large JCV file, I do appreciate your help in obtaining it for other POI Factory members & would certainly highly recommend you as next weeks COW & happy that you get thrown out in the pasture with your new red barn.

--
Nüvi 255WT with nüMaps Lifetime North America born on 602117815 / Nüvi 3597LMTHD born on 805972514 / I love Friday’s except when I’m on holidays ~ canuk

Got it today

Many thanks nandyesc. Missed 2018.3, so I made up for it now.

A Curious Happening

Thanks, this is the file I needed, or rather the one I wanted. I downloaded the JCV file and I copied and pasted the password, nandyesc, that was shown in bold type and it didn't work.

It was the oddest thing and I wondered if the bold type had anything to do with the problem. I copied and pasted the regular, non bold password, nandyesc,and it worked perfectly.

Who would have thunk it?

nandyesc Deserves the CoW

@canuk, I appreciate your thoughtfulness but recognition and acknowledgement should go to nandyesc as he's really the true and quintessential contributor. He willingly and unselfishly chooses to share his downloaded file with the POI Factory community. Like I mentioned earlier, if it wasn't for nandyesc, we likely would not have access to the comprehensive junction views, and must resort to using diminished versions of the junction views. Recognitions and accolades should be given to those that truly deserve--like nandyesc. Without his shared file, my 'contribution' is not very meaningful. I'm just a facilitator, and glad to be of service.

@mcginkleschmidt, that is indeed odd. Just curious, which OS platform? Which app/program used to unzip? I personally use 7-Zip (v16.04) on Windows x64 platforms.

WinRAR 5.50 64 bit

tli wrote:

@mcginkleschmidt, that is indeed odd. Just curious, which OS platform? Which app/program used to unzip? I personally use 7-Zip (v16.04) on Windows x64 platforms.

I'm using Windows 7 64 bit with WinRAR 5.50 64 bit.

7Zip, an alternate file archiver

mcginkleschmidt wrote:
tli wrote:

@mcginkleschmidt, that is indeed odd. Just curious, which OS platform? Which app/program used to unzip? I personally use 7-Zip (v16.04) on Windows x64 platforms.

I'm using Windows 7 64 bit with WinRAR 5.50 64 bit.

As am I, but 7Zip is a good substitute file archiver for those without WinRAR.

7-Zip home page:

The latest stable version is v16.04.

--
Garmin nuvi 3595LMT, 1450T, 2555LMT, 660, 770, too many really.

Comment

My 2597 will use the large file. My DriveSmart 60 LMT will not display the output. Time changes everything at Garmin.

Why ...

... would you want the large file in a DriveSmart? It has a splitscreen view?

--
Where there's a will ... there's a way ... DriveSmart50LMT-D, Nuvi 2508LMT-D, 1490LMT, 1310, Montana 650T, Etrex 20

Matter of opinion

sussamb wrote:

... would you want the large file in a DriveSmart? It has a splitscreen view?

Never liked the split screen. Many around DFW are just junk.

It worked well in my 3507

It worked well in my 3597 when I crossed Dallas going to Lindale last June. That said, I made the whole damn area an avoid.

--
Frank Nuvi 3597LMT 37.322760, -79.511267

Right Screen

On many junctions the right screen has a large black line with a line on it which shows nothing.

Large JCV In a Drivesmart?

jjen wrote:
sussamb wrote:

... would you want the large file in a DriveSmart? It has a splitscreen view?

Never liked the split screen. Many around DFW are just junk.

Does the full screen file even work in a Drivesmart?

--
"Anyone who is capable of getting themselves made President should on no account be allowed to do the job." --Douglas Adams

No

Strephon_Alkhalikoi wrote:
jjen wrote:
sussamb wrote:

... would you want the large file in a DriveSmart? It has a splitscreen view?

Never liked the split screen. Many around DFW are just junk.

Does the full screen file even work in a Drivesmart?

No the upper part of a window is blank.

by the by

tli wrote:

...that is indeed odd. Just curious, which OS platform? Which app/program used to unzip? I personally use 7-Zip (v16.04) on Windows x64 platforms.

tli, just curious. How do you bold text (or italicize it) here at the Factory?

Phil

--
Phil in Mentor, Ohio -- Garmin Nuvi 1450

< strong >

plunder wrote:
tli wrote:

...that is indeed odd. Just curious, which OS platform? Which app/program used to unzip? I personally use 7-Zip (v16.04) on Windows x64 platforms.

tli, just curious. How do you bold text (or italicize it) here at the Factory?

Phil

Start with < strong > (but without the two spaces, then end it with < /strong > again without the spaces.

Italics is easier since it's just em instead of strong.

More options:

http://www.poi-factory.com/filter/tips

.sum

What is the .SUM file in the JCV folder? When installing the larger JCV, do I need to do anything with that?

Never mind, found it. results of diags.

--
-Quest, Nuvi 1390T

What is the large junction

What is the large junction view file? And how does it differ from the junction view file that comes with my Garmin? Why is there a special large one?

Your wish...

WuLabsWuTecH wrote:

What is the large junction view file? And how does it differ from the junction view file that comes with my Garmin? Why is there a special large one?

Your wish, my command:

http://www.poi-factory.com/node/45292

More:

http://www.poi-factory.com/node/45291

It's way better

WuLabsWuTecH wrote:

What is the large junction view file? And how does it differ from the junction view file that comes with my Garmin? Why is there a special large one?

I don't know what kind of GPS you have, but if it's an older one (mine is a Nuvi 1450) the junction view that you have is very limited. You may not know it, but it is. If instead of keeping the smaller one that comes for the older models you were to do an additional step and replace it the the large JCV file you'd be amazed at how many more junction views you'd get. It's dramatic.

Phil

--
Phil in Mentor, Ohio -- Garmin Nuvi 1450

Many thanks tli and nandyesc...

downloaded and working great on my 1490LMT and 3597LMTHD. smile

I so appreciate...

...the continuing efforts of the team that makes the large Junction View file available to us.

Everything went quick and easy, and I enjoyed the simulation afterward.

--
Ted - Garmin Nuvi 1450 LM

I have a Drive 50. Not sure

I have a Drive 50. Not sure which junction view file I have. I think it's the split screen, but I don't pay enough attention on a day to day basis to remember off hand. Maybe that's a good thing and it means I'm paying more attention to the road?

With ...

Modern devices with a slit screen don't need the large jcv file.

--
Where there's a will ... there's a way ... DriveSmart50LMT-D, Nuvi 2508LMT-D, 1490LMT, 1310, Montana 650T, Etrex 20

Hmm

sussamb wrote:

Modern devices with a slit screen don't need the large jcv file.

Must be a Garmin opinion.

Well,

sussamb wrote:

Modern devices with a slit screen don't need the large jcv file.

Maybe the devices don't need it, but some of the owners of those devices want and enjoy using the Large JCV file. We appreciate all of those who have made, and who continue to make, the Large JCV available for us.

Thanks!

--
Garmin nüvi 3597LMTHD, 3760 LMT, & 255LMT, - "Those who wish for fairness without first protecting freedom will end up with neither freedom nor fairness." - Milton Friedman

I guess it is my old age

I guess it is my old age catching up with me but nothing I enter for a "decrypt key" works, bold or not.
Anyway, I discovered that my 765 updates with the large jcv file, so I am good, EXCEPT I don't know where to put it in a 3597 folder structure.

It

It goes in:

.system/jcv

--
Nuvi 350, 760, 1695LM, 3790LMT, 2460LMT, 3597LMTHD, DriveLuxe 50LMTHD and TomTom XXL540s, HereWeGo for Android.

Thanks for the Larger JCV File

nandyesc,

Thanks a bunch for the Large JCV file.

I truly appreciate it.

Regards.

Question

I thought the Garmin maps are locked a specific unit.

Yes

terrenjen110 wrote:

I thought the Garmin maps are locked a specific unit.

The City Navigator map file which is a *.img file, yes. But the Junction View file, a *.jcv is not locked. I have a vague memory that quite a while ago, one or two map updates did come with a locked JCV file. Does anyone else remember this? This probably would have been before the need for the Large JCV file by folks became common but being locked was removed in later map updates.

Before the Large JCV file was offered by users here for others who need want it, it was confirmed with Garmin that the file could be shared and Garmin would not be upset.

[Later] Found it but it certainly was a confusing thread. There was a time (2013) when the JCV file came with an unlock file:

http://www.poi-factory.com/node/40241

Updated 2019.10 incompatible with posted large jcv?

Hello,

When 2019.10 was originally available, I installed it and the large jcv referenced in this thread on the microSD Card on my 1390LMT using Garmin Express, and it worked fine.

I just installed the updated 2019.10 and tried the large jcv that nandysec graciously provided when the original 2019.10 came out, but I get no junction views when scrolling through the directions list for a route.

I do get junction views with the small jcv that was delivered with the updated 2019.10.

I tried changing the last letter of the large jcv file from A to B, since that is the apparent difference between the original and updated small jcv filenames. But, still no junction views using the large jcv.

I am hoping maybe someone has a workaround? Or, will the large jcv not work until someone posts the large jcv that comes with the updated 2019.10?

Thank you,
Gary

Thats what I think

garyh wrote:

Or, will the large jcv not work until someone posts the large jcv that comes with the updated 2019.10?

It was member Tli who originally shared with us the large jcv & maybe wait a few days & if he hasn't responded in this thread you can always ask for his help by email.

http://www.poi-factory.com/user/367463/contact

--
Nüvi 255WT with nüMaps Lifetime North America born on 602117815 / Nüvi 3597LMTHD born on 805972514 / I love Friday’s except when I’m on holidays ~ canuk

Welcome

garyh wrote:

Hello,

When 2019.10 was originally available,...

I tried changing the last letter of the large jcv file from A to B, since that is the apparent difference between the original and updated small jcv filenames. But, still no junction views using the large jcv.

I am hoping maybe someone has a workaround? Or, will the large jcv not work until someone posts the large jcv that comes with the updated 2019.10?

Thank you,
Gary

Welcome to The Factory. Stick around as there's a lot available here.

Regarding the large JCV file, it's clear from your experiment that a simple filename change doesn't work. Even if the filesize is the same as before, there must be a file-content issue that needs to be addressed. Running a File Comparison program like the builtin Windows comp command will almost certainly show that the old and new large JCV file are different and the original large JCV file for 2019.10 map won't work with the updated 2019.10 map based upon your experience.

As already suggested, someone here will likely post the revised Large JCV file online for download and you'll need to wait for that unless you have an old nuvi 7x5 series or zumo 6xx device with lifetime map updates in which case the Large JCV can be copied from that device to your new device.

http://www.poi-factory.com/node/45292

One possible work-around that may succeed if you backed up your device with the original 2019.10 map file is to go back to the original 2019.10 map on your device. Do not try this or do any other file tinkering without first backing up your current revised 2019.10 files.

Thanks

canuk and CraigW,

Thank you for the suggestions. Unfortunately, I do not have any of the devices CraigW mentions.

I think I will see how annoyed I get with the small jcv before reaching out to Tli. But, I do appreciate you showing me how to contact Tli!

I figure worst case, when 2019.20 comes out in a few months, someone will make available the large jcv for 2019.20.

JCV.

I had noted in our other thread regarding the newly updated and released 2019.10 map that the JCV file name (on the 3597/DriveLuxe 50) had changed from D3191250A.JCV to D3191250B.JCV. I suspect the same "A to B" naming suffix is true for the so-called "large" JCV file that you get on the nuvi 7x5 and zumo 6xx devices. As CraigW said, I guess it will take someone who has one of these models to reinstall this latest map version. I may try this myself since my 755T is just a backup/loaner and seldom used any more. I probably won't have time to try it today though.

--
Alan - Android Auto, DriveLuxe 50LMTHD, Nuvi 3597LMTHD, Oregon 550T, Nuvi 855, Nuvi 755T, Lowrance Endura Sierra

D3060260B.jcv

Large JCV for Re-released CNNANT_2019.10


https://mega.nz/#!tAxwlKbB!7eQFNoOg8wLm3nIU_IMUNT3z-CmDHPv0jWqj6qIfpcY

Password: [our benefactor's moniker]

Size: 830 MiB (870,803,526 bytes)
MD5: 48977dc123f2c679a727bad7ca26fe3f

Much thanks to nandyesc again for sharing his file!

Thanks

Thanks.

Thanks tli and nandyesc

For the new large JCV file.

Downloaded

The file works on the new map on my 1390T.

Page 1>>