Jim Freeman writes:
> 
> The analysis should enumerate the steps taken to make the
> determinations (so I can vicariously dip my toe into WINE
> internals and tools).
> 

No carefull analysis here:

1. Setup needs additional Registry entry
   Beside the values in our winedefaults.reg, the setup of
   PafSetup.exe needs
 [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion]
 "ProgramFilesDir"="C:\Program Files"
+"CommonFilesDir"="C:\Program Files\Common Files"

Patch sended to wine-patches...

2. Probably inter-process messaging needed

At present, the address space separated processes can't communicate
with each other. PafSetup.exe seems to rely on it.

3. Probably CREATE_NEW_CONSOLE flag handling in CreateProcess needed:

Call kernel32.171: CreateProcessA(00000000,4041b328 
"D:\\COMM~CP1\\INST~JM1\\ENGINE\\6\\INTE~MEX\\IKERNEL.EXE 
-Embedding",00000000,00000000,000000
00,00000010,00000000,00000000,40725db4,4072608c) ret=7ff9025c fs=008f
fixme:module:CreateProcessA (D:\common files\InstallShield\engine\6\Intel 
32\IKernel.exe,...): CREATE_NEW_CONSOLE ignored
fixme:module:CreateProcessA (D:\common files\InstallShield\engine\6\Intel 
32\IKernel.exe,...): lpStartupInfo->lpTitle D:\COMM~CP1\INST~JM1\ENGINE\
6\INTE~MEX\IKERNEL.EXE ignored

1 is easy, 2 and 3 are showstoppers for some time.

Bye

Uwe Bonnes                [EMAIL PROTECTED]

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Reply via email to