feipoa wrote on 2017-10-11, 15:13:

4DPS PIN Assignment 1 CLK 2 Data 3 GND 4 N/C 5 Vcc […]
Show full quote

4DPS
PIN Assignment
1 CLK
2 Data
3 GND
4 N/C
5 Vcc

Actually this is incorrect. 1 is Data, 2 is CLK. I have been struggling to get PS/2 working on my 4DPS but when I switched these two wires everything started working.

feipoa wrote on 2017-10-11, 15:13:

The mouse header pins on the MB-8433UUD and the 4DPS are very different. […]
Show full quote

The mouse header pins on the MB-8433UUD and the 4DPS are very different.

MB-8433UUD
PIN Assignment
1 Data
2 N/C
3 GND
4 Vcc
5 CLK

4DPS
PIN Assignment
1 CLK
2 Data
3 GND
4 N/C
5 Vcc

On the MB-8433UUD, the chipset controls the PS/2 mouse (the chipset contains a keyboard controller chip). On the 4DPS, the keyboard controller controls the PS/2 mouse.

You shouldn't need to alter modbin. Both AMIKEY and the HOLTEK should work.

sorry for hijacking so many years old post, but 4DPS pinout is wrong.
correct is
1 DATA
2 CLK
the rest is ok.

airbone-x wrote on 2024-03-02, 00:21:

sorry for hijacking so many years old post, but 4DPS pinout is wrong. correct is 1 DATA 2 CLK the rest is ok. […]
Show full quote

feipoa wrote on 2017-10-11, 15:13:

The mouse header pins on the MB-8433UUD and the 4DPS are very different. […]
Show full quote

The mouse header pins on the MB-8433UUD and the 4DPS are very different.

MB-8433UUD
PIN Assignment
1 Data
2 N/C
3 GND
4 Vcc
5 CLK

4DPS
PIN Assignment
1 CLK
2 Data
3 GND
4 N/C
5 Vcc

On the MB-8433UUD, the chipset controls the PS/2 mouse (the chipset contains a keyboard controller chip). On the 4DPS, the keyboard controller controls the PS/2 mouse.

You shouldn't need to alter modbin. Both AMIKEY and the HOLTEK should work.

sorry for hijacking so many years old post, but 4DPS pinout is wrong.
correct is
1 DATA
2 CLK
the rest is ok.

EDIT> sorry, havent see previous post from garryglitta....

Reviving this thread, I have the same 4DPS tomatoboard, although a socket 3 with a mouse pin header. I've tried flipping 1 and 2 to no avail.

Can someone verify my assumption that pin 1 on the board is the one thats black in the user manual (closest to the keyboard port)

https://theretroweb.com/motherboard/manual/4d … 18167230881.pdf

No matter how I hook it up the mouse is not detected.

Andy221 wrote on 2024-06-01, 19:20:

Reviving this thread, I have the same 4DPS tomatoboard, although a socket 3 with a mouse pin header. I've tried flipping 1 and 2 […]
Show full quote

Reviving this thread, I have the same 4DPS tomatoboard, although a socket 3 with a mouse pin header. I've tried flipping 1 and 2 to no avail.

Can someone verify my assumption that pin 1 on the board is the one thats black in the user manual (closest to the keyboard port)

https://theretroweb.com/motherboard/manual/4d … 18167230881.pdf

No matter how I hook it up the mouse is not detected.

Yes. The black pin in the diagram, the one furthest on the left out of the row of 5 pins that make up the PS/2 header, the pin closest to the AT keyboard connector if you're looking at the board with the connector facing up, is pin number 1.

As people pieced together above, the definitive PS/2 mouse header pin assignment on the 4DPS from left to right is:
1 Data
2 CLK
3 GND
4 Not Connected
5 VCC

In addition to getting the wiring between your PS/2 mouse port and the board pins right you will need to take note of the BIOS version installed on your board.

Because sadly the stock 400A, 400E and 401E versions as provided by Zita actually disable the PS/2 mouse header. And do not even offer a menu option to turn it back on. No point trying any of those latest versions.
However there are custom modded versions linked in various posts on this forum and also on theretroweb, and those might be worth a try. Newer BIOS versions add support for stuff like being able to use more than 8 or 10GB of a modern drive, Y2K ticking over correctly, and various useful menu goodies and defaults.

But I should add that I myself haven't had much luck with these more modern versions on my rev 2.1 board, with various problems including hanging during plug and play init, hanging during IDE HDD detection, hanging during ESCD update, problems loading Windows drivers for PCI cards and various other ways to spoil the fun. On the other hand, versions 1.6 (which the board came with) and 1.71e work quite well. YMMV.

Make sure you load BIOS defaults, then setup defaults, and then redo HDD detection every time you flash another BIOS version to try. GL

kanecvr wrote on 2017-10-11, 16:23:

Thanks for the response and for pointing out what I missed... mosue works fine now. […]
Show full quote

feipoa wrote:

The mouse header pins on the MB-8433UUD and the 4DPS are very different. […]
Show full quote

The mouse header pins on the MB-8433UUD and the 4DPS are very different.

MB-8433UUD
PIN Assignment
1 Data
2 N/C
3 GND
4 Vcc
5 CLK

4DPS
PIN Assignment
1 CLK
2 Data
3 GND
4 N/C
5 Vcc

On the MB-8433UUD, the chipset controls the PS/2 mouse (the chipset contains a keyboard controller chip). On the 4DPS, the keyboard controller controls the PS/2 mouse.

You shouldn't need to alter modbin. Both AMIKEY and the HOLTEK should work.

Thanks for the response and for pointing out what I missed... mosue works fine now.

I'm really hoping to find a suitable replacement for my MB-8433UUD, since it's been running unstable for a while now, even at stock clocks for any CPU used. Turns out there's really bad corrosion on the CPU socket, and I don't think I can fix it - but I'll give replacing the whole socket a go at one point. The corrosion is probably caused by the mainboard being left outside in the elements at the recycling center I got it from.

If I can get the tomato going with a PS/2 mouse, and it can run 160MHZ for an AMD and 120MHz for a cyrix stable @ 3.6v, I'm happy.

I'm glad to hear that you managed to get it working! I’m currently experiencing a similar problem with my setup ps2 mouse does not work , and I would really appreciate it if you could share the specific steps you took to resolve the issue.

It would be incredibly helpful to understand what you changed or adjusted in your BIOS or any other settings that led to the solution.

I am using v4.50G ver 1.5 Bios.

Thank you in advance for your help!

Hello everyone!
Could you please share the EEPROM model that can be used for this board? I got similar motherboard (4PDS v1.0) without BIOS ic, and want to try make it alive.
Thank you!

Kepler386 wrote on 2025-03-08, 19:11:

Hello everyone!
Could you please share the EEPROM model that can be used for this board? I got similar motherboard (4PDS v1.0) without BIOS ic, and want to try make it alive.
Thank you!

Sure, I have two of them in close proximity:
Taken PCI400-4: am27c010-205dc
Zida 4DPS 2.11: tms 27c010a-10
They're both UV erasable EEPROMs so you should be just fine with any 27c010 EEPROM. They're not flash chips/ROMs so the BIOS shouldn't get upset if the BIOS chip isn't original.