jumper

Site appears to use WorldNow.com for all media content. Video is in WNVideoWidget container. Conveniently, WorldNow offers streaming video capture software.

Last month I gave this post a "Like This" because it told me exactly what I should investigate. (I did and will pursue it soon.)> SeaMonkey 2.7.x. and 2.8 are unfortunately still freezing. In or after what API's? (Use the debug console.) > I gave a lot of info about the gimp issue a while back starting with this post: Yes, but I need to know in or after what API's the problem occurs. (Use the debug console.)

KernelEx.dll v.12 will address the UPX regression. I'll tweak the resolver code to detect UPX'd modules and use the old method if found--explicit imports will be treated the same as implicit. I think the UPX loader does all its explicit loads before calling VirtualProtect, so perhaps there I can safely toggle back to the new method. I'll also try to add back-end support for some new loader options. UI support will come later. As for the gimp/git problems, I need to know what APIs are involved.

Kexbasen.11 revealed an initialization loop vulnerability in the KernelEx 4.5 architecture. I plan to address it more completely in "Kex16." For now, the Kernel32 fixes in Kexbasen for TlsAlloc, TlsFree, TlsGetValue, TlsSetValue have been rewritten to be better, faster, and (most importantly) not need preinitialization. Along with restoring the delay-load linker options, Kexbasen should now be stable again with current SE and ME configurations. Use Kexbasen.12 with KernelEx.11 and Kexbases.11. Many thanks to everyone for their feedback and patience while I worked through this challenging puzzle. kexbasen.12.7z

I've never booted from a USB drive, but it probably needs to be FAT16 or even FAT12, partitioned accordingly (<2GB, <128MB). Depending on the level of BIOS support on your laptop, you may need to use a formatting utility that can make the USB drive look like a USB ZIP or USB floppy drive.

You can download an .iso for a Windows-compatible OS here: ReactOS

What is the chipset on the capture card? Maybe bt848 or bt878? A generic driver might work.

You might be able to hide the flash drive from BIOS/DOS by connecting it via mini-hub.

Perhaps the utility changes default registry settings that affect the second boot. Perhaps a "RunOnce" is installed that actually needs to be run every time. Remove the autorun entry for the utility. Check and compare boot logs.

A friend of mine has an early tri-channel i7 mb with six slots (some had three). He had lots of trouble getting the DDR3 ram to work at full speed, but all 3x2=6GB (and later 6x4=24GB) were recognized.

Comparison_of_file_archivers Try latest versions of 7-Zip, WinAce, WinRar, WinZip....

Because the problem is with FlsAlloc, use kwinsys-.reg to remove the registry patch and add these lines to stubs.ini to use the standard version: [Kernel32.dll]TlsAlloc=>Kernel32:TlsFree=>Kernel32:TlsGetValue=>Kernel32:TlsSetValue=>Kernel32:(In core.ini on the "contents=" line, Kexstubs/Kstub822 must be the last DLL or you will also have to add API selection lines further down.)The downside to this workaround is that there will only be 80 Thread Local Storage data slots, bad news for apps that are highly multi-threaded or use lots of plug-ins. I'm testing a new TlsAlloc implementation now. Look for a new release tomorrow! As for the installer, the only line in Update.bat before the "---Updating KernelEx 4.5.2015---" is "echo off". So the mystery commands must be in your own startup files. Ask in the Scripting forum for help locating the location of them. {Edits in bold above.}

I see three distinct problems: 1) script does not display MsgBox 2) script calls mirror file without answer "yes" 3) mirror.exe needs later version of Windows Working backwards: 3) mirror.exe needs to be set to XP mode to be immune to how it is invoked. 2) The script... You want: My script simply calls one of those mirror files, once you've answered "yes" to a yes/no prompt. You programmed: If you answer "no" the script just terminates. These are not the same thing. Try this script: On error resume nextcompstr = wscript.arguments(0)verify = MsgBox("Run QuickMirror System Backup to Drive F:?",vbYesNo, "Confirm")If verify = vbYes Then Set objShell = WScript.CreateObject( "WScript.Shell" ) objShell.Run("""C:\Utilities\QuickMirror\System Backup to Drive F.mir""") Set objShell = NothingEnd IfThe .mir will only be launched if the MsgBox appears and is answered "yes".1) Why the MsgBox doesn't display is still a mystery, but could be because an error (at bff741ca?) occurs that is handled by wscript instead of crashing. Remove "On error resume next" and see it this exposes a crash.

Almost. Make sure your CPU/heatsink combo will both generate and handle the 160+ degrees necessary to properly cook the fish without frying your whole system. And when you order the chips to go with the fish, select only those with Win9x drivers.

I see it now: Kexbasen.dll -> Cryptui.dll -> Certcli.dll I have Certcli.dll forwarded to Lz32.dll via KnownDLLs so DW shows me: Kexbasen.dll -> Cryptui.dll -> Lz32.dll I haven't written any stubs to go with the forward yet, so if you can find a Certcli.dll that will work with KernelEx, that would be great.

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?