xboxscene.org forums

Pages: 1 [2] 3 4 ... 13

Author Topic: Mxm 0.9n.5  (Read 348 times)

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Mxm 0.9n.5
« Reply #15 on: September 26, 2003, 03:29:00 AM »

QUOTE (diffident @ Sep 26 2003, 05:58 AM)
QUOTE
Everytime I log into my XBOX, it looks like a file is being left in every folder I visit with a weird name. The name changes, but it can be a folder with the name "Close..." or a shortcut with what looks like a high ascii character.
...
Anyway, about the FTP thing, I'm using Windows Explorer. I have my XBOX setup as a networked drive on my computer. The weird file thing doesn't happen in CuteFTP, so maybe the new release doesn't react well with Windows Explorer/Internet Explorer.

BJ, this sounds like the mystery file 's' problem I saw when testing WIP - the 'extra' files are visible via Explorer and WS_FTP on XP. Under OSX, they're not visible in the GUI, but show up in transcripts via Interarchy and Transmit. As DeVante says, these files turned up in every folder I opened under WIP. They're not visible (or logged in transcripts) when I move back to 0.9n4 or XBMP's FTP server, whatever the client; that suggests to me that they're not 'real' files created in the filing system, but something less tangible.

Well, if I can recreate the problem, I should be able to fix it. I will check the IE interaction.
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Mxm 0.9n.5
« Reply #16 on: September 26, 2003, 03:31:00 AM »

QUOTE (Xombe @ Sep 26 2003, 07:07 AM)
I've got an FTP issue, using FlashFXP as always.  Upon upgrading to 0.9n.5 by copying over the old xbe, my FTP isn't what it used to be.  Specifically, it sporadically hangs when I try to edit a file on the Xbox by right-clicking it and selecting 'Edit.'  Until now, it would open the file (in this case menu.xml or the like) and I could make my changes, save it, and press OK to transfer the updated file back over the old.

But now, when I click 'Edit', FXP goes through the motions but hangs short of opening the file.  It displays the usual:

257 "/C/" is current directory.
List (cached)
List Complete.
TYPE I
200 Mode is set to I.
PORT 192,168,11,2,10,167
200 PORT command successful.
RETR menu.xml
150 Opening BINARY mode data connection for file transfer.
226 Transfer complete.

but so-called 'transfered file' doesn't open.  After that, FXP just sits there, not responding.  If I disconnect, I can't connect again until I reboot MXM (running in dash mode).

It also tends to hang when moving amongst folders sometimes.  Or when uploading games.  Performance seems to degrade with use during a single session.  Anybody else?

Otherwise, thank you again, BJ, for a wonderful creation!

Hmmmm.... possibly related to the other issue, and it does give me a clue. According to your log, MXM thinks it's sent the file.
Logged

thetruethugg

  • Archived User
  • Sr. Member
  • *
  • Posts: 432
Mxm 0.9n.5
« Reply #17 on: September 26, 2003, 03:46:00 AM »

QUOTE (BenJeremy @ Sep 26 2003, 06:26 AM)
QUOTE (Telemachus @ Sep 26 2003, 02:19 AM)
So would there be a way to add a script that can enable/disable the X2 IGR?

Great stuff BenJ!

That should be a cinch with ActionScripting....

Yea, that would be cool.  The script could see if the file is named "x2_IGR_disabled", and if so, rename it to something like "x2_IGR_disabled_OFF", and if already named "x2_IGR_disabled_OFF", it could rename it back to "x2_IGR_disabled".
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Mxm 0.9n.5
« Reply #18 on: September 26, 2003, 04:45:00 AM »

QUOTE (thetruethugg @ Sep 26 2003, 07:46 AM)
QUOTE (BenJeremy @ Sep 26 2003, 06:26 AM)
QUOTE (Telemachus @ Sep 26 2003, 02:19 AM)
So would there be a way to add a script that can enable/disable the X2 IGR?

Great stuff BenJ!

That should be a cinch with ActionScripting....

Yea, that would be cool.  The script could see if the file is named "x2_IGR_disabled", and if so, rename it to something like "x2_IGR_disabled_OFF", and if already named "x2_IGR_disabled_OFF", it could rename it back to "x2_IGR_disabled".

Something like:

CODE


SETFUNC IGRSTAT FILEEXISTS E:\x2_IGR_disabled
IF %IGRSTAT% != 1 GOTO DISABLEIT
RENAME E:\x2_IGR_disabled E:\x2_IGR_enabled
MessageBox "X2 IGR Enabled"
GOTO END
:DISABLEIT
SETFUNC IGRSTAT FILEEXISTS E:\x2_IGR_enabled
IF %IGRSTAT% != 1 GOTO NOFILE
RENAME E:\x2_IGR_enabled E:\x2_IGR_disabled
MessageBox "X2 IGR Disabled"
GOTO END
:NOFILE
MessageBox "Unable to switch.$eol$E:\\x2_IGR_disabled not present"
:END



I might be leaving something out.... the next release will have file read/write routines, so the error message will not be needed then.
Logged

Nathan561

  • Archived User
  • Full Member
  • *
  • Posts: 222
Mxm 0.9n.5
« Reply #19 on: September 26, 2003, 08:19:00 AM »

sad.gif
When switching to PAL mode so that 50hz games would play HDTV was disabled and i was plunged into blackness.

As well as a Force PAL60 mode, is it possible, however wierd to add a "FORCE NTSC 50hz" ?  That would solve ALOT of problems for use VGA users playing PAL games.

Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Mxm 0.9n.5
« Reply #20 on: September 26, 2003, 08:27:00 AM »

QUOTE (Nathan561 @ Sep 26 2003, 12:19 PM)
It turns out that the PAL/NTSC switching didn't fix my problem sad.gif
When switching to PAL mode so that 50hz games would play HDTV was disabled and i was plunged into blackness.

As well as a Force PAL60 mode, is it possible, however wierd to add a "FORCE NTSC 50hz" ?  That would solve ALOT of problems for use VGA users playing PAL games.

I'm afraid there's no such beast...

Sorry. I think the only solutio for you would be had-coded patches in the game.
Logged

Ces2k3

  • Archived User
  • Sr. Member
  • *
  • Posts: 462
Mxm 0.9n.5
« Reply #21 on: September 26, 2003, 09:03:00 AM »

IS THIS GONNA  be the way mxm gonna run (action menu)? or will it go back to the other way i really dont like it but oh well i guess i need to adapt
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Mxm 0.9n.5
« Reply #22 on: September 26, 2003, 09:35:00 AM »

QUOTE (Ces2k3 @ Sep 26 2003, 01:03 PM)
IS THIS GONNA  be the way mxm gonna run (action menu)? or will it go back to the other way i really dont like it but oh well i guess i need to adapt

There no change for the "old" way.. ActionScripts are new, additional ways of doing things.

Mini-programs.
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Mxm 0.9n.5
« Reply #23 on: September 26, 2003, 09:37:00 AM »

QUOTE (Cherry @ Sep 26 2003, 01:12 PM)
QUOTE (BenJeremy @ Sep 26 2003, 05:27 PM)
QUOTE (Nathan561 @ Sep 26 2003, 12:19 PM)
It turns out that the PAL/NTSC switching didn't fix my problem sad.gif
When switching to PAL mode so that 50hz games would play HDTV was disabled and i was plunged into blackness.

As well as a Force PAL60 mode, is it possible, however wierd to add a "FORCE NTSC 50hz" ?  That would solve ALOT of problems for use VGA users playing PAL games.

I'm afraid there's no such beast...

Sorry. I think the only solutio for you would be had-coded patches in the game.

Hey BJ.

This is interesting, and something I hadn't thought of before. Shame I don't have a HDTV to test this stuff. But maybe it's possible... can't say for sure until I look into it.

I did, however, manage to find the time to add support for Debug Kernels last night - I need to do some testing first, but expect an updated code snippet soon...

Awesome!

And I do have a means for testing HDTV now (X-Blaster HDTV->VGA), so ideas would be cool.
Logged

tutu

  • Archived User
  • Full Member
  • *
  • Posts: 218
Mxm 0.9n.5
« Reply #24 on: September 26, 2003, 12:06:00 PM »

smile.gif

I re-used my MXM.xml which worked fine with the previous release btw
Logged

Xzigx

  • Archived User
  • Full Member
  • *
  • Posts: 208
Mxm 0.9n.5
« Reply #25 on: September 26, 2003, 01:08:00 PM »

QUOTE (DeVante @ Sep 26 2003, 12:47 AM)


2) I didn't like MxM picking up the descriptions on its own (usually company names), so I found out a way to leave them blank by putting <DESCR> </DESCR> in the ITEM node. Notice the space. This worked and MxM would use the blank instead of figuring out the description on its own. It looks like this no longer works.


another way to do this is to simply edit the menu node in the SKIN xml and remove the secondary descript line from the menu completely.  It used to work anyway, don't know about now
Logged

incansun

  • Archived User
  • Full Member
  • *
  • Posts: 109
Mxm 0.9n.5
« Reply #26 on: September 26, 2003, 02:44:00 PM »

I'm not sure if you addressed the issue with the menu.xml and or cache_menu.xml not auto loading games on this new version.  I know that In your previous version of MXM, it did not recognize the autodir line that I hard coded into the menu.xml file to find recently backed up games on my hard drive. Well, technically  it did but it duplicated all my games and included the demos as well (even though, I had disabled demos through the config menu). Don't get me wrong, your dash rocks! however, I would not recommend this dash to a beginner because of the fact that it  does not  auto add new game on its own w/o running it in default mode w/o any  picture or video previews. Which, in my opinion, makes a huge difference! I can show you my menu.xml file if you'd like, there is another thread on these boards that addresses the same issue with other users that have experienced the same  exact problem (Menu.xml thread). It's a pain configuring these menus and even worse for newcomers to comprehend. This is the line that I used where F:hddloader are where my games are stored. I hope that this new version resolves this issue.

<Item>
<AutoDir>F:HDDLoader</AutoDir>
</Item>

Btw, thanks for all your hard work, ill be sure to visit your tip jar.
Logged

BenJeremy

  • Archived User
  • Hero Member
  • *
  • Posts: 5645
Mxm 0.9n.5
« Reply #27 on: September 26, 2003, 02:46:00 PM »

QUOTE (incansun @ Sep 26 2003, 06:44 PM)
I'm not sure if you addressed the issue with the menu.xml and or cache_menu.xml not auto loading games on this new version.  I know that In your previous version of MXM, it did not recognize the autodir line that I hard coded into the menu.xml file to find recently backed up games on my hard drive. Well, technically  it did but it duplicated all my games and included the demos as well (even though, I had disabled demos through the config menu). Don't get me wrong, your dash rocks! however, I would not recommend this dash to a beginner because of the fact that it  does not  auto add new game on its own w/o running it in default mode w/o any  picture or video previews. Which, in my opinion, makes a huge difference! I can show you my menu.xml file if you'd like, there is another thread on these boards that addresses the same issue with other users that have experienced the same  exact problem (Menu.xml thread). It's a pain configuring these menus and even worse for newcomers to comprehend. This is the line that I used where F:hddloader are where my games are stored. I hope that this new version resolves this issue.

<Item>
<AutoDir>F:HDDLoader</AutoDir>
</Item>

Btw, thanks for all your hard work, ill be sure to visit your tip jar.

That's strange. Nothing's changed for that stuff.

I'll take a look at it.  blink.gif
Logged

DeVante

  • Archived User
  • Full Member
  • *
  • Posts: 110
Mxm 0.9n.5
« Reply #28 on: September 26, 2003, 08:56:00 PM »

QUOTE (Xzigx @ Sep 26 2003, 10:08 PM)
QUOTE (DeVante @ Sep 26 2003, 12:47 AM)


2) I didn't like MxM picking up the descriptions on its own (usually company names), so I found out a way to leave them blank by putting <DESCR> </DESCR> in the ITEM node. Notice the space. This worked and MxM would use the blank instead of figuring out the description on its own. It looks like this no longer works.


another way to do this is to simply edit the menu node in the SKIN xml and remove the secondary descript line from the menu completely.  It used to work anyway, don't know about now

This would also disable any descriptions I put in manually, wouldn't it?

I don't want that. :/

Under the main node in mxm.xml: <AUTODESCR>False</AUTODESCR>

That's all I need! ;>

Well for now fortunately my skin makes single periods very hard to see, so I can just put a period in. Maybe I can mess around with the font and make one of the odd characters (like ^) be blank. Still, it would show up in other skins. :/
Logged

geniusalz

  • Archived User
  • Hero Member
  • *
  • Posts: 1635
Mxm 0.9n.5
« Reply #29 on: September 26, 2003, 09:49:00 PM »

I don't know how MXM supports this:
But in windows, Alt+0160 makes a space-like character that isn't really a space.

Try it if you want, but no guarantee that it won't mess up stuff.
Logged
Pages: 1 [2] 3 4 ... 13