bluebolt

Hi James, I made no further attempts on the Gigabyte boards; XP 32-bit runs really well on them, so that's where those have long stood. Likewise, I moved my MSI Z97 PC Mate on to other things way back. The driver I used was BWC’s 8.9d AHCI; I don't think driver version 11.2.0.1006 will work on W2K Pro, although it works fine with XP on my Gigabyte boards. I don't know why it does not work on your Gigabyte board. The trick with W2K Pro and AHCI is using an installation disc that has BWC's Extended Kernel integrated, thus the HFSLIP package tomasz86 made. Though layering BWC's kernel versions is not ideal, after installation you can update to a newer Extended Kernel version. The latest chipset I tried with Windows 2K Pro is the ASRock X99, where all is well. I have a couple of huge Lian Li PC-V1000L cases moving lots of air with different operating systems on individual NVMe and SSD drives. If I want to change operating systems I just power up, stop at the BIOS and make my selection. If I try the Z97 again it will probably be on a ASRock Z97 Anniversary board that is currently running XP Pro 64-bit. I very much like that platform and miss not having a Windows 2000 Professional operating system there. I would also like to attempt post-facto switch over from IDE to AHCI to avoid running one extended kernel version atop another.

XP compatibility was lost at version 10.2.1 (followed by 10.2.2 and 10.3). As I tried to convince AOMEI to restore XP compatibility, they sent me a direct link to version 9.0: http://www2.aomeisoftware.com/download/pa/full/9.0/PAssist_Setup.exe I swapped "10.2.0" for "9.0" for a direct download link to version 10.2.0: http://www2.aomeisoftware.com/download/pa/full/10.2.0/PAssist_Setup.exe

However, these downloads, which I have not tested, are just slightly smaller than the original from AOMEI: https://aomei-partition-assistant.en.uptodown.com/windows/versions https://windows.apkpure.com/aomei-partition-assistant/versions

AOMEI Partition Assistant 10.2.0.0

My normal upkeep on family Windows 10 machines includes delaying updates for as long as possible. My Windows 10 laptop is currently allowing me to defer updates for a long time. Every time I open "Settings/Update & Security/Advanced options" it lets me select a date ever further in the future--as in over 600 years from now. It's not a problem, it just struck me as odd, but then I seldom use Windows 10 myself. I'm curious if anyone else has experienced this.

On the other hand...

Naturally the virus update version and signature numbers change with every update. The "Could not connect to server" isn't the update server, it's for logging into your account.

Of course it's not fake. I have BitDefender on several 32-bit XP machines -- works the same way on each (perfectly) and is updated daily, usually multiple times a day. I plugged in an old eMachines/atom that hasn't been turned on in years. It went like this:

Yes, there is a full (offline) installer for BitDefender 1.0.21.1109, and it still works fine.

BitDefender 1.0.21.1109 still works fine on XP.

I have four DTSE9 (actually two of them are DTGE9--gold in color). I checked them on XP Professional, and all show driver 5.1.2535.0. Device Manager "Update Driver" says "Windows could not find a better match for your hardware..." for what that is worth.

Just a quick test to see what would happen, using the modded Chinese repack 34.0.0.92, I pulled the pepperflash dll and replaced as usual in my Chrome Portable 49.0.2623.112, which yielded this result:

All of my installs behaved the same. I can't remember the solution, but it was simple. I think I clicked "Options" on the Primetime plugin and then clicked "Check for Updates" from the Tools dropdown. It's possible I also turned Automatic Updates on and then back to Default, but I'm not sure about that.