Bally alpha 2 conversion firelink fatal error no signal afterwards

[a69mopar]

Regardless of the cabinet configuration is, has anyone had board failures on the alpha2s? Are there any known issues out there?  If anyone has this information, it may help.
Thanks,
Wayne

[Ankitp23]

Took both cpu’s out from non working machine  and put them inside another working machine, Bally logo and loading screen came on  (hard disk game from working machine.)

Then I took the working cpu that was from the machine mentioned above (completely working one) and put my hard disk game in no luck no signals on the machine that was down originally.

Then I took the working cpu and it’s working hard disk game (didn’t remove disk from cpu, machine that was working completely fine) to test it on the machine that wasn’t receiving signal and it still didn’t work on that machine.

THEN WTF

when putting back the working cpu (Intack hard disk) in the working machine again and now that’s not receiving any signal for display.

There is something going on or I missing it.

After leaving machine on for 8 mins or so on the ideck I get this writing (boot log) see picture

What’s going on….

[rickhunter]

Some things I observed here:

1.  Using  hard drives on A2 MPU's (I've never seen that, it has always been SSD's.  Not sure if this makes any difference, I would think not, but who knows for sure).
2.  Since you are not even getting an image when you power up, I would test the monitor with a laptop to make sure the monitor is working right.

3.  Replace the video cable, cheap enough to give it a try, plus you should always have spares anyway.

3. The message that the system could not find a monitor means, the video card is bad or it is not getting a valid EDID message and thus the video card does not output to the monitor since it doesn't know what it handle.  This is sometimes the case with monitors that have not been specifically made to work with the alpha 2 hardware since the video card's bios expects certain resolutions and timings to be available before it starts up.  Unsupported hardware will cause red screens when the system polls hardware for capabilities and it doesn't receive the expected message back.

[Ankitp23]

Your right, I mean SSD When I say hard drive.

When I pulled the cpu box out, do I need to pull out the video card and reinsert it into the cpu slot again?

I’ll try that tomorrow,  I’ll try connecting laptop to monitor as well and new cables from working machines as well. But all of theses happening now on 3 machines….

[Ankitp23]

Fixed it, power supply to the monitor was bad,
That’s why no input or nothing was showing up on monitor,

[Stayouttadabunker]

Good job! 
I can mark this topic as Solved!

[rickhunter]

The photo of the MPU you posted has a hard drive in it.  SSD's do not look like that on the electronics side, you can see the silver circle where the platter spindle is centered on the photo.

[Melissarmdlm]

This is an old thread but I thought I'd reply too. I've fixed genuine Bally's via A/D board despite the boot sometimes working, sometimes going to 'no screens attached' fail. They never exhibited a visual monitor error.