Goodmaneuver

1.50.1164.0 should work in Win95 with the Ole32 update, yes 4.71.3328.0 will work as this is WinME's version. What version of WBEM you use will not matter much unless you are using specific Windows programs that rely on some updated files like Framedyn and Fastproxy but you can not mix and match much, it is a specific OS thing. Do not take notice of version numbers that much also as 1.50.1164 has a link time stamp of 09/06/2000 - WinME time stamp. Look for link time stamp in Dependency Walker. Although the majority of Win2K or early Whistler WBEM can be used, it has little or no advantage in normal operation with games and other 3rd party applications. So you can use what you like and just make sure there are no errors in Dependency Walker and that all appropriate files register OK and executables do what they are supposed to do. I think WinME's version is a good choice. If you install DCOM95 ( which is a part of the DSclient package ) make sure that the new Ole32 4.71.3328.0 is in the system folder or just copy over the files off line. To get pre-release versions of WinMe, Google WinWorldPC then select Library. ( Win2K uses 1.50.1085 version files, I am not familiar with Win98 WBEM version numbers ) BTW the VXD's in the DSclient package are for 95 and 98 and do not work in ME. Some executables need registering first time. Create shortcut with space then /regserver suffix. These are the 2; WinMgmt.exe; unsecapp.exe. Or alternatively run the WBEM.inf.

WinME has WBEM version 1.50.1164.0. It will work if you update Ole32.dll to that of Win98 vs 4.71.2900.0 will do. Place WBEM from from WinME in system folder or folder of choice then register all files that have DllRegisterServer as a function export. Check with Dependency Walker and also make sure there are no missing files or mismatches I have overlooked other than Ole32. Several games and several other programs as well as those you have mentioned use WBEM files. If you already have WBEM folder in Win95 or had it before then do not change its location. Empty it and replace with WinME folders and files. Make sure you still register files and WinMgmt.exe ( Microsoft Web-Based Enterprise Management Common Information Model Object Manager ) should be set to run at runtime. Check with Process Explorer that it is running.

There are 2 x GlobalMemoryStatusEx Kernel32 ;kexbases shown on Ktree, is this OK? These functions are not mentioned in Ktree and are working RtlImageNtHeaderEx => RtlImageNtHeader LdrProcessRelocationBlock => RtlReAllocateHeap These 2 are tested with ImageHlp up to version 6.1.7601.22484 for several years and OK. ( RtlImageNtHeader is mentioned in Ktree but why when it is a function already in Ntdll )

There are a lot of Errata in the chipset spec update https://www.intel.com/content/www/us/en/products/docs/chipsets/x99-chipset-pch-spec-update.html mainly due to USB problems.

Java uses local variables which after the function ends, the variable name does not exist. C/C++, Visual Basic, and VB.NET use static variables ( local ) that stay in RAM which allows a value to be retained for different function calls. I am wondering if there is a race situation that does not favor the saving in Eclipse as JVM not working unless assigned DCFG1 or BASE - could be a timing speed problem. MSHTML vs 6.2800 needs KEX disabled due to speed before the graphics output outputs. Experiment using explorer in a window and then go full screen and back with different MSHTML KEX settings. Will have to restart Windows for accurate results between KEX setting changes on the MSHTML as it is loaded at all times. MSHTML also has many registry settings and I found that it will not register any more, time wise, I would imagine since the original install of IE6 or IE5.5 : - ( WinME original install ).

>> Do I need an FX5200 for DOS or would a modern (RX570 for example) blow it out of water? Universal VESA driver has no 3D support. Apart from this the VESA drivers on the RX570 would be good. Some of us use a 7900 series nVidia PCIe card as an all rounder or just for best 98/ME performance. Flash should work with the VESA driver. >>So, just set BIOS priority to PCI and disable device not needed in XP. It could be required for 98 though if the BIOS does not auto switch the the PCI card and you want to run 98 on this card. I had to change my original post here because the native WinME OpenGl screen savers did work on the standard driver so did various 3rd party screen savers. Unfortunately the VESA driver does not like my video card - 7900GS when going above 16 colors. In so testing at 16 colors native WinME and 3rd party OpenGL screen savers did work using WinME's OpenGL.dll. ( Slowly though due to no video card 3D acceleration )

System file protection should not be a problem, perhaps you mean the version conflict manager. SFC from 98 should not make any difference unless it does not work I would think. I do not like automatic registry cleaners but I did not think there were any from Microsoft. https://www.majorgeeks.com/files/details/regcleaner.html link to RegCleanr.exe. You could replace both files in the system and VCM folder off line and update the VCM module version numbers in registry after reboot. If system files need registering then that can be done too after reboot.

I have not done this myself so I do not know exactly. I would make the BIOS have the PCI card be the one to boot to if possible or otherwise Win98 will boot to the PCIe card of which a standard or Universal VESA driver would be installed. If BIOS has no discrepancy between PCI and PCIe then possibly the PCIe card has to be disabled in Device Manager in Win98 once all is established but look for default display device in Display Properties; graphics's cards control panel or Device Manager etcetera first. I have just seen Rainy Shadows post above and that reminds me. The BIOS should switch to the card the monitor is plugged into and a KVM switch unit for the monitor would be the go. Switch manually the desired input to the KVM before booting. If it does not work then a mechanical switch may need to be used but introduces degraded graphics display as the impedance is difficult to be kept at the correct value and also cross talk is a problem. A Quad slide switch might be best with ground on one pole of each switch. I had a home made rotary switcher for this early on, now using a proper KVM between computers.

Unofficial SP GDI32 upgrade for instance creates streaking across the page when typing with WinWord8 ( Office 97 ). I have checked it all and the User upgrade does not seem to do any harm and I do use the CDVSD VREDIR NETBIOS and NWLINK.vxd's . Some updates like CDVSD may not have been necessary though. The Dlls and OCXs are OK but I have updated many to moderner since. Have to be careful here and if they do not register when they are supposed to then there is something wrong about it and should not be used, look into the functioning and see if it is a step forward or backward. About the User upgrade. It will show some functions being there when Advapi32 of a WinNT file is checked with Dependency Walker, whether it works for these functions I do not know. Comctl32 from Neptune was used in the chain of Dlls in the test. I did try this arrangement, the graphics did work but there was an error in loading a module or modules requiring Comctl32 and I have overwritten the hard drive since. The advapi32 I used I can not find anymore and may not have been an upgrade as such. Why certain files were changed in the USP remains a mystery unless the coder explains it and or says what other modules were used.

NUSB uses the Win2K Stack as well, they are similar drivers. Note I have updated my last post just before you posted yours. I do not use any of the USB drivers from UWMESP3.

VIA has supplied 2005 drivers specifically for 98 and WinME. USB20DRV uses VIA 's USBhub20.sys and has older files for USBPORT.sys and USBEHCI.sys. VIA drivers work faultlessly and I have tried USBB20DRV. USB20DRV will rely on the Unofficial SPack3 VXD's for 98. Correction it was a while ago and I have used the 98SP3 files but they are not quite the same as USB20DRV files. I still recommend the VIA SYS files and any not covered by this driver then get from Unofficial SPack1 for WinME. ( No I do not use any of these only the original ME ones ).

NUSB is not for WinME. There are 3 VXDs in NUSB3.3 - CDVSD; DISKTSD and IOS.vxd. Use the download link I gave here https://msfn.org/board/topic/97588-modern-motherboards-which-are-working-with-windows-98-discussion/?do=findComment&comment=1181746 for VIA drivers.

>>Personally, I prefer to use the USB 2.0 support included with the 98SE USP3 No Win98 VXDs do not work with winME. Use drivers from manufacturer.

This statement had me puzzled from the start. BWC's Msvcrt working is fine but where does Msvcr90 play a role. If BWC's Msvcrt and Msvcr80 wrapper is used then Msvcr80 is the only one that will work and the wrapped Dll of Msvcrt and Msvcr80 did not work for me in VLC. So I am asking what has Msvcr90 got to do with it. Another thing is if using BWC's Msvcrt.dw7 vs from Dx9W2kFx.zip, then Msvcr80 should to link to Crtdll.dll for _getdrives for a better alternative than loading the full Msvcrt for _getdrives and necessary if the wrapper is named Msvcrt.

DCFG1 is not the same as BASE as if JAVA*.EXE is set to BASE then the JAVA control panel does not work. It complains that Javacpl.exe has a device not functioning. This is because of the VerSetConditionMask and VerifyVersionInfoW functions. I run Explorer with DCFG1 to allow more programs to run without the need for extra individual settings. *\JRE\* is a idea that I had not known about and assigns all modules to the desired setting, but JVM.dll only works with BASE or DCFG1 and there are the Java, Javaw and Javaws executables in the WinDir as well. The phenomenon of why the other files had the BASE setting in the Java\Bin location is still a mystery when they should have just been in following mode. The other problem which may not be a KernelEx one but is important is the assigning of folders like .folder in Java 1.7 and above. I think Java has a problem finding the correct folders. Some programs I have that use Java are VUZE 5.4; Art of Illusion vs 3.1; and Eclipse Luna 2014. It is important as saving of work in Eclipse can not be done properly and Vuze always wants to install the Swt download in an incorrect location or something like it. Edit: The assigning of folders like .folder in Java 1.7 and above happens with other NT operating systems; it puts a full stop in front of the folder and places it in a parent folder. I am still looking into this issue but would appreciate help. Eclipse is storing in correct location but 0 kB, see picture. I have decided to have the java 1.7.0.0 runtime as is and let the Java control panel update the 1.8.0_51 runtime location. This will negate any errors associated with manual registry updates for Java 1.8. In so doing this, the 1.8.0_51 runtime location bin has all the executables KEX set to DCFG1 with KEX AppSettings *\Java*.exe = DCFG1. The DLLs in the 1.8 folder are in follower mode.

The latest NUSB has a WinME file and installing a previous version of NUSB might fix this as the ME file may need accompanying ME files. VIA USB driver files for Win9x should have suffix 11 which are the latest ones and are required for some game controllers. I need these for the USB steering wheel and USB hand held game controller. The updated drivers are also best in a general sense as the original WinME divers only accessed up to 32GB. The latest VIA USB divers are contained in VIA_USB2.0_v2.7.zip. Link https://www.techspot.com/drivers/driver/file/information/1210/

I have manually installed Java 1.8.0_51 in WinDir subdirectory JAVA\JDK\jre after installing JDK 1.7.0.0. Since some executables and control panel now need 2K settings I needed to update KEX AppSettings. My original settings were *\Java*.exe = DCFG1. This original setting results in other executables having names not starting with Java in the JRE folder having BASE setting. Tested in 2 different builds and happens with JDK/JRE 1.7.0.0 as well. Is this intensional? I still use DCFG1 for *\JAVA*.EXE and now use *\*.CPL.EXE = NOHEAP and over riding the BASE auto setting that I found for these two exes Jp2Launcher.exe and SsvAgent.exe to NOHEAP.

Unsigned drivers are not necessary. When you go to install the driver there should be an advanced option which will allow settings of warn about unsigned drivers and always allow unsigned drivers. This is the case with WinME. In DirectX diagnostic tool do not have the 'Check for WHQL digital signatures' box ticked. You need to restart with Fdisk after partitioning before formatting with Win9x. ( in-case you didn't ).

Remember I said Notepad++Portable needed KEX setting Win2K_MT because of a plugin. Well this is not correct; NppNetNoteA.dll needs setting disabled in the ANSI plugins. Because I mentioned File64 stopping pshExports, File64 also stops Glory of the Roman Empire and Ancient Wars - Sparta the games. : - Fixed see https://msfn.org/board/topic/131040-revolutions-pack-97/?do=findComment&comment=1185503

There still could be hardware not toggling. If it is the board that makes a crackling sound through the sound then I would check temperatures of all chips and put in extra cooling if necessary and still use a slow HT bus speed and hope it comes good.

I checked it out myself. If you test XUL.dll in Dependency Walker it is not compatible with NT4 Service Pack 6. Msimg32 might be made compatible if it and Gdi32 are taken from from Microsoft Windows 2000 (''NT 5.0'' 5.00.1515.1 Professional) but this is only a part of the incompatibility.

Check msimg32.dll with Dependency Walker you might have wrong version?

>>I love Revolutions Pack, but using it with KernelEx causes problems with explorer. What problems, please explain?

There has been several in the past that were free but now may not be available like Image Folio 4.30 and Artweaver 0.5. There is PhotoFiltre 7.2.1 which is available Free. Can find at AfterDawn.com - Image Editing or at other sites.

You may have forgot to install nusb33e.exe on your system.