Changes between Version 12 and Version 13 of Download

Timestamp:

2012-07-18T19:56:33+02:00 (14 years ago)

Author:

skyper

Comment:

typo + format

Download

@@ -79 +79 @@
 === useful options ===
 
-If JOSM runs out of memory, you can increase the maximum size of allocated memory (in megabytes - max ±1.5GB for 32bit java, system dependent):
+If JOSM runs out of memory, you can increase the maximum size of allocated memory (in megabytes - max ± 1.5GB for 32bit java, system dependent):
 {{{
 JAVA_OPTS="-Xmx400M" josm
@@ -91 +91 @@
 === VM selection on Windows x64 ===
 
-For Windows, beware that some browsers may install their own JRE only in 32 bit mode, but may also install their version of the Javawebstart tool somewhere else with different file associations. This may cause your JNLP to start with this alternate JRE becaue it runs the wring version of Javawebstart which only supports the 32 bit VM, and sometimes built with a restricted support for VM options, and a max VM size not exceeding 256MB.
+For Windows, beware that some browsers may install their own JRE only in 32 bit mode, but may also install their version of the Javawebstart tool somewhere else with different file associations. This may cause your JNLP to start with this alternate JRE because it runs the wrong version of Javawebstart which only supports the 32 bit VM, and sometimes is built with a restricted support for VM options and a max VM size not exceeding 256MB.
 
-Check for example if there's no other javawebstart in \Windows\SysWow64. You should not need it (the Java control panel will not detect it) and could safely delete it. Perfom cleanup and only keep the latest version of the JRE (1 for the 32-bit mode, another one for the 64-bit mode).
+Check, for example, if there's no other javawebstart in {{{\Windows\SysWow64}}}. You should not need it (the Java control panel will not detect it) and can safely delete it. Perfom cleanup and only keep the latest version of the JRE (1 for the 32-bit mode, another one for the 64-bit mode).
 
-For shortcuts created on the desktop for JNLP and running the Javawebstart launcher (from \windows\system32), make sure to pass VM parameters prefixed with -J and no intermediate space before the VM option. If you have installd bith the 32-bit and 64-bit version, you should pass the option "-d64" if you want to select the preferred the 64-bit VM. Note that some Oracle documentation pages indicates the option "-D64" with the incorrect capitalization!)
+For shortcuts created on the desktop for JNLP and running the Javawebstart launcher (from {{{\windows\system32}}}), make sure to pass VM parameters prefixed with -J and no intermediate space before the VM option. If you have installd bith the 32-bit and 64-bit version, you should pass the option "{{{-d64}}}" if you want to select the preferred the 64-bit VM. Note that some Oracle documentation pages indicates the option "-D64" with the incorrect capitalization!)
 
 Example of an edited commandline for the shortcut created on the windows desktop after running JOSM just once from the JNMP and exiting:
@@ -101 +101 @@
 C:\Windows\System32\javaws.exe -J-d64 -Xmx=2048m -localfile -J-Djnlp.application.href=http://josm.openstreetmap.de/download/josm.jnlp "C:\Users\<snipped user name>\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\21\7311<snipped-hex-number>7f8"
 }}}
-You don't need to change the end of the command line with the snipped parts here. Just check the path for javaws.exe and add options "-J-d64" for the 64-bit mode needed to work with large OSM datasets, and "-Xmx=2048m" to increase the VM size (to 2GB here).
+You don't need to change the end of the command line with the snipped parts here. Just check the path for {{{javaws.exe}}} and add options "{{{-J-d64}}}" for the 64-bit mode needed to work with large OSM datasets, and "{{{-Xmx=2048m}}}" to increase the VM size (to 2GB here).