
- Mapsend-INI-file
- 11-21-2006
![]() Re: Mapsend INI file
| Jack Erbes | 11-21-2006 |
![]() ![]() ![]() Re: Mapsend INI file
| Earl F. Parrish | 11-22-2006 |
![]() ![]() ![]() ![]() Re: Mapsend INI file
| Ron Hunter | 11-23-2006 |
![]() ![]() ![]() Re: Mapsend INI file
| Jack Erbes | 11-23-2006 |
If you were Registered and logged in, you could reply and use other advanced thread options
Some time ago, I altered my mapsend INI file to allow for larger maps for my
meridian. Alas, my computer bit the dust. I lost everything, including the
info on how to make the needed alterations. Any help on this would be
greatly appreciated.
Jay
jseig wrote:
http://gpsinformation.net/MeridianFAQv2_0.pdf
I think it is in that FAQ.
Jack
--
Jack Erbes in Ellsworth, Maine, USA (jackerbes at adelphia dot net)
(also receiving email at jacker at midmaine dot com)
> jseig wrote:
> > Some time ago, I altered my mapsend INI file to allow for larger maps
for my
> > meridian. Alas, my computer bit the dust. I lost everything, including
the
> > info on how to make the needed alterations. Any help on this would be
> > greatly appreciated.
> > Jay
> > greatly appreciated.
> > Jay
> http://gpsinformation.net/MeridianFAQv2_0.pdf
> I think it is in that FAQ.
> Jack
> --
> I think it is in that FAQ.
> Jack
> --
Thanks for the info. While this is very good, it does not have the
instructions on modifying the mapsend.ini file for larger regions.
Jay
>> jseig wrote:
>> > Some time ago, I altered my mapsend INI file to allow for larger maps
> for my
>> > meridian. Alas, my computer bit the dust. I lost everything,
>> > including
>> > including
> the
>> > info on how to make the needed alterations. Any help on this would be
>> > greatly appreciated.
>> > Jay
>> > greatly appreciated.
>> > Jay
>> http://gpsinformation.net/MeridianFAQv2_0.pdf
>> I think it is in that FAQ.
>> Jack
>> --
>> I think it is in that FAQ.
>> Jack
>> --
> Thanks for the info. While this is very good, it does not have the
> instructions on modifying the mapsend.ini file for larger regions.
> Jay
> instructions on modifying the mapsend.ini file for larger regions.
> Jay
Modify this section:
[DEVICE_DEFAULTS]
Com_Port=-1
Baud_rate=-1
Memory_Size=8000
Conv_Maximum_Number_of_Regions=9
Maximum_Number_of_Regions=1
Conv_Memory_Size=65536
Write_Export_Log=0
Write_GPS_Log=0
Write_upload_Log=0
Write_Routing_Log=0
UploadDevice=14
MMC_NAME=detail00.img
SDSpeed=504
Change the "Conv_Memory_Size=65536"
Here is the section from the FAQs:
50) Troubleshooting - Map Size Limits
Thanks to "jvavrus2000"
With the 3.08 version of the Meridian firmware, size restrictions on the
size of map files have been removed.
However, the existing MapSend software does not know this, and will try to
restrict the size of maps unless told
otherwise.
First, using Windows Explorer, navigate to the MapSend installation
directory. This should be under C:\Program
Files\Magellan. Open the MAPSEND.INI file using your favorite text editor.
Inside this file, there is a parameter
called "Conv_Memory_Size" which is the maximum region size in bytes.
Multiply this number by four, and you
should be able to have much larger regions. If this line does not exist,
then add the following line (case sensitive)
under the [Device Defaults] section:
Conv_Memory_Size=65536
Note that the larger the region is, the longer your computer will take to
process this region. Processing a 64MB
region is likely to take a very long time. You are much better off making
smaller maps, and loading multiple map
files on your SD card, as described in question 13.
Large maps do have some side effect. The larger the map, the more likely the
map is to suffer from corruption. Maps
larger than 30MB are prone to corruption and very large maps can result in
slow screen updates (Topo seems to be
more sensitive to this than S&D). To minimize the chance of corruption
during map generation, run the Mapsend
software to create the maps and do not run any other programs, surf the net,
check your email - nothing, nada, nil.
Don't even think about touching your computer.
--
Earl F. Parrish
Earl F. Parrish wrote:
>>> jseig wrote:
>>>> Some time ago, I altered my mapsend INI file to allow for larger maps
>>>> Some time ago, I altered my mapsend INI file to allow for larger maps
>> for my
>>>> meridian. Alas, my computer bit the dust. I lost everything,
>>>> including
>>>> including
>> the
>>>> info on how to make the needed alterations. Any help on this would be
>>>> greatly appreciated.
>>>> Jay
>>> http://gpsinformation.net/MeridianFAQv2_0.pdf
>>> I think it is in that FAQ.
>>> Jack
>>> --
>>>> greatly appreciated.
>>>> Jay
>>> http://gpsinformation.net/MeridianFAQv2_0.pdf
>>> I think it is in that FAQ.
>>> Jack
>>> --
>> Thanks for the info. While this is very good, it does not have the
>> instructions on modifying the mapsend.ini file for larger regions.
>> Jay
>> instructions on modifying the mapsend.ini file for larger regions.
>> Jay
>
> Modify this section:
> [DEVICE_DEFAULTS]
> Com_Port=-1
> Baud_rate=-1
> Memory_Size=8000
> Conv_Maximum_Number_of_Regions=9
> Maximum_Number_of_Regions=1
> Conv_Memory_Size=65536
> Write_Export_Log=0
> Write_GPS_Log=0
> Write_upload_Log=0
> Write_Routing_Log=0
> UploadDevice=14
> MMC_NAME=detail00.img
> SDSpeed=504
>
>
> Change the "Conv_Memory_Size=65536"
>
> Here is the section from the FAQs:
>
> 50) Troubleshooting - Map Size Limits
>
> Thanks to "jvavrus2000"
>
> With the 3.08 version of the Meridian firmware, size restrictions on the
> size of map files have been removed.
>
> However, the existing MapSend software does not know this, and will try to
> restrict the size of maps unless told
>
> otherwise.
>
> First, using Windows Explorer, navigate to the MapSend installation
> directory. This should be under C:\Program
>
> Files\Magellan. Open the MAPSEND.INI file using your favorite text editor.
> Inside this file, there is a parameter
>
> called "Conv_Memory_Size" which is the maximum region size in bytes.
> Multiply this number by four, and you
>
> should be able to have much larger regions. If this line does not exist,
> then add the following line (case sensitive)
>
> under the [Device Defaults] section:
>
> Conv_Memory_Size=65536
>
> Note that the larger the region is, the longer your computer will take to
> process this region. Processing a 64MB
>
> region is likely to take a very long time. You are much better off making
> smaller maps, and loading multiple map
>
> files on your SD card, as described in question 13.
>
> Large maps do have some side effect. The larger the map, the more likely the
> map is to suffer from corruption. Maps
>
> larger than 30MB are prone to corruption and very large maps can result in
> slow screen updates (Topo seems to be
>
> more sensitive to this than S&D). To minimize the chance of corruption
> during map generation, run the Mapsend
>
> software to create the maps and do not run any other programs, surf the net,
> check your email - nothing, nada, nil.
>
> Don't even think about touching your computer.
>
>
>
Funny. I use Mapsend DirectRoute V2, and when I am creating a region, I
> Modify this section:
> [DEVICE_DEFAULTS]
> Com_Port=-1
> Baud_rate=-1
> Memory_Size=8000
> Conv_Maximum_Number_of_Regions=9
> Maximum_Number_of_Regions=1
> Conv_Memory_Size=65536
> Write_Export_Log=0
> Write_GPS_Log=0
> Write_upload_Log=0
> Write_Routing_Log=0
> UploadDevice=14
> MMC_NAME=detail00.img
> SDSpeed=504
>
>
> Change the "Conv_Memory_Size=65536"
>
> Here is the section from the FAQs:
>
> 50) Troubleshooting - Map Size Limits
>
> Thanks to "jvavrus2000"
>
> With the 3.08 version of the Meridian firmware, size restrictions on the
> size of map files have been removed.
>
> However, the existing MapSend software does not know this, and will try to
> restrict the size of maps unless told
>
> otherwise.
>
> First, using Windows Explorer, navigate to the MapSend installation
> directory. This should be under C:\Program
>
> Files\Magellan. Open the MAPSEND.INI file using your favorite text editor.
> Inside this file, there is a parameter
>
> called "Conv_Memory_Size" which is the maximum region size in bytes.
> Multiply this number by four, and you
>
> should be able to have much larger regions. If this line does not exist,
> then add the following line (case sensitive)
>
> under the [Device Defaults] section:
>
> Conv_Memory_Size=65536
>
> Note that the larger the region is, the longer your computer will take to
> process this region. Processing a 64MB
>
> region is likely to take a very long time. You are much better off making
> smaller maps, and loading multiple map
>
> files on your SD card, as described in question 13.
>
> Large maps do have some side effect. The larger the map, the more likely the
> map is to suffer from corruption. Maps
>
> larger than 30MB are prone to corruption and very large maps can result in
> slow screen updates (Topo seems to be
>
> more sensitive to this than S&D). To minimize the chance of corruption
> during map generation, run the Mapsend
>
> software to create the maps and do not run any other programs, surf the net,
> check your email - nothing, nada, nil.
>
> Don't even think about touching your computer.
>
>
>
use my computer for other things. When doing this on my laptop, it is
quite slow, and impacts other processes, but on my desktop (which is
MUCH faster), it takes much less time to process, and I always do other
things at the same time. Note that how much ram your computer has, and
how fast the processor runs makes a LOT of difference.








> meridian. Alas, my computer bit the dust. I lost everything, including the
> info on how to make the needed alterations. Any help on this would be
> greatly appreciated.
> Jay