Print

[fiscus]

I just installed V71.1b abd whenever I am playing a ROM and i press back and start (to exit the game) the XBOX just hard locks and I have to turn the machine off and then on.

As far as I can see no one else is having this issue - and ideas?

EDIT: sorry about that, after being a little more PATIENT i realised that the screen was just pausing/freezing and then it eventually would go back to the menu. Does it normally take a little while for it to exit the game and go back to the Mame-ox UI???

Thanks

[noodle1009]

For some people yes, for some people, no.  You seem to be one of the unfortuante people that has to wait 30 seconds to get back to the romlist.

I only have to wait a maximum of 5 seconds.  Since none of the developers or people on the mameox team can reproduce this problem, we're kinda stuck for fixing it.  You would think with the number of people encountering this problem though, someone would have found a fix for it.

Could you post the following for me:

1.  Version of xbox (1.0, 1.1, 1.2)
2.  Modchip type
3.  Bios you are using (IGR on, IGR off, ect)
4.  Dash you are using
5.  Original or replacement HD, what kind of HD (i.e. 120 GB WD)
6.  How are you launching MAMEoX (XBMP?  EvoX?)

Thanks in advance.

[fiscus]

Ok - well atleast I am not alone.

1. Version of xbox = 1.1
2. Modchip type = Executer2
3. Bios you are using (IGR on, IGR off, ect) = Executer 4977 IGR on
4. Dash you are using = I am using MXM and launching from MXM
5. Original or replacement HD, what kind of HD (i.e. 120 GB WD) = You got it - WD 120gb 7200rpm 8mg cache
6. How are you launching MAMEoX (XBMP? EvoX?) = Launching from MXM

Hope this heaps - it does seem a very strange problem.

[Havok1210]

Hey noodle i posted on mame ox forum yest with a list of games that worked on the last release but appear broken on this one=
Cabal (says files are missing)
Double dragon 2 (says files are missing)
Karnov revenge (says files are missing)
NAM 1975 (says files are missing)
Rainbow islands extra (Crashes)
The newzealand story (crashes)
Ultimate tenis (Crashes)
Vigilante (Crashes)
Yei ar kung fu (Crashes)

Did u report these or shall i repost each idividually?
Im 99% sure all these were workin before the update

[fiscus]

Thanks for the info - I'll give some of those things a shot and see how I got.

Could it be anything network related?

I'll post back once I have done some testing.

[splattered]

double dragon 1-3 work on my mameox 71.1b ... what version of mame32 roms do you have? maybe ya need to update some? dunno...

[noodle1009]

QUOTE (Havok1210 @ Jul 11 2003, 02:55 PM)

Hey noodle i posted on mame ox forum yest with a list of games that worked on the last release but appear broken on this one= Cabal (says files are missing) Double dragon 2 (says files are missing) Karnov revenge (says files are missing) NAM 1975 (says files are missing) Rainbow islands extra (Crashes) The newzealand story (crashes) Ultimate tenis (Crashes) Vigilante (Crashes) Yei ar kung fu (Crashes) Did u report these or shall i repost each idividually? Im 99% sure all these were workin before the update

Yeah, that was me  Sorry, I didn't mean to be a pain, and we _really_ appreciate the bug reports, trust me.  Very soon we will have a new system for reporting them that will make it a _lot_ easier to do as well - the problem is right now that some of the roms you list might not start for different reasons, and depending on what those reasons are, Erik might have to change the priority of fixing it.  That, and it makes it easier for those people who are checking to see if there is a bug reported already if they can see it on the subject line.

Here is something that might help you out from the mameox faq:

QUOTE

Q.  How do I post a bug report? A.  We're glad you asked   Bugs can be posted on the Sourceforge website      under the subheading, 'bugs'. If you take the time to post a "good"      report, it both saves the dev team a _lot_ of time (you'd be surprised      how quickly the time spent reading through bug reports adds up when      you need to open and read 50), and makes your bug a better candidate      for developer attention. Bad reports make it much harder for us to      find and fix the problems, and often take up time that we would      otherwise spend fixing problems or adding features.      Here are some tips:    1.  Make sure you've looked at the pending and closed bug reports             before posting your bug.  Duplicate bug reports are annoying             and time consuming to process, even if we ignore it. You can             see these "hidden" reports by switching the "status" option             on the bug page to "any".         2.  Please post the following if you're posting a bug related to             a specific game:   - Game name  (for example, Mortal Kombat)   - Rom name   (for example, mk.zip)   - Rom bios   (for example, neogeo.zip)   - Size  (please list size in zipped / unzipped)   - Post the problem in the subject with the game title     (for example, Mortal Kombat - out of memory)   - Post a brief description of the problem in your     comments   - Assign bug to eabair    3.  All other bugs should follow in principle the above format             as it would apply to the bug you are reporting.  In general             please post a short description if possible in the subject      line so we have an idea of what the bug is before we read             further. This allows us to prioritize bugs without eating up             alot of time, which allows the overall development to move             along much faster.    4.  Please, only post one bug per report.  Do not report             multiple nonworking games in one bug report.  Please do not             report multiple bugs in one bug report.  Split them up as      each bug is assigned a priority. Failing to do this will             often result in us missing bugs, as only the first item             mentioned in the report will be worked on.    5.  It always helps us if you're having a problem using MAMEoX      if you respond to the forum topic on Sourceforge entitled,      'Poll for info about user's X-Box' so we know what your      setup is (very useful as sometimes we can not duplicate             problems). If you don't do this, you'll probably just get             a reply from the team asking you to provide this info before             we can even start looking into it.                     6.  Lastly, please keep in mind that MAMEoX is a port of MAME.             any problems that are in the MAME core will likely be             present in MAMEoX.  There is not much we can do about this.             Please check the rom in Mame32 or your favorite 'flavor' of             MAME prior to reporting a bug with a rom in MAMEoX.  It is             unlikely that we will fix a bug that is present in the             MAME core.

Erik spends a lot of time looking at bugs that are duplicates, or not bugs at all.  This cuts into the time he needs to make MAMEoX better, so any time we can shave off that helps immensely!

On a sidenote, can you check NAM 1975 again, I remember that one in your list seemed strange because it was a neogeo game, and most of those have been problem free.  I checked it in the cvs build I have and it loads without problems.  Can you check it one more time for me?

[noodle1009]

QUOTE (fiscus @ Jul 11 2003, 03:07 PM)

Thanks for the info - I'll give some of those things a shot and see how I got. Could it be anything network related? I'll post back once I have done some testing.

do you use samba shares?  In the currently released build I don't believe it makes a difference if network is enabled or disabled, it's always loaded up by default.  I don't _think_ the problem is there...but you never know

I suspect it's a problem either 1.  reloading the launcher or 2.  loading up the romlist.