[GH-ISSUE #44] How to install "Intel Chipset Support II"? #41

New issue

Closed

opened 2026-03-03 18:48:29 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 18:48:29 +03:00

Owner

Originally created by @tinue on GitHub (May 31, 2025).
Original GitHub issue: https://github.com/oerg866/win98-quickinstall/issues/44

Computers that are newer than Windows 98, but still support the operating system, often require chip support software. One example is the Thinkpad T40. This chipset support installed IDE, USB, Processor support and much more. Without this, one can't even install e.g. a display driver.

The trouble is: This driver is a single .exe file, and not a proper windows driver with .inf files etc. When executing the .exe, it copies .inf files and dlls directly into windows directories, and after reboot Windows 98 starts to detect hardware.

Is it possible to slipstream this driver somehow?

Originally created by @tinue on GitHub (May 31, 2025). Original GitHub issue: https://github.com/oerg866/win98-quickinstall/issues/44 Computers that are newer than Windows 98, but still support the operating system, often require chip support software. One example is the Thinkpad T40. This chipset support installed IDE, USB, Processor support and much more. Without this, one can't even install e.g. a display driver. The trouble is: This driver is a single .exe file, and not a proper windows driver with .inf files etc. When executing the .exe, it copies .inf files and dlls directly into windows directories, and after reboot Windows 98 starts to detect hardware. Is it possible to slipstream this driver somehow?

kerem closed this issue

2026-03-03 18:48:30 +03:00

kerem commented

2026-03-03 18:48:30 +03:00

Author

Owner

@oerg866 commented on GitHub (May 31, 2025):

I never advise to integrate Chipset drivers especially not these intel ones
which aren't really drivers but just some lists of device names basically
but if you absolutely must then you can use some method like UniExtract to
extract all the driver files from the exe and then use them with sysprep as
normal, that should work

The only problem you get is when the exe itself does registry or file
modifications that aren't part of the inf, then those obviously wouldn't
work. Not aware of intel drivers doing that though

On Sat, May 31, 2025, 13:22 Martin @.***> wrote:

tinue created an issue (oerg866/win98-quickinstall#44)
https://github.com/oerg866/win98-quickinstall/issues/44

Computers that are newer than Windows 98, but still support the operating
system, often require chip support software. One example is the Thinkpad
T40. This chipset support installed IDE, USB, Processor support any much
more. Without this, one can't even install e.g. a display driver.

The trouble is: This driver is a single .exe file, and not a proper
windows driver with .inf files etc. When executing the .exe, it copies .inf
files and dlls directly into windows directories, and after reboot Windows
98 starts to detect hardware.

Is it possible to slipstream this driver somehow?

—
Reply to this email directly, view it on GitHub
https://github.com/oerg866/win98-quickinstall/issues/44, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAISOPPKBYEPHVZIE2KUMWL3BGGI7AVCNFSM6AAAAAB6JY6KCOVHI2DSMVQWIX3LMV43ASLTON2WKOZTGEYDKMZUGMZDMMA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@oerg866 commented on GitHub (May 31, 2025): I never advise to integrate Chipset drivers especially not these intel ones which aren't really drivers but just some lists of device names basically but if you absolutely must then you can use some method like UniExtract to extract all the driver files from the exe and then use them with sysprep as normal, that should work The only problem you get is when the exe itself does registry or file modifications that aren't part of the inf, then those obviously wouldn't work. Not aware of intel drivers doing that though On Sat, May 31, 2025, 13:22 Martin ***@***.***> wrote: > *tinue* created an issue (oerg866/win98-quickinstall#44) > <https://github.com/oerg866/win98-quickinstall/issues/44> > > Computers that are newer than Windows 98, but still support the operating > system, often require chip support software. One example is the Thinkpad > T40. This chipset support installed IDE, USB, Processor support any much > more. Without this, one can't even install e.g. a display driver. > > The trouble is: This driver is a single .exe file, and not a proper > windows driver with .inf files etc. When executing the .exe, it copies .inf > files and dlls directly into windows directories, and after reboot Windows > 98 starts to detect hardware. > > Is it possible to slipstream this driver somehow? > > — > Reply to this email directly, view it on GitHub > <https://github.com/oerg866/win98-quickinstall/issues/44>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAISOPPKBYEPHVZIE2KUMWL3BGGI7AVCNFSM6AAAAAB6JY6KCOVHI2DSMVQWIX3LMV43ASLTON2WKOZTGEYDKMZUGMZDMMA> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >

kerem commented

2026-03-03 18:48:30 +03:00

Author

Owner

@tinue commented on GitHub (May 31, 2025):

Thanks, I can see now why you do not advise this. The .exe did have a command line option that extracted the driver files. I added them to the slipstream directory, and installed the Thinkpad. The result was mixed: Some drivers got installed, others are installed, but show a conflict in device manager, and some devices completely disappeared, e.g. the Intel Ethernet adapter.

@tinue commented on GitHub (May 31, 2025): Thanks, I can see now why you do not advise this. The .exe did have a command line option that extracted the driver files. I added them to the slipstream directory, and installed the Thinkpad. The result was mixed: Some drivers got installed, others are installed, but show a conflict in device manager, and some devices completely disappeared, e.g. the Intel Ethernet adapter.