jumper

My Ole32.dll is 98se stock 4.71.2900. Yours? No version of Ke*.dll is dependent on Certcli.dll. In DW find the module reference in the tree and report the modules (and their versions) above it. Is it a delay-load (hour glass)?

Sounds like you have a DLL in System that needs KernelEx enabled. The message is from VLC, not the OS, so VLC does in fact start to start. Try profiling it in Depends to see what delay-loads might be failing. Also, "Use API Hook" and then "Output to log file" in KernelEx ApiLog Console (DebugWindow.exe) to see what modules KernelEx is loading. (Install the ApiHook "Extra" into KernelEx folder if you haven't already.) Kexstubs is a method for users to create and test their own new stubs. It was always meant for the best stubs to be migrated into KernelEx's base offerings. I am now doing that.

When I right-click on the hard drive, the context menu does not have the SendTo item. It is only in the context menu for files and folders. I have stock IE 5.00.2614.3500 with Active Desktop disabled.

@Mikl Yes, disable KernelEx extensions on Lz32.dll. Disabling prevents a DLL from using Kex, not Kex from using the DLL. Use the registry patch to quickly and completely disable KernelEx on all system DLL's. That should eliminate the Runonce error. Once you reach the desktop, check the loaded module list for Mprexe in a process viewer such as ProcWin and see if KernelEx, Kexbasen, Kexbases, and Kstub822 are all loaded. If one is not, apps that need it will not work. @Dave-H QuickMirror 1.32 is an XP app, so set its mode to 2K or XP. Despite their claims to still support Win9x, Dependency Walker shows the required subsystem on mirror.exe as 5.1 and also shows unresolved dependencies in Kernel32 and Shell32 on my 98se system. QM1.32 also bundles an old version of Unicows.dll, so you may want to delete it. Wscript.exe should be in the Windows folder, but if your scripts work best with it in System then leave it there. This Wscript.exe placement issue is most likely unrelated to the problem at hand or KernelEx in general. Unfortunately, you can't check "Don't use these settings in child processes" on it, so you'll have to manually enable KernelEx on any apps such as QuickMirror that require it and are invoked by script.

Compatibility with USP3 and other packs and upgrades is the goal. So please add the registry default mode setting for winsys and change the mode manually for any files that need KernelEx. Better yet, treat them as Auxiliary DLL's--move them into the KernelEx folder and add a [HKEY_LOCAL_MACHINE\Software\KernelEx\KnownDLLs] entry for each.

We can easily redirect these. Details tonight. The API Set Schema for Windows 7 Windows 7 Kernel Architecture Changes - api-ms-win-core files API-MS-Win7.reg: 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"""API-MS-Win-Core-DelayLoad-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-ErrorHandling-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-Fibers-L1-1-0.dll"="Kernel32.dll"""API-MS-Win-Core-File-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-Handle-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-Heap-L1-1-0.dll"="Kernel32.dll"""API-MS-Win-Core-Interlocked-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-IO-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-LibraryLoader-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-Localization-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-LocalRegistry-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-Memory-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-Misc-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-NamedPipe-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-ProcessThreads-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-Profile-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-RtlSupport-L1-1-0.dll"="Ntdll.dll"API-MS-Win-Core-String-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-Synch-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-SysInfo-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-ThreadPool-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-UMS-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-Util-L1-1-0.dll"="Kernel32.dll""API-MS-Win-Core-XState-L1-1-0.dll"="Ntdll.dll"API-MS-Win-Security-Base-L1-1-0.dll"="Advapi32.dll""API-MS-Win-Security-LSALookup-L1-1-0.dll"="Advapi32.dll""API-MS-Win-Security-SDDL-L1-1-0.dll"="Advapi32.dll""API-MS-Win-Service-Core-L1-1-0.dll"="Advapi32.dll""API-MS-Win-Service-Management-L1-1-0.dll"="Advapi32.dll""API-MS-Win-Service-Management-L2-1-0.dll"="Advapi32.dll""API-MS-Win-Service-winsvc-L1-1-0.dll"="Advapi32.dll""Kernelbase.dll"="Kernel32.dll""Sechost.dll"="Advapi32.dll"stubs.ini: [Kernel32.dll]ImpersonateNamedPipeClient=>Advapi32:For Windows 8 and beyond we will need quite a few more. Windows 8 API Sets

Over the years I've booted a few Linux live CD's. I've also downloaded three React OS live CD's, but haven't tried to boot from one. So far I've just been testing the DLL's for use on Win98se with KernelEx. I recently acquired a system that dual boots Ubuntu and XP-MCE, but haven't done any virtual machines yet. Other than some KernelEx development on an older XP system and a bit of Android 2.3 tablet use, 98se is still my primary computing platform.

The fix for Release 4.5.2015.11 is kwinsys.reg: REGEDIT4[HKEY_LOCAL_MACHINE\Software\KernelEx\AppSettings\Flags]"C:\\WINDOWS\\SYSTEM\\*"=dword:00000001It can be undone with kwinsys-.reg: REGEDIT4[HKEY_LOCAL_MACHINE\Software\KernelEx\AppSettings\Flags]"C:\\WINDOWS\\SYSTEM\\*"=-

The solution to guest wifi is to have a secondary Access Point (with its own password) that only provides Internet access. Or offer to let them use your dial-up.

Is that Virtual Box peaking out from under the Mate Terminal window? It looks like you are also experimenting with a React OS VM installation. I'd like to hear how usable ROS is becoming. Maybe not so usable, since you didn't mention it?

> I know you can run 98 with that much ram...but am unsure about the processor speed and that its 64 bit. I don't think 64-bit cpu's can boot 16-bit DOS, a requirement for Win9x.

> about 750MB harddisk free This is less than the size of the file you are trying to compact. Free ~2GB by moving files to a thumb drive and then retry the compaction. Otherwise, instead of compacting the Inbox in-place, compact by moving all emails to a new folder. Use OE to create a new folder "Oldbox" (both on the server and locally) and move all contents from Inbox to Oldbox. This will require having >900MB free locally. Then you should be able to easily compact the empty Inbox or just delete its .dbx. The Inbox on the server will also be empty, so no worries about redownloading "everything". (There also should be a setting somewhere named something like "Leave mail on server" that prevents email from downloading unless you open it.)

If FlashGet works on the command line, it should take a timeout parameter and return an error code that the script can check to determine if the download was successful or timed out. What scripting environment and language are you using?

No -- I need help debugging now more than ever! Follow the instructions in post #243 and then post #232. Please ignore most of post #229--the important values to note are EIP=bff741ca (or bff641a2) and EDX=00000000, and also Stack dump: 7d00b90d. Use Procwin to debug.

This Google search of MSFN will find what you're looking for:

EnumDisplayMonitors would be present under Import->USER32.dll. If it is not, this driver file will not have that particular problem but still might not work. If EnumDisplayMonitors is present, you could try using Importpatcher or a hex editor to change it to another four-parameter function that is available in Win95's User32.dll such as CreateDC, CreateIC, EnumObjects, or DrawEscape, but with low chance of success.

I recently received a request to update NetapiEx to handle NetLocalGroupGetMembers. Until I do, here is the Kexstubs definition: [Netapi32.dll] NetLocalGroupGetMembers=o8

Sorry, I was confused by the misplaced modifier: "If you create a shortcut for a file to be placed on the desktop" It should read: "If you create on the desktop a shortcut to a file" And mistook the following parenthetical as an example of what you were trying to create, not a method for creating it. > (right-click -> send to -> Desktop (create shortcut) ) The special "Desktop (create shortcut) " SendTo target is the "mysterious" one I mentioned--because it wasn't there, and then it was! All that said, when I test the original process and create on the desktop a shortcut to a file using the right-click -> send to -> Desktop (create shortcut) method, a shortcut is indeed created but without any pop-up. I've tested many file types ranging from EXE and REG to URL and LNK. What file type was involved in you pic, PROBLEMCHYLD? My Shell32.dll is unmodified original Win98se -- 4/23/99 checksum 0x00162873 (DW). Footnote: shortcuts to BAT files created with this method go to my temp folder, not to the desktop!

Dieter (alias Fernando) at Win-raid.com: Preliminary Notes regarding Intel's Chipset "Drivers" And discussion: http://www.win-raid.com/t895f42-Intel-Chipset-Device-quot-Drivers-quot-INF-files.html#msg15789 There also exist versions: 10.0.13, 14, 20 WHQL, 22, 24, 27 and v10.1.2.10 WHQL.

https://web.archive.org/web/20131217103733/http://downloadmirror.intel.com/23411/eng/INF_allOS_9.4.4.1006_readme.txt http://downloadmirror.intel.com/23061/eng/inf_9.4.0.1027_readme.txt Version: 9.4.0.1027 as mentioned in the top post appears to be more recent (September 02) than Version: 9.4.4.1006 (August 01) What Target should we be searching for? Edit:Then there's SuperMicro's ftp://ftp.supermicro.com/CDR-X10_1.03_for_Intel_X10_platform/Intel/INF/Chipset_v9.3.2.1020/Releasenote_9.3.2.1020.htm with History and changelog from 2012-2014And Intel's link for Intel desktop boards.

I don't understand the problem. On my SE system I just now did a right-click drag of my desktop folder into my SendTo folder and upon release selected "Create Shortcut Here". It did it without any extra dialogs. So what exactly is the method you are refering to and what is the "extra" dialog? There is also a special empty file named "Desktop (create shortcut)" that sometimes mysteriously appears in the SendTo folder (but I don't know how to create it on-demand). Files sent to it will get a shortcut created on the Desktop. edit: quick reply posts are being mangled again....

DumpPE is a 32-bit console app. Run it in a DOS box, or from a batch file such as: DumpPE-disasm.bat @echo off%0\..\DumpPE -disasm %1 > %1.asmclsI have a shortcut (renamed simply "DumpPE -disasm") to this batch file in my SendTo folder.Last version of DumpPE is 2.32. I'll add a Wayback link to it in Post #1.

Crypt32.dll might not be the only file we need to change the compatibility setting for.... Before proceeding, export HKEY_LOCAL_MACHINE\Software\KernelEx with RegEdit! (in addition to a ScanReg backup) Open Kexbasen.dll (v.11) in Dependency Walker and go to the Module List (non-tree) panel. Select the first entry and press Alt+Enter to bring up the Property sheet for that DLL. Then click the next entry and press the down arrow key and then Alt+Enter to bring up the next sheet. Quickly repeat until sheets for all DLL's are open. Then for each sheet click: the KernelEx tab, "Disable KernelEx extensions", OK. Now export HKEY_LOCAL_MACHINE\Software\KernelEx again and use Windiff or fc to isolate the changes. You are now ready to try Kexbasen.dll v.11 again.

Great information, everyone! bff*41ca (in Kernel32.dll) and 7d00b90d (in Kexbasen.dll) are the common keys. More about this later (even if someone else makes use of the new PDB files, runs DumpPE on Kexbasen, and reports back before me ).... I looked at Kexbasen in Dependency Walker and found 21 non-delay-load system file dependencies. Most of them I have disabled Kernelex on. Crypt32.dll was the key (haha)--I un-disabled KernelEx on it and was finally able to reproduce the crash (ironically with DumpPE): DUMPPE caused an invalid page fault in module KERNEL32.DLL at 016f:bff741ca. Registers: EAX=c140bad0 CS=016f EIP=bff741ca EFLGS=00010202 EBX=00000001 SS=0177 ESP=006bfb18 EBP=006bfb44 ECX=7d00b90d DS=0177 ESI=5cf01500 FS=3497 EDX=00000000 ES=0177 EDI=00000000 GS=0000 Bytes at CS:EIP: ff 4a 10 75 08 89 42 08 ff 42 04 90 c3 39 42 08 Stack dump: 7d00b90d 00000000 5cf01500 00000001 8181f7c8 bff741f7 bffc9490 bff8433d 00000000 5cf01500 8181dde0 006bfb8c 5cf33132 00000001 5cf01500 00000001 Re-disabling KernelEx on Crypt32.dll fixed the problem again. (Note: in KernelEx property tab, the Apply button is broken and will prevent changes from being applied; use the Okay button!)

I think I know what change triggered the problem, but am still trying to determine what the actual problem is. I haven't been able to reproduce the problem on my SE system, but it may have to do with what DLL's (names and versions) are dynamically linked to by Kexbasen at load time. Here is my Taskinfo2000 Process Pane and MPREXE.EXE Current Process Pane (sorted by name) right after a full reboot: Process PaneID Process % CPU LT % CPU CPU Sw/s InMem KB Total KB Th Pri Ver State Path + Idle 98.54% 94.52% 3:33 14 0 0 1 Idle 4.0 Idle + KERNEL32.DLL 0.05% 0.10% 10 32 44 3 High 4.3 32 C:\WINDOWS\SYSTEM\KERNEL32.DLL + MSGSRV32.EXE 0.05% 0.04% 0:03 2 52 64 1 Norm 4.0 16 Sys C:\WINDOWS\SYSTEM\MSGSRV32.EXE + MPREXE.EXE 0:01 0 0 0 1 Norm 4.0 32 Sys C:\WINDOWS\SYSTEM\MPREXE.EXE + mmtask.tsk 0 0 0 1 Norm 4.0 16 Sys C:\WINDOWS\SYSTEM\mmtask.tsk + EXPLORER.EXE 0.05% 0.07% 0:04 2 1,932 8,064 4 Norm 4.0 32 C:\WINDOWS\EXPLORER.EXE + SYSTRAY.EXE 1 668 2,900 1 Norm 4.0 32 C:\WINDOWS\SYSTEM\SYSTRAY.EXE + TASKINFO.EXE 1.23% 4.83% 0:05 13 904 2,840 1 Norm 4.0 32 D:\PROGRAM FILES\TASKINFO\TASKINFO.EXE + VxD NTKERN 0.05% 0.38% 0:01 22 0 0 7 Norm 4.3 NTKERN Current Process PaneName Base Size Version Description Company Full Path ADVAPI32.DLL BFE80000 65,536 4.80.1675 Win32 ADVAPI32 core component Microsoft Corporation C:\WINDOWS\SYSTEM\ADVAPI32.DLL COMCTL32.DLL BFB70000 581,632 5.81 Common Controls Library Microsoft Corporation C:\WINDOWS\SYSTEM\COMCTL32.DLL COMDLG32.DLL 7FE10000 184,320 4.72.3510.2300 Common Dialogs DLL Microsoft Corporation C:\WINDOWS\SYSTEM\COMDLG32.DLL CRYPT32.DLL 5CF00000 479,232 5.131.1880.14 Crypto API32 Microsoft Corporation C:\WINDOWS\SYSTEM\CRYPT32.DLL CRYPTUI.DLL 61400000 450,560 5.131.1878.14 Microsoft Trust UI Provider Microsoft Corporation C:\WINDOWS\SYSTEM\CRYPTUI.DLL GDI32.DLL BFF20000 155,648 4.10.2227 Win32 GDI core component Microsoft Corporation C:\WINDOWS\SYSTEM\GDI32.DLL IMAGEHLP.DLL 7CC00000 118,784 4.00 Windows NT Image Helper Microsoft Corporation C:\WINDOWS\SYSTEM\IMAGEHLP.DLL IMM32.DLL BFE20000 16,384 4.10.1998 Win32 IMM32 core component Microsoft Corporation C:\WINDOWS\SYSTEM\IMM32.DLL KERNEL32.DLL BFF70000 471,040 4.10.2222 Win32 Kernel core component Microsoft Corporation C:\WINDOWS\SYSTEM\KERNEL32.DLL KERNELEX.DLL BFA00000 233,472 4.5.2015.11 KernelEx Core with ApiHook Xeno86 C:\WINDOWS\KERNELEX\KERNELEX.DLL KEXBASEN.DLL 7D000000 118,784 4.5.2015.11 KernelEx Base Non-shared Api Library Xeno86 C:\WINDOWS\KERNELEX\KEXBASEN.DLL KEXBASES.DLL BFA40000 274,432 4.5.2015.11 KernelEx Base Shared Api Library Xeno86 C:\WINDOWS\KERNELEX\KEXBASES.DLL KSTUB822.DLL 19980000 65,536 C:\WINDOWS\KERNELEX\KSTUB822.DLL LZ32.DLL BFE60000 24,576 4.10.1998 Win32 LZ32 core component Microsoft Corporation C:\WINDOWS\SYSTEM\LZ32.DLL MPR.DLL 7FBF0000 57,344 4.10.1998 WIN32 Network Interface DLL Microsoft Corporation C:\WINDOWS\SYSTEM\MPR.DLL MPREXE.EXE 00500000 28,672 4.10.1998 WIN32 Network Interface Service Process Microsoft Corporation C:\WINDOWS\SYSTEM\MPREXE.EXE MPRSERV.DLL 7FAD0000 155,648 4.10.2222 Multinet Router Microsoft Corporation C:\WINDOWS\SYSTEM\MPRSERV.DLL MSASN1.DLL 77430000 69,632 5.00.2195.6905 ASN.1 Runtime APIs Microsoft Corporation C:\WINDOWS\SYSTEM\MSASN1.DLL MSNET32.DLL 7FB00000 77,824 4.10.1998 Microsoft 32-bit Network API Library Microsoft Corporation C:\WINDOWS\SYSTEM\MSNET32.DLL MSNP32.DLL 7FB20000 81,920 4.10.2222 Network provider for Microsoft networks Microsoft Corporation C:\WINDOWS\SYSTEM\MSNP32.DLL MSPWL32.DLL 7FB40000 40,960 4.10.1998 Password list management library Microsoft Corporation C:\WINDOWS\SYSTEM\MSPWL32.DLL MSVCR70.DLL 7C000000 344,064 7.00.9981.0 Microsoft® C Runtime Library Microsoft Corporation C:\WINDOWS\SYSTEM\MSVCR70.DLL NTDLL.DLL BFEE0000 20,480 4.10.1998 Win32 NTDLL core component Microsoft Corporation C:\WINDOWS\SYSTEM\NTDLL.DLL OLE32.DLL 7FF20000 790,528 4.71.2900 Microsoft OLE for Windows and Windows NT Microsoft Corporation C:\WINDOWS\SYSTEM\OLE32.DLL RPCRT4.DLL 7FB90000 335,872 4.71.2900 Remote Procedure Call DLL Microsoft Corporation C:\WINDOWS\SYSTEM\RPCRT4.DLL SHELL32.DLL 7FCB0000 1,400,832 4.72.3612.1700 Windows Shell Common Dll Microsoft Corporation C:\WINDOWS\SYSTEM\SHELL32.DLL SHLWAPI.DLL 70BD0000 278,528 5.00.2614.3500 Shell Light-weight Utility Library Microsoft Corporation C:\WINDOWS\SYSTEM\SHLWAPI.DLL USER32.DLL BFC00000 69,632 4.10.2233 Win32 USER32 core component Microsoft Corporation C:\WINDOWS\SYSTEM\USER32.DLL USP10.DLL 66650000 344,064 1.0325.2180.1 Uniscribe Unicode script processor Microsoft Corporation C:\WINDOWS\SYSTEM\USP10.DLL VERSION.DLL BFE70000 24,576 4.10.1998 Win32 VERSION core component Microsoft Corporation C:\WINDOWS\SYSTEM\VERSION.DLL WININET.DLL 76280000 458,752 5.00.2614.3500 Internet Extensions for Win32 Microsoft Corporation C:\WINDOWS\SYSTEM\WININET.DLL WINMM.DLL BFDF0000 65,536 4.03.1998 System APIs for Multimedia Microsoft Corporation C:\WINDOWS\SYSTEM\WINMM.DLL WINSPOOL.DRV 7FE40000 36,864 4.10.1998 Win32 WINSPOOL core component Microsoft Corporation C:\WINDOWS\SYSTEM\WINSPOOL.DRV WINTRUST.DLL 47600000 172,032 5.131.1880.14 Microsoft Trust Verification APIs Microsoft Corporation C:\WINDOWS\SYSTEM\WINTRUST.DLL WS2_32.DLL 76000000 73,728 4.10.2222 Windows Socket 2.0 32-Bit DLL Microsoft Corporation C:\WINDOWS\SYSTEM\WS2_32.DLL WS2HELP.DLL 75FE0000 24,576 4.10.1998 Windows Socket 2.0 Helper for Windows 98 Microsoft Corporation C:\WINDOWS\SYSTEM\WS2HELP.DLL Please test your systems with the latest version of Kexbasen that will allow you to reach the desktop and report any DLL differences that might be significant.