On Mi, 2010-02-17 at 11:15 +0100, Alexandre Julliard wrote:
Detlef Riekenberg <wine.dev(a)web.de> writes:
@@ -905,6 +905,7 @@ HKLM,%CurrentVersionNT%\Ports,"COM1:",2,"9600,n,8,1" HKLM,%CurrentVersionNT%\Ports,"COM2:",2,"9600,n,8,1" HKLM,%CurrentVersionNT%\Ports,"COM3:",2,"9600,n,8,1" HKLM,%CurrentVersionNT%\Ports,"COM4:",2,"9600,n,8,1" +HKLM,%CurrentVersionNT%\Print\Printers,"SymbolicLinkValue",0x60000,"\Registry\Machine\%Control%\Print\Printers"
It looks like it should be the other way around.
All current Code read and write to HKLM\System\CurrentControlSet\Control\Print\* When creating the registry symlink the other way around, how does it work with existing installations? I tested the other symlink: HKLM\System\CurrentControlSet\Control\Print\Printers has the magic entry (SymbolicLinkValue with REG_LINK) with (cannot display value) as data, but the link doesn't work. Creating the link target (HKLM\Software\Microsoft\Windows NT \CurrentVersion\Print\Printer) doesn't help. Deleting the current data followed by a "wineboot -u" doesn't help. -- By by ... Detlef