Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

wyrdness

macrumors 6502
Dec 2, 2008
274
322
Has anyone tried booting the ARM version of Windows (from UUP Dump) on the M1? I have it running on my Pi 3 and 4. Performance is poor due to the lack of drivers however.
And how would anyone do that? The only two ways would be to boot straight into it (impossible) or to use a Virtual Machine (doesn't exist yet).
 

Macalway

macrumors 601
Aug 7, 2013
4,183
2,934
Just a heads up

One solution is to use that Luna Display thing in Mac to Mac mode. I saw the post on the front page today (here) about the update they made (or whatever it is), so I dragged mine out (that little red thing). I've got my M1 Air as a display for an Intel Mac (a MacBook Pro 15").

I'm typing this on an M1 Air now but the OS is Big Sur MacBook Pro 15" in mirror mode. It feels good. A decent solution. This MacBook Pro has VMware fusion with the Windows apps.

Thing is, this new M1 has so much power it's not unexpected. Of course, a different solution would be better, but that Crossover at 7fps, and the double emulation is perhaps a stretch.

No heat out of the Air. I will check various things and update this post. I just started it so it will take time. People ask what's the difference between the Luna and Sidecar. I think one difference is this Mac to Mac mode, which is the point of this post. I don't think Sidecar does that. I need Windows apps also, and the ones I need aren't particularly demanding so that Crossover thing I will try also. I think Microsoft may give us an Arm version at some point, as it's just more sales. :)
 
  • Like
Reactions: filmak

dukebound85

macrumors Core
Jul 17, 2005
19,167
4,165
5045 feet above sea level
Expect both Parallels and VMware to run slower since now it has to provide a CPU emulation in addition to the emulation it was previously providing. Think back to the old days when we had PowerPC machines trying to emulate Intel machines.
VirtualPC days.....man I remember trying to run CAD programs in college in XP on my emac. Talk about SLOW
 
  • Haha
Reactions: Stridr69

pshufd

macrumors G4
Oct 24, 2013
10,149
14,574
New Hampshire
VirtualPC days.....man I remember trying to run CAD programs in college in XP on my emac. Talk about SLOW

A friend has a PowerBook and wanted to show me it running Windows. So I watched him boot it up. And I waited and waited and waited and he was proud when it came up. I thought that it wasn't all that impressive but didn't say so. Windows PCs were a lot more expensive back then so it was a bit harder to have two laptops.
 
Last edited:

pshufd

macrumors G4
Oct 24, 2013
10,149
14,574
New Hampshire

take a look at this @fab5freddy

I'd guess that Microsoft would expect Apple to pay for the port.

The company I used to work for ran on dozens of platforms. We did the work on the high-volume platforms. For low-volume platforms, the platform vendor paid us to do the porting work. So HP paid us a ton of money to do an Itanium port. I don't see Apple paying Microsoft to do a Windows port and I bet that Microsoft's applications group are porting to macOS/AS anyways.
 

AppleTO

macrumors 65816
Oct 31, 2018
1,106
3,056
Toronto, Canada
And how would anyone do that? The only two ways would be to boot straight into it (impossible) or to use a Virtual Machine (doesn't exist yet).
Ah okay, I was under the impression booting other OSes from USB was still possible in a less-secure mode. But I must be thinking of something else.
 

weckart

macrumors 603
Nov 7, 2004
5,976
3,697
Back in the 1990s, Windows also ran on three other platforms: PPC, Alpha and one other. Maybe MIPs. Microsoft made the binaries and the kits. I worked on porting an application to Alpha/NT. I even have about four tee-shirts from the project. There was a product, similar to Rosetta, that ran x86 binaries via code translation.

So Microsoft could do this if they had the inclination to do so.


There were two of which I am aware. NT Alpha had a code switching application FX!32, which translated calls to the CPU from Intel code into native Alpha code and recompiled, so that the more you used an Intel app, the faster it would eventually run as more and more of the Intel code was replaced by native code. Having said that, even running something like Winzip under Alpha was painfully slow.

As for PPC and, I think, MIPS both ran 16 bit Windows Intel apps under emulation with the obvious overhead costs in terms of speed and responsiveness. MS never bothered with a 32 bit layer so I don't hold out much hope for AS. It all depends on how smoothly Apple makes the full transition over to AS and whether MS can see a business case for putting in the work for making Windows and key MS applications running on Apple hardware.
 

pshufd

macrumors G4
Oct 24, 2013
10,149
14,574
New Hampshire
There were two of which I am aware. NT Alpha had a code switching application FX!32, which translated calls to the CPU from Intel code into native Alpha code and recompiled, so that the more you used an Intel app, the faster it would eventually run as more and more of the Intel code was replaced by native code. Having said that, even running something like Winzip under Alpha was painfully slow.

As for PPC and, I think, MIPS both ran 16 bit Windows Intel apps under emulation with the obvious overhead costs in terms of speed and responsiveness. MS never bothered with a 32 bit layer so I don't hold out much hope for AS. It all depends on how smoothly Apple makes the full transition over to AS and whether MS can see a business case for putting in the work for making Windows and key MS applications running on Apple hardware.

The thing is that many key applications already run on macOS Intel or on the cloud and they can just port the application without porting Windows.
 

weckart

macrumors 603
Nov 7, 2004
5,976
3,697
The thing is that many key applications already run on macOS Intel or on the cloud and they can just port the application without porting Windows.
MS Office and Adobe whatever is a given but the rest is down to individual vendors. The problem starts when people have legacy 64 bit versions, which aren't going to be updated, even under Intel, since that platform is being jettisoned in short measure or need those particular versions to work with particular hardware or workflows, which break under newer versions. Some vendors might put a lot of time and effort into porting their software for very little reward.
 
  • Like
Reactions: m-a

Marbles1

macrumors 6502a
Nov 27, 2011
545
2,833
Yeah, this is one reason why my next Mac I plan to buy either at the very end of this year or the start of next year is the 13" 2.0 GHz quad-core i5 MacBook Pro (with 16 GB of RAM and 512 GB SSD), so I can still run Windows virtual machines if need be. Especially since I like to make Let's Play commentary videos of old computer games of my childhood that won't run on any operating systems newer than Windows XP, and since Anthro New England in 2022 is going to have a 1990s theme and I plan to host a panel about 1990s kids' computer games, and if I use that MacBook Pro I can run a Windows XP virtual machine on VMware Fusion to play said older games! (Any that use the Scumm engine I can just use ScummVM, though, and I may also demonstrate at least a couple of DOS games using Boxer, which has a 64-bit Beta available.)
Plus, I read on EveryMac.com that the 13" M1 MacBook Pro does indeed outperform the 2.0 GHz i5 MacBook Pro a bit, especially if it has 16 GB of RAM, but I'm not fully ready to take the jump into the M1 world yet; I might wait a year or two until they come out with the more powerful version of the M1 chip for the higher-end Macs and they make a nicely beefed-up Mac Mini using that, and get that to replace my 2012 quad-core i7 Mini. Besides, with the 13" i5 MacBook Pro I can at least run Mac OS 11 Big Sur, AND still use the Mini as my main desktop (maybe even get a KVM machine for running the Pro like a desktop alongside the Mini!)

This is exactly what I did. 13", 2ghz quad core i5, 16b ram and 512 GB SSD. the perfect machine to last for 3-4 years, and longer if needed. Can run windows 10. Will run all my steam games if they continue to lose support (Just like I can run games which no longer run on Mac since the move to 64 bit only with Catalina - It's great to have bought these on steam rather than the Mac app store, so I still have a way of playing them. I'll never buy games on the Mac app store; and am only really comfortable with subscription software as I don't trust apple not to pull up the drawbridge again).
 

radus

macrumors 6502a
Jan 12, 2009
720
447
Expect both Parallels and VMware to run slower since now it has to provide a CPU emulation in addition to the emulation it was previously providing. Think back to the old days when we had PowerPC machines trying to emulate Intel machines
Remember - one has to put a 386-PCI-Card in to run Windows - was a hard time in the end I worked with a Mac and a PC side by side.
 

AlanBrowne

macrumors newbie
Jan 31, 2010
7
2
Is there any way to run Windows 10 if i get the new M1 Macbook Pro?

VMWare will be coming out with an Mx solution for VM. That should be more than adequate. (I assume Parallels will too). And VM's are far better than bootcamp for most solutions until the word "gaming" comes up.
 
  • Like
Reactions: m-a

AlanBrowne

macrumors newbie
Jan 31, 2010
7
2
There are two types of "Windows VM" at play here.

Native ARM Windows 10 VM, running native ARM code on M1. This would require Microsoft making an "Apple Silicon" version of Windows 10/ARM. This is "simple" for the VM software - Parallels has already demonstrated a version of their software running an ARM Linux. And the ARM version of Windows even has an Intel emulator so it can run Intel Windows software. But this requires Microsoft to make this version of Windows available to Mac owners.

Intel Windows 10 VM, running in a virtual machine program that includes an Intel code emulator. This would run bone-standard Windows 10 that you can buy from Microsoft today; but requires a lot more work on the VM software's part to add the Intel emulation.
I would hope that it is translation (which can be deeply optimized if approached correctly) and not emulation which is necessarily slower. ie: A Rosetta 2 type approach to installing the Windows (or Linux, though an ARM Linux would obviously be a better VM).
I'm close to the point where I can abandon Windows altogether. I have a couple apps to replace and I'm done - just not very satisfied with the offerings in Mac space.
 

laptech

macrumors 601
Apr 26, 2013
4,130
4,455
Earth
What bewilders me is that not only Apple but others as well are saying it's up to Microsoft if they want to support Apple silicon so it can run Windows but here's the thing, Apple had to re-write OSX when they transitioned from powerpc to Intel. Apple wrote OSX for M1 ARM chip. Apple therefore have the knowhow and tools to build their own x86 emulator to allow Windows to run on their machines but they wont, they are expecting others to do it for them. Whilst the Apple developers were re-writing OSX from Intel to ARM, Apple could have easily setup a team to work along side the M1 developers to design a x86 emulator that would allow mac owners who use both OS's to carry on doing so. So the question has to be, why didn't they? Granted having a dedicated ARM version of Windows is the ideal solution BUT it requires Microsoft to do it and more importantly, the requirement to WANT to do it.

Apple knows there are thousands, possibly millions of mac users who need to run Windows along side Mac OS so why didn't they plan for this?, rather than saying 'oh, well it's up to Microsoft'. They have the man power, they have the expertise, they have the developers and they have the tools to build an x86 emulator that would have worked out the box on the M1 but they didn't. Now people are asking when will Windows be ready for M1 and all Apple can say is 'well, it's up to others, not us'.
 

Squeak825

macrumors 6502
Sep 5, 2007
440
308
VMWare will be coming out with an Mx solution for VM. That should be more than adequate. (I assume Parallels will too). And VM's are far better than bootcamp for most solutions until the word "gaming" comes up.

No. This is a common misunderstanding. Until Microsoft allows for the ARM version to be purchased individually, the VMWare solution they are going out for the M1 will NOT run Windows. It will not run x86 Windows.
 

dogslobber

macrumors 601
Oct 19, 2014
4,670
7,809
Apple Campus, Cupertino CA
Has anyone tried booting the ARM version of Windows (from UUP Dump) on the M1? I have it running on my Pi 3 and 4. Performance is poor due to the lack of drivers however.
Should be straightforward.

Copy the Terminal.app
Set Terminal.app to run under Rosetta2
Install brew from brew.sh
brew install qemu
Create an ARM ISO for Windows from UUP Dump
Boot ARM Windows ISO via qemu
Boom

ARM Windows running on M1.
 

pshufd

macrumors G4
Oct 24, 2013
10,149
14,574
New Hampshire
What bewilders me is that not only Apple but others as well are saying it's up to Microsoft if they want to support Apple silicon so it can run Windows but here's the thing, Apple had to re-write OSX when they transitioned from powerpc to Intel. Apple wrote OSX for M1 ARM chip. Apple therefore have the knowhow and tools to build their own x86 emulator to allow Windows to run on their machines but they wont, they are expecting others to do it for them. Whilst the Apple developers were re-writing OSX from Intel to ARM, Apple could have easily setup a team to work along side the M1 developers to design a x86 emulator that would allow mac owners who use both OS's to carry on doing so. So the question has to be, why didn't they? Granted having a dedicated ARM version of Windows is the ideal solution BUT it requires Microsoft to do it and more importantly, the requirement to WANT to do it.

Apple knows there are thousands, possibly millions of mac users who need to run Windows along side Mac OS so why didn't they plan for this?, rather than saying 'oh, well it's up to Microsoft'. They have the man power, they have the expertise, they have the developers and they have the tools to build an x86 emulator that would have worked out the box on the M1 but they didn't. Now people are asking when will Windows be ready for M1 and all Apple can say is 'well, it's up to others, not us'.
That's not how ports work.

You use the same code for multiple platforms and you have conditional code, sometimes in macros, to deal with machine/operating system - specific issues.

You don't do a rewrite for a port.
 
  • Like
Reactions: m-a

laptech

macrumors 601
Apr 26, 2013
4,130
4,455
Earth
That's not how ports work.

You use the same code for multiple platforms and you have conditional code, sometimes in macros, to deal with machine/operating system - specific issues.

You don't do a rewrite for a port.
If that is not how it works then please explain why Apple did not write an x86 port to work on the M1? because what you suggest is a lot easier than do a complete re-write. They know many businesses use Windows on their Macs for business purposes. Apple has the code for x86, they have the code for M1 but instead of writing an x86 port whilst they were developing the M1 and writing the code so MacOS would work on ARM, instead they are telling others to make x86 work on the M1, why?
 
  • Like
Reactions: Stridr69 and m-a
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.