A mate just bought a rescue (Australia) version of WoZ. It was playing OK, then we downloaded the latest code from the jjp website - note there is only one version (7.03), no option for delta, and it does say use this version for YBR version - however given there are no other options, i assume this is the code for the rescue version?

I downloaded the utility to make a bootable USB and that worked fine - there was a file right at the end where it said it already exists, and click yes to override, which i did.

The machine did update the code, however after that, it sometiomes loads the JJP logo, and then just stays a blank LCD, and does appear to be cycling in that the light aroudn the backglass flicks occasionally. Other times it just flicks the light on the backglass every 30-40 seconds, and nothing appears on the LCD. The CPU fan is spinning, and lights are on all the boards in the base of the machine.

I tried this with 2 different USB sticks, both times there were some errors, and at one stage i did get the machine to appear to paritally boot, but then it got stuck and LCD went blank.

I will upload a few pics of some of the text on the screen during code update in the next post.

Any help greatly appreciated - the machine is not here, its at my mates place

Pics

20210918_112807 (resized).jpg

20210918_113226 (resized).jpg

20210918_113244 (resized).jpg

20210918_113257 (resized).jpg

20210918_113300 (resized).jpg

20210918_113410 (resized).jpg

Update: So a day later, without doing anything different, my mate turned the machine on and it played fine. Played for a few hours, turning on and off in between a few times and it was all good.

Now he's just messaged me and says its back to its old tricks ie: turn on, then machine shows JJP logo, then LCD stays blank, lights on PC are on, but nothing else.

So that really sounds like a hardware issue to me, just not sure if its MPU, power supply or hard drive.

Any suggestions on what to test or do?

Looks ok visually?1632126633388 (resized).jpg1632126634178 (resized).jpg

Bump - any suggestions?

OK, a bit of an update. My mate has worked out that if he turns the monitor off, the machine boots and plays perfectly (obviously no display). Then if he turns the monitor on, it reboots.
So appears to be like a WPC reset. Does this indicate a power supply issue or a monitor issue?

I have suggested (since i am a deecent drive away) that he try and power the monitor externally (not sure if this is possible).

Does this point to the power supply of the mahcine - are there components that fail, not even sure where/what the power supply looks like in a WOZ - is it just a normal PC power supply?

He has also commented this only has occurred since the code update - that siad, he only had owned the machine for 4 days prior - so it had some use from him, but not extensive. I can't see the code update would cause this sort of issue?

Ok. Didn't realise you were meant to unzip as jjp website doesn't specify this. Will try over the weekend

Ok. Just spent a few hours. Reloaded new code again with a different USB and also replaced the battery.

It is consistently resets as soon as I got the power on button on the monitor. If you leave the monitor off the game boots as per normal and you can play a game. However once you power the monitor it goes into a continuous reset cycle.

That said, my mate commented that if it's left off for 12 hours or so you can sometimes boot it and play a game with the monitor on but after a while it resets.

Its got a DVI cable. I didn't have a vga one on me. Monitor is supplied by 12v daisy chained to heaps of other stuff.

So I disconnected the DVI cable at the PC and it would still reset when the monitor was powered on. So this tells me that the issue is not the code or computer or port but rather a power supply issue.

I plan to set the monitor up on a separate 12v external source next time and test this theory. Any other advice or ideas on what components on the power supply board may require replacement? I did reseat all connectors and made no difference

Yep. We did try that and it was still resetting