[Bug 17161] New: Provide lodctr.exe tool to prevent misleading process spawn failure console messages (.NET installers)

http://bugs.winehq.org/show_bug.cgi?id=17161

Summary: Provide lodctr.exe tool to prevent misleading process
                    spawn failure console messages (.NET installers)
           Product: Wine
           Version: 1.1.13
          Platform: Other
               URL: http://www.microsoft.com/downloads/details.aspx?FamilyID
                    =262d25e3-f589-4842-8157-034d1e7cf3a3
        OS/Version: other
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Hello,

a minor nuisance that can be easily fixed...

I had to add notes to .NET Framework appdb entries because people wrote about
messages which looked like install errors to them.

--- snip ---
wine: could not load L"C:\windows\system32\lodctr.exe": Module not found
--- snip ---

Such failures are in fact harmless, not relevant to overall installer status.

"lodctr.exe" is a simple command line executable for loading performance data
into registry.
It is often called from .NET Framework v1.x, 2.x, 3.x installers.

MSDN info:

http://technet.microsoft.com/en-us/library/bb490926.aspx

http://msdn.microsoft.com/en-us/library/aa934371.aspx

--- quote ---
The loading function of lodctr, LoadPerfCounterTextStrings, is declared in
Loadperf.h and exported from Loadperf.dll. You can call this function directly
from your install program.

The following example shows the syntax for this function.

LONG LoadPerfCounterTextStrings(
LPSTR lpCommandLine, 
BOOL bQuietModeArg 
);

The lpCommandLine parameter is the name of your .ini file.

The bQuietModeArg parameter is a Boolean value that specifies whether to
display output during the loading of the text strings for the counter. 
--- quote ---

MSDN note suggests that this command line tool is only a thin wrapper which
simply calls LoadPerfCounterTextStrings() as workhorse, passing/forwarding the
command line as-is.

It should be easy to add this tool - even with LoadPerfCounterTextStringsA/W
being stubs - to silence installers which try to spawn it.

Typical installer logs:

--- snip ---
1: 0 2: C:\windows\system32\lodctr.exe
C:\windows\Microsoft.NET\Framework\v2.0.50727_Networkingperfcounters.ini;18;C:\windows\system32\
3:  4:  5:  6:  7:  8:  9:  10:  
Action 21:27:31: RunProcess. Installing Performance Counters for ".NET CLR
Networking"
...
--- snip ---

--- snip ---
...
1: 0 2: C:\windows\system32\lodctr.exe
"C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication
Foundation_TransactionBridgePerfCounters.ini";dummy;C:\windows\system32\ 3: 
4:  5:  6:  7:  8:  9:  10:  
1: C:\windows\system32\lodctr.exe
"C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication
Foundation_TransactionBridgePerfCounters.ini" 2:  
1: 0 2: C:\windows\system32\lodctr.exe
"C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication
Foundation_TransactionBridgePerfCounters.ini";dummy;C:\windows\system32\ 3: 
4:  5:  6:  7:  8:  9:  10:  
1: 0 2: C:\windows\system32\lodctr.exe
"C:\windows\Microsoft.NET\Framework\v3.0\Windows Communication
Foundation_TransactionBridgePerfCounters.ini";dummy;C:\windows\system32\ 3: 
4:  5:  6:  7:  8:  9:  10:  
...
--- snip ---

Regards