Dave-H

Strange, I do exactly the same thing myself, and it has always worked. This is my shortcut run properties - "C:\Utilities\Registry Utilities\NT Restore XP\AUTOBACK.EXE" D:\WIN-NT\RegBack\AutoBackup\#Date# sysreg curuser otherusers /noconfirmdelete /noprogresswindow /days:5Try using an absolute path instead of %SystemRoot%.

I've noticed that Opera 12.02 no longer puts up its popup notification at the bottom right when a download is completed. I assume that all such messages are now not working. It was fine using KernelEx 4.5.2015.10, and I'm pretty sure it was OK with 4.5.2015.11 too when I had the registry fix applied using the original files. I think it probably stopped working when I replaced the 4.5.2015.11 version of kexbasen.dll with the 4.5.2015.12 version to fix the startup problem. I will do some tests. I do seem to remember this Opera problem happening once before, but I can't remember what the fix was!

KEXBASEN.DLL 4.5.2015.12 will fix this, which you can download from the link in this post.

All fine here.

I agree with this. When I got involved in the long discussion about the various versions of EMET and how to install and configure them on XP, mainly with @heinoganda, who has been incredibly helpful to me with this, I quickly realised that we were getting very off-topic! It did seem relevant at the start as EMET was one of the recommended applications to install to maintain XP security, but the posts about it took over for a while. This thread should only be about getting official updates from Microsoft for our XP systems, using the POSReady and Embedded updates, and any problems with them.

I can see your concern Den. This thread will potentially be important for another three years! I also use Digital Spy forums, and they seem happy to let threads get up to many thousands of posts, but I can see why this might be a problem. They do split threads sometimes, but they do tend to just keep the original tile appended with "(Part 2)" or "(Part 3)" which is a bit boring! I don't really know that would be better I'm afraid, to keep that link with the original(s).

Am I missing something here, I thought Service Pack 4 included hotfixes, as well as the patch to allow future ones to be offered from Windows Update for hopefully several more years? This reminds me of the row a few years ago over on the Windows 98 board about a new Service Pack, which was accused of having the same issue, actually being more bloatware than a worthwhile security enhancement. The answer then was the same as the answer now, all features are optional. If you don't want some or all of any non-security extras offered, don't install them, simple as that!

I don't think many people will be mourning the final demise of IE6, a browser without even tabs! Such a shame that some versions of Windows use its files so much for other purposes, like Windows Explorer. Anyway, all today's offerings have been installed on my system with no apparent problems. I noticed that some files dating from 2008 have been updated!

Well as I'm still using Opera 12 as my main browser, which is now abandoned and hasn't been updated for several years, I guess I am leaving myself a bit at risk, but it's still my favourite browser by a country mile!

Well I'm not seeing any ads, so I'm not complaining!

Well I'm using Opera 12.17, with the AdBlock extension and the Opera Content Blocker enabled too, and the Forbes articles all still work for me! I'm not even seeing the nags about the blocking.

Strange, I'm not a subscriber to Forbes either, and I can read the article, and all the other articles linked from it, with no problem.

I'm using EMET 4.1 Update 1, and just for the record, I have had to disable the EAF, MemProt, and StackPivot functions for Firefox to work properly, the EAF, LoadLib, MemProt, Caller, SimExecFlow, and StackPivot functions to get Google Chrome to work properly, and the LoadLib, MemProt, Caller, SimExecFlow, and StackPivot functions to get IE8 to work properly. If any of these are enabled, the browsers concerned either won't start properly, or keep crashing.

@jumper Just to confirm that the new version of kexbasen.dll has completely fixed the problems here! I have removed the registry patch, and put all my scripting files back in the system folder, and all is working well, including VLC Player again. Thanks very much for sorting this out!

Thank you @jumper for sticking with this! I'll try it out tomorrow and let you know the outcome. I assume I can now remove the registry patch, which I haven't yet done? Cheers, Dave.

Thanks @jumper! Am I right in assuming that this should remove the need for the registry patch? I hope so, as I could see that potentially causing a lot of future problems. I already have an entry for kernel32.dll in stubs.ini - [Kernel32.dll]GetGeoInfoA=z5eGetGeoInfoW=z5eGetUserGeoID=t1GetVolumeNameForVolumeMountPointA=z3eGetVolumeNameForVolumeMountPointW=z3eGetSystemWow64DirectoryA=z2e120Should I just add your entries to that? I don't have a file called "code.ini". Do you mean "core.ini"? Kstub822 doesn't seem to be mentioned anywhere. A mystery about the error messages I'm getting apparently from the batch file. I had looked at its contents of course, and as you say there's nothing there that should generate any messages. I'll have to investigate further! Cheers, Dave.

Hi again! I've found that I've got a problem with VLC Player as well now (version 2.0.5). It used to work fine, now when I run it, apparently nothing at all happens. No error messages, just nothing! Anyone got any fix for this? @jumper I forgot to mention earlier that when I run your updater file, it correctly prompts to switch to DOS mode, but when it does, before the "---Updating KernelEx 4.5.2015---" line, there are five "Bad Command or File Name" lines. It then seems to work OK. Not sure where those error lines are coming from, or why there are five of them. Just thought I'd mention it, it could be only me seeing it because my system is non-standard of course!

Thank you harkaz!

OK, back again! I've got the scripting working again. I had to move all the related files out of the \system folder into the \windows folder, and edit all the registry entries to reflect this. It then worked fine! Incidentally it's the Unofficial Windows Script 5.7.0.20550 update installer that puts wscript.exe and cscript.exe in the \system folder, which is not where the original Windows 98 installer puts them. I think whoever compiled the INF file got things confused with the NT install, which puts both those files in the \system32 folder. Anyway, after moving them to the \windows folder, along with their associated dlls, it all came good. I am going to keep your version of the script @jumper, as it looks neater!

If it's any help, some ATI graphics cards have a "VIVO" (video in, video out) hardware system built into them which will capture from a composite video or s-video input with the appropriate software. I have a Radeon X600 series card which I use with Windows 98SE, which was the first series to have PCI-E versions available. The Radeon X700 series and Radeon X800 series have the same facility, but it isn't physically there on all models so you would need to check carefully when buying one that it is a VIVO card. Hope this helps. Good luck! Cheers, Dave.

Thanks again @jumper. I'll check all that out and get back to you. I am just wondering, presumably the files that have a problem with 2015.11 are some system files in the \system folder. Is it really necessary to do a blanket disable of KernelEx on all the files in the folder to fix this? The problem with that is that the registry entry over-rides everything else, and you can't re-enable KernelEx on individual files. This is awkward if disabling KernelEx causes problems with some applications, as people have already found with VLC and my problems, which must be caused by this. Is there no hope of finding out exactly what system files have the problem and stop the desktop loading, and just disabling KernelEx on those?

@jumper I've been experimenting trying to get my script to work when KEx 2015.11 is installed, but no luck as yet. QuickMirror runs fine with the default KernelEx setting, both directly and by using shortcuts, included saved mirror configuration files that are associated with it. My script simply calls one of those mirror files, once you've answered "yes" to a yes/no prompt. If you answer "no" the script just terminates. The script is as follows - On error resume nextcompstr = wscript.arguments(0)verify = MsgBox("Run QuickMirror System Backup to Drive F:?",vbYesNo, "Confirm")If verify = vbNo Then wscript.quitEnd IfSet objShell = WScript.CreateObject( "WScript.Shell" )objShell.Run("""C:\Utilities\QuickMirror\System Backup to Drive F.mir""")Set objShell = NothingIs there anything wrong there, anyone that knows about scripting? This script works fine when run from a shortcut with KEx 2015.10 installed, but with 2015.11 installed with the registry fix I just get the message about mirror.exe needing a later version of Windows. If I play with the KEx settings on mirror.exe, and/or on wscript.exe I either get the same result, or the mirror just immediately runs without showing the yes/no prompt message box! The fact that it's not showing the prompt message box would indicate to me that it's wscript.exe that's the problem, not mirror.exe. It should show the message box before even attempting to run QuickMirror of course. I've tried moving wscript.exe out of the \system folder to the \windows folder, which made no difference, but I assume the wscript dlls are still in the system folder, which may be the problem. I'm using the Unofficial Windows Script 5.7.0.20550 update BTW, if that makes any difference.

Thanks @jumper! Strange what you say about QuickMirror as I've been using it for many years on 98SE, I would have thought even before i had KernelEx installed, but it may have been an earlier version back then of course. When the recent problem was there, it still ran fine when run directly, but didn't when run through the vbs shortcut, which is why I assumed that the problem was actually with wscript, not with QuickMirror. Wscript.exe has always been in my windows\system folder AFAIK. Interesting that you say it should be in the \windows folder, but as I said, moving it made the Windows version error go away, but the shortcut still didn't work properly, bypassing the "are you sure" prompt part of the script. I will try your suggestions and report back. Cheers, Dave.

Sorry @jumper, the 2015.11 update has caused me more problems I'm afraid. I have a shortcut which runs a .vbs file to prompt me as to whether or not I want to run a mirror program (QuickMirror) to backup my system drives under 98SE. If I click "yes" on the message box prompt it runs it, if I click "no" it doesn't. this is to prevent it being run accidentally. It has always worked fine until I applied the 2015.11 registry fix. Suddenly running the shortcut just produced a message saying that QuickMirror needs a later version of Windows (it doesn't). I assumed this was because wscript.exe was now having the wrong KernelEx settings applied to it as it's in the Windows\System folder. I tried changing the KernelEx settings on wscript.exe, but every setting I tried either made no difference, or caused the shortcut to immediately run the program without the prompt, which is useless. I then tried moving wscript.exe to the Windows folder and changing the folder options to reflect this, and the shortcut also then worked but again immediately just ran the QuickMirror program without prompting me as to whether I wanted to or not, so that was no good either. I could find no way of resolving this, so I'm back on 2015.10 I'm afraid. After reinstalling that and putting everything else back as it was, everything now works as it should. Any idea how I can resolve this problem? Cheers, Dave.

Yes, I got it working on Firefox 43 eventually too. Still no joy with Opera 12 though, the plugin substitution workaround no longer seems to work.