導航配置文件是哪個

⑴ 車載導航的凱立德地圖打開提示配置文件不存在或被破壞

是不是以前安過凱立德，如果安過就先卸載，然後刪除NaviOne文件夾，重新考一次，考完再安裝手機端。

⑵ 為什麼導航埠改成和配置文件一樣了還是不可以導航呢

你好！
如果導航軟體的埠、波特率已改成與導航儀一致，仍無法導航的話，那肯定是你用的導航軟體的專版程序不適合你的導航儀機器。
如華陽導航CE4601，要用C1413的專版主程序，如果用了飛歌的C1204的專版主程序，即使埠、波特率已改成與導航儀一致，也是用不了的。
希望能幫到你，望採納！

⑶ 導航顯示配置文件不存在或被破壞

你好，請問你是用什麼工具下載的，如果是用IE的下載工具下載的話則會慢，下載的文件越大則越慢，還會發生斷點，所謂斷點是指在下載文件過程中發生中途中斷，比如網路原因，文件過大等，建議你使用下載工具下載文件，尤其是大文件，下載工具有訊雷，快車等，謝謝。

如果對您有幫助，請記得採納為滿意答案，謝謝！祝您生活愉快！

vae la

⑷ 汽車導航 凱立德地圖，顯示「配置文件丟失或被破壞」

大部分人讓他把地圖文件放到手機自帶存儲中，本來放在SD卡完全好用，盡量不要挪動。
SD卡中的導航文件不必移動，你把手機調到大容量存儲狀態。
如果你看到你的手機存儲中有個NAVIONE的文件，刪除掉，在手機中運行導航時，系統在手機存儲中找不到導航地圖，自然調到SD卡中，就好了。
如果你手機存儲中還有這個文件，而這個文件很小，根本不是地圖文件，當然出現 配置文件不存在或被破壞的提示了。

⑸ 網站導航在哪裡修改 哪個文件

一般地說，都在模板文件的hear.html中修改，當然也有可能不在，得看看你的程序

⑹ 車載DVD導航「沒有配置文件」（凱立德）

在設置裡面找到導航路徑設置
重新設置一下
路徑
找到EXE
後綴
就行了
在不行的話
重新拷貝一份地圖到GPS卡裡面

⑺ 凱立德車載導航打不開，在車上打開顯示沒有配置文件！

估計是某項配置文件丟失造成的軟體無法打開 你可以根據你車載導航的型號 去網上下載凱立德的ROM包 重新覆蓋一遍即可 希望能夠幫到你 望採納！

⑻ jsf導航配置文件的問題

我們的是直接配置一個filter.xml文件。希望對你有所幫助。
<!-- filters.xml starts -->
<!-- context-params.xml does not work. put here -->
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>server</param-value>
</context-param>

<context-param>
<param-name>org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS</param-name>
<param-value>true</param-value>
</context-param>

<context-param>
<param-name>org.apache.myfaces.ADD_RESOURCE_CLASS</param-name>
<param-value>org.apache.myfaces.renderkit.html.util.DefaultAddResource</param-value>
</context-param>

<context-param>
<param-name>org.apache.myfaces.RESOURCE_VIRTUAL_PATH</param-name>
<param-value>/faces/myFacesExtensionResource</param-value>
</context-param>

<context-param>
<param-name>org.apache.myfaces.CHECK_EXTENSIONS_FILTER</param-name>
<param-value>true</param-value>
</context-param>

<context-param>
<param-name>javax.faces.CONFIG_FILES</param-name>
<param-value>/WEB-INF/模塊一.xml,
/WEB-INF/模塊二.xml, /WEB-INF/模塊三.xml
</param-value>
</context-param>

<context-param>
<param-name>org.apache.myfaces.ALLOW_JAVASCRIPT</param-name>
<param-value>true</param-value>
<!--
<description>
This parameter tells MyFaces if javascript code should be allowed in the
rendered HTML output.
If javascript is allowed, command_link anchors will have javascript code
that submits the corresponding form.
If javascript is not allowed, the state saving info and nested parameters
will be added as url parameters.
Default: "true"
</description>
-->
</context-param>

<context-param>
<param-name>org.apache.myfaces.DETECT_JAVASCRIPT</param-name>
<param-value>false</param-value>
<!--
<description>
This parameter tells MyFaces if javascript code should be allowed in the
rendered HTML output.
If javascript is allowed, command_link anchors will have javascript code
that submits the corresponding form.
If javascript is not allowed, the state saving info and nested parameters
will be added as url parameters.
Default: "false"

Setting this param to true should be combined with STATE_SAVING_METHOD "server" for
best results.

This is an EXPERIMENTAL feature. You also have to enable the detector filter/filter mapping below to get
JavaScript detection working.
</description>
-->
</context-param>

<context-param>
<param-name>javax.faces.PARTIAL_STATE_SAVING_METHOD</param-name>
<param-value>false</param-value>
</context-param>

<context-param>
<param-name>org.apache.myfaces.PRETTY_HTML</param-name>
<param-value>true</param-value>
<!--
<description>
If true, rendered HTML code will be formatted, so that it is "human readable".
i.e. additional line separators and whitespace will be written, that do not
influence the HTML code.
Default: "true"
</description>
-->
</context-param>

<context-param>
<param-name>org.apache.myfaces.AUTO_SCROLL</param-name>
<param-value>true</param-value>
<!--
<description>
If true, a javascript function will be rendered that is able to restore the
former vertical scroll on every request. Convenient feature if you have pages
with long lists and you do not want the browser page to always jump to the top
if you trigger a link or button action that stays on the same page.
Default: "false"
</description>
-->
</context-param>

<!-- WelcomeFile Filter -->
<!--
<filter>
<filter-name>WelcomeFile Filter</filter-name>
<filter-class>org.apache.myfaces.webapp.filter.WelcomeFileFilter</filter-class>
<description>
Due to the manner in which the JSP / servlet lifecycle
functions, it is not currently possible to specify default
welcome files for a web application and map them to the
MyFacesServlet. Normally they will be mapped to the
default servlet for the JSP container. To offset this
shortcoming, we utilize a servlet Filter which examines
the URI of all incoming requests.
</description>
</filter>
-->

<!-- JavaScriptDetector Filter -->
<!--
<filter>
<filter-name>javascriptDetector</filter-name>
<filter-class>org.apache.myfaces.webapp.filter.JavaScriptDetectorFilter</filter-class>
</filter>
-->

<filter>
<filter-name>MyFacesExtensionsFilter</filter-name>
<filter-class>org.apache.myfaces.webapp.filter.ExtensionsFilter</filter-class>
<init-param>
<param-name>uploadMaxFileSize</param-name>
<param-value>200m</param-value>
</init-param>
<init-param>
<param-name>uploadThresholdSize</param-name>
<param-value>100k</param-value>
</init-param>
</filter>

<filter>
<display-name>Ajax4jsf Filter</display-name>
<filter-name>ajax4jsf</filter-name>
<filter-class>org.ajax4jsf.Filter</filter-class>
<init-param>
<param-name>forceparser</param-name>
<param-value>false</param-value>
</init-param>
</filter>
<!-- filters.xml ends -->

⑼ 凱立德導航文件中哪個配置文件可以調整提示音

看圖,用工具打開NaviConfig.dll