VOGONS


Reply 720 of 721, by Yoghoo

User metadata
Rank Oldbie
Rank
Oldbie
Jules_nerd wrote on 2026-08-12, 20:24:

Well, there really isn't much to go wrong on the PS2 mouse port in this design, so long as that input on the M6117 is working...
Did you get a chance to check it out?

Checked the connections from the PS/2 port to the M6117 which seem okay. Also checked a couple of resistors and capacitors and they check out okay as well.

I'm out of ideas at the moment. So going to reassemble the laptop again. Can only hope that the flux I removed was conductive and that it magically is solved. 😜

Reply 721 of 721, by javispedro1

User metadata
Rank Member
Rank
Member
Jules_nerd wrote on 2026-08-12, 08:23:

Incidentally, I assume that on the BOOK you can see BIOS config options for LPT2? In the soundcard manual's description of the COVOX it mentions that a real LPT2 hardware must exist if your COVOX software looks for a parallel port. If the BIOS allows you to set a different address for LPT2 it may 'break' covox software that does these checks; Whilst BIOS may be fine setting the 'real' LPT2 address in the M5113, the COVOX has its own, separate address decoding is fixed in hardware to the default address.

I forgot to reply to this. No, LPT2 settings do not show at all in the BIOS setup -- same as the Pocket386.
I am much less familiar with parallel. I don't even know of a good program to play with it in DOS --- I use Kermit for serial.

By the way, on the topic of the touchpad and its frequent mis-detections, it seems that both OS/2 and Linux have no problem: they consistently detect it on each boot with no issue.
So it must be something related to the initial handshake that MS mouse drivers (specially Win95) don't like, rather than a HW fault. (Albeit since we can't change the FW....).