xboxscene.org forums

Author Topic: Config Question  (Read 50 times)

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Config Question
« on: August 01, 2003, 02:08:00 PM »
QUOTE (onthereal @ Aug 1 2003, 05:37 PM)
When making configuration changes to MXM from the dashboard mode, why are they written to E:UDATA0004321pref.xml instead of rewriting the C:MXM.xml?  Also, since this seems to be the case, does the pref.xml supercede the MXM.xml's settings?  Lastly, can I put the entries from the BIOSMD5.xml in the MXM.xml?  I would like to have 1 all encompassing config file if possible.

Thanks!

The prefs are meant to be "global" in scope, hence the 'standardized' location. Normally, the user shouldn't even worry about this file.

The Prefs supercede the MXM.xml - when running from the hard drive. When running from the DVD, MXM.xml takes precedence. Eventually, everything will be settable in the prefs.xml through dialogs in MXM.

I am working on cleaning up the BIOSMD5 support, too.... there are several ideas I have to make things work a bit smoother in the future (including an online interactive database)
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Config Question
« Reply #1 on: August 02, 2003, 05:16:00 AM »
QUOTE (onthereal @ Aug 1 2003, 07:58 PM)
What about conflicting entries?

Example:

MXM.xml = <FTPPriority>Normal</FTPPriority>
Pref.xml = <FTPPriority>9</FTPPriority>

By your reply, the value "9" would take precedence over my "Normal" entry.  If for what ever reason I were to set my MXM.xml to <FTPPriority>Low</FTPPriority> the 9 would still supercede my later hand edit change.  I think a typical user (non dash tweaker) would know to change the entry in the pref.xml or make the change in-dash.  They would assume, just as I did (until I found the perf.xml), that the change to the MXM.xml would be enough.

Not to compare MXM to evox, but changes made in-dash resulted in a rewrite of the evox.ini.  I won't even pretend to understand the difference in complexity if rewriting a multi-node xml file vs. a line-by-line ini file, but it would seem to be better for the end user to have a single well documented MXM.xml, than several xml's in varying locations.

Please keep in mind. This is by no means a criticism of your great work.  I just think more in terms of MXM being an excellent dash, not a DVD launcher.

Well, as I said, in conflicting entries, "
prefs" takes precedence on the HD launched MXM.

In reality, the MXM will not even be used on the HD launched MXM, only for the DVD-R Compilations, so once the System UI is done, and all of the settings can be made internally using dialogs, MXM may even complain, then rename the MXM.xml file, if need be.

...but that's off in the future at the moment.
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Config Question
« Reply #2 on: August 02, 2003, 06:42:00 AM »
QUOTE (onthereal @ Aug 2 2003, 10:37 AM)
Oh yeah... can I put the entries from the BIOSMD5.xml in the MXM.xml?

Not yet.  huh.gif

I'll work out something.... I was thinking about adding it internally, then having additions added either dynamically or manually.
Logged