Am Samstag, 24. April 2004 00:54 schrieb Jakob Eriksson:
> From a run of winetest 20040423 on Windows XP:
>
> file.c:1075: Test failed: mapping should succeed
> file.c:1077: Test failed: can't close mapping handle
> file: 487696 tests executed, 0 marked as todo, 2 fai
On April 23, 2004 10:01 pm, Ferenc Wagner wrote:
> Yes, I think it's a valid concern. I can implement an
> option in winetest to dump the build info or whatever; this
> way a upx-packed .exe could serve well while being totally
> transparent.
I think it's a valid thing as well, but please let's w
On April 23, 2004 9:55 pm, Ferenc Wagner wrote:
> That's clear. What about stuffing all this info into the
> Tag dashes and dots are allowed in there.
In effect yes, but this is an implementation detail, we should
do it internally on the server side, not expose it outside.
The format shouldn't n
Jakob Eriksson <[EMAIL PROTECTED]> writes:
> Dimitrie O. Paun wrote:
>
>> 2. Uploading to SF
>> This works nice now, but I'm afraid it may not when we
>> have more than one person doing it. Namely, a release
>> needs to be created, will that not fail if it already
>> exists? Can w
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> On Fri, 23 Apr 2004, Ferenc Wagner wrote:
>
>> "Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
>>
>>> For a given BUILD_ID, we can have reports comming from
>>> different builds now, that is from different winetest-*.exe.
>>> That means a much of U
Brian Vincent wrote:
I didn't add in a formal method for doing this, but what we have right
now is pretty much two different scenarios:
1) winrash client has never downloaded a test.
- so we send them every winetest we have
2) winrash client has downloaded a winetest
- we send them only the mo
As it was written in the Book of Jakob Eriksson <[EMAIL PROTECTED]>:
> I don't understand any of this and it worries me.
It's ok, really ;)
> Do you mean separate tests, like "kernel32_crosstest.exe", or do you mean
> "winetest.exe"?
The two examples I listed are the only two things we support r
"chris", case sensitive
2) If you stick an exe in a zip file, it must have the same filename as the
.zip, just with an exe extension. So,
winetest-20040423-0859-blah.zip must contain winetest-20040423-0859-blah.exe
> We can have different distribution policies: pick
> a ra
Okay, but am I missing the point? winetest.exe is already
self-extracting in itself...
regards,
Jakob
[EMAIL PROTECTED] wrote:
Lately I've been doing a lot of installer building with the NSIS
installer(http://nsis.sf.net). We could easily package winetest as a
self-extracting and executing
Lately I've been doing a lot of installer building with the NSIS
installer(http://nsis.sf.net). We could easily package winetest as a self-extracting
and executing installer that was transparent to the user. The installer would simply
extract the actual winetest.exe to windows/temp, start it u
Found some additional tidbits of info on "David" scattered among the
following:
http://www.linuxelectrons.com/article.php/20040421225912693
http://www.mb.com.ph/INFO200404207565.html
http://sg.biz.yahoo.com/040422/15/3joiz.html
http://www.linuxworld.com/story/44568.htm
http://www.desktoplinux
Tim Hentenaar wrote:
On Fri, 23 Apr 2004 11:53:40 -0500
"R.U. Deranged" <[EMAIL PROTECTED]> wrote:
The article states "David" is currently 80 MB. Anyone care to wager on how
much of that is Wine code? Their developers sure have been busy...
Yeah, I can almost predict that it will be at
Dimitrie O. Paun wrote:
2. Uploading to SF
This works nice now, but I'm afraid it may not when we
have more than one person doing it. Namely, a release
needs to be created, will that not fail if it already
exists? Can we check that? If that's a problem, how are
we going to dea
Hello,
The following change makes the google page unavailable here. why would you
change it since it still works ?
Patch: http://cvs.winehq.org/patch.py?id=12121
Old revision New revision Changes Path
1.2 1.3 +1 -1 lostwages/news/2004040701.xml
-(23 April 200
On Friday 23 April 2004 10:55 am, Dimitrie O. Paun wrote:
> 1. Build Info
> Feri want to move that in the resources, with good
> reason. This will probably affect you very little,
> but needs to be done. We can still keep it in the .zip
> file (it is tiny) as it's a lot easier
On Friday 23 April 2004 1:17 pm, Joel Konkle-Parker wrote:
> Did the demo happen? What was the outcome?
Unknown. I'm still scanning for any word on that.
In the meantime, here's some more info I dug up:
http://www.theinquirer.net/?article=15496
http://www.cxotoday.com/cxo/jsp/
index.jsp?section
R.U. Deranged wrote:
I'd also like to respond, as if their BS actually needs to be taken seriously,
that I have personally never had a Win32 application under Wine crash my
Linux kernel, nor have I experienced a Blue Screen of Death while running an
application under Wine. For me, that pretty mu
On Fri, 23 Apr 2004 11:53:40 -0500
"R.U. Deranged" <[EMAIL PROTECTED]> wrote:
>
> The article states "David" is currently 80 MB. Anyone care to wager on how
> much of that is Wine code? Their developers sure have been busy...
>
Yeah, I can almost predict that it will be at least 75% Wine code
Chris McKenzie <[EMAIL PROTECTED]> writes:
> GetVolumeInformation's new implementation has 2 problems:
>
> 1. For software that was previously registered with a "made up" serial
> number via the "serial=" directive in the config file, the software (for
> me Altera MaxPlus) will no refuse to run cl
A story on this has finally hit the AP wire today:
http://story.news.yahoo.com/news?tmpl=story&cid=562&ncid=738&e=9&u=/
ap/20040423/ap_on_hi_te/philippines_linux
Unfortunately the reporter hasn't done his homework and is obviously ignorant
about running Windows application
The refers to the 2004-03-09 ChangeLog, specifically:
* dlls/kernel/Makefile.in, dlls/kernel/volume.c,
dlls/ntdll/file.c,
documentation/samples/config, documentation/wine.conf.man,
files/drive.c, include/drive.h, include/winnt.h:
Reimplemented GetVolumeInformati
R.U. Deranged wrote:
>
> On Thursday 22 April 2004 12:08 pm, Rein Klazes wrote:
>>
>> Somehow, we are doing something far to complicated:
>>
>> http://www.specopslabs.com/david.htm
>
> If you can pierce through all that marketing hype, it seems to indicate
> they're using some code from the Wine p
On Thu, 2004-04-22 at 20:12 +0100, Mike Hearn wrote:
> On Thu, 2004-04-22 at 14:38 -0400, Paul Davis wrote:
> > JACK runs on OS X (and is proving very popular there). It is written
> > in strict ANSI C and attempts to be strictly POSIX compatible. There
> > is an OSS-API driver enabling it to be us
As it was written in the Book of "Dimitrie O. Paun" <[EMAIL PROTECTED]>:
> B. Naming
> ---[-].
Good.
>
> C. Publishing
> After the files have been successfully uploaded to the
> server (for winetest, this will be sf.net), a publish
> event will be sent to WineHQ, w
Ferenc Wagner wrote:
> Henk Poley <[EMAIL PROTECTED]> writes:
>
>> The thing halted at the :input stuff (yes, I know, known
>> bug), so the report was never sent. I waited 15 minutes or
>> so, so the 2 minutes timout should have happened if it was
>> just 'stuck' somewhere.
>
> Now that's strange
On Fri, 2004-04-23 at 10:08, Dimitrie O. Paun wrote:
> So is the 'template/' namespace flat? That is, no matter in what subdir
> we place the file, we always access it as /site/{filename}?
No, subdirs are carried over. So if you put a file as:
templates/en/foo/bar.template
The website url would b
On Fri, 23 Apr 2004, Jeremy Newman wrote:
> 1. name the file {filename}.template
> 2. no need for , , tags.
Just to clarify: we *shouldn't* have these.
> 3. the files would need to be copied into the templates/en
>subdir of the website.
> 4. the url would then be /site/{filename}
>
> I'd p
On Fri, 23 Apr 2004, Ferenc Wagner wrote:
> "Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
>
> > 1. Multiple builds
> >
> > For a given BUILD_ID, we can have reports comming from
> > different builds now, that is from different winetest-*.exe.
> > That means a much of URLs, etc.
>
> That's abus
Hi folks,
I've checked the build this morning on SF, and it looks
beautiful! So let's review the possible problems still
outstanding:
1. Build Info
Feri want to move that in the resources, with good
reason. This will probably affect you very little,
but needs to be done. We can s
On Thursday 22 April 2004 19:37, Alexandre Julliard wrote:
> > Alexandre, can we add this flag to our makefiles? If so,
> > I can produce a patch...
>
> No, I think it's better to avoid this. Our test environment is useful
> for testing not only Wine but also Mingw, we have already found a
> numb
On Fri, 2004-04-23 at 09:00, Dimitrie O. Paun wrote:
> Not a biggie, but maybe we can transform the generated report
> into a template so that it integrates nicely with the rest of
> the site (menu to the left, etc). Jer, what do we need to do
> to achive that? I think it should be very easy, but..
On Fri, 2004-04-23 at 09:30, Ferenc Wagner wrote:
> willing to change gather, but seems like Jer is bogged down
> too much...
Heh, just a tad. CodeWeavers is close to releasing it's next version of
CrossOver so we are all busy here. And on top of that, we are going to
be moving to a new office. So
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> 1. Multiple builds
>
> For a given BUILD_ID, we can have reports comming from
> different builds now, that is from different winetest-*.exe.
> That means a much of URLs, etc.
That's abuse. :) BUILD_ID is intended to identify winetest,
not Wine. W
Hi Feri,
Here is a list of things that I see as potential problems:
(I haven't checked the code, so they may already be handled)
1. Multiple builds
For a given BUILD_ID, we can have reports comming from
different builds now, that is from different winetest-*.exe.
That means a much of URLs, etc.
On Friday 23 April 2004 08:48 am, Ferenc Wagner wrote:
> Well, they already have to take care about the WINE_BUILD
> environmental variable. We could instead/also mandate the
> presence of script which is run by maketest and produces all
> the build information we need: tag, archive url and build
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> On April 22, 2004 8:38 pm, Ferenc Wagner wrote:
>
>> Why not to put this into a resource instead? I implemented
>> the URL option because I thought the permanent archive URL
>> may not be known at build time; it's surely not the case now.
>
> Yes,
On April 23, 2004 7:52 am, Paul Millar wrote:
> Please, could we all agree to use UTC? It is *the* universal timezone.
> Expressing time in any other tz always introduces the possibility of
> confusion.
Paul, sorry but there's no confusion. Let's not go back on that,
*that* would cause confusio
On Thu, 22 Apr 2004, Kevin Koltzau wrote:
> If we are always explicitly using EST, daylight savings will never
> affect it (its always UTC-5) as when in daylight savings,
> the timezone changes to EDT (which is UTC-4)
Please, could we all agree to use UTC? It is *the* universal timezone.
Expres
http://news.zdnet.co.uk/0,39020330,39152686,00.htm
At least they're honest about it - I especially love this quote:
In the commission's report, Contorer's email was also blunt about
Microsoft's shortcomings.
"It is this switching cost that has given the customers the patience to
stick with Win
On Thu, 22 Apr 2004 17:49:43 -0500, Ryan Underwood wrote:
> I have seen some mentions of work on DirectPlay. Who is currently
> working on this, and what are the implementation plans?
AFAIK nobody. I haven't seen any DirectPlay patches for ages. Not many
games use it.
> I am mainly curious if it
A couple of statements on their web site:
"One of the problems of the MS Windows OS is that it is subject to crash
applications and itself. While studying the Microsoft Windows OS, we
found the design flaw that causes this problem."
_the_ design flaw? Marketing hype. It seems from later state
And what about their claim that they will "incorporate the OS into a
browser", meaning that "an OS will become virtually useless?".
:-S.
Robert
42 matches
Mail list logo
