New Life Games LLC

**Video Poker, Keno, Slots, 21** Gaming machines => WMS Williams Video => Topic started by: igt66 on February 17, 2018, 02:58:23 PM

Title: USB OLED Firmware Mismatch
Post by: igt66 on February 17, 2018, 02:58:23 PM
Hello Everyone,

So I have not played WOZ Ruby Slippers in a while so decided to install the game again.
I am getting a USB OLED Firmware Mismatch so I am guessing that the firmware was upgraded when I installed a different OS/game.
So, can I just run a newer version of an OS that will work with Ruby Slippers or it looks like there is a program available to downgrade the firmware.
I am currently running Ruby Slippers with SSSG-000-1670 H13.21

Thanks for you help,
Steve
Title: Re: USB OLED Firmware Mismatch
Post by: idesign on February 17, 2018, 03:26:39 PM
Use a newer OS like SSSG-000-1696 or newer to update the firmware in your OLED deck
Title: Re: USB OLED Firmware Mismatch
Post by: igt66 on February 18, 2018, 12:52:46 PM
I was able to get it to work with SSSG-000-1693.
I have 16F0 and 16BB but they were giving me DSS partition errors.
Not sure what happened to them but I did back them up to my Windows 10 system with WinImage. I am not sure if that may have corrupted them.
WinImage does not seem to backup properly on a Windows 10 OS so I need to fid something else or go back to a Windows XP system.

Thanks for your help,
Steve
Title: Re: USB OLED Firmware Mismatch
Post by: idesign on February 18, 2018, 01:21:04 PM
Dont use winimage with windows 10, use Windows 7 or XP
Title: Re: USB OLED Firmware Mismatch
Post by: idesign on February 18, 2018, 01:50:00 PM
Also avoid using 16BB like the plague. That version of the OS has issues.
Title: Re: USB OLED Firmware Mismatch
Post by: rickhunter on February 18, 2018, 08:02:55 PM
Windows 10 with the creator's update will screw up your CF cards if you insert them into your PC.  Also writing out a card will also mess up the image, as the system will also screw it up after it's done.  The reason why it is doing this is because microsoft in their ever infinite wisdom decided to write a 4 byte code in the partition area of any device that is inserted into the system for reasons yet unknown to me.  Nevertheless, you can no longer successfully use windows 10 for winimage or any other image program.  It really sucks.  I would recommend you find an old laptop with windows 7 and NEVER upgrade it.
Title: Re: USB OLED Firmware Mismatch
Post by: igt66 on February 20, 2018, 10:24:55 AM
Windows 10 with the creator's update will screw up your CF cards if you insert them into your PC.  Also writing out a card will also mess up the image, as the system will also screw it up after it's done.  The reason why it is doing this is because microsoft in their ever infinite wisdom decided to write a 4 byte code in the partition area of any device that is inserted into the system for reasons yet unknown to me.  Nevertheless, you can no longer successfully use windows 10 for winimage or any other image program.  It really sucks.  I would recommend you find an old laptop with windows 7 and NEVER upgrade it.

Rick, thanks for information and at least I now know why. It looks like I have at least 6 cards that will need to be replaced.
Expensive lesson to learn and Thanks Microsoft!!
Title: Re: USB OLED Firmware Mismatch
Post by: Paladin on February 02, 2019, 02:59:53 PM
Windows 10 with the creator's update will screw up your CF cards if you insert them into your PC.  Also writing out a card will also mess up the image, as the system will also screw it up after it's done.  The reason why it is doing this is because microsoft in their ever infinite wisdom decided to write a 4 byte code in the partition area of any device that is inserted into the system for reasons yet unknown to me.  Nevertheless, you can no longer successfully use windows 10 for winimage or any other image program.  It really sucks.  I would recommend you find an old laptop with windows 7 and NEVER upgrade it.


Well, I wish I saw this post before I tried backing up a game! 
I decided I should make backups of the 3 games I have for my BB1.  I started with Village People Party since it came with the replacement MPU I purchased to get my machine up and running, and the game/OS appears to have been over written on cards from a different game anyway.  I figured I'd be safe as imaging software should never write to the original media.  I didn't take Windows 10 into consideration.


I should have done some more research, as I now cannot load that game.  I get "Prepart DSS signature validation with all keys failed.".  I'm able to run a clear and load the other 2 games, so it's definitely due to the media.


The good news is that I backed up and then tested one game so I could verify that I didn't mess anything up before I did the others.
The bad news is that Village People Party has turned into the wife's favorite game of the 3:(


Is there any way to edit the cards or image files to get them to work again, or am I stuck buying replacements?
Title: Re: USB OLED Firmware Mismatch
Post by: badlanding on February 04, 2019, 10:06:18 PM
I did the same thing with an OS card, backed it up with winimage on Windows 10 and had problems. I re-backed it up using winimage on my old Vista computer and it worked fine. Used the same CF card (an ancient OS card) both times.


Also my experience with the OLED firmware mismatch is that the button bootloader software needs to be updated. I did my OLED deck by installing Airplane with H13.471 (16CJ). This OS card automatically updates the button bootloader, you can see when it does it. No more OLED fw mismatch problems.
Title: Re: USB OLED Firmware Mismatch
Post by: Paladin on February 05, 2019, 12:07:51 PM
Thanks for the tip on trying to back up the cards on a different OS.  I don't have Win7 but I do have a laptop with XP.  I installed the 32bit version of Winimage on it and backed up the card again, still doesn't work.
Title: Re: USB OLED Firmware Mismatch
Post by: rickhunter on February 05, 2019, 12:16:09 PM
If you have already inserted the CF card into a windows 10 machine, it is already trashed.  You can't fix it by trying to back it up and restoring it back on a different version of windows (you would just be backing up a card that is already bad).  You will need to obtain a working image of the card.
SimplePortal 2.3.5 © 2008-2012, SimplePortal