Goodmaneuver

>>but it just power cycles every 25-30 sec By this does do you mean that it shuts down then power up itself automatically itself or does it just shut down? If it auto restarts the BIOS can be trying defaults then rebooting. If no beep code then I would try different CPU and is the Corsair CX500M new?

Yes probably but mine has 6 heat pipes and the top of the heat stack is cool and the surface of the CPU can be hot. The heat exchanger/grid section is 9cm cubed. I my heatsink is not big enough theoretically and I have two high speed fans. A heat gun is good to check temperatures, I have a cheap one which works good. When all is OK the CPU will throttle back on yours and it is when CPU load is flat-out is when you need to check temperature. Never the less 40 degrees is indicating that the heatsink is in full contact with the CPU and things are OK. When there is a motherboard fault CMOS transistors are not toggling having a short circuit like condition and the CPU not only heats up due to CPU activity it can have shorted transistor conditions as well. What can happen in booting if the fan speed is set up to operate auto is that it goes fast for a short while then slows done when the hardware is booted and the video output occurs. The fan is set up in auto for CPU temperature changes. I have many boards that do not boot and were second hand. It is best to take note/mark or put aside the best RAM and video cards for testing. The best AMD video card I found is one that stepped down in transistor size and still is the old modal like HD4770 but some boards I got going only booted with a good nVidia. Secondhand CPUs are not advisable unless you are lucky and the supplier tests in several boards. They need testing with a 64bit OS. All of my second hand socket 754 ones I bought from general public individuals were faulty in one way or another, some worked on 32bit OS but not on 64. The best one was one that worked fully but only with 256MB of ram installed. Second hand ones from shops can be weakened and just work on a healthy board. A new CPU should have enough push in reserve to be able to overclock when all hardware is good and used to be about 30% but things may have changed. If you can afford a different CPU then I would try it because the motherboard is new and most sellers should test to boot screen at least. Was the battery still OK it should be over 3 volts otherwise I do not use them. The battery can discharge within a month or two without standby power but depends on the motherboard. This slow decay can be dangerous with different ambient temperature changes and BIOS could be corrupted. I do not store boards with battery in place. Unplug the PSU mains cord, wait for capacitors to discharge, remove battery and short the reset pins for at least 10 seconds to clear CMOS. Make sure shorting jumper is back in the non clearing position. If the shutting down time was closer to 10 seconds then the power switch could be sticking in. I have had that before and some light oil spray on the plastic case button fixed it.

That is why I have suggested to try my method. CPU can heat up very fast and 25 seconds to shut down due to thermal sounds about right. The air cooling heatsink will not prevent overheating heating due to outputs that are not toggling. The other power supply could be weaker or its output may rise slower. My old Opteron usually sits at 55 degrees but when I had instability after turning on high efficiency ACPI in BIOS I got gobbledygook printed on the screen with a CPU temp of 95 degrees. So I needed to work on the board. I added some caps on the CPU output buss and around the RAM and lowered the high frequency impedance across the main supply caps of the CPU. I experimented after this with RAM speed on auto which gave the best result on bench so far of over 6000 but after having supply unplugged while working on the other hardware install I had the same trouble as you and I did what I suggested and it booted up OK. I then set RAM speed back to 133 and had no trouble since then with a bench figure of over 4000. Auto setting was 200 MHz and sometimes you need the best RAM or RAM that has more conservative SDP settings or lower speed RAM for a motherboard to boot. I have still trouble on the PCI buss which can be emulating from further upstream and I need to retire my SCSI card which is stopping the software restart/rebooting by not allowing the PCI to fully function. If the motherboard has power supplied to it the network socket should have the green LED lit. This LED light did not go out on my board within the unplugging period I estimate as I investigated it again but not sure about this as I did not look/notice when I did the power cycle after the non-boot episode. The network cable needs to be connected to an active network, a powered up switch should do and the PSU needs the mains plugged in for standby supply. I will be working on the board again shortly but it did lock up sudden just tonight and after about 15 seconds it shut itself down. It did not happen after this as the transistors and capacitors heated up I estimate but still had a stutter every so often for a while. It is unacceptable and I value the hardware so necessary attempted repairs will be taken.

I have got Msvcr80 40607 working better. The library has these strings within which are referenced to Msvcrt. __get_app_type.. __set_app_type.. ?unexpected@@YAXXZ.. ?terminate@@YAXXZ... ?set_unexpected@@YAP6AXXZP6AXXZ@Z... ?set_terminate@@YAP6AXXZP6AXXZ@Z.... _set_error_mode.msvcrt.dll.. __GLOBAL_HEAP_SELECTED.. __MSVCRT_HEAP_SELECT Because I wanted to use this library as Msvcrt then the reference cannot be Msvcrt and leaving it untouched meant there were a lot of executable load errors. The previous comments I have made of using Crtdll in the child module for _getdrives does not work out very well and Msvcrt10 is better. Msvcrt after the _set_error_mode function string has to be changed and then use Msvcrt10 for the _getdrives function link. Posting here as I thought it be helpful for KernelEx development because of the results. The results were that I can play videos on KMP and MPC_HC using all of the Lav filters. I can use WMP and Mplayer2 with the LavSplitter and other non Lav filters but I cannot use LavSpitter with the LavVideo and LavAudio filters in WMplayers and Zoom player. YouTube source_filter still worked the same for Mplayer2 and having to load through DW with all Lav filters in use for the decoding. Wbemcomn.dll still needs msvcr70. The advantage if using the Msvcr80 40607 apart from more functions available is that it will improve framerate slightly and more so in relation to games due to video card and CPU limitations.

Only work on the machine with PSU mains plug unplugged. You need RAM installed for boot to get the video output. Use only one RAM stick and video card. You will know from before approximately how long it took to boot, only allow that time and a bit more do not wait 25 seconds your CPU is probably getting hot. Plug in PSU to the mains once you have the video card and Ram stick installed. Be careful with the RAM stick and make sure it is seated properly. Turn on the start button on the case wait 5 seconds if no boot pull the PSU mains plug out wait about 5 seconds and plug the mains plug back in then press the case start switch again. The idea is that there will be still some residual voltage on the busses before you cycle it again. Try a different RAM stick with the procedure and try a different video card. If you have both nVidia and AMD cards then try both. If you are using an air cooled CPU it may not be enough, there usually is not enough heat conductivity from the CPUs copper plate though to the cooling grid and if so then water cooling is most likely essential. If you have it booting again manually setting RAM speed back from auto if allowable might help with this start problem.

MOZCRT is a renamed MOZCRT19.dll last used in FF8, it has some rather updated functions which is best shown with an upload of comparison differences. LOGONSRV and RLOCAL32 are found in U98SESP3.64; - just extract DSCLIENT.exe. Functions in NETUI1.dll will have to match RADMIN32 functions if used when Radmin32 strings have been altered. TQUERY is from Office XP I think, vs is 10.109.3705.2 not all functions are there to replace QUERY.dll but a lot are. MaxAPI.dll is to correct a "MAX" module name that was missing in DW for a module. MaxAPI.dll is a PaperPort11 module - which is WinME compatible. NLS.dll from LH5381 will do. CLFS.sys from LH5048 will do. SDBAPI is from MESP1 which is SP2 AFAIK; - just extract INSTMSIA.exe. Me not knowing much about KexStubs wasted a lot of our time. I would like to know the Core.ini - (KexStubs is missing) details. Thanks for the driver link. Some LH prereleases can be obtained from winwoldpc.com MSVCRT compare.zip

@jumper LsaAddAccountRights is stubbed but we need LsaRemoveAccountRights stubbed as they go together in numerous cases or we can redirect functions to Pkmws.dll or Mssws.dll. Mssws is the better one vs 10.109.3705.2 original name "mssws9x.dll" from properties. They have these along with other sort after functions. LsaAddAccountRights LsaClose LsaEnumerateAccountRights LsaFreeMemory LsaNtStatusToWinError LsaOpenPolicy LsaRemoveAccountRights LsaRetrievePrivateData LsaStorePrivateData Radmin32 has these LsaAddPrivilegesToAccount LsaClearAuditLog LsaClose LsaCreateAccount LsaCreateSecret LsaCreateTrustedDomain LsaDelete LsaEnumerateAccounts LsaEnumeratePrivileges LsaEnumeratePrivilegesOfAccount LsaEnumerateTrustedDomains LsaFreeMemory LsaGetQuotasForAccount LsaGetSystemAccessAccount LsaICLookupNames LsaICLookupSids LsaLookupNames LsaLookupPrivilegeDisplayName LsaLookupPrivilegeName LsaLookupPrivilegeValue LsaLookupSids LsaOpenAccount LsaOpenPolicy LsaOpenSecret LsaOpenTrustedDomain LsaQueryInformationPolicy LsaQueryInfoTrustedDomain LsaQuerySecret LsaQuerySecurityObject LsaRemovePrivilegesFromAccount LsaSetInformationPolicy LsaSetInformationTrustedDomain LsaSetQuotasForAccount LsaSetSecret LsaSetSecurityObject LsaSetSystemAccessAccount NtFsControlFile is stubbed but I think from memory Kernel32 > DeviceIoControl will work.

I noticed that AC97 audio which I am using RealTek VIA drivers seem to cut the lower bass off. To counteract this I chose Underwater environmental effect which gives the bass back. You can choose Quartz up to LH5384 with Bcrypt from ROS it gives extra 1-2 FPS with test video from https://msfn.org/board/topic/181784-streaming-downloading-youtube-videos-in-2020/?do=findComment&comment=1186281 over LH5270 version. I get min FPS 23.8 max 25 and frame rate for AV1 is more to do with CPU cache size than CPU speed as increasing the RAM speed from 100 -133Mhz gave a better frame rate result than increasing CPU speed by 10%.

I was able to reply for a test but only has a very small window to type in with Opera 12.02 and WinME. I edited this with above mentioned system.

WinME use it for all I can use it for, viewed on large screen. Fast to boot, responsive, reliable. Usage examples, media center, email, web browsing, games. Motherboard ECS K8T890-A has SCSI hot swap bay, Quadro FX5500 GPU and is used for testing KernelEx and upgrading. Some software running on startup includes RP9 and Ieplore6 with http://www.bing.com/?scope=web&FORM=Z9LH as active desktop image. I have built 3 more AMD machines, a GigaByte GA-MA78LM-S2, an ASUS M5A78L LE and a VIA P4M900 P5VD2-VM. All Intel machines I tested would not get past the BIOS boot screen when a 2TB USB external drive was plugged into a USB port. Some BIOS's do not have configurable SATA access timings in which case reliable long term SATA drive usage can be a problem or used boards have SATA chip damage in which case I have used a SCSI card. The internal gigabit network controllers will work if WinME service pack 2 is installed from the installer to which a limit of how much RAM can be accessed is applied. The installer adds System.ini MaxPhyPage=40000. I could up this value a bit higher but even when changing the size of the C: drive up in size meant the MaxPhyPage size had to be lowered. I found this unfavorable and used an add on PCI network 100Mb card instead. MaxPhyPage does not work with WinME native - it does not make any difference. It only worked after SP2 was installed via the installer. EDIT: I have a faulty GB add in card and even Win10 could not use it with a resource allocation problem. I also now have a good but different same model GB controller which works with ME after changing some capacitors. MaxPhyPage with good controller does not need to be restricted and I have no MaxPhyPage setting in System.ini. For the GigaByte and ASUS board's USB hardware, of which the South Bridge chip is ATI SB750, I found that a forced install of AMD 756 PCI to USB Open Host Controller WinMe original driver was a better match than the Standard OpenHCI USB Host Controller of which will want to install. It has no green ? marks against the driver and has a bit better throughput but USB 1.1 throughput is only working on this board. The USB 2 driver was from OrangeWare OWC OUSB2 2004 drivers PCI Class USB 2.0 Enhanced Host Controller and will install naturally. The legacy USB support is good in safe mode having access to USB devices but if left enabled in BIOS there will be 2 drives letters installed for the 1 drive if the USB drive is plugged in at boot time. To resolve this NTFSfor98 can be installed and the drive formatted to NTFS remembering not to try and use files over 4.1GB unless split with FILE64. The K8T890 with 2.5 inch USB HDDs USB works at their speed limit of over 20MB/s for non externally powered HDDs. Network and USB speed has improved after exercising. The GA-MA78LM-S2 needed to go trough the add new hardware control panel to get the video card installed. Most do not need to be done this way, see next paragraph. One of my Intel processor boards now can boot up with a 2GB USB external storage HDD attached. It is an nForce 790i and as such not Intel. It has been exercising with Vista. The ASUS M5A78L LE board is available from AliExpress and the are about 3000 available. It came with BIOS 1601 which meant the FX processors can be used. It has an IDE port if needed. It has very good BIOS configuration adjustments where the SATA ports access timings can be adjusted. I am running 2 SATA drives. The CPU's for this board are a little harder to get but available. I am using an FX4170. 5GHz processors are selling for very high prices and I do not want to pay that amount for them. The Turbo CORE technology can be used if cores 3 & 4 are turned off in BIOS. I have short term overclocked the FX4170 to 4.5GHz just to try and had no problems. The board installed hardware easily and resource sharing conflicts can be removed so that there are exclusive resource sharing without any motherboard resources as a device by removing all system devices while in Windows and installing the PCI buss device first manually next boot. The ACPI devices do not return but ACPI could still be controlled through BIOS or can be disabled in BIOS. The ACPI BIOS device or PCI buss has to be removed last. Under the legacy support enabled is the USB2 speed setting Full Speed 12MB/s and Hi Speed 480MB/s. I am using a USB audio device for sound and once set to Hi Speed I have turned USB legacy support off.

The 16 bit cache / buffer sizes could be written into the drivers so the 82.16 graphics driver could be significant but I can not find it. I tried opening XUL FF47 several times with DW and the extra files that Schwups sees are not showing in my DW but if he is profiling FF47 then this is different and my previous post comments about it will be not relevant.

Yes API-MS-Win.reg should not be used as it directs the APIset modules to Msvcrt not Ucrtbase. The older version of knowndlls.reg should be disbanded too as I had not added and changed all APIsets that call UcrtBase to use UcrtBase. XPCOM is not an error as such really, it is asking for that file which was provided up until FF13 but then was dropped and it might be a default error message. The XPCOM message is a step in the right direction over a module we have installed error. What you did is find out how marginal the loading of FF is. Did you try keeping a FF profile after FF47 works with a smooth exit then reinstalling that profile after the XPcom mis-load or re-instate the registry by doing a scanregw /restore. I would do a second reboot first after the registry reinstatement to be sure. Patching the disc with backed up data might be easier than erasing the whole disc each time, it may not work though will narrow down easier the issues. Can you browse pages properly in different sites good without browser locking up? Referring to your last paragraph: You have started up FF52 because UcrtBase is used. This will affect your system and the gives XPcom message when starting FF47 afterwards is that right? See Schwups has to start DW several times to get the missing modules to indicate. This is unusual and indicates that his resources are stretched to the limit in some area which I do not know. It will be set in registry as a buffer size / cache and operate from there but knowing what / where the setting is is the challenge. What is the cache that DW uses when opening many different modules, the text is first to go but is probably a different cache to that of having to start DW several times. The cache size might be the same but it is filled more before Schwups opens DW or something like this. This is different for me. There has a lot of effort placed in getting FF later versions working but this browser is a cross platform one with a lot of overheads as a consequence. I would like to see Maxthon browsers looked at as they can work the websites properly. Maxthon Nitro is a slim browser I will comment elsewhere if after testing in Win7 and is OK.

I could not get the HD audio working with XP either. If you try Vista or Win7 then that worked for me and it will test your hardware.

Do you mean that you tried FF47 and FF52? If so did you try FF47 first, You used to be able to use different FF executables to start FF and then you edit the application.ini and platform.ini to suit your extensions. Perhaps if you set FF47 working again then you might be able to swap out FF52 executable with FF47's for a try. Check with DW if compatible first. Your KnownDlls has still got the error ones I made in it. Do a search of -0.dll in the KnownDlls section of the registry and delete the entries then do a search of -1.dll and delete those. It might also be a good idea to wait till Schwups gets back as I have not been experimenting on FF. The extra KnownDlls would have been placed there by the OS they are not essential because the module name is not changed. The 16bit Known16dlls will return though if deleted. I removed any reference entries that were 32 bit modules in the Known16dlls section. Schwups Jumpers explanation of the kex\\..\\ is precise. There is no quote-mistakes ("") inside the Win7 APIs file but if file redirection did not occur then there is a problem. You removed KEX\\..\\ and redirect did occur. That is what happened isn't it? >>"The DependencyWalker doesn't find these files. In other words, it can't handle KernelEx" It is because KernelEx folder is not mapped to an environmental variable, that is, not in a mapped/known path. Thus means for PDH and WTSAPI32 modules that are in the KernelEx directory are only known by KernelEx. The FF or any other program or module cannot directly link to the files in the unmapped directory. I do not think that these two files are used at all by the startup of FF but if they are found by FF then we get the XPcom.dll is missing error.

Just have them no mode selected in registry. This means the right click module properties will have the top 'Use default compatibility options (KernelEx is enabled)' radio button selected. I was thinking then perhaps not have UCRTBASE selected KernelEx BASE. In other words do not change any KernelEx settings. Keep a Known good profile of FF. It might have been FF profile changes. The other thing is depending on how the LZ32.reg affected the registry. I think Lz32.reg redirected Dnsapi to lz32 along with other other redirects. Registry could have changed or if processor hit hard against a solid fault then hardware could have changed momentarily and it is OK now.

Not really the .dll on the name is referring to modules that do not exist and should be cleaned. LZ32 is an old file and there are no extra functions other than that were present in WinME's version which I think is the best (check Win10's module). I remember trying LZ32.reg from KEX18 and it directed DNSAPI to LZ32 so "Dnsapi"="Kex\\..\\LZ32.dll" must work with KEX18. I commented about this in the Core-Updates topic. Those reg settings in KEX18 are to be avoided. You can go back to original Core.ini but I doubt very much that adding IsProcessorFeaturePresent back to the Kernel has got anything to do with stopping FF47. When you said you reverted do that mean you restored the registry and when was FF47 last working, you may need to go back in time to that period. The Core.ini has just got 2 lines of text removed that should not have been there. Check by comparing with your original. Once you try and launch a different version of FF the application data is shared unless a portable version is used and the directories are different or replaced with the new modules. The thing is though with different directories means the registry may not 100% as some settings may still be with the old directory. I would only experiment on a backup of your system and keep a copy of the application data/profile to go back to. Best thing to try is leave registry as it is without the LZ32.reg and remove the profile of FF or restore it if you have a copy. It is kept in Application Data\Mozilla if not portable version. I am not sure were portable profile is kept. >>Replaced it, now it just says it couldn't load XPCOM PDH amd WTSAPI32 must be a KernelEx knownDll in same folder as KernelEx and be in follower mode see https://msfn.org/board/topic/181424-firefox-24-for-me-and-98/?do=findComment&comment=1180695 otherwise XPCOM is missing error will occur. The last XPcom.dll that was compiled was for FF13 and it is not compatible with newer FF versions.

Yes Core.ini should be edited and I have done so in an upload here https://msfn.org/board/topic/178283-how-you-really-browse-the-web-on-98me-in-2019/?do=findComment&comment=1178441 Replace Core.ini with my edited one and then reboot : - it is what Jumper wanted. The errors in the KnownDlls were that I left some with .dll on the end of their name and they were double ups except for the Unicows one so if you go into the registry location HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\KnownDLLs delete any entries with .dll an the end of their name in the name section. If you merged the new upload then the Unicows one would be corrected but there will still be the old entry with .dll at the end of its name.

I have discovered that if an executable needs to be run to load the implicit module/s then it can ignore the registry settings (many Win10 system executables with inbuilt icons exhibit this behavior). If this is the case then there are a few alternatives, 1 for example, rename UcrtBase.dll to the APIset name that the Exe is looking for or 2 edit the Exe to by changing the API-MS-WIN string to UcrtBase.dll if it allows it. KnownDlls redirect to UcrtBase.dll should solve the error with api-ms-win-crt-convert-l1-1-0.dll on start though. I am glad to have looked into the KnownDlls again as I had made some errors and have cleaned it up into the upload again. The file comparison is an exclusive difference, that is, if the function exists in all compared modules then it is not shown. I can do a comparison for other modules if anyone wants it. The new upload of KnownDlls should fix the VCRUNTIME140.dll errors. If looking into my KnownDlls there is ANSI version of Radmin32 in the Value data. KernelEx has worked functions that Radmin32 has but KEX works with the module name first for those, that is, KernelEx does not react to Radmin32's functions as Radmin32 it is not named Ntdll nor Advapi32 as examples. Most function calls now do not have "A" at the end which signifies ANSI so the Radmin32 functions that do have the A at the end will need the A removed in the Radmin32 function strings. Check with DW. It is a choice to make and check whether Radmin32 is acceptable as a Dll redirect or not.

You are using a Win7 x64 system then. The same thing happens with 16 bit modules in WinME. The same solution is required. Remember when you right click a module then it introduces the context menu programing. An alternative to right click delete is left click the module then press the delete key but this must be done after a fresh boot only otherwise that doesn't work either. There is some talk of it here too but I do not think it will solve the issue. https://msfn.org/board/topic/178181-the-action-cant-be-completed/?do=findComment&comment=1161234 I have Win7 32 bit installed only and it does not have your issue when ownership is taken over from the system correctly.

I have just checked out your API-MS-WIN modules and they need UCRTBASE.dll - they call for it anyway. UCRTBASE.dll uses API-MS-WIN modules so it is made WinME compatible with my KnownDlls.reg upload and UCRTBASE.dll set KernelEx BASE. You need to obtain module UCRTBASE.dll - (a Win10 module) and the API-MS-WIN modules are set to load UCRTBASE.dll in registry KnownDlls as explained. UCRTBASE loads with KEX24 I have tested it and am fairly sure of that. I will update my KnownDlls again once I have made changes to include the new API-MS-WIN modules.

WinME's Kernel32.dll can not be loaded in two different memory locations even if renamed, it is not relocatable, it would be locked in place with the hardware I would think. It sounds like api-ms-win-crt-runtime-l1-1-0.dll file being unable to access the desired address means you have not redirected it in registry because you would not get an api-ms-win-crt-runtime-l1-1-0.dll error, you would get the redirected DLL's name error. AFAIK Jumper's registry settings can not be used as they are written. The registry should have just KERNEL32.DLL for example as the Value data. If Ktree says that KernelEx has catered for the function then KernelEx will do its thing, either stub it or redirect the function. Kernel32.dll and all KernelEx files like Kexbasen.dll should be set KEX disabled as Jumper said in the KernelEx-45-Core-Updates topic. I have not got api-ms-win-crt-runtime-l1-1-0.dll listed in my KnownDlls either so I have not come across its use or I have not got a suitable Dll for its replacement : - redirect. So I am not sure about Jumper's API-MS-Win.reg list unless the functions that the parent module calls are catered for by KernelEx. My current full KnownDlls reg entries are uploaded back into https://msfn.org/board/topic/173233-kernelex-45-core-updates-45201617/?do=findComment&comment=1157548 if anyone is interested and it will be zipped. I am using MSVCR80 vs 8.0.31113.25 renamed as MSVCRT as a system DLL in this build that uses the known Dll upload. Not all functions are catered for in some redirects so check with Dependency Walker by loading the module that calls the API-MS-WIN Dll module.

Because DLL forwarding does not work in WinME we forward the DLL in the registry by using KnownDlls. If the API set forwarded functions are in the DLL then just use KnownDLLs in registry to forward API set to the DLL. For example Jumper's API-MS-Win.reg would look like this for the first 3 registry additions. Kernel32.dll is in a mapped/known path so the full path name does not need to be shown to the registry. REGEDIT4 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\KnownDLLs] "API-MS-Win-Core-Console-L1-1-0.dll"="Kernel32.dll" "API-MS-Win-Core-DateTime-L1-1-0.dll"="Kernel32.dll" "API-MS-Win-Core-Debug-L1-1-0.dll"="Kernel32.dll" The .. means go to the parent folder (one above current one). The \ in the registry and folder paths means end of folder name and there is a child folder if named after the \. The \\ I do not think would make any difference to the \ but I would appreciate the difference explained. I think it would look 2 folders down but the \\ means that there would be nothing in the folder between the 2 \\ as it is unnamed and therefore would only look in child folder. I hope this makes sense. Note I gave my known DLL list here https://msfn.org/board/topic/173233-kernelex-45-core-updates-45201617/?do=findComment&comment=1157548 which is out of date now but it will show more API sets and add Jumper's list to my list too. I just downloaded my KnowDlls.txt and not all Msvcr90.dll redirects are the best choice for the API sets as some functions are not included in Msvcr90 so use DW to check for compatibility. I have chosen Msvcrt.dll now but it depends on what version of Msvcrt that you are using and you will need to choose an appropriate DLL for the redirect although if the missing function is not called then the redirect will still work for functions that are called. This is an advantage of using a forwarding DLL to a known DLL.

I think you need a zip of the program, I do not think it will install with the exe. Also you need Azul OpenJDK 8 Update 262. See https://msfn.org/board/topic/178283-how-you-really-browse-the-web-on-98me-in-2019/?do=findComment&comment=1184509 and next few pages.

When testing, it was FF35, some web pages worked and some froze. I believe it was FF8 that was supported with K4.5.2 and FF9 also worked latter. There is still freezing with FF4 and above for me really, - it depends on the web page and FF4 - 9 does not make a difference as far as the freezing is concerned with the particular pages. FF3.6 had no Gif animation image support. Originally when accessing my network drive, - NAS, the NIC cards were freezing and It was the directory sub directories. The deeper I explored then the freeze would happen. They got better over time. I have very few add on cards that work, - most second hand. The Realtek ones and the Marvel one is worth a try.