pangoomis

Code 10 means dead end, sorry

Would be nice to see the exact device ID of the exact card you have @MERCURY127 WikiDevi says it's PCI\VEN_1814&DEV_5360. The drivers mentioned in the topic @LoneCrusader mentioned from here: https://www.download3k.com/Install-Asus-ET1602-Wireless-LAN-Driver.html support only PCI\VEN_1814&DEV_0601 and PCI\VEN_1814&DEV_0681. Those are RT2800 PCI and RT2890 PCIe chipsets respectively. Those are dated 2007, and I'm pretty sure Ralink would not bother with 9x drivers after 2007, I think only Realtek kept making 9x drivers after 2007 until 2008. WikiDevi also says the RT5360 chipset was approved by the FCC at the end of 2009. Seeing as the earliest drivers on the D-Link drivers are from 2010, I'm pretty sure those are the earliest ones. So I think those older Ralink chipsets are supported, but not newer ones under 9x. As a side note, I really would not bet on any official 9x drivers with devices manufactured after 2008 (not counting unofficial ones like the AHCI driver)

Can't really find Windows 9x drivers for it, earliest one is for Windows 2000, I would try the Win2K driver with a modified INF and see if it works with the Odyssey Client.

GeForce 8000 series and newer DOES NOT work with 98SE! This is a false information circulating in the Internet! The INF file of the 82.69 drivers contain device IDs of newer GPUs that DO NOT WORK! Latest/best 98SE NVIDIA GPU that DOES work with the 82.69 drivers is the 7900GTX! Which is the 7000 series, not 8000 series. 7000 series does work with 82.69, and so does earlier series. As for the 320GB partition, you will encounter data corruption if your partition is more than 137GB, I recommend setting up a smaller partition, or using the patch as schwups mentioned. As for your motherboard, it's too new for 98SE. There are no HD Audio drivers for 98SE, so you have to use PCI or a USB Audio Card. As for LAN (Ethernet), try Marvell ones from here: https://soggi.org/drivers/marvell.htm

Does this happen on regular 98SE? (Reference for others: 98IF is an unofficial Russian 98SE distribution, with a heavily modified setup process) DevicePath adds installation source directory to path for INFs. If it doesn't happen on regular 98SE, I would check if there is a .cab that makes that error. Maybe it doesn't like some INFs included or something.

I was talking about reverting the Windows 98 OS files, not the MBR.

Here are drivers for your graphic card for Windows XP 64-bit: https://downloadcenter.intel.com/download/22876/Intel-HD-Graphics-driver-for-Windows-XP64-Embedded They support those Device IDs (Ivy Bridge and Haswell): PCI\VEN_8086&DEV_0162 PCI\VEN_8086&DEV_0166 PCI\VEN_8086&DEV_016A PCI\VEN_8086&DEV_0152 PCI\VEN_8086&DEV_0156 PCI\VEN_8086&DEV_015A PCI\VEN_8086&DEV_0C02 PCI\VEN_8086&DEV_0C06 PCI\VEN_8086&DEV_0C12 PCI\VEN_8086&DEV_0C16 PCI\VEN_8086&DEV_0C22 PCI\VEN_8086&DEV_0C26 PCI\VEN_8086&DEV_0402 PCI\VEN_8086&DEV_0406 PCI\VEN_8086&DEV_0412 PCI\VEN_8086&DEV_0416 <- yours PCI\VEN_8086&DEV_0A06 PCI\VEN_8086&DEV_0A16 PCI\VEN_8086&DEV_0A26 PCI\VEN_8086&DEV_0D06 PCI\VEN_8086&DEV_0D16 PCI\VEN_8086&DEV_0D26 As for GPU drivers for anything newer than Haswell for XP - probably no chance.

Nah, I'm pretty sure I had days when I've installed 98SE more than 17 times That's how I've memorized the full 98SE OEM CD-Key by now, very useful skill. As for the problem, I know why MERCURY127 is annoyed, in fact, all Windows versions really like to completely overwrite MBR and cause annoyance. Would be interesting to know at what EXACT point does Setup program modify the MBR in the first part of the install. Making a backup and restoring it whenever you need a fresh start is easiest workaround, since 98SE really doesn't care about anything else than the registry (system/user.dat), the DOS environment (io.sys/command.com), the MBR, and the OS files itself. All those things, except the MBR, are very easy to backup/restore, best time to do a backup is right after the first part of install, since no PC specific stuff has been done by then (hardware detection and user settings). Something like a restore.bat file that reverts everything at command in pure DOS is something I would have done in your case. That's just my few cents/rubles

I'm pretty sure he wants the "common tasks" to be there, but with selective tasks removed from it while browsing photo/video folders.

What was the error? The Universal C Runtime (KB2999226) is NOT telemetry/upgrade to Windows 10! It is the API that programs built using Visual Studio 2015/2017 (such as your game) uses. It is required for Windows 7 to support such programs. Dunno who tells it's a bad update, but the source has to be updated. Try installing it to see if the game starts working: https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows

One thing I can add is that Dependency Walker is very old and produces misleading results on modern OS. The last version is from 2006! Way before the Universal C Runtime (those api-ms-win files) was introduced. Use Dependencies from here: https://github.com/lucasg/Dependencies/releases It should give more accurate results.

I just remembered that Win9x USB mouse behaviour differ between different USB mice! I had one when it worked fine, and other that was acting strangely. So it might be a problem of the mouse itself. Enable USB Legacy Support and PS/2 Emulator (if there is an option like that) in your BIOS.

You can try using a PS/2 mouse, unless your motherboard doesn't have a PS/2 port. Did you try changing the mouse speed in the Control Panel Mouse applet?

Hmm, I'm sure I've used it to create working Win9X CABs, did you set it for 16bit extractor and MSZIP compression?

The more interesting related question I have is, do you even need CABs other than MINI.CAB and PRECOPY1/2.CAB at all? Win9x setup program recognizes bare files put alongside the setup program. (Which can be seen in the official OSR2.5 win95 folder on the CD) Can we just dump all files from Win9x_*.CABs and be done with it? Is there a way to automatize the creation of the Layout*.inf files? Those control all the files in all the CABs. I remember using CabPack to make my own CAB files (I think it's a GUI wrapper for CLI CAB programs): https://www.softpedia.com/get/File-managers/CabPack.shtml

I can confirm what cov3rt said, Realtek RTL8185 WiFi chipset has Windows 98SE drivers. Will note that.

Try looking here as a reference: https://translate.google.pl/translate?sl=ru&amp;tl=en&amp;js=y&amp;prev=_t&amp;hl=pl&amp;ie=UTF-8&amp;u=http%3A%2F%2Fbust.narod.ru%2Fwin98.html&amp;edit-text= It lists some drivers that are available. As I've said in the other topic, here are the absolute latest Atheros WiFi drivers for 98SE: ftp://ftp.eutronix.be/4pos/POS700/POS700_V1.0/Common/Wireless_LAN/802.11abg/UNEX_CM10/Win98_ME/DV4.1.2.71/Driver/98Me/

Search for any Mini PCI WiFi card with an Atheros chipset. Then use the drivers I've posted before: ftp://ftp.eutronix.be/4pos/POS700/POS700_V1.0/Common/Wireless_LAN/802.11abg/UNEX_CM10/Win98_ME/DV4.1.2.71/Driver/98Me/ And use Odyssey Client for connecting with WPA2, works for me. I wish I could provide experience with other manufacturers, but only Atheros comes to my mind when it comes for WPA2 802.11g WiFi under 98SE.

Driver_98ME_5707_1120.zip is for PCI(-E) network cards starting with PCI\ in their device ID's, not USB! Before giving him the answer, I've took a look at the Realtek's website, and did not found any drivers for USB WiFi adapters for Win9x with their chips.

I've took a look at the .sys file itself. The one from my Atheros' WiFi card is designed with 9x in mind, the Realtek USB WiFi one is not. I'm afraid there will be no drivers for your USB WiFi dongle. Code 2 in non-Win9x Network drivers means no luck, the VXD of Win98SE does not understand the SYS file, sorry. In the future, try to find out the device ID of the device before you buy it. Then, check if the drivers are available. In this way, you won't waste time. That's how I knew what WiFi card to buy for my ThinkPad. Just a tip from experience

Earliest I can find is for Windows 2000: http://drivers.zedt.eu/sd/Wireless/Edimax EW-7811Un/20101210_v1.08_windows/88_92_CU_Driver/Win2K/ Try editing the INF to make it similar to a Win9x compatible WiFi adapter INF, like this one I use in my ThinkPad T42p: ftp://ftp.eutronix.be/4pos/POS700/POS700_V1.0/Common/Wireless_LAN/802.11abg/UNEX_CM10/Win98_ME/DV4.1.2.71/Driver/98Me/ Look for "ATHER Win9x specific" - Win9x expects ndis3, while the Win2K inf has ndis5 written, and different strings...

You're not alone. I would like to know such things as well. Here are just some thoughts from the top of my head in no particular order: Win9x was relevant from 1995 to about 2004ish (when XP SP2 was released). Good thing is to limit books/articles released in that time period. IDA Pro is a nice tool (a must?) to have while dealing with Win9x. @rloew might give some ideas as well. Try looking in old articles from The Wayback Archive. Look inside Win9x disks content, there might be references to some books (tours/guides/cd sampler thingies alike). Download and have a look inside the SDKs. I know that Visual Studio 2005 is last version to compile Win98 compatible stuff. (even if you have to compile apps inside WinXP) Learn about the limitations (limited API calls, Unicode support) Driver architecture (VXD, PDR, MPD) is unique to Win9x, so it's hard to make drivers, since you cannot use knowledge from other OSes. I would like for someone to dive deep into NTKERN.VXD - expand it so the NT compatibility is much greater, if even possible. Don't get your hopes high for writing ground-breaking drivers, Nouveau for Linux is made for decades and is not perfect. Maybe basic stuff like an universal better IDE driver to replace the Microsoft's default one, or an universal HD Audio driver is possible. But something like GPU drivers? Probably impossible. Keep in mind that a lot of the Win9x kernel is still 16-bit and even DOS based, making it even harder to improve it!

You can try the old Network Indicator from here:

I'm pretty sure this update pack is not suited for 486 machines. It's for those people who really do not like Win98FE/SE/ME Delta City got a big update, it should include everything a 95 user might possibly need, now on 3 ISO files! Check it out here! http://deltacity.stare.pro/

At least the site is compatible with old browsers/OSes. That's the spirit. Author claims some updates will be on the way. Has anyone tried to do automated WinSock2 installer for 95? It doesn't use the same update mechanism as other updates.