Konami Viper - Repair - NETWORK CHECK

I don't think it'll be a problem that it was a code one dispatch


besides the Jurassic park, you needed a Warzaid as well? Any CF cards to go with or are you good?

I have JP3 CF (and RTC), so I would just need the JP3 NVRAM.

I don't have a CF for Warzaid, I would need both the CF and the NVRAM.

I have an extra CF I could flash it onto if you have a working image you could send me.
 
I have JP3 CF (and RTC), so I would just need the JP3 NVRAM.

I don't have a CF for Warzaid, I would need both the CF and the NVRAM.

I have an extra CF I could flash it onto if you have a working image you could send me.


go ahead and PM, let's discuss
 
Hi everybody,

I have the same problem on my Warzaid 4 players Cab.



My Viper system version is AAD:B and my flash card is C22D02



My 2 RTC are Bad! I have changed and reprogrammed with navram u39 from Mame file.

Now RTC is '' ok'' at the screen but then I have network check and then ''network bad'' with code 2-1010-0000



I have tested with Other Mame file (world combat AAD alt, UCD) and I have the same problem.



Please help.



Thanks
 

Attachments

  • IMG_20201208_092825.jpg
    IMG_20201208_092825.jpg
    3.6 MB · Views: 6
Hi everybody,

I have the same problem on my Warzaid 4 players Cab.



My Viper system version is AAD:B and my flash card is C22D02



My 2 RTC are Bad! I have changed and reprogrammed with navram u39 from Mame file.

Now RTC is '' ok'' at the screen but then I have network check and then ''network bad'' with code 2-1010-0000



I have tested with Other Mame file (world combat AAD alt, UCD) and I have the same problem.



Please help.



Thanks
Check the dips on both pcbs. PCB 1/Left has to have all DIPS off and PCB 2/right has to have DIP 2 on and all others off. This switch supposedly determines the network ID and both have to be different.
 
Check the dips on both pcbs. PCB 1/Left has to have all DIPS off and PCB 2/right has to have DIP 2 on and all others off. This switch supposedly determines the network ID and both have to be different.
Thank you for your reply.

I have that but not working
 
After a few minutes and several rebooting I have this message only on the first system
 

Attachments

  • IMG_20201209_173137.jpg
    IMG_20201209_173137.jpg
    3.5 MB · Views: 13
After a few minutes and several rebooting I have this message only on the first system
Ouchies. This is within the ethernet related board. The timekeeper for this game is probably meant to store network (not LANC) info to connect for a server (possibly eAmuse) for competition and leaderboards. I wonder what happens if you hold the test button down while booting up the system (since there is only one test button and it's connected to PCB 1; also if that button is pressed, both pcbs go in test mode).
 
Ouchies. This is within the ethernet related board. The timekeeper for this game is probably meant to store network (not LANC) info to connect for a server (possibly eAmuse) for competition and leaderboards. I wonder what happens if you hold the test button down while booting up the system (since there is only one test button and it's connected to PCB 1; also if that button is pressed, both pcbs go in test mode).
When I press test button for the first PCB and I link GND to jamma pin test for PCB2 I have '' initializing RTC memory'' for both,
Only this.
 
When I press test button for the first PCB and I link GND to jamma pin test for PCB2 I have '' initializing RTC memory'' for both,
Only this.
I suggest not linking gnd to jamma test for pcb 2 because pcb 2 was never programmed to go into test mode. RTC data for pcb 2 will be refreshed as that is SPECIFICALLY linked to pcb 1. I'd reset and hold test ONLY for pcb 1 while booting both pcbs.
 
I suggest not linking gnd to jamma test for pcb 2 because pcb 2 was never programmed to go into test mode. RTC data for pcb 2 will be refreshed as that is SPECIFICALLY linked to pcb 1. I'd reset and hold test ONLY for pcb 1 while booting both pcbs.
OK thanks, tomorrow I will test it.
Hope this will work.

You think the problem is not RTC file?
 
OK thanks, tomorrow I will test it.
Hope this will work.

You think the problem is not RTC file?
The problem is within the RTC only because the MAC address stored on the timekeeper doesn't match the one hardwired on the network interface hardware, a W3100a. Konami themselves had initialize the RTC with the correct MAC address from the factory which was why I suggested to initialize the RTC. If that doesn't work, then Konami must have manually programmed the RTC themselves out of the factory and fixing this would only be a matter of finding the MAC address is stored on the timekeeper.

Honestly, I didn't know that "network check" for this game meant its actual ethernet related hardware as opposed to communications with another pcb (in this case, LANC check). Rather a devious form of protection if you ask me. Extreme Hunting 2 also did something similar where the game has to boot with a network board, regardless if its connected to the internet or not, but without having to store the MAC address on nonvolatile ram.
 
Hi, good news
Now my Warzaid 4p is 100% working!!!

I have find the good files u39 Nvram (UAA:B) on Mame source.

Now it's all right, thank you very much for all.
 

Attachments

  • IMG_20201210_180516.jpg
    IMG_20201210_180516.jpg
    3.1 MB · Views: 4
Hi, good news
Now my Warzaid 4p is 100% working!!!

I have find the good files u39 Nvram (UAA:B) on Mame source.

Now it's all right, thank you very much for all.
(Darn, you aren't located in the U.S.) I'm glad this worked out in the end but a "UAA:B" doesn't exist. You probably used "AAD:B" used in the parent set on Mame source. It turns out my prediction of the game storing MAC address related data on the timekeeper may have been incorrect. I am now interested to see how the game fully boots up now that you got it working.
 
(Darn, you aren't located in the U.S.) I'm glad this worked out in the end but a "UAA:B" doesn't exist. You probably used "AAD:B" used in the parent set on Mame source. It turns out my prediction of the game storing MAC address related data on the timekeeper may have been incorrect. I am now interested to see how the game fully boots up now that you got it working.
Hi,
Yes I'm not in the USA. I'm from France ;)

Sorry yes I want to say AAD:B

Grrrrrr!!!!
It's not 100% working, I have a problem when I boot the cab, after RTC "OK" Checking network, I have an error message (hardware error)

If I puch test button at the network checking message it's all right, game working but if I don't puch test button I have hardware error and rebooting.

Why???? :(
 
Because you can enter test mode, I would go into "bookkeeping" and then select the "clear all data" option. It's likely this will clear the data from both RTCs at once. I'm kind of curious to see what happens if you boot the game with the internet network board unplugged (from pcb 1).
 
Hi,
Yes I'm not in the USA. I'm from France ;)

Sorry yes I want to say AAD:B

Grrrrrr!!!!
It's not 100% working, I have a problem when I boot the cab, after RTC "OK" Checking network, I have an error message (hardware error)

If I puch test button at the network checking message it's all right, game working but if I don't puch test button I have hardware error and rebooting.

Why???? :(

Because you can enter test mode, I would go into "bookkeeping" and then select the "clear all data" option. It's likely this will clear the data from both RTCs at once. I'm kind of curious to see what happens if you boot the game with the internet network board unplugged (from pcb 1).
I have tested to clear all options in test menu via bookkeeping and I have tested to initialize RTC but I have the same problem.

I haven't internet board in my cab. My 2 viper system don't had LAN port inside.
 

Attachments

  • IMG_20201211_092656.jpg
    IMG_20201211_092656.jpg
    2.2 MB · Views: 5
I haven't internet board in my cab. My 2 viper system don't had LAN port inside.
It seems the pieces of the puzzle are coming together. This is what I can conclude based off of various sources of info from here and Mame's source:
  • The title of the game was referred to as "World Combat" in Japanese and Asia and "Warzaid" in U.S. and Europe.
  • Because you don't see any networking hardware, this means any "Warzaid" cabinet never came shipped with network connection to the internet. This means the network check only happens for JP and Asia versions but not U.S. or EU versions.
  • The game region is determined the timekeeper. In an attempt to restore the timekeeper, you changed the region to "AAB:D" meaning the game will check for its (nonexistent) network hardware.
So with all that in hand, the only way to "fix" all this is to change the timekeeper's region to U.S. or EU. No timekeeper that has a four player cab configured for U.S. or EU region isn't dumped in Mame yet. The UCD timekeeper dump is configured for the two player cab meaning that is useless. You'll have to find someone in this region with a good timekeeper for this type of cab config so that the contents can be used for your cab.
 
It seems the pieces of the puzzle are coming together. This is what I can conclude based off of various sources of info from here and Mame's source:
  • The title of the game was referred to as "World Combat" in Japanese and Asia and "Warzaid" in U.S. and Europe.
  • Because you don't see any networking hardware, this means any "Warzaid" cabinet never came shipped with network connection to the internet. This means the network check only happens for JP and Asia versions but not U.S. or EU versions.
  • The game region is determined the timekeeper. In an attempt to restore the timekeeper, you changed the region to "AAB:D" meaning the game will check for its (nonexistent) network hardware.
So with all that in hand, the only way to "fix" all this is to change the timekeeper's region to U.S. or EU. No timekeeper that has a four player cab configured for U.S. or EU region isn't dumped in Mame yet. The UCD timekeeper dump is configured for the two player cab meaning that is useless. You'll have to find someone in this region with a good timekeeper for this type of cab config so that the contents can be used for your cab.
OK thanks, I understand.
Now the hardest part is to find someone to share the US or EU Warzaid (AAD:B) RTC files in 4 players and working ... 😅
 
Back
Top Bottom