dencorso

It seems elevation is not enough. Try running as the "Trusted Installer", jaclaz. It can work miracles.

Sometimes it's working, sometimes it's not... I'm with 5eraph: probably too much traffic. Well, I can offer a shortcut: usually one serches and selects the updates from the front page, then goes to the basket and downloads from there. Now, after selecting the updates and putting them in the basket, instead of going to the basket, click <this link>, and you'll get directly to the download folder selection page, which is the last one. If it gives error, close the window and try again in a new window, until it works. HTH

The only person that comes to my mind who's capable of doing that fast enough is WildBill, supposing he finds time for it. Otherwise, it's better to wait for the next win32k.sys in some new fix further on, because it'll sure incorporate the fonts fix, since they're now always from the QFE branch.

It was just a temporary quirk, fortunately! It working OK again!

Problems with MS Update Catalog... when I click on the basket, o have it download the updates put in, this is what I get, instead:

Build 6712 is the problematic one. It clearly did no install. Build 6648 is the one I have on my machines (remember I blocked KB3013455).

The only 5.2 files known to work OK on XP are some of the 2k3 USB drivers modules. Now, since all updates released by MS for XP, from sometime before EoL are solely from the QFE branch, Outbreaker's finding is actually pretty good news: QFE updates are cumulative and include all previous fixes... so that whenever another win32k.sys eventually is released for POS Ready 2009, it'll actualy also contain the fix from KB3037639, so it's just a question of waiting for it.

It does more than simply circumventing the SYSTEM.INI entries. It gives Windows 9x full access to all of the RAM. Those entries make Windows 9x think there is only 1GiB of RAM. And it makes the system more stable overall, by fixing various bugs left over by MS on the VMM module, so that win 9x/ME actually becomes stabler after applying the "RAM Limitation Patch", even with RAM amounts that do not, in principle, require patching (that is, 1152 MiB or less).

Get a cheap multimeter and measure the +5 V and the + 12 V in real time from a molex. That's how it's done. Then you can move on to a monitoring app if you like, but if what you read on the multimeter is OK, that's that.

Are you sure?.x.(.x.) Yes (.x.) No ... at least since 7 SP1, it's very doubtful whether MS has made anything better at all, but it sure made Windows look a whole lot worse! Why not move over to macOS? Because not move is good enough.

loblo is right! Stop everything and do this first! It's easy and it will provide valuable info.

By disabling the PagingExecutive one prevents the Kernel and all Drivers from being paged by Win NT. Other things continue to be paged normally. Now, since the Gavotte Ramdisk is itself implemented as a Driver (viz. rramdisk.sys), one cannot risk allowing the OS to try to move that driver to the pagefile, because it actually holds the pagefile in itself and, hence, the the system will crash on attempting it. However, there no sure way to prevent the OS from moving just rramdisk.sys... the best that can be done is to disable the PagingExecutive, and it works great.

@bluebolt:

For what it's worth, here's what I'd do: 1) Disconnect the current HDD (I remember you said there's just one on that machine), but leave it where it is. 2) Grab another PATA HDD of any size (say... >= 20 GB) and partition it with a single active primary partition. 3) Install *plain vanilla* 98SE, add RLoew's RAM Limitation Patch *only*, tweak the desktop minimally for confort (without any third party app, except perhaps MS's own TweakUI), add Opera 10.10 for connectivity and super-pi to give the OS something to do, then run super-pi and let it churn some for 6 to 30h (unless it crashes before that) to decide whether I do have a hardware problem (and if so, then troubleshoot for it) or not. In case it crashes soon, reboot it some 3 to 4 times to make sure it's crashing consistently If it does not crash and behaves solidly, then disconnect the new HDD, reconnect the old one and troubleshoot instead the Win 98SE setup. This is just my 2¢, of course... please feel free to ignore it completely.

Sorry but I can beat that! I'm using Office 97 with the 2007 compatibility pack on my main machine (I think I was the 1st to find out and report it worked with Office 97). I do also have KB2926765 installed on my machines, with no adverse effects, actually, but some users have reported having problems with it.

I think AnX meant KB2926765 (shlwapi.dll v. 6.0.2900.6540 qfe), mentioned above on post #253...

Yes.

Few people ever cooked their own golden-egg-laying hen and remained long enough in the market in any form to tell about it. MS is trying hard to do that, and has already gotten a place in the Guinness as the longest-own-feet-shooting record-holder.

Yes. We do understand you. OTOH, you've got to understand bigmuscle has also made it crystal-clear he accepts PayPal only. It's a classical standoff (aka deadlock):

That is one of the details that makes the Asus Eee PC 900 a great netbook: it *does have* a reset pinhole in the back (although one straightened paper clip is needed to actually reset the machine)!

IMHO, it's a lot of trouble, and simply not worth the effort. Then again, it surely is possible. So, at the end of the day, YMMV.

No need to be rude, ever. Yes! At that point, Win 95 is already ended, and the machine is back to real mode, and the BIOS is again servicing the KBD interrupt, and that includes rebooting on <Ctrl><Alt><Del>, since the original IBM PC BIOS. The NT-OSes,OTOH, do not bother to handle control back to BIOS, when they're shut down.

All you need is: AdbeRdr830_en_US.msi + AdbeRdrUpd831_all_incr.msp ... IIRR, they still are available from Adobe.

Like, say, an active antivirus protecting all bootsectors?