Dave-H

Thanks guys. I no longer have the X700 card, I returned it to the eBay seller for a refund as there was a hardware problem with it. Not with the graphics section, which worked fine apart from the crashing on Windows 98, which I expected would probably happen, but the VIVO Rage Theater on-board video capture hardware, which would not accept any drivers, with a "device cannot start" error in Device Manager on all three operating systems. The capture hardware works fine on the X600 and did on the X800 and X850 cards, so I had to put it down to a hardware problem on the X700 card, even though the seller tried very hard to convince me that it couldn't be that, and had to be a driver problem! Well, I tried many different drivers, and not one worked, so back it's gone. If they get it to work I'll be very surprised! All the cards certainly all worked fine with the basic MS driver, although only at a very low resolution of course. Next time I have the machine apart I will temporarily put back the X850 and see what memory range resources it's using on Windows 98, and then do the same with the X600 card. Maybe that will provide a clue.

Yes, it is very strange. The only reason I tried earlier versions of the ATI card was because I was having system temperature problems, and I wanted to try a less powerful, and therefore less heat producing, card. My graphics card intensive work like video editing and rendering is all done now under Windows 8.1 with the Nvidia Quadro card, so I don't need a powerful ATI card as well. The ATI card is only really there at all for Windows 98 as there are no 98 drivers for the Quadro card of course. All the ATI cards I've tried have had the same amount of graphics memory on them (256 MB) and are using the same driver (Catalyst 6.2, the last Windows 98 version) and yet the X800s and the X700 crash, and the X600 doesn't! Maybe there is something different about how the X600 uses memory or something, I guess we'll never know. I wasn't expecting the X600 to solve the crashing problem, but I'm obviously pleased that it has!

Not a gratuitous bump, just wanted to report, for anyone that's still interested, that I now have an ATI X600 card installed, and it doesn't crash! I had tried an X700 card, and that did crash the same as the X800/X850 cards, but going all the way back to an X600 (the first ATI series that had PCI-E versions) seems to have finally fixed the problem! Cheers, Dave.

I thought I'd spoken too soon after my main machine updated fine. When I did the updates on my netbook it all seemed fine too, but when I went to MS Update to check afterwards, it did not work, although it was apparently still working on the main machine! I tried a few more times, and without changing anything, it started working again on the netbook too, so I guess it is a server problem at Microsoft's end. It does say "Error 500 - Internal Server Error" at the top left of the error page, and I guess that's exactly what it was!

All still working perfectly here too after installing the same five updates.

And again this afternoon! I guess they are being immediately removed. Certainly that removes all doubt about the messages being spam, they are all identical, but all apparently posted by different people!

Hmm, that does make sense, but I'm still getting e-mail notifications (two this morning) of new posts to this thread, which when I follow the link in the e-mail, they're not there!

What's happened to the rest of this thread?

The "problem" is that you haven't yet rushed to install Windows 10 I would imagine!

The version checker showed that no files were changed by installing the newer version over the older version, but after uninstalling the older version and then installing the newer version quite a number of files were changed, from 3.0.6920.4087 to 3.0.6920.4089, as you say.

OK, but strange that just installing the later version does not appear to do that anyway. Presumably the differences between the file versions are only very minor. I'll run my file version checker and see if anything was actually changed.

Yes, I had the earlier version installed, and tried to install the later version, and while it didn't say that the update was already installed, it said that the install was done almost immediately. It did run the .NET Framework NGEN v4.0.30319_X86 service, but it only ran for about 12 minutes before stopping again, which is much quicker than normal! I suspect that it didn't actually do anything, but if I find different when I next run my system file version checker, I'll let you know!

Glad it helped you! Actually purely by coincidence I had to repair several task on my machine again only a couple of days ago, so had to re-remember the procedure. They must have got corrupted after I installed the Windows 10 "upgrade" and then swiftly reversed it by restoring an ISO backup of 8.1! I later noticed that the automatic system maintenance wasn't kicking in, and I found that two of its associated tasks were corrupted.

They are certainly different versions. Version 9.0.30729.4087 is signed on 20th July 2015, and version 9.0.30729.4089 is signed on 29th July 2015. Why they produced a second version so soon after the first, and didn't remove the first, is a bit of a mystery!

How strange! Presumably your copying of kexbases.dll actually failed for some unknown reason even though it appeared to work. Glad you got it sorted anyway. Cheers, Dave.

I just meant re-registering the DLLs with Windows by running "regsvr32 C:\Windows\KernelEx\xxxxx.dll" for each one in turn. I'm not actually sure whether they even need registering, but it can't do any harm! If you just get an error message when you try they probably don't support it.

What you did should have worked. Did the batch file give you an overwrite prompt for each DLL? Are the DLL files in your C:\Windows\KernelEx folder now all exactly the same as those in the update 7z file? You could try re-registering them.

All OK here (touch wood!)

Great to hear, glad it's all OK now. Cheers, Dave.

Glad you got there! There should be no danger of Windows 10 installing now as you've trashed its installation files. If Windows Update is still prompting about it, try running the Windows Update Troubleshooter if you haven't already, that should reset everything. You will lose your update history.

I certainly didn't have to do it one file at a time, but I did have to start with the sub-folders and work my way up to the top. If you get the error message, just go one more level down and try deleting the individual folders at that level. As Noel says, make sure that you have the checkmarks ticked to inherit permissions down the chain.

Glad to hear that you fixed it! Interesting that it is working with the new version of the dll.

When I deleted that folder on my friend's machine, I seem to remember that I had to do some of the folders separately, taking ownership of them and their contents and then giving myself full control over them. It was a very tedious process, but I got them all eventually!

Did you replace the dll? You'll still have to do that!

Yes, the Windows Update page will lose its list of updates that you installed in the past, but they should all still appear in Add/Remove Programs so you can still uninstall them, if they can be uninstalled of course, some can't. You will need to have the "show updates" option checked there of course.