Re: Pipe names are case sensitive.

2005-04-19 Thread Robert Shearman
Alexandre Julliard wrote: It doesn't seem to me there is much to marshal in the OBJECT_ATTRIBUTES structure apart from the security descriptor, so I'm not sure what you plan to do. The useful fields are RootDirectory, ObjectName, Attributes (for the OBJ_INHERIT and OBJ_CASE_INSENSITIVE flags) and

Re: Pipe names are case sensitive.

2005-04-19 Thread Alexandre Julliard
Rob Shearman <[EMAIL PROTECTED]> writes: > I plan to address (1) with a rewrite of the way the OBJECT_ATTRIBUTES > structure is marshaled to the server. This will include making shared > marshaling, sizing, unmarshaling and freeing routines for the > structure and it contains the information about

Re: Pipe names are case sensitive.

2005-04-19 Thread Rob Shearman
Troy Rollo wrote: Pipe names are currently case sensitive. This affects instmsiw.exe since the service is created as "MSIService" and connected to as "MsiService". [a solution] would be to have find_object and create_object take a flag that forces case insensitivity even in a case sensitive nam

Re: Pipe names are case sensitive.

2005-04-18 Thread Troy Rollo
On Tue, 19 Apr 2005 16:20, Troy Rollo wrote: > I have insmsiw.exe from Office 2K working (at least to get as far as > installing Microsoft's version of MSI) with the patches I just sent through > to wine-patches, plus the hack below (which will also fix the problem for > other IPC objects). Correc

Pipe names are case sensitive.

2005-04-18 Thread Troy Rollo
Pipe names are currently case sensitive. This affects instmsiw.exe since the service is created as "MSIService" and connected to as "MsiService". The result is that instmsiw.exe always fails to query the service status. I have insmsiw.exe from Office 2K working (at least to get as far as instal