Welcome to the M1 Windows project

Post by dev_tty01 » Tue, Jun 07, 2022, 11:07 PM UTC

fckgw wrote: post #40

spacedcowboy wrote: post #22

Earlier quoted context omitted.

You don't have to pirate windows, you have to buy Parallels, which then downloads and installs Arm windows onto your M1 - and Arm Windows will run x86 binaries. I used this to run FPGA bitstream-creation software on my Mac Studio. Worked like a dream. I'm generally fine with running on the PC on the bookshelf and serving s/w via MS Remote Desktop, but having it on the machine itself is a bit more useful in terms of s…

Parallels in operating in a legal gray area and using Insider builds of Windows on ARM that are not licensed for M1 hardware. There is currently no legal way, from a licensing standpoint, to have an ARM build running on a device that Microsoft does not have an existing agreement with. If you're running an M1 with Parallels in any type of business or money-making environment then you're putting yourself at risk.

Post by zeusk » Tue, Jun 07, 2022, 11:10 PM UTC

frostwarrior wrote: post #95

zeusk wrote: post #80

Earlier quoted context omitted.

I work on the NT kernel and DirectX, I'll definitely take a look at this over the weekend.

Did you start working since the Windows NT era? I'm curious. IMHO, windows things aside, the NT kernel is an impressive feat of engineering and I'm surprised it's still going after so many years.

Post by GeekyBear » Tue, Jun 07, 2022, 11:19 PM UTC

kitsunesoba wrote: post #27

spacedcowboy wrote: post #22

Earlier quoted context omitted.

You don't have to pirate windows, you have to buy Parallels, which then downloads and installs Arm windows onto your M1 - and Arm Windows will run x86 binaries. I used this to run FPGA bitstream-creation software on my Mac Studio. Worked like a dream. I'm generally fine with running on the PC on the bookshelf and serving s/w via MS Remote Desktop, but having it on the machine itself is a bit more useful in terms of s…

It's technically pirating because the license of Windows for ARM does not allow end users to run it on arbitrary hardware or virtualize it. I have doubts that they'd ever actually enforce those terms though.

Post by pbronez » Tue, Jun 07, 2022, 11:23 PM UTC

tediousdemise wrote: post #154

dataflow wrote: post #133

Earlier quoted context omitted.

May I suggest you don't license the work in a way that allows it to be commercialized without your explicit permission and handsome compensation to you and any other contributors. You'll need this to be sustainable and it'll be incredibly frustrating if a company de-facto hijacks the development and takes it in a direction you don't expect or want.

IANAL but I'd like a license that goes something like this: Companies: If you are working for a company/corporation/profit-generating entity, or otherwise intend to sell or use such code derived from this repository for profit-generating purposes, you shall not be permitted to use any of the source code herein until you email me (author email here) and we can come up with the appropriate terms and conditions for your…

Post by stavros » Wed, Jun 08, 2022, 12:25 AM UTC

tediousdemise wrote: post #154

dataflow wrote: post #133

Earlier quoted context omitted.

May I suggest you don't license the work in a way that allows it to be commercialized without your explicit permission and handsome compensation to you and any other contributors. You'll need this to be sustainable and it'll be incredibly frustrating if a company de-facto hijacks the development and takes it in a direction you don't expect or want.

IANAL but I'd like a license that goes something like this: Companies: If you are working for a company/corporation/profit-generating entity, or otherwise intend to sell or use such code derived from this repository for profit-generating purposes, you shall not be permitted to use any of the source code herein until you email me (author email here) and we can come up with the appropriate terms and conditions for your…