Component responsible for PSSupportErrorInfo entry?

  • Thread starter Thread starter Eberhard Schefold
  • Start date Start date
E

Eberhard Schefold

There's a vital registry entry in XP as follows:

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{DF0B3D60-548F-101B-8E65-
08002B2BD119}]
@="PSSupportErrorInfo"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{DF0B3D60-548F-101B-8E65-
08002B2BD119}\InprocServer]
@="ole2disp.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{DF0B3D60-548F-101B-8E65-
08002B2BD119}\InprocServer32]
@="oleaut32.dll"

It is necessary for proper marshaling of the ISupportErrorInfo interface.
Without it, COM clients erroneously discard valid IErrorInfo error
information because the QueryInterface for ISupportErrorInfo fails. Thus,
applications show different behaviour under XPE, namely they don't show
important error information which is transmitted via IErrorInfo.

Which XPE component is responsible for this entry? I've selected everything
that seems remotely involved but cannot find it.
 
Will the purpose of making these entries explicitely fed into the
registry via Component solve the purpose rather than having the
component itself coz' from your issue I guess that just having this
entry would facilitate the Query Interface !!!
In tat case proably you might need old2disp.dll in your runtime
registered.I dont think the Repository got this file,however the XP
Pro includes.

Regards,
Kesavan
 
Kesavan schrieb/wrote:
Will the purpose of making these entries explicitely fed into the
registry via Component solve the purpose rather than having the
component itself coz' from your issue I guess that just having this
entry would facilitate the Query Interface !!!
Click to expand...

Thank you for your answer, but I'm not sure I understand. The registry entry
does in fact solve the problem, and of course I can think of a way to get it
onto the image by myself. However, the ISupportErrorInfo mechanism is
standard in COM, documented and recommended in MSDN. Many, if not most
applications that use COM also use this mechanism. Therefore, there must be a
standard way to enable ISupportErrorInfo, a way that is intended by the XPE
developers. They could do it either as an explicit registry entry in some
component, or implicitly by registering a COM server file that is included
with a component. Either way there must be a ready-made TD component for
that, otherwise it would be a defect in XPE, right?
In tat case proably you might need old2disp.dll in your runtime
registered.I dont think the Repository got this file,however the XP
Pro includes.
Click to expand...

For 32 bit applications, oleaut32.dll would be responsible. It is available
as a TD primitive, however, registering it (regsvr32) does not set the key in
question.
 
Eberhard,

There is nothin' like for Xpe developers coz' you work on XP then it
should work in right there in XPE and if there is any prob' in
sumthin' missing in XPe as Slobodan suggested put it across to MS.

I guess the oleaut32 registering wont wrk .. u may need to see sum
previous postings that had similar issues .

Regards
Kesavan
 
Eberhard,

Since file old2disp.dll is missing in repository and it is pressent in
Windows XP Pro, then it is probably defect in XPe.
Missing registry keys or files should not suprise you when you deal with XP
Embedded.

You should report problems like this to MS, and this NG. And make fix
yourself, so MS can make some QFE to fix the problem later on.

Regards,
Slobodan
 
Slobodan Brcin schrieb/wrote:
Since file old2disp.dll is missing in repository and it is pressent in
Windows XP Pro, then it is probably defect in XPe.
Missing registry keys or files should not suprise you when you deal
with XP Embedded.

You should report problems like this to MS, and this NG. And make fix
yourself, so MS can make some QFE to fix the problem later on.
Click to expand...

Thank you both.

I'm probably just very dumb, but I didn't find a way to report an XPE
problem to Microsoft, apart from opening a support incident (I know that I
don't have to pay if MS acknowledges the problem as their own fault, but I
don't like the idea that this decision is at their own discretion.)

Have I overlooked a different possibility?
 
Back
Top