.exe
- Thread starter StarLee
- Start date
Zammy-Sam
Desertchild
You can't open unless you have an x86 emulator. There is VPC which is best but also most expensive one. Take a look at this:
http://macosx.com/forums/showthread.php?t=30652
and there is also Wintel:
http://macosx.com/forums/showthread.php?t=36477
http://macosx.com/forums/showthread.php?t=30652
and there is also Wintel:
http://macosx.com/forums/showthread.php?t=36477
cachymunkey
Registered
There are options out there, but to talk about it I would have to shoot myself afterwards.
a_iver
Registered
It probably won't be available for quite some time but check out darwine on sourceforge.net . They're working on a way to open windows files on mac. Without an emulator. Here's the link http://darwine.opendarwin.org/
ok folks, this is probably a really dumb question, but can anyone tell me exactly what a .exe document is ? I have officeX for mac that opens word /
poserpt stuff but not .exe...... some windows folks tried to explain it but said it indicates.... blah blah......... which I didnt understand...... any mac folks who can give a SIMPLE clear explanation what it is and how it differs from word etc?
thanks
sue
Newnan, GA
poserpt stuff but not .exe...... some windows folks tried to explain it but said it indicates.... blah blah......... which I didnt understand...... any mac folks who can give a SIMPLE clear explanation what it is and how it differs from word etc?
thanks
sue
Newnan, GA
dlloyd
Official Pianist
Well, quite simply, .exe is the extension for an EXEcutable, or Application, on a Windows computer (the extension under OS X for an application is .app, BTW).
An .exe cannot be run on a Mac because it is compiled for an X86 processor, the processor a PC uses, not the PowerPC processor that a Macintosh is built around.
You are able to open a word (.doc) file (and many others: .txt, .html, .rtf, .gif, .jpg, .bmp, for example) on both Mac and PC because they are not compiled. In other words, they are not Applications. They are merely data that an application, running on either Mac OR PC, can interpret.
Not to complicate things, but there are some applications that can be opened both Mac and PC (and others: Linux, etc.). These include applications coded in Java. The reason for this is that they are also interpreted, not compiled (part of the reason Java apps are so slow). To run a Java program you must have the correct Libraries installed for your OS.
a_iver: That is not quite correct. Darwine will not run .exes without emulation. In order to run a .exe you must have an X86 processor, so Darwine will have an X86 emulator built in. I'm not sure how they'll do this, but if you go look, it's on their site.
An .exe cannot be run on a Mac because it is compiled for an X86 processor, the processor a PC uses, not the PowerPC processor that a Macintosh is built around.
You are able to open a word (.doc) file (and many others: .txt, .html, .rtf, .gif, .jpg, .bmp, for example) on both Mac and PC because they are not compiled. In other words, they are not Applications. They are merely data that an application, running on either Mac OR PC, can interpret.
Not to complicate things, but there are some applications that can be opened both Mac and PC (and others: Linux, etc.). These include applications coded in Java. The reason for this is that they are also interpreted, not compiled (part of the reason Java apps are so slow). To run a Java program you must have the correct Libraries installed for your OS.
a_iver: That is not quite correct. Darwine will not run .exes without emulation. In order to run a .exe you must have an X86 processor, so Darwine will have an X86 emulator built in. I'm not sure how they'll do this, but if you go look, it's on their site.
symphonix
Scratch & Sniff Committee
a_iver: The Mac OS X operating system is based on Unix, in essence it is a Unix operating system underneath the Mac interface that the end user sees. That's why it is a relatively easy task for software makers to bring software from Unix/Linux to Mac.
EXE files, however, are built to run on a DOS/Windows environment and often use code that accesses the x86 processor directly. They also "talk" in commands that are only found in the Windows environment. So what's the problem? Firstly, Windows is a closely guarded proprietary environment owned by Microsoft, while Linux/Unix (more or less) is based on open-source code that is freely available. The second difference is that the PowerPC processors used in Macs has a completely different structure to the x86 based processors used in PCs.
Programs like Virtual PC and Bochs emulate a PC by "pretending" that they are a PC hardware. They take the EXE file and handle it in the same way that a PC would by working out how a PC would respond to the code. It takes each little bit of code and works out how a PC processor would deal with it, by translating it into something the Mac can handle.
WINE is different to other emulators. It replaces the Windows part of the environment, but it doesn't try and emulate an x86 processor. Instead, WINE was originally designed to run on PCs with Linux installed instead of Windows. This is slowly being altered to become platform independent, but it still only emulates some of the Windows environment and some of the processor functions. Thus it can currently run some windows software on PCs and even less on Mac.
EXE files, however, are built to run on a DOS/Windows environment and often use code that accesses the x86 processor directly. They also "talk" in commands that are only found in the Windows environment. So what's the problem? Firstly, Windows is a closely guarded proprietary environment owned by Microsoft, while Linux/Unix (more or less) is based on open-source code that is freely available. The second difference is that the PowerPC processors used in Macs has a completely different structure to the x86 based processors used in PCs.
Programs like Virtual PC and Bochs emulate a PC by "pretending" that they are a PC hardware. They take the EXE file and handle it in the same way that a PC would by working out how a PC would respond to the code. It takes each little bit of code and works out how a PC processor would deal with it, by translating it into something the Mac can handle.
WINE is different to other emulators. It replaces the Windows part of the environment, but it doesn't try and emulate an x86 processor. Instead, WINE was originally designed to run on PCs with Linux installed instead of Windows. This is slowly being altered to become platform independent, but it still only emulates some of the Windows environment and some of the processor functions. Thus it can currently run some windows software on PCs and even less on Mac.
octane
I have issues, OK!
StarLee said:
Yes! Of course you can.
What ever application you're using on Windows will allow you to save what you're doing, just the same way as they would when running on a full-blown pc.
What you can do -- and this is what I tend to do -- I set up a shared folder within VirtualPC; which can be any folder you create on your mac, and save your files there.
That way, both your mac and pc can see and work with the same files.
The shared folder shows up as a mounted volume on your pc.
StarLee said:
Sorry missis .. didn't know you were a Sheila!..
