VOGONS


First post, by Marco

User metadata
Rank Oldbie
Rank
Oldbie

Hello all,

Any experiences in above topic? Due to hardware limits I have to stick to w95 on my 386 system. I wonder whether it could make sense using latest w98 non wdm driver within w95 as eg for:

- cirrus logic graphics
- 3com 509 Ethernet

Not more. I would hope for better optimized drivers at the end. Any experiences?

Regards and thanks

1) VLSI SCAMP 311 | 386SX25@TI486SXLC2-50@63 | 16MB | CL-GD5434 | CT2830| SCC-1 | MT32 | WDC160GB/7200/8MB | Fast-SCSI AHA 1542CF + BlueSCSI v2/15k U320
2) SIS486 | 486DX/2 66(@80) | 32MB | TGUI9440 | LAPC-I

Reply 1 of 7, by jakethompson1

User metadata
Rank l33t
Rank
l33t

Looking at the discs, the EtherLink III driver appears to have already moved to WDM (elnk3.sys instead of .vxd) even in "first edition" Windows 98.

The Cirrus Logic 542x drivers stayed as VXD, however, there is no guarantee they would still be compatible with Win95. I guess you could try overwriting cirrus.vxd, cirrus.dll, and cirrus.drv with the Windows 98 versions if you wanted to see. I didn't see any BSWAP or XADD insructions in them in a quick check via objdump.

I vaguely recall claims that installing DirectX would update video drivers, but looking at the DX5 package on the OSR2.5 CD, I don't see any drivers. Anyone know the backstory there?

Note that both the Cirrus 542x and 3Com EtherLink III predate Windows 95, and were both ubiquitous both during Windows 95 development, and during the window (pun) of development between the original release and OSR2.5. If there were any fixes they needed, they would've made it into OSR2.5. By then, both of these were old in the tooth, and I can't imagine the priority for 98 was anything other than don't break them.

Reply 2 of 7, by Marco

User metadata
Rank Oldbie
Rank
Oldbie

Thanks.
Regarding DX5: the latest driver for Cirrus GD are in the DX6.1 package.

1) VLSI SCAMP 311 | 386SX25@TI486SXLC2-50@63 | 16MB | CL-GD5434 | CT2830| SCC-1 | MT32 | WDC160GB/7200/8MB | Fast-SCSI AHA 1542CF + BlueSCSI v2/15k U320
2) SIS486 | 486DX/2 66(@80) | 32MB | TGUI9440 | LAPC-I

Reply 3 of 7, by marxveix

User metadata
Rank Oldbie
Rank
Oldbie

What drivers are you talking about? Some of them have problems, its because of VXD vs WDM i think.
I have no problems to install ATi Rage Pro drivers with Win95B to WinME, havent tested orig Win95A.

Best ATi Rage3 drivers for 3DCIF / Direct3D / OpenGL / DVD : ATi RagePro drivers and software
30+MiniGL / OpenGL Win 9x dll files for all ATi Rage3 cards : Re: ATi RagePro OpenGL files

Reply 4 of 7, by Marco

User metadata
Rank Oldbie
Rank
Oldbie

Oh I am sorry. Double post as I alread posted this question earlier this year. Sorry

Topic 107431

I thought about SB16, GD5434, 3c515, MPU401, 1542C etc.

So at the end I understand it’s about a) identical driver model and b) testing 😀

Anyway thanks and sorry for the double posting

Last edited by Marco on 2025-10-26, 12:48. Edited 2 times in total.

1) VLSI SCAMP 311 | 386SX25@TI486SXLC2-50@63 | 16MB | CL-GD5434 | CT2830| SCC-1 | MT32 | WDC160GB/7200/8MB | Fast-SCSI AHA 1542CF + BlueSCSI v2/15k U320
2) SIS486 | 486DX/2 66(@80) | 32MB | TGUI9440 | LAPC-I

Reply 5 of 7, by dionb

User metadata
Rank l33t++
Rank
l33t++

WDM is >Win98 only, VXD is same model as Win95 so might work. However the devices you're mentioning there are all old enough there should be mature Win95 drivers for them. 'Newer' is only better if the updates are relevant and useful. In quite a few cases (think: Via 4-in-1, nVidia Detonator) newer drivers than needed will add bloat and harm performance and you actively want older ones more suited to your hardware. Sometimes functionality is also deprecated in newer drivers, particularly relating to supporting older hard and software.

What exactly do you hope to be getting with say MPU-401 (a very basic serial protocol...) in a newer driver that would not already be present in the oldest stable driver in Win95?

Reply 6 of 7, by Marco

User metadata
Rank Oldbie
Rank
Oldbie

Fully agree with what you said. The MPU was really a bad example and yes newest not always means better / faster

1) VLSI SCAMP 311 | 386SX25@TI486SXLC2-50@63 | 16MB | CL-GD5434 | CT2830| SCC-1 | MT32 | WDC160GB/7200/8MB | Fast-SCSI AHA 1542CF + BlueSCSI v2/15k U320
2) SIS486 | 486DX/2 66(@80) | 32MB | TGUI9440 | LAPC-I

Reply 7 of 7, by Marco

User metadata
Rank Oldbie
Rank
Oldbie

It’s indeed not that easy (for me) as most drivers of win98 (same in w95) are stored in their internal driver library and not availablevia simple .inf files to update driver. Most closely solution is the 1:1 file replacement

1) VLSI SCAMP 311 | 386SX25@TI486SXLC2-50@63 | 16MB | CL-GD5434 | CT2830| SCC-1 | MT32 | WDC160GB/7200/8MB | Fast-SCSI AHA 1542CF + BlueSCSI v2/15k U320
2) SIS486 | 486DX/2 66(@80) | 32MB | TGUI9440 | LAPC-I