spaztron64

I've upgraded yesterday from v31 to v31l, and for some reason the machine now acts like it's domain joined and treats it's own computer name as an AD domain. As such, I can't log into any account, not even the local administrator (yes, I tried the .\ prefix). I should note that the machine was domain joined at some point for an RIS homelab, but it's been several months since I unjoined it and moved it back into the default WORKGROUP.

Yep, we're doing this song and dance all over again. https://archive.org/details/steam_202401 I dunno if next year's first build will still work or not, and I don't wanna risk finding out, so I'm sharing what we currently have.

Has anybody been able to get 360chrome v13 working on Win2000 with BWC's kernel? All it does for me is memory leak without loading any websites. Only v11 works right, but sites are breaking on it more and more now.

It appears that MyPal is dead, and Pale Moon devs are responsible for it. https://www.reddit.com/r/palemoon/comments/pexate/pale_moon_developers_abuse_mozilla_public_license/ https://github.com/Feodor2/Mypal/issues/5 https://github.com/Feodor2/Mypal/issues/3

Two issues I've had regarding the last XP compatible version of Steam are invalid SSL certificates for the CEF and in-home streaming not working on my client machine when running XP x64 (works fine under 7 x64). The latter is especially troublesome. At first, streaming_client.exe couldn't create a socket. I fixed that by installing the IPv6 protocol on the XP client. Sadly, the streaming client still fails with the "Couldn't connect to the remote computer." error. Updating root certs and using ProxHTTPSProxy didn't fix anything. Any advice?

So a few of you might know that trying to install Win2k to devices it treats as removable will result in INACCESSIBLE_BOOT_DEVICE, especially modern CompactFlash cards that can't be set to fixed disk mode. Recently I tried to install the Hitachi Microdrive (cfadisk.sys) driver on a platter drive installation that pointed to a CF card. Then I dd-ed the installation from the platter to the CF and it actually worked....kinda. The OS got severely corrupt in the transfer process to the point of unusability. Then, I've been trying to somehow slipstream cfadisk.sys into the text-mode and GUI-mode setups, but that didn't work out. And no, this (http://vega.pgw.jp/~kabe/win/atapirv/W2kRmvInst.html) did not work. I should mention that I've been doing this on a PC-98 and the PC-98 version of Win2k, but there's not much difference when it comes to this between it and the IBM PC versions. If anybody's got ideas, please share them.

The fact that it uses an ancient version of Resource Hacker without support for x64 stuff and that the wfpdisable.exe it comes with doesn't work on XP x64 are probably it's biggest issue. I haven't found a way to edit the contents of the installer to replace these two, and manually editing all the system files is highly error-prone.

Good news, @blackwingcat's modded acpi.sys (http://blog.livedoor.jp/blackwingcat/archives/1974336.html) fixes everything!

Unfortunately, even after updating to Extended Core, switching to ACPI Multiprocessor PC results in INACCESSIBLE_BOOT_DEVICE. I have also just read this topic (https://www.experts-exchange.com/questions/20820090/inaccessible-boot-device-after-Multiprocessor-Upgrade.html) that says that switching from non-ACPI to ACPI is very problematic. EDIT: Switching to MPS Multiprocessor after installing ExCore v16a results in a hang at Mup.sys

EDIT: @blackwingcat's modded 2018 acpi.sys fixes everything (http://blog.livedoor.jp/blackwingcat/archives/1974336.html). Man, where do I even begin? The setup complains how the BIOS is not ACPI compliant. Skipping this is only possible by using the "Standard PC" HAL...which is obviously not good for a multicore laptop. Switching to ACPI Multiprocessor HAL post-install leads to 0x7b "INACCESSIBLE BOOT DEVICE", and switching to MPS Multiprocessor leads to c000021a "The Session Manager Initialization system process terminated unexpectedly with a status of 0xc000026c". The EHCI controller drivers refuse to work, likely because of the Standard PC HAL. Hjalp mig.

What about earlier versions? Do you have a working version archived somewhere?

Blackwingcat, what's the current situation regarding Steam? Installing Extended Kernel still doesn't launch my archived Nov. 2018 build of the client. Is there anything else I need to install or have you still not fixed the problem?

I'm aware of the 32-bit iCafe driver which works pretty well on my XP x86 installation, but I was curious to know if there was an x64 variant that has been removed from the net. I wasn't able to find anything, so if anybody has something hit me up.

Same issue Andreasmir. And even when I disable steamerrorreporter, Steam allocates about 7 megabytes of resources into RAM and just quits.

Hello, blackwingcat. I have been using the Extended Kernel for several years and I am generally satisfied, but there are 2 things that still Irk me. 1) Many raw Input dependant applications (MAME, PCem, 86box etc.) are unusable because Win2000 doesn't accept raw input. Is there a patch that I've missed that could solve this issue? 2) Steam is very quirky. Now If I would to launch steam, it would load about 7,900K of it's data into RAM and Immediately close. What's strange is that I've used Steam on Win2000 before Just fine. Any suggestions?