At first I thought the problem was that I was using gcc-4, so I installed gcc-3.4.6, but I still get the same errors:gcc-3.4 -Wall -O2 -g -fno-strict-aliasing -I. -I.. -I/tmp/qemu-0.8.1/target-i386 -I/tmp/qemu-0.8.1
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/tmp/qemu-0.8.1/fpu
On 8/24/05, Francois Rioux [EMAIL PROTECTED] wrote:
What I manage to do with a certain success is to map network shares of the
host in the guest (net use z: 10.0.2.2\MyShare in the guest). I can browse
and read files from the mapped drive. However I can't write to it from the
guest. I
My own experience is the effect of these types of optimizations is
usually negligible, although it is still the first thing I do when
optimizing a program. The main improvement I find is reducing the
time required to initialize variables and improved code readability.
If you know values are
On Wed, Aug 24, 2005 at 02:41:44PM +0100, Paul Brook wrote:
Probably more important is to make sure none constant data structures
are done on the stack. There is no good reason why any code page
should be read-write.
Huh? this is nonsense.
I stand corrected, I ment to say on the
If you are running Linux under Windows, I highly recommend using
coLinux. It is more of a pain to initially configure, but once it is
the code runs just as fast as with a native Linux boot. Maybe
someday, someone will merge the front ends to these two entirely
different programs...
If anyone
In your original message, you mentioned setup had finished. One thing
I can recommend trying on your second attempt is to make sure you
create more than one user account when prompted. XP Pro seems to
behave differently depending on if there is one or more than one
accounts.
I actually had the
Just out of curiousity, I verified Norton Ghost Floppies still produce
the same error. I was hoping the patch I saw a few weeks ago to allow
self modifing x86 code would fix the problem...
Bill
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
I don't have any actual benchmarks, but it is definitely much faster
than under Windows with kqemu. Under XP Pro windows are opening about
4 times faster... Note that there appears to be a few new bugs in the
emulation. First off, I could not get Explore.exe to finish
initializing in default
Yes, it definitely acts like a stuck key. But none of the pressing
none of the keys on my keyboard relieves the problem. Only restarting
the QEMU virtual machine. However, I
did figure out 90% of the time the problem occurs because I press the
windows key to switch tasks. If I remember to
On 6/30/05, Doctor Bill [EMAIL PROTECTED] wrote:
The first problem I noticed is that with the 0.70 version, keys are
not mapped correctly. For example, if I try to type in a URL as soon
as I press the letter e explorer opens. As soon as I type the letter
m, the window minimizes I
10 matches
Mail list logo
