bluebolt

I wish I could relate, in order to lend a hand, but in my setup the browser history is scratched every time I close Firefox. Or by "browser history and such" are you talking about your bookmarks? Are you able to "Bookmarks / Show All Bookmarks / Backup / Restore" same, and transfer to a fresh install?

Or just save yourself all that trouble, and take advantage of the good work already done by tomasz86, and download the HFSLIP2000_FullPack_09092017.

Here's a good one, with a 20-pin connector for the cable to the front of my case: En-Labs PCIEU3ACS20 I'm using blackwingcat's ASMedia driver v1.16.1.0 available here: http://blog.livedoor.jp/blackwingcat/archives/1708066.html This is what the same USB stick looks like in Windows 7 x64 on a Z77 motherboard using the built-in USB 3.0 port: Possibly the benchmark difference is accounted for by the independent controller mentioned by BWC on the page linked above, as allowing the ASMedia driver to work at all with Windows 2000 Professional.

Same here. It's been a long time since 64-bit Firefox worked on XP x64, though I haven't been able to determine, much less download, that version. Anyway, 52.9.1 was a good find, Stephen.

Firefox 52.9.1 is a no-go on XP x64.

The specifics are in this thread, which I plan to update soon: https://msfn.org/board/topic/175368-windows-2000-professional-on-the-x99-platform/ In the meantime if no one objects I'd like to just answer your question here, generally... The one main, overriding consideration is whether a particular model of motherboard (and its BIOS) will give quarter to Windows 2000 Professional, or in other words, whether the board will allow anyone of whatever level of experience to succeed; but there is no way to know that beforehand. In any event the motherboard MUST have at least one PS/2 port, or it will not be possible to install Windows 2000 Professional (two PS/2 ports will make the job easier). At that, choose the simplest motherboard (with the added advantage that they are generally less expensive) with as little hardware on it as possible. Even then, you will definitely need to go into the BIOS settings and disable extraneous hardware, especially to include any COM port or Parallel Port. Choosing a board with Realtek audio and LAN hardware (or adding Realtek cards) will increase the odds of success, because Realtek has W2K Pro drivers available. It may be piling inference upon inference, but I would avoid a board that looks fanciful in any sense, as if the marketing department had a hand in the product formation, including boards with colorful graphics or names. If installation will not proceed beyond initial hardware detection (i.e. stalls at "Setup is starting Windows 2000"), try selecting something other than ACPI Multiprocessor PC mode. This may allow the installation to complete, though curtailed, but at least allowing you to use the OS (especially Device Manager) to get a handle on the problem.

I tested 12.18 on a plain Windows 2000 Professional OS updated through EOL, which currently has Opera 12.02 installed on it. Opera 12.18 setup went like this: ...then clicking "OK" produced this:

I ran a quick test this evening, installing Windows XP 64-bit on the ASRock X99 Extreme4 mainboard I use for Windows 2000 Professional. I ran nLite 1.4.9.3 to integrate 5eraph's update pack and IE8 Addon, and Fernando's AHCI SATA and sSATA drivers. I tested Microsoft Update to get the .net frameworks and updates, just to see that it (MU) worked okay. I think the screenshot has all the other information. The OS installation and so forth was trouble-free. I have no plans to pursue this further for now, but wanted to post this brief FYI before I button up this hardware with W2K Pro.

Gee, there's an original idea. Probably never thought of that.

You could consider Bitdefender's free edition, which has worked perfectly here for some time now. The closest thing to a problem I've had with it was a year or two ago when notices popped up at every boot about their imminent dropping of XP support; but eventually those nags stopped.

Don't we already have a thread for "whether XP" generally?

Obviously not, since your second sentence begins "As for Windows 10..."

This again?

Anyone who sees the light at the end of this tunnel...is seeing another train.

When this problem first came up five-and-a-half years ago, tomasz86 similarly suggested trying a clean W2K/SP4 source (no INFs or drivers integrated with the CD), but there was still no USB function. https://msfn.org/board/topic/156521-unofficial-sp-52-for-microsoft-windows-2000-wip/?do=findComment&comment=1033054 I don't remember what it looked like in Device Manager, it's been so long. I may try it again and take a look. This issue has been posted about a number of times over the years, going back to even (slightly) earlier hardware, and it is a strange one. I would have thought that if it could be dealt with by modifying the INFs, blackwingcat would have done so in his custom infinst, but that is just conjecture, and I don't know of his ever having addressed this issue.

When attempting to install W2K Pro on modern Intel hardware, the OS tries (unsuccessfully) to use that hardware's newer USB drivers. You need to force it to use the older USB drivers. In order to do that, you need to hook up your keyboard to the PS/2 port, thereby to enter Device Manager (by pressing the Start key and the Break/Pause key at the same time, or by pressing the Start key and R to run "devmgmt.msc"), and force Device Manager to the other USB drivers. This screenshot comes from installing W2K Pro on a Z77/LGA 1155 motherboard: Windows 2000 Professional defaults to the highlighted driver, which it considers to be "a suitable driver [that] is already installed". It needs to be directed to the alternative drivers in order to achieve USB function.

https://msfn.org/board/topic/175782-ntdetect-failed-during-setup/?do=findComment&comment=1126466 https://msfn.org/board/topic/177140-keyboard-not-detected-at-repair-and-install/?do=findComment&comment=1146027

When that happened to me, I deleted both the temp and .bak profiles; when I rebooted, Windows had recreated the correct profile, solving the problem.

Since you're able to log in normally and can do everything, there is probably no real corruption. Run regedit and go to: HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NT/Current Version/ProfileList Highlight each entry and you will be able to see the temporary profiles that were created and are being used. The correct profiles are still there but have had ".bak" extensions added to them. Delete the temporary ones and rename the correct profiles by getting rid of the .bak extensions, which will probably fix it. However, the last time it happened to me, Windows kept recreating the temporary profiles, so I just deleted the temporary profiles and the ones with the .bak extensions, and rebooted, which fixed it.

I have had these errors as well, though never to the extent as Dave-H, and not at boot. They come--and then go away--over time. I will try to keep closer tabs on my Event Viewer, to see if I can determine what I'm doing when they happen.

I haven't tried anything more powerful than the GTX 960, so I don't know whether higher-end 900 cards may work or not. I tested 64 GB of RAM at one point, but the system still only showed 32 GB, so that looks to be the limit in my setup (much improved memory performance, otherwise no real downside). The biggest hurdle is finding a motherboard that will allow installation of W2K Pro -- we are really at the mercy of the BIOS. I think even blackwingcat "quit the motherboard" (or words to that effect) when the OS install would not proceed. The X99 thread has a little more information, which I hope to update at some point.

At least: X99 motherboard with i7-6950X Broadwell-E 10-core CPU, GTX 960 / 4GB video card, maximum 32GB RAM in PAE mode.

Maybe not, but the specific issue/solution seems to match exactly the OP.

A guy on YouTube says he fixed his Win10-to-Win7/ACPI problem with a BIOS update, so you could check that (his was a slightly different model number, an HP 15-233wm).