It may work if the app would close 0,1,2 and reopen them
on standard handles
Do you mean StdHandles a la Windows? I'm not sure a GUI app
has them. Even if it had, there's no way to convert them
into libc handles or streams AFAIK.
a GUI app gets the std-handles its parent requires it to have.
th
Eric Pouech <[EMAIL PROTECTED]> writes:
>> The output redirection didn't work from a GUI app: the libc
>> streams weren't initialized and thus the output disappeared.
>> Wouldn't DETACHED_PROCESS result the same? It's not crucial
>> for winetest itself, but making it a console app helped
>> debug
The output redirection didn't work from a GUI app: the libc
streams weren't initialized and thus the output disappeared.
Wouldn't DETACHED_PROCESS result the same? It's not crucial
for winetest itself, but making it a console app helped
debugging tremendously.
I think the stream (handle) point of
On Wed, Apr 28, 2004 at 12:25:31PM +0200, Francois Gouget wrote:
> On Tue, 27 Apr 2004, Kevin Koltzau wrote:
> [...]
> > Under NT, services run under a dedicated window station separate from the
> > interactive
> > window station. It is not possible for them to create windows, as there is no
> >
Kevin Koltzau wrote:
If the service is flagged as interactive, everything acts normally
Except you can take control over the process, thus escalating priveleges.
MS's reply? "It's an application bug. Don't use interactive services".
With such a reply, you would really expect them not to ship
Kevin Koltzau wrote:
GINA runs on a completely dedicated, secure windows station, there are 2 such
window stations, the one displayed at login (which is also the one shown when you
hit ctrl-alt-del), the other is used by the screen saver
the only windows that can be displayed on these are generate
On Wednesday 28 April 2004 07:59 am, Shachar Shemesh wrote:
> First of all, we are talking about "non-interactive serivces" only.
Yes
> Actually, I think the user WILL see them if she presses "ctrl-alt-del".
> The GINA login window is one such window opened by a service, as well as
> that thing
On Wednesday 28 April 2004 06:25 am, Francois Gouget wrote:
> I don't think that it is correct to say that services cannot cerate
> windows. From what I remember from the time I wrote a service and how I
> read the information at the URLs you provided, what happens is that a
> service can create wi
Francois Gouget wrote:
On Tue, 27 Apr 2004, Kevin Koltzau wrote:
[...]
Under NT, services run under a dedicated window station separate from the interactive
window station. It is not possible for them to create windows, as there is no display or
user input associated with this windows station,
On Wednesday 28 April 2004 07:38 am, Jakob Eriksson wrote:
> What about "Allow service to interact with desktop" I have seen
> somewhere in Windows?
You run the service under the local system account and pass
SERVICE_INTERACTIVE_PROCESS for service type when
calling CreateService
On Tue, 27 Apr 2004, Kevin Koltzau wrote:
[...]
> Under NT, services run under a dedicated window station separate from the interactive
> window station. It is not possible for them to create windows, as there is no
> display or
> user input associated with this windows station, they can however h
On Tuesday 27 April 2004 08:57 pm, Chris Morgan wrote:
> When I was trying to run the winetests in gui mode they simply wouldn't run.
> Winetest would start but wouldn't spawn any of the subtests. Ferenc's
> winetest build with console windows worked much better. I don't have any
> idea why t
On Monday 26 April 2004 7:11 pm, Ferenc Wagner wrote:
> Eric Pouech <[EMAIL PROTECTED]> writes:
> > Ferenc Wagner a écrit :
> >> Eric Pouech <[EMAIL PROTECTED]> writes:
> The second part, yes. But winetest must have been made
> into a console app, so it pops up a console when it
> s
Eric Pouech <[EMAIL PROTECTED]> writes:
> Ferenc Wagner a écrit :
>
>> Eric Pouech <[EMAIL PROTECTED]> writes:
>>
The second part, yes. But winetest must have been made
into a console app, so it pops up a console when it
starts.
>>>
>>> why do you need a console?
>>
>> Er, I don't
Ferenc Wagner a écrit :
Eric Pouech <[EMAIL PROTECTED]> writes:
The second part, yes. But winetest must have been made
into a console app, so it pops up a console when it
starts.
why do you need a console?
Er, I don't know. Winetest itself doesn't really need it,
but WinRash (the service) cou
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
Ferenc Wagner wrote:
Eric Pouech <[EMAIL PROTECTED]> writes:
The second part, yes. But winetest must have been made
into a console app, so it pops up a console when it
starts.
why do you need a console?
Er, I don't know. Winetest itself doesn't really need it,
but WinRash (the se
On Wednesday 21 April 2004 06:07 pm, Ferenc Wagner wrote:
> Er, I don't know. Winetest itself doesn't really need it,
> but WinRash (the service) couldn't execute it otherwise. We
> don't understand this. Apart from this, winetest has
> console mode, when it doesn't display a gui but logs into
>
Eric Pouech <[EMAIL PROTECTED]> writes:
>> The second part, yes. But winetest must have been made
>> into a console app, so it pops up a console when it
>> starts.
>
> why do you need a console?
Er, I don't know. Winetest itself doesn't really need it,
but WinRash (the service) couldn't execute
Henk Poley <[EMAIL PROTECTED]> writes:
> Ferenc Wagner wrote:
>
>> Henk Poley <[EMAIL PROTECTED]> writes:
>>
>>> Dimitrie O. Paun wrote:
>>>
Can you please run this .exe on your Windows box:
http://afavant.elte.hu/~wferi/wine/winetest.exe
We are trying to test the winetes
The second part, yes. But winetest must have been made into
a console app, so it pops up a console when it starts.
why do you need a console ?
either you don't care about the output to the console, or you do care
but you've already redirected the output to a log file
so, passing DETACHED_PROCES
Ferenc Wagner wrote:
> Henk Poley <[EMAIL PROTECTED]> writes:
>
>> Dimitrie O. Paun wrote:
>>
>>> Can you please run this .exe on your Windows box:
>>> http://afavant.elte.hu/~wferi/wine/winetest.exe
>>>
>>> We are trying to test the winetest infrastructure.
>>
>> On my (dutch) Windows 98 SE
On April 20, 2004 5:32 pm, Ferenc Wagner wrote:
> kernel32:file leaves a temp file behind
> kernel32:pipe loops forever on Win9x/Me (not included in my
> version of winetest)
> oleaut32:vartest takes too long to complete
> user32:dialog tends to hose Win9x
>
Ferenc Wagner wrote:
Jakob Eriksson <[EMAIL PROTECTED]> writes:
And then winetest.exe can no longer pop up little dialogs
everywhen there is a timeout, that would kind of defeat
the purpose of having a service in the first place...
Winetest's main purpose isn't harassing nice users with
p
Ferenc Wagner wrote:
Thanks everybody for helping us testing this thing! There
is more to come: a program running as a Windows service in
the background, downloading and running new versions of
winetest as they come out: WinRash! Watch this place! :)
And then winetest.exe can no longer pop up
Jakob Eriksson <[EMAIL PROTECTED]> writes:
> Ferenc Wagner wrote:
>
>>Thanks everybody for helping us testing this thing! There
>>is more to come: a program running as a Windows service in
>>the background, downloading and running new versions of
>>winetest as they come out: WinRash! Watch this
Henk Poley <[EMAIL PROTECTED]> writes:
> Dimitrie O. Paun wrote:
>
>> Can you please run this .exe on your Windows box:
>> http://afavant.elte.hu/~wferi/wine/winetest.exe
>>
>> We are trying to test the winetest infrastructure.
>
> On my (dutch) Windows 98 SE Lite (see www.litepc.net)
> insta
Dimitrie O. Paun wrote:
> Can you please run this .exe on your Windows box:
> http://afavant.elte.hu/~wferi/wine/winetest.exe
>
> We are trying to test the winetest infrastructure.
On my (dutch) Windows 98 SE Lite (see www.litepc.net) install it needed
quite a lot of user interaction. In the
> 5. the icon of "winetest.exe" has a dark background, is it on purpose ?
> (my video card is configured to 16 bits/pixel)
It looks here like the background is the 'inverse' colour (invert the
underlying colour) -- in the app's title bar it shows up as a pale yellow
background, but on the taskbar
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> On Tue, 20 Apr 2004, Mehmet YASAR wrote:
>
>> 5. the icon of "winetest.exe" has a dark background, is
>> it on purpose ? (my video card is configured to 16
>> bits/pixel)
>
> Hmmm. Feri?
That icon behaves pretty strange: it has a transparent
back
Eric Pouech <[EMAIL PROTECTED]> writes:
>>> 2. With the GUI, a shell is created (it should display
>>> debug traces ??) but I see only some weird caracters
>>> like "abcdf g" and one line : "tests/process.c: 6 tests
>>> executed, 0 marked as todo, 0 failures.??"
>>
>> That's expected. Windows jus
On Tue, 20 Apr 2004, Mehmet YASAR wrote:
> Test run on Win2K sp4 (French)
>
> 1. I have a error with comctrl32_test.exe (it's seems to occur during
> extraction).
> Translated from french : "Can't find PDA_Search entry point in
> COMCTL32.DLL" (I have version 5.81.4916.400)
Yes, expected.
> 2
On Tue, 20 Apr 2004, Ferenc Wagner wrote:
> Mehmet YASAR <[EMAIL PROTECTED]> writes:
> > 1. I have a error with comctrl32_test.exe
>
> That's probably due to my old MinGW, newer versions
> hopefully won't produce this. Can anybody confirm this?
You could try with the auto-built versions here:
2. With the GUI, a shell is created (it should display
debug traces ??) but I see only some weird caracters like
"abcdf g" and one line : "tests/process.c: 6 tests
executed, 0 marked as todo, 0 failures.??"
That's expected. Windows just can't do without this. :(
I'd say it's part of kernel32 tes
Mehmet YASAR <[EMAIL PROTECTED]> writes:
> 1. I have a error with comctrl32_test.exe (it's seems to
> occur during extraction). Translated from french : "Can't
> find PDA_Search entry point in COMCTL32.DLL" (I have
> version 5.81.4916.400)
That's probably due to my old MinGW, newer versions
hope
> 4. Programme stops on "user32:input" (the progressbar is at about 90%)
Sorry, I made a mistake.
I thought tests stopped on "user32:input" whereas there were running.
After waiting I see a timeout error and a dialog box asking to send data
to server.
Test run on Win2K sp4 (French)
1. I have a error with comctrl32_test.exe (it's seems to occur during
extraction).
Translated from french : "Can't find PDA_Search entry point in
COMCTL32.DLL" (I have version 5.81.4916.400)
2. With the GUI, a shell is created (it should display debug traces ??)
Just tried this on win98, XP and Win2k3
On win98 it totally locks my system up on user32:dialog
On Tuesday 20 April 2004 01:01 pm, Dimitrie O. Paun wrote:
> Folks,
>
> Can you please run this .exe on your Windows box:
> http://afavant.elte.hu/~wferi/wine/winetest.exe
>
> We are trying to tes
Folks,
Can you please run this .exe on your Windows box:
http://afavant.elte.hu/~wferi/wine/winetest.exe
We are trying to test the winetest infrastructure.
TIA!
--
Dimi.
39 matches
Mail list logo
