"U n d e r a c h i e v e r"
> I wanted to submit a new OS image (CentOS 4 on x86) to FreeOSZoo.org.
>
> I'm getting taken to what looks like a search or cyber-squatter's site.
> Any idea what's up?
They were unable to transfer domain ownership to the new host. And since it
wasn't renewed, it ex
"Herbert Poetzl"
>> Some, such as myself, still use 800x600. I do it out of necessity. I
>> have
>> poor eyesight and don't have the spare cash (or desk space!) for a 21
>> inch
>> monitor. And LCD monitors tend to have too high a native resolution.
>> With
>> my current 17" monitor, I simply c
"Jim C. Brown"
>> Or the same size. Don't forget, Windows XP will cover up part of the
>> window
>> even when the GTK version switches to 'full screen'.
>
> This is easily worked around by activiating the auto-hide feature of the
> taskbar.
Kludge.
You should *never* have to modify your host f
"Jim C. Brown"
>I personally feel that a scrollable window is not very useful unless your
>host
> resolution is smaller than your guest resolution. Hard to see what the
> point is
Or the same size. Don't forget, Windows XP will cover up part of the window
even when the GTK version switches t
"Jim C. Brown"
>> Late last year, QEMU reworked the disk geometry, and that can confuse old
>> disk images. The images expect an old style and the newer qemu offers a
>> different geometry.
>
> No, the geometry reported by 0.7.0 (which sees the disk properly and can
> mount
> partition) and CVS (w
"Jm C. Brown"
>
> This should be fixed now. (At least, this now works in Windows 98 and XP.)
> I
> managed to combine the 3 separate mouse handlers into a single function as
> well,
> so there is less redundant code.
It does appear to be fixed.
> Also, I managed to get rid of the all of the GTK
Ouch!
Would it be a good idea to have it hosted on FreeOSZoo?
After all, he did originally set up one.
Maybe you could just move your backup there? (Assuming he's willing, etc.
He might not be, since it's a university server. You might not be allowed
access to it as admin, etc.)
I hope you
"John R. Hogerhuis"
>
> I can't say. But even if it were, I'd guess most here would rather work
> under Unix-like OS.
Undoubtably.
The Linux builders outnumber the Win builders by probably 50 to one. If not
more.
But I know from the effort I went through to get qemu to build under windows
th
"John R. Hogerhuis"
> BTW, one problem with WIndows is that QEMU developers do not have access
> to Windows licenses. Might be nice for non-programmers who want to
> contribute to donate old licensed copies of Windows for testing work.
Does the ReactOS build work well enough to do Mingw etc. deve
"Christian MICHON"
>untrue.
>http://www.microsoft.com/windowsserver2003/evaluation/trial/default.mspx
>
>that would give 6 months to complete development...
I think they did one of them for a year.
However, I doubt they'd appreciate you distributing anything of theirs...
Can ReactOS be used to
"Tero Kaarlela"
>I tried to boot linuxppc image from freeoszoo with QemuCVS. kernel
> boots ok but then I get errors that it cant read filesystem from dev hda.
>Also tried with 0.7.0 and it freezes at: Freeing unused kernel memory
What's the date of the disk image itself?
Late last year
"Jim C. Brown"
>
> Ok this is probably the final revision. I had the code vindicated by an
> actual
> Windows programmer. He says it should work fine. It should compile, run,
> and make
Okay... I compiled it and the keys do appear to work.
That problem does appear to be fixed.
It doesn't look
"Jim C. Brown"
> I must disagree here. If a user already has xchat 2 installed, and that
> person
> wants to try to use qemu with the GTK interface, they already have the
> libraries
> that they need.
>
> Including a set of GTK libraries just for qemu would not only be redundant
> in
> this cas
"Jim C. Brown"
> I disagree. I think distributing the GTK library with qemu (even for
> windows
> versions) is a very bad idea. At most, the qemu installer should just
> download
> and run the GTK installer. At most.
It's a very bad idea to have the installer need to go back on to the net to
do
"Jernej Simonèiè"
>Hmm, it's been a while since I last tried compiling Qemu, but maybe you'll
>need to edit the makefiles to actually include that flag.
That's what I did. He sent me the patch to do that.
It runs, but there are keyboard problems.
>> The gtk libraries are more than 6 meg and w
"Jernej Simonèiè" <[EMAIL PROTECTED]>
>> The unzip into the proper mingw directory structure.
>Did you unzip to /mingw or to /? If the latter, you'll probably have
Into the mingw directory.
That part seems to compile etc. It's the resulting program that is screwed
up some how.
>export CFLAG
> This is a particularly perplexing error, considering that a) this error
> should
> only show up if you 1) use a MSVC compiled GTK with a mingw/cygwin
> compiled
I downloaded the libraries and devel files from the link Jernej Simoncic
recommended. It does seem to be a main win gtk distrib loc
From: "Jernej Simonèiè"
>> No idea what it really means. Other than what it actually says.
>Do a export CFLAGS="$CFLAGS -mms-bitfields" before configuring and
>compiling
>any GTK+ program on Windows - the libraries are always built to be
>compatible with MSVC so that you can use 1 set of librar
"Jim C. Brown"
>> There's not much telling what is causing it to fail. Qemu seems rather
>> sensitive to the slightest change in build environment.
>
> Not the most reliable development environment.
No, it's not...
I think some of it is inherent in the GCC stuff. Others, just the general
buil
"Jim C. Brown"
Sorry I hadn't got back to you sooner, but I was busy Some good news...
Keep reading.
>> So I copied about 6 meg of library files to my qemu test directory.
>
> Strange. I'm not too familiar with the Windows equivulent of
> LD_LIBRARY_PATH.
MingW's MSYS is a seperate, isola
From: "Jim C. Brown"
> Minor changes to gtk2_send_mouse_move() for GTK 2.6
Under Windows with MingW & MSYS, I'm still getting the same compiler error
that I reported to you before.
Along with an assortment of warnings in the GDK stuff. Plus the usual qemu
warnings.
I'm still using the same s
From: "Jernej Simonèiè"
>> I'll have to hunt around. I'm not familiar with gtk2.
>http://www.gimp.org/win32/ has the development headers and libraries for
>GTK+ 2.4 and 2.6 (compiling GTK+ on Windows is a PITA).
Thanks for the link
It was starting to look a bit more complicated than I coul
"Jim C. Brown"
> They weren't committed to the CVS tree yet. You'll need to get it in patch
> form. I'm reattaching all the necessary patches and files here, so you can
> get
> it all in one place. (The .c files I've attached should be dropped in the
> main qemu
> directory).
Here are the steps
"Jim C. Brown"
>> I'm willing to do some testing. But you'll have to tell me how to do the
>> gtk2 interface under windows.
>>
>
> Well, you will need to apply the patches and compile from source yourself.
> Not to mention, you'll have to download the windows versions of the GTK2
> libraries
"Jim C. Brown"
>> Some of us do a bit more, by deliberately testing qemu with lots of
>> software, looking for bugs. And reporting bugs when they are found.
>
> If you really want a bug to be fixed badly, and you have no idea of how to
> fix
> it, what you need to do is contact the developer of
From: "Henrik Nordstrom"
>> The best that many can do is test qemu and report problems when they are
>> found.
>
> Then you have to accept that the developers do the best they can in their
> interest for the benefit of all.
Generally, the way open source works is that a bug that directly effect
"Henrik Nordstrom"
>> All us users can do is make a report and sit back and wait to see if
>> anything happens. Sometimes it can be a long wait.
>
> Or you could go the open-source approach and hire a developer (there is
That's more than a little extreme.
Frankly, it'd be a heck of a lot cheape
From: "Henrik Nordstrom" <[EMAIL PROTECTED]>
>> A points to note:
>>
>> It is free software, doesn't work for you, do not use it.
>
> I would put it in slightly different words:
>
> It's free software (as in free speech, not gratis), if it doesn't work for
> you fix it or have it fixed for you by
As near as I can tell, they haven't done a thing, and weren't the slightest
bit interested in the bug report.
They don't even seem to keep track of reported bugs. If a developer happens
to see a bug report about something he worked on, he might check into it.
But otherwise it gets forgotten in
>"Oliver Gerlich"
> Hi,
> maybe it's the same problem as mentioned here:
> http://lists.gnu.org/archive/html/qemu-devel/2005-06/msg00077.html
>
> Could you try the patch given there?
That's it. Thanks.
I don't always get all of the mailing list messages. (Of course, it's
better than my ISP's
I've been following the qemu-user's forum thread with CoMiKe describing how
to build qemu under windows with MingW. For those of us who don't use
Linux, the regular instructions are about as clear as mud.
CoMiKe's instructions are pretty good, and as soon as a few more people give
it a try and
Stefano;
Also, I see that you are doing the Windows daily cvs builds again!
That's good to see... Thanks Stefano. Thanks Ronald.
As for the forum...
Obviously there are still some issues (for example, language issues), but I
think most people will still prefer the qemu forum at
http://m2.d
From: "David Woodhouse"
> On Wed, 2005-05-18 at 21:48 +0100, Paul Brook wrote:
>> It's been said before that the long-term solution is to
>> [incrementally] remove dyngen altogether, and replace it with a
>> had-written code generator. I've discussed this in a bit more detail
>
> How feasible woul
>Why not choose QEMU + QVM86, The QVM86 do same thing with accelerator
>module, but it is Open Source Project.
Because at the moment, qvm86 doesn't work well. Still has bugs and
limitations. And it actually seems to be *slower* than qemu without it. Or
at least not much faster.
That's based
>euh... I only meant sharing my compiled version of qemu.
>Sorry it was interpreted wrongly. The offer still stands :)
I'm already using the latest FreeOSZoo windows build. There hasn't been any
patches posted since it was built.
___
Qemu-devel ma
I originally was creating a new hard drive image. (Actually, I was just
copying one I already had, but same result.) Plus in other tests before I
did the original post, I sometimes unpartitioned and repartitioned,
reformatted, etc. A variety.
Later, when I did the retests with bochs vs qemu,
44m, 2.88m, 820k, 1.72m and 1.68m and set the hardware type
accordingly at startup. (Again, I don't know what sizes the bios can
support.)
(Actually, if you check the disk sizes, you may have to allow a few k-bytes
either way, since some disk images may not be the exact byte size, even
t
Hetz;
Thanks for checking into this.
>partitions, format and boot the system) at http://bootdisk.com
I know that place well... I've downloaded all of the boot disks from there
and a few other places.
>All of the above OS's recognized the hard disk (although DOS 3.3
>recognized 32MB of it, if
I've been trying to install various old versions of DOS under Window's v0.70
of qemu from FreeOSZoo.
And since so few people appear to be using the Windows version, I've been
making a point to do as much testing as I can, with as wide a variety of
operating systems as I can find.
>From version
In a previous mesasge last weekend
http://marc.theaimsgroup.com/?l=qemu-devel&m=111523670008882&w=1
where I listed a number of problems with v0.70 (Windows build), some things
that did work right, and some suggestions, I'm going to have to retract the
part where I said freedos seems to work okay,
There is definetly a problem with the mailing list.
It's very slow, plus I'm not receiving all the messages.
There was a notice on the savanah web site (where qemu is officially hosted)
saying they were moving the mail server, but that was last weekend. It
should be done by now, so I don't kno
Now that FreeOSZoo finally has the 0.70 build (and will hopefully do regular
cvs builds again), I decided to test it.
1) a nonexistant cd image should give an error. It's easy to make a typo in
the monitor when doing a 'change cdrom' command. But qemu just quietly accepts
it.
2) qemu still
Thomas;
>> Unfortunately, there aren't too many disk imaging programs I'd recommend.
>> Both Norton Ghost (the old version) and DriveImage (the old version) have
>> problems.
>I agree here. Norton really seems like technology from the past (DOS,
>16bit mode etc).
I disagree about that part.
T
Ben;
> The rescue disks aren't an OEM copy of WinXP Home, they
> are a set of 6 CD's containing a very fixed version of
> Partition Quest's partition restorer. I went down into
Ahh...
Yeah, you got screwed.
I thought those kinds of practices went out with Win98.
But yeah, I guess some manufac
Ben;
>> > the bat files that manipulate this thing, and there is
>> > a bios checker to make sure that the bios of the laptop
>>
>> I'm pretty sure the 'bios checker' is probably checking for the digital
>> signature in the BIOS.
>
> It just looks for a string. You wanna see the bat files?
> I
Ben;
Hertz has alreadyc ommented a bit, but I thought I'd add a few thoughts.
> It dawned on me that I really hate the fact that I can't
> really install my HP restore CD's on anything but my
Welcome to Microsoft's grip on the world
I've never seen an HP restore cd, but if it's anything lik
All tests were made with the current cvs version 20050426 on freeoszoo.org
1) There is still the cdrom change problem. If you have an upgrade version of
Windows, this can bring the installation to a dead end. Sometimes the win
installer even locks up when it tries to access the just changed c
47 matches
Mail list logo
