Do we have a Bug in XPE DirectX Script?
Line 1407 gives me a Regwrite error, guess caused by missing quotes.RegWrite,HKLM,0x3,"Tmp_software\Classes\DirectShow\MediaObjects\dafd8210-5711-4b91-9fe3-f75b7ae279bf","InputTypes","61,75,64,73,00....Should beRegWrite,HKLM,0x3,"Tmp_software\Classes\DirectShow\MediaObjects\dafd8210-5711-4b91-9fe3-f75b7ae279bf","InputTypes","61","75","64","73","00"....
Correct would be to remove all quotes. The single quotes around the single binary values are currently still tolerated by WinBuilder. But who knows how long ...
First some rules:
In most cases user violation of that rules are accepted by WinBuilder and processed as assumed.
- WinBuilder Script Line Parameters are separated by a comma.
If a comma is inside an argument, it must be 'escaped' by #$c- Besides some special cases (e.g. parameters in ShellExecute) generally enclosing quotes are not needed.
- Enclosing quotes MUST be used if the WinBuilder Script Line Parameters contain spaces
If the spaces are replaced by the escape #$s, the enclosing quotes should be ommitted.
E.g. unnecessary enclosing quotes or a comma inside an item enclosed by quotes.
But sometimes that can bring unexpected results.
Peter
BTW: The Magic Wand delivers:
RegWrite,HKLM,0x3,Section,Key(Binary),00,01,00Why so many people neglect this, use quotes and report an error, and somebody else 'fixes' the error by a new error, ...