MAMEHub 72 Live Updates On Vista Home 32-Bit

[teol]

This is what happens to me now every time. On both new updated versions every time and even reinstalling from the original 0.5 again which did work for troubleshooting previous updates but not this one.

Grrrrrr I WANT MY MAMEHUB BACK!!!!!!


Yes, this happens with Norton On or Norton Off. Our good old friend Norton doesn't make a difference with running this live update as I think I tried it once but it still failed on the update version before this V71.

This thing is making me feel very baffled and disgruntled about MAMEHub's live updating as it does to the end then crashes every time now.

I'm ported correctly and everything as you know I've been having a load of fun on 0.4 until 0.5 came along and messed me up and now I can never get a good update unless I'm extremely lucky on one of my re-installs and it works that time for about 1 day before a new live update comes and it always fails again.



I'm going to have one more go with Norton Off during the update now I think before giving up for today. Wish me luck because I am going to need it as the update really are hit and miss for me on 0.5 when I didn't have any updating problems on 0.4 ever.

Failed again, surprised I am not.

[Krusty]

TEOL, I appreciate that you went to the trouble of making a video to demonstrate what your issue was. After seeing the video, I think I'm starting to understand the issue you're experiencing.

svn is working as expected and updated the client. There is no need to reinstall MAMEHub with this problem you're experiencing.

The actual problem appears to be happening during the audit process. The mamehub.exe.log that was generated in your video is complaining about encountering a non-ascii unicode character in a path or filename somewhere. Specifically, it cites encountering the unicode character "u03b2".

u03b2 is the character code for "β". See here for more information on this character code.

Do you have the β character somewhere in your mamehub paths or rom filenames? That appears to be the problem.

---

postscript: What app did you use to record that video?


Update: I forgot to explain the next step. Assuming you do have the β character somewhere in your paths and have removed it then the next step would be to delete *.dmp from your mamehub\dist folder and then launch mamehub.bat. This will delete the auditing cache (with the bad character) and perform a fresh audit (just like when launching MAMEHub for the first time).

[teol]

All of my bios files are all standard English text format.

My rom location is like it always is.

F:Dan\Desktop\MAMEHub\roms

I do have the full bios set of both MAME and MESS in there.

If it's a problem with a bios what is the complete systems list compatible so I get rid of the rest which is probably the cause?

I presume the * means all the DMP files in that folder right?

Edit: I'm back on for now and all is working.

[digitalghost]

Sept 9, 2011 8:45:35 GMT -5 teol said:

All of my bios files are all standard English text format.

My rom location is like it always is.

F:Dan\Desktop\MAMEHub\roms

I do have the full bios set of both MAME and MESS in there.

If it's a problem with a bios what is the complete systems list compatible so I get rid of the rest which is probably the cause?

I presume the * means all the DMP files in that folder right?

Edit: I'm back on for now and all is working.

What did you do to fix this?

I'm thinking of upgrading to python 3.0. Python 2.X has unicode problems that are almost impossible to find and fix.

[Krusty]

Sept 12, 2011 17:13:20 GMT -5 digitalghost said:

What did you do to fix this?

I think he removed the entire MESS 0.143 BIOS ROM set from his audit paths.

---

Update:

The problem is actually in messROMs.xml on line 26718 for the fm16beta system. Here's how fm16beta looks in ansi form (text editor):



Here's how it's meant to look in something like MESSUI:

---

Extra:

The channelf.hsi hash has unicode characters and can produce similar errors if a user tries to audit the channelf software list. It is the only hsi file with unicode characters.

I have a fixed channelf.hsi in my hsi update pack I'm working on.

[teol]

Yeah. I would like that one hsi ASAP. I want my problems gone.

So I swap my channelf.hsi with the newer one you are uploading and stick fm16beta in a different folder or is fm16beta fixed?

[Krusty]

Sept 15, 2011 4:58:31 GMT -5 teol said:

Yeah. I would like that one hsi ASAP. I want my problems gone.

So I swap my channelf.hsi with the newer one you are uploading and stick fm16beta in a different folder or is fm16beta fixed?

Actually, the issue with channelf.hsi didn't really apply here. That issue will only manifest itself if one of the channelf software images with a unicode character in its description is present during auditing.

Removing fm16beta.zip would have solved your issue that prompted this post, but it is not a recommended option. MAMEHub Advisory 03 has the full details on the issue you experienced here.

Thanks again for posting about your issue with MAMEHub. The video was really helpful.