dencorso

Maybe. But non-SSE2. As it is, I'd advise you to go up a little, and move on to an SSE2 capable processor. Any Pentium 4 or later will do, as well as will any Athlon 64 X2 or later. I'm about to decommision two perfecly good Athlon XP machines, because I envisage more and more software, which otherwise still supports 2k/XP, becoming inviable because of lack of SSE2 support, since MS decided to make compilation for SSE2 the default for MSVS 2012 and later. While everybody thinks about software activation, MS is undercutting users from the other side (and Intel relishes on it, because AMD started to support SSE2 much later than Intel).

I stand corrected. Thanks!

With all due respect, that's just alarmist FUD.

Maybe MS is fated to be bought by Symantec (you all remember how Norton products were great before that happened to them)...

Welcome to MSFN! You want a machine to recognize and use up to 1152 MiB, you can do it just with tweaking on 98SE. You want it to actually recognize and use more you've got two options: buy RLoew RAM Limitation Patch (then you can go up to somewhat less than 4 GiB) or upgrade to ME (then you can go up to just somewhat less than 2 GiB, but for free). There are no other ways.

Would there perchance be a PNP8fff in the registry, under /ENUM, at HKLM/, Dave? If so, what does it contain? I also have a feeling the installation of the MS Network Client 3.0 for DOS has something to do with it suddenly staring to work...

Problems with drivers on enabling PAE usually are due to poorly written drivers. 95% of the time, upgrading the drivers solves it. Cheers!

Are you sure you've got the most recent compatible drivers?

Now, that's great news! Congratulations! So, I guess, that also means your add-on network card is about to be decommissioned...

Another place which uses to have interesting stuff is recycledgoods...

Redownload a fresh copy from MS and try again with the newly downloaded copy: IE7, one never knows, your installer might be defective... then again, it used to require SP2, so it may bark at SP3 or, more probably, POSReady 2009. Let's see.

But, for that, he must have a local area network... In case Dave-H's machine is standalone, that's not an option, while TCP/IP remains viable.

Here is the link to it: StartIsBack+

Then again, now we google, while, then, we used to search (wirh) Alta Vista... and we liked it!

Well, MS Basic Mouse is robust and reliable, optical, has a scroll wheel and works both on USB and on the PS/2 port with a passive adapter (included), and is not EoL. Give its DataSheet a look. I have two of them working great for a long time already.

There have been no updates to usbhub.sys for XP, so, AFAIK, the same holds true for 2k3. That means you'd have to get the SP2 (for 2k3) package to get at usbhub.sys.

Seems good. Best choice would be to send one toast board, recieve the replacement and see whether it works. In any case you'd have the 2nd HDD as backup. But do post the photos. If it turns out to be just a TVS diode, all you'll need to do is remove it (which you can do yourself) and it'll spring back to life... well, at least it should... Later addition: attached you'll find a sample of what I mean by "good quality" pic...

No. They are not too tiny, but to transfer sucessfully one BIOS chip from one board to another you'll need someone who's very proficient at doing it. Ususally it's done at a soldering station, but there are some people who can do it by hand, but they are really hard to find. Unless one knows what he's doing, the chance of a successful transferral are really nil, so select carefully whom you'll trust to do it. BTW, can you post any good resolution pics from both fried boards? If you don't have a good enough camera on hand, a scanner can do real miracles for things like those boards... If so, we may be able to identify which components are toast.

Wow! Sorry about that! Then again, are you sure both are fried? Sometimes one fried HDD is enough to prevent booting. Did you test each individually?

No. It works, all right, but you don't want to do that! I've just downloaded it to check, and it's v. 4.6.305.0... That's one of the naggy versions: the last nagless version is 4.4.304.0, which can be found, for instance, on filehippo. After installing, take care to hide updates to it on MU, and disable any auto updating, and just update the virus definitions, or it'll become naggy, after being updated. More about it on this page, elsewhere, at dslreports.

You're welcome! When appropriately unique hexstrings can be found, patching by hexstring search and instruction replace is very reliable, and quite robust to localization... and to updated versions of files. Glad you found it useful. BTW, the older XP64G.EXE I had on archive is v. 1.0.0.1, from 2011, while the one inside the file you gave a link to is v. 1.0.0.2, from 2013... so, obviously the unnamed developer worked two full years before releasing the new version, and this may conceivably reflect a lot of work done (although it might also mean, among other possibilities, the project was shelved then, lay dormant for some time and was restarted recently, of course) ...

It sure means somebody has been working on refining the patch since we last discussed it. You see, 75 means "jump when not zero", 74 means "jump when not zero", EB is an unconditional jump and 90 means "do nothing"... So, clearly the new patch inverts the sense of two jumps, instead of simply avoiding them... But unfortunately most assembly is not so straightforward, so a good local disassembly would be needed, to get to the meaning of the new patches. And, even so, it'd demand quite some time. Now, the patches we knew did work, sort of, but had issues which remained unsolved. Does this new Chinese mod work right? Does it solve the known issues? If so, we may even try to understand them better. But further testing is in order, before doing anything really time-consuming, don't you agree?

Great find! And welcome to MSFN! Now, just for the record, knowing 下载 means "download" does help some, at the site you gave a link to...

Your links show my Patch for the Current Directory issue.I didn't see the Patch for the IO.SYS Patch required unless it is at the Website in German. Isn't it this one (viz. 3xSTART.EXE) jaclaz had already provided a link for?

You mean these, also discussed further in this other thread staring on this post, right?