Operating Systems > Not Quite Mainstream OSes

ReactOS ....

<< < (9/12) > >>

insomnia:

quote:Originally posted by Aloone:
I have included a link to this in a previouse post and I don't know why I didn't do this before, as it illustrates my point!

     
Wine is not a CPU emulator it is emulation of the Windows API under Linux/UNIX.
--- End quote ---

No it doesn't.
Wine does not emulate any existing MS Windows API stucture. (If it would, you could run ALL Windows programs on it.)
They made their own compatible structure.
Just resemble their size, the one from Wine is much smaller.
An amulated API structure would also mean that it doesn't actually exist.
THE ONE FROM WINE DOES EXIST.

 
quote:Originally posted by Aloone:
BUT:
WINE AND DOSEMU BOTH WORK ON A SIMILAR PRINCIPLE!

IF WINE IS NOT AN EMULATOR THEN; IF YOU'RE DEFINITION IS TO BE CORRECT... DOSEMU IS NOT AN EMULATOR EITHER!

[/b]
--- End quote ---


They're not alike.
Dosemu uses code from an existing OS, Wine doesn't

Ps: Don't even bother to keep replying. I will simply ignore you.

[ July 26, 2004: Message edited by: insomnia ]

Aloone_Jonez:

quote:
You seem to be very literal and quite inflexible in your comprehension.

--- End quote ---


Maybe I am... maybe you are... maybe we all are!

The names Wine and DOSEMU must be both bullshit then!

IF:   Wine Is Not an Emulator.
THEN: DOSEMU can't also be an emulator.

AND

IF:   DOSEMU is an emulator.
THEN: Wine must also be an emulator.

Round and round we go!

Wine and DOSEMU both work on a similar principle.

Neither DOSEMU, nor WINE are CPU emulators.
They are both compatibility layers or dare I say it, examples of API emulation of a different OS.

The phrase "compatibility layer" is also very non-descript, you could also argue that a CPU emulator is an example of a "compatibility layer"
 since it is literly a layer of code between the OS or program bieng executed, to serve to make the forign code compatible with the host CPU.

Perhaps we should email the developers of both projects and tell them.

Hay it's fun to play word games!  

Aloone_Jonez:
Oh and insomnia,

DOSEMU dose not contain the whole FreeDOS code base, and it will not run all DOS programs.

Not all the Win API is documented some is HIDDEN, thus not all Windows programs run under Wine.

DOSEMU has a totally different structure to FreeDOS just as Wine

insomnia:

quote:Originally posted by Aloone:
Oh and insomnia,

Not all the Win API is documented some is HIDDEN, thus not all Windows programs run under Wine.

DOSEMU has a totally different structure to FreeDOS just as Wine

pofnlice:
Yet again, read the whole thing...

 
quote:Myth 1: "Wine is slow because it is an emulator"
Some people mean by that that Wine must emulate each processor instruction of the Windows application. This is plain wrong. As Wine's name says: "Wine Is Not an Emulator": Wine does not emulate the Intel x86 processor. It will thus not be as slow as Wabi which, since it is not running on a x86 Intel processor, also has to emulate the processor. Windows applications that do not make system calls will run just as fast as on Windows (no more no less).
Some people argue that since Wine introduces an extra layer above the system a Windows application will run slowly. It is true that, in theory, Windows applications that run in Wine or are recompiled with Winelib will not be able to achieve the same performance as native Unix applications. But that's theory. In practice you will find that a well written Windows application can beat a badly written Unix application at any time. The efficiency of the algorithms used by the application will have a greater impact on its performance than Wine.
Also, and that's what people are usually interested in, the combination Wine+Unix may be more efficient that Windows. Just as before it's just how good/bad their respective algorithms are. Now to be frank, performance is not yet a Wine priority. Getting more applications to actually work in Wine is much more important right now. For instance most benchmarks do not work yet in Wine and getting them to work at all should obviously have a higher priority than getting them to perform well.
But for those applications that do work and from a purely subjective point of view, performance is good. There is no obvious performance loss, except for some slow graphics due to unoptimized Wine code and X11 driver translation performance loss (which can be a problem sometimes, though).

--- End quote ---


[ July 26, 2004: Message edited by: AmericanBastard ]

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version