Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Welcome to the M1 Windows project

amarioguy.github.io

Post reply on HN
Print view View original

121–130 of 276 posts

Re: Welcome to the M1 Windows project

#121

Post by unholiness »

tonguez wrote: post #117
scoopertrooper wrote: post #113

Earlier quoted context omitted.

> I have already delegated this to after I get Windows working under the thin hypervisor Not to be 'that guy', but that's an odd use of of the word 'delegated'. 'Relegated' might have been the word for which you were looking. Edit: I know this will be down voted because I'm critiquing the word usage of OP instead of focusing on how cool their project is. I get that. I'm just pedantic and this sort of thing eats me al…

Quoted post unavailable.

Following this completely imaginary "never end a sentence with a preposition" rule is some bullshit up with which I will not put.

Re: Welcome to the M1 Windows project

#122

Post by bpye »

jamesfmilne wrote: post #69

m1n1 in this case is a bit like ESXi, and this overall will be a bit like running Windows under VMware. I imagine this will be quite achievable. Windows 11 already runs ok in Parallels. Doing it "properly" native will require Microsoft to make changes to Windows though.

I’m not convinced the distinction is really important. Would you say running Windows with Hyper-V enabled is non-native for example?

Re: Welcome to the M1 Windows project

#123

Post by technovader »

oofbey wrote: post #103
jokoon wrote: post #10

Can't microsoft work on this instead? I don't get it.

Microsoft and Apple are traditional enemies. Microsoft has no reason to make Apple's hardware more attractive to customers. The thing I don't get is why a consumer would want this. You want an _extremely expensive_ windows laptop. I guess the hope would be that the battery life is worlds better than anything you'd get in standard windows-land. But in reality battery life optimization requires paying careful to the de…

You can't imagine why a Windows user would want to run it on better hardware?

Or that there are Windows workflows that just don't work on OSX?

Or want a fanless laptop with good performance?

Re: Welcome to the M1 Windows project

#124

Post by amarioguy »

AshamedCaptain wrote: post #54
roblabla wrote: post #39

Earlier quoted context omitted.

That's only true up to a certain point. ARM is a very weird target, because a lot of standardized stuff we take for granted in x86/PC land aren't standardized on ARM. In particular, take the Interrupt Controller: x86 has a standard for it (well, technically has two, the PIC and APIC). The "standard" in ARM-land is the GICv3 or GICv4, but many different CPU vendors have their own. Apple has the "Apple Interrupt Contro…

Actually you might be surprised. Windows NT is _older_ than many of the "standards we take for granted in x86/PC land", and for example it does support multiple types of pre-ACPI ways of bringing up multiprocessor systems and specifically multiple types of interrupt controllers. Heck, x86 Windows even supports non-PC servers from Compaq and others; ever tried to press F5 during (old) Windows NT setup ? As the OP said…

Generally speaking part of the issue with a custom HAL nowadays is that Microsoft moved the HAL from being a DLL to being a statically linked library within the kernel (likely as a performance optimization and because there's no real need for a new HAL in most instances when HAL Extensions exist)

This merger of the kernel and HAL invariably means patching the HAL is now equivalent to patching the kernel

Re: Welcome to the M1 Windows project

#125

Post by amarioguy »

emptysongglass wrote: post #84
roblabla wrote: post #39

Earlier quoted context omitted.

That's only true up to a certain point. ARM is a very weird target, because a lot of standardized stuff we take for granted in x86/PC land aren't standardized on ARM. In particular, take the Interrupt Controller: x86 has a standard for it (well, technically has two, the PIC and APIC). The "standard" in ARM-land is the GICv3 or GICv4, but many different CPU vendors have their own. Apple has the "Apple Interrupt Contro…

This part is why I hope x86 has a long life ahead of it. Everybody and their dog have their own standard for things in ARM-land.

for what it's worth amd64 is not going anywhere outside of Macs for at least the next decade, possibly two.

Despite the benefits ARM provides amd64 undeniably has advantages and non-trivial ones at that.

personally, I'm of the opinion it'll come to a coexistence for a time rather than one dominating the other immediately.

Re: Welcome to the M1 Windows project

#127

Post by [deleted] »

amarioguy wrote: post #87

hey, OP here, figured i'd clarify some things about this project: 1) yes, I realize this is going to be way harder than it seems, but I'm actually going to do my best to hopefully get a good user experience out of this and I'm easily preparing for this to be a multi-year effort, but I'm not going to give up right at the gate 2) Custom HALs were actually an option, up until very recently, since as of Windows 10, versi…

[deleted]

Re: Welcome to the M1 Windows project

#128

Post by JonathonW »

can16358p wrote: post #118
JonathonW wrote: post #111

Earlier quoted context omitted.

The current version of Parallels uses the stable build of Windows 11 for ARM. Once you've installed Windows, it's possible to pay for and license Windows directly from Microsoft via the Windows Store app. There might be a brief period where you're technically unlicensed (not sure what the exact verbiage is in the current Windows EULA about trial/grace periods), but the end result is a properly-licensed Windows 11 ins…

Last time I checked I could not purchase a license to activate Windows 11 ARM on Parallels on Mac. It gave all sorts of not founds/errors in the store app. This was a few months ago. Did it change or am I missing something?

Probably changed-- I had no issues buying a license back in March.

Re: Welcome to the M1 Windows project

#129

Post by nomel »

scoopertrooper wrote: post #113
amarioguy wrote: post #87

hey, OP here, figured i'd clarify some things about this project: 1) yes, I realize this is going to be way harder than it seems, but I'm actually going to do my best to hopefully get a good user experience out of this and I'm easily preparing for this to be a multi-year effort, but I'm not going to give up right at the gate 2) Custom HALs were actually an option, up until very recently, since as of Windows 10, versi…

> I have already delegated this to after I get Windows working under the thin hypervisor Not to be 'that guy', but that's an odd use of of the word 'delegated'. 'Relegated' might have been the word for which you were looking. Edit: I know this will be down voted because I'm critiquing the word usage of OP instead of focusing on how cool their project is. I get that. I'm just pedantic and this sort of thing eats me al…

Personally, I've learned to talk more precisely from these sorts of comments than anywhere else. In real life, people will rarely correct you. I think the concept of a "meta comment" is interesting, where you could push this sort of thing into a separate parallel thread that would normally be hidden.

Re: Welcome to the M1 Windows project

#130

Post by loudmax »

yazaddaruvala wrote: post #97
boardwaalk wrote: post #52

I’d frankly be surprised if you were able to muster the talent/willpower for something like this. 1. Most of the people able to do this sort of thing probably work in Linux/FreeBSD/etc land. 2. You’re really working doubly against the tide here. You have proprietary stuff on the Mac and on the Windows side. 3. (Personal opinion) Dear God that sounds like a lot of work for something that is a fairly unfriendly experie…

Fortunately, Microsoft seems to be moving towards: Windows as "just another Linux distribution" with a backwards compatibility layer. Previous Step: Linux compatibility layer on Windows. https://docs.microsoft.com/en-us/windows/wsl/install Current Step: Get DirectX to be first-class on Linux. https://www.phoronix.com/scan.php?page=news_item&px=Microsof... Next Steps: Get the Windows GUI + Win32 APIs + backwards compa…

After embracing Linux, that would definitely extend it. Wonder what would come next.
Post reply on HN