NEOSD MVS Support thread !

[Morden]

reset your backupRAM, I guess it has corrupted.

Thanks Raz. That did it. I'll have to check MotW and KoF '99 protection messages, but Shock Troopers 2 boots, finally. I'll do some more tests, but it would seem Shock Troopers 2 needs a clean reset to run. I erased backup RAM and booted up with Metal Slug 3. Flashed Shock Troopers 2 and got the exception. I reset the RAM with Shock Troopers 2 flashed and ready to go and it booted up right away.

 

[Razoola]

I suspect maybe there is something in the new firmware thats causing backupRAM to corrupt. neodev mentioned the saving works differently now.

 

[GadgetUK]

That crystal can is not grounded! Will try clearing the backup RAM and will re -test.

 

[neodev]

I suspect maybe there is something in the new firmware thats causing backupRAM to corrupt. neodev mentioned the saving works differently now.

Yes, the backup ram is handled differently now, but it was also happening before the new firmware so I guess it had corrupted somehow and it was saved that way to the sd so everytime it restored the bad backram.

About motw and kof99. Are you using unibios? If so, which region and mode (arcade or console) isconfigured in unibios?
If not using unibios, which region and mode (aes or mvs) is set in options?

 

[Morden]

About motw and kof99. Are you using unibios? If so, which region and mode (arcade or console) isconfigured in unibios?
If not using unibios, which region and mode (aes or mvs) is set in options?

I'm using Uni Bios 2.0 set to Japan / Arcade.

 

[GadgetUK]

Very odd! I just re-tested after Raz suggesting clearing the BRAM, and that works - so thanks for that =D. I don't use a battery and as a result each time I start using the MVS I would have expected it to be initialised - but maybe it doesn't do that itself? And I don't use the auto load / save thing, I only do it manually and didn't have a save for this game yet. After resetting the BRAM it seemed OK - played the first 3 opponents without any issues.

Morden, you might not need to do anything with that crystal, unless you are getting any CRC errors reported. For whatever reason I think those LP type crystals (the short small ones like you have), might not have the same issue the larger ones seem to have on the 1FZ. I have a 1FZ also with that type of crystal and that board is fine for me without grounding the can.

 

[Razoola]

The backupRAM selfchecks and reinits if its header is not found at power on (even if the hwcheck is disabled in unibios).

 

[Morden]

So, after testing this and that, this is how things work for me on the new firmware. I've disabled backup RAM saving in NeoSD, I reset the RAM via DIP switches, and this seems to help with the Shock Troopers 2 issue. However, since the firmware update, I'm having issues with MotW and KoF '99, both of which throw the same message at me: This ROM cartridge is for use with original SNK boards only (...)

If i reset the backup RAM before running KoF '99, it seems to work fine. I say seems, because I haven't played it all the way through, but MotW is just not having it. Once again, this issue was not present in the previous iteration of the firmware. So I guess that's something to look at, because setting the DIPs each time I want to run these is a pain, though not as much of a pain as removing the cartridge for each game change.

 

[GadgetUK]

The backupRAM selfchecks and reinits if its header is not found at power on (even if the hwcheck is disabled in unibios).

That's strange then, because that suggests after powering up from cold with no battery, it shouldn't have given me the protection message in MOTW? Could it be because I booted the game in MVS mode, then went into unibios and changed to AES mode?

The second time I tested later, I did the switch from MVS to AES first, then cleared the BRAM and it seemed OK.

 

[Razoola]

changing region may have played a part if there was no backram in place

 

[neodev]

That's strange then, because that suggests after powering up from cold with no battery, it shouldn't have given me the protection message in MOTW? Could it be because I booted the game in MVS mode, then went into unibios and changed to AES mode?

The second time I tested later, I did the switch from MVS to AES first, then cleared the BRAM and it seemed OK.

I've just realized that firmware doesn't include the latest backup ram code, it's just the plain retail firmware with a few fpga changes, but there is a change in the fpga that might be triggering the protection if they are doing a very specific check. GadgetUK, can you check if it also happens in your cart with retail firmware?

 

[MkidTrigun]

On my MV-1FZ, I'm running into the same issue with MOTW where it kicks me to the protection message after completing a single match - resetting the backup RAM either through DIPS or through the HW test cleared it out to let me try again, but still a no-go. I tried this on both USA-Arcade and USA-Console on UniBIOS 3.2, with my NeoSD running firmware received after mailing in about issues with it rebooting in the middle of the MOTW opening, and the backup RAM autosave turned off, as well as previous saves cleared from the microSD.

I ran through a full game of KOF'99 and didn't see the message appear at all, and my Shock Troopers 2 loaded and played fine (with a tiny exception of the 'four specialists' scrolling text during the opening not displaying correctly), but for MOTW the only 'variant' that worked more than one full match was the bootleg set.

I was running into some issues with Crossed Swords II where the graphics were all distorted and attempts to start the game ran into an exception, but acquiring another set to convert and re-adding it to the SD card seemed to make it work.

Would be willing to do some further testing tomorrow and Monday!

 

[GadgetUK]

On my MV-1FZ, I'm running into the same issue with MOTW where it kicks me to the protection message after completing a single match - resetting the backup RAM either through DIPS or through the HW test cleared it out to let me try again, but still a no-go. I tried this on both USA-Arcade and USA-Console on UniBIOS 3.2, with my NeoSD running firmware received after mailing in about issues with it rebooting in the middle of the MOTW opening, and the backup RAM autosave turned off, as well as previous saves cleared from the microSD.

I ran through a full game of KOF'99 and didn't see the message appear at all, and my Shock Troopers 2 loaded and played fine (with a tiny exception of the 'four specialists' scrolling text during the opening not displaying correctly), but for MOTW the only 'variant' that worked more than one full match was the bootleg set.

I was running into some issues with Crossed Swords II where the graphics were all distorted and attempts to start the game ran into an exception, but acquiring another set to convert and re-adding it to the SD card seemed to make it work.

Would be willing to do some further testing tomorrow and Monday!

Have you checked you've not got the automatic BRAM load / save enabled? Because despite you clearing your BRAM, if auto load is on it could be loading a corrupt BRAM save back over the cleared BRAM - if that makes sense?

 

[GadgetUK]

I've just realized that firmware doesn't include the latest backup ram code, it's just the plain retail firmware with a few fpga changes, but there is a change in the fpga that might be triggering the protection if they are doing a very specific check. GadgetUK, can you check if it also happens in your cart with retail firmware?

Just to be clear - is the retail firmware the version I've not updated to the very latest version? I will test on both shortly.

 

[MkidTrigun]

Have you checked you've not got the automatic BRAM load / save enabled? Because despite you clearing your BRAM, if auto load is on it could be loading a corrupt BRAM save back over the cleared BRAM - if that makes sense?

I do have that feaure disabled, and the BUP folder has been cleared from my microSD.

Trying it again today, decided to put the NeoSD into Arcade Mode and take out the microSD with Garou flashed onto it, to then try out from varying states (soft/hard resets, different regions, resetting/not resetting Backup RAM) to see if I could track what worked and what didn't, and the results are... rather inconsistent.

For example, having UniBIOS set on USA/CONSOLE before boot, I tried to play it from startup but ran into the screen before the first match. Soft reset from the UniBIOS menu, held BCD to get to Test Mode and reset my Backup RAM from there, and another Soft Reset from that screen. Load up the game, was able to play the first match then got the screen.

I then turned off the unit, waited 5 seconds to turn it back on to walk through what I just did to confirm, and I was able to play the first match without touching the Backup RAM. Did it once more, and it behaved like it did before, not letting me play the first match. I then walked through the same steps as the first attempt and I was still greeted with the screen before my first matchup.

At this point, I'm wondering if there's any issues with my MVS board that could be causing this. I will be able to test the NeoSD in another MVS on Tuesday to see if the same thing happens on that setup, or if it behaves regularly.

 

[Morden]

At this point, I'm wondering if there's any issues with my MVS board that could be causing this. I will be able to test the NeoSD in another MVS on Tuesday to see if the same thing happens on that setup, or if it behaves regularly.

I'm almost certain it's not your MVS. I started having these issues after updating to the latest firmware which fixes the reset loop [which I assume isn't the retail firmware, and doesn't contain the latest backup RAM code, as mentioned by neodev]. I too get random results, and the protection might trigger on the first or second round. Also, before I wiped backup RAM, which apparently was corrupted and caused Shock Troopers 2 to crash, MotW was setting itself to difficulty level 1 and 1 round per fight. Weird.

 

[MkidTrigun]

Also, before I wiped backup RAM, which apparently was corrupted and caused Shock Troopers 2 to crash, MotW was setting itself to difficulty level 1 and 1 round per fight. Weird.

I had that happen to me as well! Also, just to do a check on it, when I went in after resetting the Backup RAM to check the soft dip settings, I came across this-
http://imgur.com/5BDefrp

Is this supposed to happen after doing a soft reset after resetting the Backup RAM?

Edit: Tested this several times with and without HW tests enabled, I guess I'm not giving the system enough time to read the cart after the Backup RAM is reset.

In running further tests, I figured out that the DEMO CUT option in AES mode disables the scene transitions and cutscenes when enabled, and that's been allowing me to play the game without the warning screen ever appearing. It's a nice workaround for the time being.

 

[neodev]

I had that happen to me as well! Also, just to do a check on it, when I went in after resetting the Backup RAM to check the soft dip settings, I came across this-
http://imgur.com/5BDefrp

Is this supposed to happen after doing a soft reset after resetting the Backup RAM?

Edit: Tested this several times with and without HW tests enabled, I guess I'm not giving the system enough time to read the cart after the Backup RAM is reset.

In running further tests, I figured out that the DEMO CUT option in AES mode disables the scene transitions and cutscenes when enabled, and that's been allowing me to play the game without the warning screen ever appearing. It's a nice workaround for the time being.

We think we have found the issue. We are testing a new firmware right now with that fixed, we'll contact you both shortly with updated firmware.

 

[Morden]

We think we have found the issue. We are testing a new firmware right now with that fixed, we'll contact you both shortly with updated firmware.

Nice! Here's to hoping it's the last time I'll be seeing those disclaimer messages, because aside from the Shock Troopers 2 issue [which hopefully won't be coming back to haunt me], that's the last obvious thing that needed fixing.

Any idea when a new retail firmware with all the fixes and the jukebox function will be released? Just curious. No pressure.

 

[neosd]

Nice! Here's to hoping it's the last time I'll be seeing those disclaimer messages, because aside from the Shock Troopers 2 issue [which hopefully won't be coming back to haunt me], that's the last obvious thing that needed fixing.

Any idea when a new retail firmware with all the fixes and the jukebox function will be released? Just curious. No pressure.

Patience, we canï½´t give you a date cause it deppends on so many things.

The time we spend adressing issues that are not real issues, but hardware problems : dirty cartridge slot, bad psu, bad psu connectors, bad neogeos.

The time we spend addressing real issues : this issue that only happens on beta firmware that we sent to users with issues.



Honestly, everytime an email arrives with : regular cartridges work, there is an issue on my neosd, i remember about SD2SNES FAQ :

I really recomend reading it, based on my own experience, it answers to 90% of the emails/issues we get.

Q5: My sd2snes doesn稚 seem to run reliably. A large number of games crash at random, or the sd2snes doesn稚 boot up at all.

A5: One of the following could be the case:

Weak capacitors in your SNES: The sd2snes draws more power than a normal game cartridge (and the Super Everdrive or Powerpak, for that matter). Weak capacitors in the power section of the SNES may cause the console to crash. Try another SNES or, if you feel like it, have the caps replaced.

Faulty power brick: The external power supply of the SNES doesn稚 provide properly stabilized power, or the voltage has dropped. Try using a different power brick.

Dirty slot contacts: The sd2snes is more timing sensitive than a normal game cartridge. If the slot contacts are dirty it might introduce enough resistance to delay the signals coming from the SNES, or going to the SNES, enough to make it crash. Clean the slot contacts on the SNES and the sd2snes thoroughly and retry.

Freak SNES: Some consoles exhibit strange timing behaviour or excessive address line noise. Try another console.

Freak SD Card: Some SD Cards might draw excessive power or exhibit other strange behaviour. Try another card.

Faulty SNES: The SNES itself might be at fault. Verify that original game cartridges run properly on your SNES.

So resuming :
Issues afecting one or two users are delaying software updates.
We decided to spend time achieving 100% compatibility with every neogeo board (not board revision, different boards from the same revision), instead of telling this 0,05% of the user base : get another board such as the SD2SNES guys are doing.


This takes a lot of time and work.

Patience please.

 

[fenikso]

I was having problems with RotD and SvC randomly resetting. Thoroughly cleaned the contacts on my MVS1FS this morning and they now play flawlessly. Clean yo' stuff people (mostly directing this at myself )

I can't tell you guys enough how awesome your product is.

 

[neosd]

I was having problems with RotD and SvC randomly resetting. Thoroughly cleaned the contacts on my MVS1FS this morning and they now play flawlessly. Clean yo' stuff people (mostly directing this at myself )

I can't tell you guys enough how awesome your product is.

Hello, most of the issues are caused by dirty slot connector and for bad contacts on the psu connectors aswel.
I am talking from my own experiences, as user i have suffered from both of those.
From the support experience i can tell the same.

Anyways, we have just sent a firmware update to GadgetUK with Garou fix, based on our experience he is pretty good finding issues, so be patient, we are working on it.

Thanks

 

[Rot]

Anyways, we have just sent a firmware update to GadgetUK with Garou fix, based on our experience he is pretty good finding issues, so be patient, we are working on it.

Thanks

NG.com... the home of the ultimate nerd base...

GadgetUK is helping making the firmware pretty solid... can't complain man

xROTx

 

[GadgetUK]

Hello, most of the issues are caused by dirty slot connector and for bad contacts on the psu connectors aswel.
I am talking from my own experiences, as user i have suffered from both of those.
From the support experience i can tell the same.

Anyways, we have just sent a firmware update to GadgetUK with Garou fix, based on our experience he is pretty good finding issues, so be patient, we are working on it.

Thanks

Thanks! Dropped you an email - still testing at the moment but it looks fine to me! I had the issue straight away before the update (just after 1 round). After applying the update I managed to play several rounds without issue, and that was without resetting my BRAM or doing anything manual to try and remedy the problem. So it looks like the fix to Garou works. Tested a number of other games (KoF2003, Magician Lord, Shock Troopers, Metal Slug 5) and everything looks good so far! =D

NG.com... the home of the ultimate nerd base...

GadgetUK is helping making the firmware pretty solid... can't complain man

xROTx

Thanks lol =D I think the general consensus is - if it works on my 1FZ, it will probably work on any one slot lol.

 

[neosd]

Thanks lol =D I think the general consensus is - if it works on my 1FZ, it will probably work on any one slot lol.

Big thanks to you Gadget, you have been helping us so much for the last months, we really apreciate that. And yes, i agree that if it works in your setup it should work on any 1FZ