I am trying to replicate your issue on my board. I might not be able to because I have a SY-5EMAPRO, and it does appear that it is a bit of a board redesign, they are still very similar. I am not sure if I have figured something out, but I have some steps for you:
1. Is a PS/2 keyboard connected when you try to boot? I don't care if you are still using a USB to PS/2 adapter like you were before. Just make sure the adapter with your chosen keyboard works on another machine.
2. With the PS/2 keyboard connected, push the power button and turn the computer on. If it does not finish POST correctly (or quickly enough) push the reset button. Does it POST quickly now? Try it a few times if using the reset button seems reliable.
3. Power off the machine. Unplug the PS/2 keyboard, and leave no keyboard. Power on the machine. Does it boot faster now? You'll get a keyboard error and maybe cmos settings cleared error, floppy error, etc, since I guess you have everything unhooked and cleared your settings.
4. If the machine posts correctly with the reset button install your PS/2 keyboard, power on with the reset button, and go into the BIOS settings. And enable USB keyboard support. Save and exit. You probably should install your cmos battery if you still haven't (unclear from your last thread). Shutdown your computer. Then replace the PS/2 keyboard with a USB keyboard.
5. If you want to use a PS/2 keyboard, try a different keyboard. You'll want to try this if you can't seem to get your machine to boot at all with that USB->PS/2 adapter. What is the keyboard or keyboards you are using?
The reason why I say this is because I do see a potential stability issue over here with the power delivery circuitry when powering on and the model of keyboard used. I don't know if your USB adapter is part of it, so get some keyboards handy.
If none of this makes a difference, then get a post diagnostic card, but probably leave the keyboard unhooked in one of the attempts. Also see the one last note from my manual later on.
cookertron wrote on 2023-01-28, 19:43:
CoffeeOne wrote on 2023-01-28, 19:32:
cookertron wrote on 2023-01-28, 19:21:
No I was just pointing out that the BIOS has been updated but before the fault occurred so it's not necessarily the cause. I was trying to pre-empt someone suggesting I should upgrade the firmware to the latest.
Thanks for your help
Sorry, but now I have to ask again. What do you mean eaxctly with "before the fault occured"?
Where you using this board before?
Yes I was testing it out with Window 98SE and DOS. I had it running for about 4 days before updating the BIOS. Two weeks after the update the board starts to exhibit this behaviour.
When you created the prior thread, you did not mention this, and no one said to upgrade the BIOS when you had trouble. It would be a mistake since to suggest a BIOS update when you said the board was previously working, why attempt to do introduce something unknown, when you can just go back to the original configuration that was working. So reversing steps back to a working configuration is the correct thing to do. Knowing that you flashed it recently, could have been a factor when I started thinking about your post today. I am not sure, but this is why: I have a "1AA2" BIOS, a newer variant, perhaps specifically for 5EMAPRO.
5EMA_PRO 1AA2
11/28/2000-VP3-686A-6A5LES29C-00
(Your earlier post for reference SOYO SY-5EMA posting very slowly.)
I believe I had flashed the BIOS at some point. But please note, I have no idea if this is related or even compatible. But it could be a clue. The reason why it is a clue, is because of this site, and the information here:
https://pcrebuilding.altervista.org/44/183/BI … 2B+V1.0%29.html
This is suggesting that your "1EA1" and the 5EMA+ & PRO are the same family, and the 5/11/2000 might have been the original BIOS date this board came with, considering they are in a family, at least updated together? (Note to anyone hitting this with a search engine, please research out the exact variant that SOYO supplied ... I can't seem to find it today ... don't trust someone post that it looks "similar") I have always had some minor boot issue with this machine, now known to be also related to the keyboard plugged in, but nothing exactly like yours. I don't remember when I flashed this board as I've had this board for nearly 23 years.
I wonder if there is a BIOS issue in the later versions. Now I don't know if this warrants further experimenting, but it wouldn't hurt to go back to the earlier BIOS revision if for some reason the 5/11/2000 BIOS (or later) is connected some keyboard issues. But I think I'll want to inspect the power circuitry some, because I am finding certain PS/2 keyboards are fine and others are not, so I am suspecting power draw.
BTW, the 5emapro manual says this, which I find very odd:
Video (no display) related issues
I built a new computer system using a Soyo board and nothing
happens when turning it on, no video and no beeps from the PC
speaker. What is happening and how can it be fixed?
... deleted some nonsensical speak from the manual ...
1) 1. Press and hold down on the “Ins” (insert) key while turning on the
computer until you get video. If you do not get video then,
I have found this to sort-of make a difference ?? But it is not consistent. I wonder if there is really something in the BIOS that checks for this key and does something. Or it is a hacky work-around due to a power issue.
I'm glad some how your issue and something that has bugging me has converged. At least it helped me narrow down a problem. I may investigate this some more, when I get time.