Programming in Altivec in nicer than most machine languages due to the nice set of C macros provided, but regular Bochs almost certainly has no Altivec code.
Would someone please give me a clue what this is about?
Essentially, it's the same as Classic.app, except it gives you a Windows environment instead of a Mac OS 9 environment. Basically. More or Less. Kinda sorta.
Essentially, it's the same as Classic.app, except it gives you a Windows environment instead of a Mac OS 9 environment. Basically. More or Less. Kinda sorta.
Nope Classic was not an emulator. Think of this as another version of VPC...
Nope Classic was not an emulator. Think of this as another version of VPC...
Except WINE stands for Wine Is Not an Emulator. WINE translates windows instructions into the equivelent Linux instructions. So although it's not like Classic (which actually boots inside a virtual machine), it's closer to Classic than VPC.
Except WINE stands for Wine Is Not an Emulator. WINE translates windows instructions into the equivelent Linux instructions. So although it's not like Classic (which actually boots inside a virtual machine), it's closer to Classic than VPC.
Right.. it would be if they did not have to emulate the x86 code. Which is what BOCHs is for.. WINE may not be an emu but BOCHs is.. Like I said its closer to VPC than classic.
WINE itself may be like classic but this whole DarWINE setup is not.
WINE converts the Windows apps (in x86 code) into comparable Linux calls (in x86 code). BOCHS then takes that x86 code and converts it to PowerPC code, which is actually executed.
So WINE is *STILL* 'Not an Emulator'. It doesn't emulate squat. BOCHS does that. Two separate jobs, two separate tools.
Well, classic emulates 68k, but no one goes on about that.
Without looking at the code for darwine, I will make the following leap:
WINE translates windows api calls to linux api calls. This can still be done natively. WINE still uses x11 to do its windowing. So some amount of darwine will run natively.
However, to determine what calls are being made, the code needs to be executed by bochs. I think you'll find that bochs will be jumping between native and x86 code all over the place as it encounters windows api calls that are handled by WINE.
WINE, however can quite happily make use of windows dlls to carry out some of its magic, so Im not sure how much ends being converted to linux api calls.
The indication that this is how it works is that darwine is _SOURCE_ compatible now. You can compile windows programs on the mac and have them work - they are running in the x11 enviroment. One aim of darwine is to eventually map those calls to aqua instead.
OT: Im using VNC on my iMac, and win2VNC on my PC to controll my PC and Mac seemlessy from one keyboard and mouse. Its just like having a dual head ( except for drag and drop ). VNC even supports cut and paste between them. Sooooo sweet.
OT: Im using VNC on my iMac, and win2VNC on my PC to controll my PC and Mac seemlessy from one keyboard and mouse. Its just like having a dual head ( except for drag and drop ). VNC even supports cut and paste between them. Sooooo sweet.
Come on dude... try and stay on topic... this ain't a VNC thread.. its about Darwine Stay on topic damnit
Err Yeah it will be rootless but the apps are still emulated.. Regardless of what WINE stands for...
At this point in time, there is no emulation involved in Darwine. All it does right now is translate instructions from Windows API calls to Linux API calls.
And EVEN IF they manage to shim BOCHS into WINE, it's still very, VERY unlike VirtualPC. The individual instructions may be converted to PowerPC like in VPC, but whereas VirtualPC is a virtual machine WINE is a translation engine.
Comments
That means no Altivec, right?
Programming in Altivec in nicer than most machine languages due to the nice set of C macros provided, but regular Bochs almost certainly has no Altivec code.
Originally posted by Aquatic
Bochs is crap. I wish Orangemicro would make PC cards again.
Haha...P4's and G5's in the same box == bad idea
Originally posted by Anders
Would someone please give me a clue what this is about?
Essentially, it's the same as Classic.app, except it gives you a Windows environment instead of a Mac OS 9 environment. Basically. More or Less. Kinda sorta.
just sayin...
but if WINE on MAC works, it would be a nail in a coffin, a powerbook will be my next buy,
bye bye windoze
Originally posted by Whisper
Essentially, it's the same as Classic.app, except it gives you a Windows environment instead of a Mac OS 9 environment. Basically. More or Less. Kinda sorta.
Nope Classic was not an emulator. Think of this as another version of VPC...
Originally posted by SilentEchoes
Nope Classic was not an emulator. Think of this as another version of VPC...
Except WINE stands for Wine Is Not an Emulator. WINE translates windows instructions into the equivelent Linux instructions. So although it's not like Classic (which actually boots inside a virtual machine), it's closer to Classic than VPC.
or is it not really.:consufed:
Originally posted by Barto
Except WINE stands for Wine Is Not an Emulator. WINE translates windows instructions into the equivelent Linux instructions. So although it's not like Classic (which actually boots inside a virtual machine), it's closer to Classic than VPC.
Right.. it would be if they did not have to emulate the x86 code. Which is what BOCHs is for.. WINE may not be an emu but BOCHs is.. Like I said its closer to VPC than classic.
WINE itself may be like classic but this whole DarWINE setup is not.
Of course, there would need to be emulation, but if MS Windows wasn't needed, then it would be like Classic - there's no Classic Finder in OS X.
Try this on for size:
Windows apps
------------
WINE
------------
BOCHS
------------
Darwin
WINE converts the Windows apps (in x86 code) into comparable Linux calls (in x86 code). BOCHS then takes that x86 code and converts it to PowerPC code, which is actually executed.
So WINE is *STILL* 'Not an Emulator'. It doesn't emulate squat. BOCHS does that. Two separate jobs, two separate tools.
Darwine = WINE + BOCHS.
WINE does not emulate. BOCHS does. Darwine will have to by definition, and will do so through BOCHS.
WINE itself may be like classic but this whole DarWINE setup is not.
Originally posted by SilentEchoes
Thanks. Thats what I have been saying all along.
Well, classic emulates 68k, but no one goes on about that.
Without looking at the code for darwine, I will make the following leap:
WINE translates windows api calls to linux api calls. This can still be done natively. WINE still uses x11 to do its windowing. So some amount of darwine will run natively.
However, to determine what calls are being made, the code needs to be executed by bochs. I think you'll find that bochs will be jumping between native and x86 code all over the place as it encounters windows api calls that are handled by WINE.
WINE, however can quite happily make use of windows dlls to carry out some of its magic, so Im not sure how much ends being converted to linux api calls.
The indication that this is how it works is that darwine is _SOURCE_ compatible now. You can compile windows programs on the mac and have them work - they are running in the x11 enviroment. One aim of darwine is to eventually map those calls to aqua instead.
Originally posted by mmmpie
OT: Im using VNC on my iMac, and win2VNC on my PC to controll my PC and Mac seemlessy from one keyboard and mouse. Its just like having a dual head ( except for drag and drop ). VNC even supports cut and paste between them. Sooooo sweet.
Come on dude... try and stay on topic... this ain't a VNC thread.. its about Darwine Stay on topic damnit
Originally posted by SilentEchoes
Err Yeah it will be rootless but the apps are still emulated.. Regardless of what WINE stands for...
At this point in time, there is no emulation involved in Darwine. All it does right now is translate instructions from Windows API calls to Linux API calls.
And EVEN IF they manage to shim BOCHS into WINE, it's still very, VERY unlike VirtualPC. The individual instructions may be converted to PowerPC like in VPC, but whereas VirtualPC is a virtual machine WINE is a translation engine.
Barto