[Bug 30901] 32-bit services fail to run in 64-bit WINEPREFIX/shared wow64 (PunkBuster, SafeDisc, ...)

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=30901

--- Comment #11 from Nikolay Sivov <bunglehead at gmail.com> ---
(In reply to Anastasius Focht from comment #4)
> PnkBstrA/B/K.exe in syswow64 is by design due to wow64 filesystem
> redirection (this is where the 32-bit parts end up).
> The PunkBuster logfiles in "c:\windows\system\LogFiles\PunkBuster\*" are
> special.
> Folders like "LogFiles" are excluded from wow64 filesystem redirection (by
> design).

Is it actually installed in proper location on 64 bit setup?

> 
> When the service is created using CreateService() API, the request is
> handled by 64-bit services.exe which works on the 64-bit registry branch.
> Hence all registry entries related to PB services end in 64-bit registry
> while the 32-bit service executables live in redirected 32-bit folder
> (syswow64).

That's not how it works - 'Services' key is never redirected.

> Well you made the 32-bit executables "visible" for the 64-bit Service
> Control Manager by putting them in 64-bit system32 (64-bit WINEPREFIX).
> The services are of course started as 32-bit processes.

What I can think of is that server is supposed to expand ImagePath differently
depending on it being wow64 or 64bit service. I'll try to test with this tool
more.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.