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
On Tue, 14 Jun 2005 [EMAIL PROTECTED] wrote:
But it gets more than a little darn frustrating when you are enthused about
the project, you try to help the devlopers and project by deliberately doing
the testing to find bugs and problems, you report the bugs and problems.
And nothing happens.
On Tue, 14 Jun 2005 [EMAIL PROTECTED] wrote:
Seperate patches aren't necessarily the right thing to do
It is without question.
It really hurts a project in long term is if users by default run
something else than the main version.
A good way to help this area would be a compile farm d
On Wednesday, June 15, 2005, 1:02:45, [EMAIL PROTECTED] wrote:
> 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).
--
< Jernej Simoncic ><><><><>< http://deeptho
On Tue, Jun 14, 2005 at 01:51:10PM -0500, [EMAIL PROTECTED] wrote:
> 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 benef
"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
On Tue, Jun 14, 2005 at 04:15:41PM -0500, [EMAIL PROTECTED] wrote:
> "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 ha
"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
On Tue, Jun 14, 2005 at 12:14:05PM -0500, [EMAIL PROTECTED] wrote:
> Not all of us are developers.
>
> The best that many can do is test qemu and report problems when they are
> found.
>
> Some of us do a bit more, by deliberately testing qemu with lots of
> software, looking for bugs. And rep
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
On Tue, 14 Jun 2005 [EMAIL PROTECTED] wrote:
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 whatever means you find suitable.
If you do not want to have it fixed find an alternative which suits you
better.
Not all of us are dev
"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
On Mon, 13 Jun 2005 [EMAIL PROTECTED] wrote:
If a developer has a problem, then they can check into it themselves, of
course.
Yes.
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 approa
On Tue, 14 Jun 2005, Ishwar Rattan wrote:
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 whatever means
4, 2005 3:55 PM
> To: qemu-devel@nongnu.org
> Subject: Re: [Qemu-devel] Norton Ghost crashes with page
> fault for me too.
>
>
> If you are using
> Windows: Try qvm86 + qemu (there was an old build of these
> two in freeoszoo)
> Linux: Try kqemu + qemu
>
>
A points to note:
It is free software, doesn't work for you, do not use it.
-ishwar
On Mon, 13 Jun 2005 [EMAIL PROTECTED] wrote:
> As near as I can tell, they haven't done a thing, and weren't the slightest
> bit interested in the bug report.
___
Qe
If you are using
Windows: Try qvm86 + qemu (there was an old build of these two in freeoszoo)
Linux: Try kqemu + qemu
There are some problems that the combination of qemu + kqemu or qvm86
solve.
lefteris.
Jeff Wiegley wrote:
I noticed that one other person a long time back had
this same p
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
19 matches
Mail list logo
