Print

[BenJeremy]

QUOTE (Yuyu @ Jan 10 2004, 05:19 PM)

They are all the same brands, that why I think it just shows them as same MU number, otherwise I am not sure why it does not show up different... I have been inserting them as simultaneously as possible, and just comes up showing what I already posted...

Hmmm... that's not good. They should have different device names.

[BenJeremy]

QUOTE (Kthulu @ Jan 10 2004, 05:25 PM)

the controller is Mad Catz, but the mem is MS...i will switch to MS controller and MS mem... with no debugserver running... (looking with flashftp) G - contains only TitleMeta.xbx (this is MXM's TitleMeta.xbx) S - seems to be mapped to E:TDATA T - only contains MXM_State.xml U - contains: (MXM save stuff)  hosts.xml  pref.xml  TitleImage.xbx V - seems to be mapped to E:UDATA

The drives are correct, BTW.

[BenJeremy]

MXM is set up to handle up to 8 memory cards inserted (This is something you have to specify).

I might try playing with that here to see if I the device number changes.

It truly is strange if more than one inserted simultaneously results int he same device name.

[Kthulu]

QUOTE

The drives are correct, BTW.

so even with a mem card in that contains a Halo save, G is supposed to (for the moment) still point to somewhere on E: ?

[BenJeremy]

QUOTE (geniusalz @ Jan 10 2004, 03:18 PM)

What's with the debugserver eating 99% cpu when its idle but connected?

Well, I haven't dug into it to be sure, but I assume the original programmer screwed something simple up.

I'll fix it soon... I noticed that when I first started using the code (before I had a Debug BIOS)

[BenJeremy]

QUOTE (Kthulu @ Jan 10 2004, 05:42 PM)

QUOTE The drives are correct, BTW. so even with a mem card in that contains a Halo save, G is supposed to (for the moment) still point to somewhere on E: ?

Actually, it's pointing to the memory card. That 00004321 you see inthe insertion message is a path the Xbox creates on the memory card when I mount it using their APIs.

[BenJeremy]

By setting MXM to different "limits" I find, arbitrarily, that the Xbox has a limit of 7 controllers, and as I change the number the "MU_7" will change to whatever limit I set (except for - So if I limit it to 4, for example, I get "MU_4", while 6 gives a report of "MU_6"


I'm wondering if the memory cards resort through names... i.e. the last card is always MU_7, and the next plugged in causes the previous to change to MU_6 and the new one to MU_7.


So M$ cards also report MU_7... that fits my theory, at least. I may have it generate a slightly different report in an update tonight (reporting all drives paths on a memory card insertion).

[Kthulu]

ok, i guess my real point is this...

i have a Halo save on the card and i don't see the Halo save thru ftp...i only see the TitleMeta.xbx for MXM...

is that to be expected (for this WIP)?

[geniusalz]

Yeah

[BenJeremy]

QUOTE (Kthulu @ Jan 10 2004, 05:53 PM)

ok, i guess my real point is this... i have a Halo save on the card and i don't see the Halo save thru ftp...i only see the TitleMeta.xbx for MXM... is that to be expected (for this WIP)?

Yes.

The XBOX is setting the path when I use the Memory Card mounting routine. All drive letters are "virtual" - apps get a special mapping, but MMX does it's own thing normally. You can map a device, partition, and path to a drive letter. If I know the device name for sure, I can map the memory cards where I want to map them.

[BenJeremy]

I've upped a new "WIP" binaries update (no source update) with a small changein the way the memory unit stuff works.

Can YuYu check this out with multiple cards inserted at the same time?

[Kthulu]

sorry i was annoying yesterday.  i'm very curious if your theory turned out to be correct...the theory of mem cards resorting their device names...

[BenJeremy]

QUOTE (Kthulu @ Jan 11 2004, 11:40 AM)

sorry i was annoying yesterday.  i'm very curious if your theory turned out to be correct...the theory of mem cards resorting their device names...

Well, since YuYu hasn't gotten back to me on the multiple inserts with the new code, I'll have to run and pick up another memory card (that's OK, though... my son can use our original when going over to his friend's house to play Xbox there)

[yourwishismine]

QUOTE (BenJeremy @ Jan 11 2004, 11:45 AM)

I'll have to run and pick up another memory card (that's OK, though... my son can use our original when going over to his friend's house to play Xbox there)

Sh*t, wish I would have known you needed memory cards, I have 4 of them, of which I use zero... they just sit on my shelf looking stupid an being irritating...

Guess perhaps I'll use them in another contest...

[BenJeremy]

CODE

00:07:47.612 I3 SYS Memory Unit Insertion: H: (DeviceMU_60004321) 00:07:49.770 I3 SYS Memory Unit Insertion: H: (DeviceMU_60004321) 00:07:49.771 I3 SYS Memory Unit Insertion: I: (DeviceMU_50004321) 00:07:56.142 I3 SYS Memory Unit Insertion: G: (DeviceMU_50004321) 00:07:56.142 I3 SYS Memory Unit Insertion: H: (DeviceMU_60004321)

The logic changes, though when removals... If I have two cards inserted, and remove one, the last "name" removed becomes the first one available. I I remove MU_5, and reinsert it elsewhere, it becomes MU_5 again, but if I remove it, then MU_6, the next insertion becomes MU_6.

So it's rather complicated.

I'm not sure what might happen with 3 or 4, but I'll limit support to two memory cards at a time to force the issue. You shouldn't need to have more than 2 cards in at one time, anyway.