Jump to content

ssjkakaroto

Members
  • Posts

    99
  • Joined

  • Last visited

Posts posted by ssjkakaroto

  1. Hi Daystrom M5, I found something about it, but I still don't know how to fix it. I already had the VB 6.0 runtimes installed.

     

    Run Time Error 438 - Object Doesn't Support this Property or Method

    The most common cause of error 438 is not maintaining binary compatibility between successive versions of your components. Each COM interface has an associated GUID that is called an interface ID (IID). Each coclass has an associated GUID that is called class ID (CLSID). When you compile an ActiveX component in Visual Basic, the CLSIDs and IIDs are compiled into the component's type library.

    Example

    A program that consists of a Visual Basic client and an ActiveX DLL is released to the user community. At a later time, additional functionality is to be added to the DLL component. The necessary modifications are made, and the ActiveX DLL is compiled without maintaining binary compatibility. When the DLL is released, the client that is trying to use the DLL will throw run time error 438. The reason this occurs is that when the DLL was compiled, a fresh set of GUIDs was compiled into the DLL, and the client has no reference to these new GUIDs. This is why it is important to maintain binary compatibility with the last-released version of the component when you are trying to release a newer version.

     

    Another example for the runtime error 438 would be including the wrong version of Microsoft Data Access Components (MDAC) in the distribution package. For example, a Visual Basic 6 Service Pack 5 program is built on Microsoft Windows 2000 Service Pack 2 by using the latest version of MDAC that is present (version 2.6). When the distribution is built, an earlier version of MDAC (version 2.5) is used (unless MDAC 2.6 is downloaded), causing an error 438 to be thrown when the distributed program is run.

     

    Another scenario would be misspelled method or property names, and this scenario is described in the following Microsoft Knowledge Base article:

     

    This may be as simple as adding a reference for the ActiveX data Access Object that the older Access database would have used created.

    For instance if you are now using Excel 2003 as a database with ADO2.8 library and the Access records were created using ADO2.4 (as an example). The differences within the newer library may not be supported.

    By adding a reference to the older ADO dll that the Access database used to create the records this may fix the issue.

  2. Hi Daystrom M5, I'm trying to run BurnPlot through wine and I get the following error:

     

    fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)

    err:ole:ITypeInfo_fnInvoke did not find member id 0, flags 0x2!

    fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}

    fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}

    fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}

    fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}

    fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}

    fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}

    fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}

    fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for c0000109

     

    Also the attached error.

     

    Do you know what runtimes I might be missing?

    post-1457-125987476377.png

  3. Hi LUK, I just found a bug you reported about Imgburn 2.5.0.0 crashing under Wine when closing (http://bugs.winehq.org/show_bug.cgi?id=19839).

    That bug was "fixed" in version 1.1.29.

    I just did a fresh install of Ubuntu 9.10 and Wine 1.1.33 (x64) but Imgburn was crashing when I closed it. I didn't even had to go to the 'Disc Layout Editor', just opening and then closing was enough for it to crash. I saw that someone installed comctl32 to fix the issue, so I used winetricks to install comctl32 and comctl32.ocx and the problem was gone indeed.

     

    Maybe you could ask for the Wine devs to reopen that bug as it came back with the latest version.

     

    Best regards

  4. I don't remember getting any "cute" error messages from Imgburn, quite the contrary in fact.

    Also, all errors, almost in raw format (what the burner outputs), can be found in the log and can be used for debugging.

    Maybe what you want is to disable error messages completely and just have the log?

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.