GetProcessWindowStation

[Mathias Berchtold]

Hello ...

I get the following error when trying to run SmartFTP on Wine.

fixme:advapi:RevertToSelf (), stub
fixme:advapi:SetThreadToken ((nil), 0xa0): stub (NT impl. only)
fixme:win:GetProcessWindowStation (void): stub
fixme:win32:GetUserObjectInformationA (0x1 1 0x4078e8e4 12 0x4078e8d8),stub!

And afer that I get a Debug ASSERT from the Microsoft Visual C++ Library.

File: Allocate.cpp
Line: 108
Expression: bSuccess

I think the Assert is caused because of the missing function implementations.
Do you have any plans to implement them in the future?

Wine Information
================
wine --version
Wine 20031016

windows="win2k" ("win98" doesn't work because wine "ignores" the unicows.dll)

[AppDefaults\smartftp.exe\DllOverrides]
"ole32" = "native"
"oleaut32" = "native"
"rpcrt4" = "native"
"urlmon" = "native"
"comctl32" = "builtin"
"wininet" = "builtin"
"shdocvw" = "native"
"shlwapi" = "native"
"crypt32" = "native"
"mshtml" = "native"
"unicows" = "native"
"crypt32" = "native"
"cryptui" = "native"
"wintrust" = "native"

If you need the debug build of SmartFTP to test please contact me.

Thanks a lot
-Mat
SmartFTP.com

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of Alexandre Julliard
Sent: Mittwoch, 22. Oktober 2003 04:20
To: Vincent Béron
Cc: Wine devel
Subject: Re: Changes to kernel messages lang

Vincent Béron  writes:
> Attached program says so on W2K SP4. There's a message table in 
> kernel32 for 0x0000, for the others it returns NULL. Is that way to do 
> it different from yours?

Yes, FindResource with language 0 is going to return a resource in all sorts of cases, so it's not a good test. And actually if the resource was really NEUTRAL, then all your FindResource calls should have succeeded. The best way to find out is to dump the resource table of the dll, using something like winedump -x.

--
Alexandre Julliard
[e-mail]

[Mike Hearn]

These stubs are related to the NT security model. Try setting Wine to
emulate win98 for this code, maybe they will disappear. If the app still
asserts (likely) try a +relay trace to see what is going on just before
the crash.

thanks -mike

On Wed, 2003-10-22 at 03:51, Mathias Berchtold wrote:
> Hello ...
>
> I get the following error when trying to run SmartFTP on Wine.
>
> fixme:advapi:RevertToSelf (), stub
> fixme:advapi:SetThreadToken ((nil), 0xa0): stub (NT impl. only)
> fixme:win:GetProcessWindowStation (void): stub
> fixme:win32:GetUserObjectInformationA (0x1 1 0x4078e8e4 12 0x4078e8d8),stub!
>
> And afer that I get a Debug ASSERT from the Microsoft Visual C++ Library.
>
> File: Allocate.cpp
> Line: 108
> Expression: bSuccess
>
> I think the Assert is caused because of the missing function implementations.
> Do you have any plans to implement them in the future?
> Wine Information
>
> wine --version
> Wine 20031016
>
> windows="win2k" ("win98" doesn't work because wine "ignores" the unicows.dll)
>
> [AppDefaults\smartftp.exe\DllOverrides]
> "ole32" = "native"
> "oleaut32" = "native"
> "rpcrt4" = "native"
> "urlmon" = "native"
> "comctl32" = "builtin"
> "wininet" = "builtin"
> "shdocvw" = "native"
> "shlwapi" = "native"
> "crypt32" = "native"
> "mshtml" = "native"
> "unicows" = "native"
> "crypt32" = "native"
> "cryptui" = "native"
> "wintrust" = "native"
>
> If you need the debug build of SmartFTP to test please contact me.
>
> Thanks a lot
> -Mat
> SmartFTP.com
>
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of Alexandre Julliard
> Sent: Mittwoch, 22. Oktober 2003 04:20
> To: Vincent Béron
> Cc: Wine devel
> Subject: Re: Changes to kernel messages lang
>
> Vincent Béron  writes:
> > Attached program says so on W2K SP4. There's a message table in 
> > kernel32 for 0x0000, for the others it returns NULL. Is that way to do 
> > it different from yours?
>
> Yes, FindResource with language 0 is going to return a resource in all sorts of cases, so it's not a good test. And actually if the resource was really NEUTRAL, then all your FindResource calls should have succeeded. The best way to find out is to dump the resource table of the dll, using something like winedump -x.
>
> --
> Alexandre Julliard
> [e-mail]