Leaderboard

DIFF patch in first post updated to v6 for Windows XP and Windows 2003 Changes: Fix for XOR opcode ACPI0007 CPU definition

The processor driver is primarily for power management, so it would probably not do anything. I might try my luck with a HAL wrapper eventually, as that seems plausible due to the kernel resolving export forwards for NTOSKRNL and HAL (but no other kernel mode modules, though the Xbox kernel might be different based on its inclusion of MmGetSystemRoutineAddressEx which works on all kernel mode modules). The binary patches to the HAL were not cutting it and I could not implement the TSC correction in any form as the system would get stuck in fence loops on boot. And if export forwards don't work out, there are only 81 exports to duplicate in 6003's HAL. But I still have to get NVIDIA 4xx drivers, make NVIDIA 36x+ work 100% by adding functions for Vulkan and OpenCL, not to mention the Windows 10-compliant implementation of job objects. And all kinds of odds and ends along the way! This morning I got very annoyed with continuing printer driver issues on Windows 8.1 (and 10 is not much better). Nothing like that on 2000/XP/Vista (and maybe not 7 either).

How is browser talking to itself "privacy risk"?

This thread has been getting too derailed lately. Please stick to the thread topic and remember to stay respectful of everyone, even if you don't agree with their opinions. Let's refer to: 7.b This community is built upon mutual respect. You are not allowed to flame other members. People who do not respect personal opinions and/or personal work will be warned in first instance. If you ignore the warning and keep on flaming, you will be banned without notice. This is the last warning that will be posted on the matter. Do not make us start taking further actions. Stay on topic and be nice! Please and thank you!

@Damnation Here is the fresh from @Mov AX, 0xDEAD via Patch compiled by me, acpi.sys v6 and its acpi.pdb for XP SP3 Dietmar https://ufile.io/6iesmav8 and here its Debug version https://ufile.io/7kciqjd2

I will rebuild it in few hours, when I’m back on my PC

There are two base issues: #1 the Surface Go is a UEFI only machine, as such has no BIOS (or CSM) whilst Windows 7 has not built-in proper support for UEFI booting, this can usually worked around using a later Windows OS bootloader and a couple of tricks #2 if I recall correctly (but I may well be wrong) the Surface has UEFI GOP video which adds an additional problem, there is (right now the whole board is down, unfortunately) thread on reboot.pro about a possible way to force a Windows 7 to use a GOP driver through an extremely risky procedure (and BTW I cannot remember if it was a generic solution or specific to some particular hardware) AND a third one: #3 the hardware of a Surface (and particularly of the Go type) will need device drivers that simply do not exist for Windows 7 So, in theory everything is possible, but the issue is not "jailbreaking" (that usually means to expose existing functionalities that are locked down or inaccessible), one would need to have a whole replacement firmware AND all the needed drivers, as a parallel example you cannot install a *common* Linux distro on it, you need particular files: https://github.com/linux-surface/linux-surface because the Microsoft hardware on the Surface has its own peculiarities. jaclaz

That's kind of my primary point. If we truly want to be "fair", then we MUST use the same "magnifying glass" that we use during 360Chrome "criticism" and look at other browsers with the same "magnifying glass". 360Chrome did not "introduce" this newly-discovered HDD spin. It was already a part of the underlying code. "American" code. Not Chinese code. Not Russian code. But American code! It also still boils down to "pros" and "cons". I personally do not trust Mozilla/UXP browsers because they all require a "loopback rule" for firewall software such as WiseVector StopX and Comodo Personal Firewall 2.4.18.184. We literally "enable" Mozilla/UXP to do "anything and everything" because we cannot "monitor" what traffic is going through that "loopback". But if we truly use the same "magnifying glass", we should ask ourselves why we "accept" that loopback rule for one browser but not for another. Mozilla/UXP and Chrome/Chromium do things so much differently than each other that sometimes it is very difficult to decide which one to 'trust'. If you are going to be "connected" to the internet, there are some risks that you simply have to accept. Some of us will view Mozilla/UXP "loopback" a much larger privacy risk than an idle HDD waking up for no real reason but our DNS Traffic Logs showing no data being sent when that HDD spun up for no real reason.

Sure, but whether Microsoft supports (or fails to support) any given OS does not imply that another OS can run on it. While, as said, it is very unlikely that 7 can be installed on a Surface Go for technical reasons, the fact that MS does not support it is not particularly relevant. jaclaz

I have added only few “improvements” to @Mov AX, 0xDEAD latest release. You can see changelog on GitHub.

acpi.sys v7777.5, Virtual 12 Cores CPU qemu 2.10: qemu 3.1: After reboot both qemus show right names on all cores First Device detection log is same for "Processor" and "QEMU Virtual CPU version 2.5+"