JayFoxRox said:Wineboot doesn't even take a second for me. And it really depends on what you have in your wine install. I'm not even sure what wineboot does. In theory wine itself should ask for much initialization anyway as it mainly forwards calls to the host.
I can only talk about my own experiences. In Ubuntu it takes about 10 seconds to load on first usage. This is on a Pentium M, 1.7ghz laptop. I've used Wine on lighter distros such as Puppy Linux (on various machines), and it didn't seem much better. Once loaded it does start apps pretty quickly, I just get the delay while Wine first loads (on a fresh Linux boot).
JayFoxRox said:No, wine+linux is not slower than windows. On my old PC it's faster in nearly every case. I didn't test it on my new PC but would expect similar results as this is what I often hear. Only some things which are not optimized yet or more complex things are slower. However, especially older games are usually way faster in wine than on windows.
Not sure about the winamp problem, but it might even be a problem with the window manager, not wine directly.
I'd love to use whatever version of Wine you have. It's always been slower for me! Am I doing something wrong?
No, I think the bug is well known about. I recall reading about it on the Wine buglist not that long ago. People were recommending a more modern Winamp (version 5). In the old version of Winamp, you have to move the window extremely slowly, or it flies out of the viewable screen area!
JayFoxRox said:Qemu was designed for simplicity (at least I found an PDF claiming that) and portability. Qemu was not really designed for x86 to x86 tho. I would assume Qemu does the full thing while VirtualBox takes some optimized route.
Okay, but that doesn't make sense to me. Is there some delay when the program looks at an x86 instruction, and then simply executes that instruction? Does the analysis cause a delay?
Last edited by a moderator: