Results 1 to 12 of 12

Thread: RegSvr32 Problem

  1. #1

    Thread Starter
    Hyperactive Member GlenW's Avatar
    Join Date
    Nov 2001
    Location
    Gateshead, England
    Posts
    479

    RegSvr32 Problem

    I need to register a Dll but keep getting this message from RegSvr32.
    Any ideas?
    Attached Images Attached Images  

  2. #2
    Try starting Windows in Safe Mode and doing it again.

  3. #3

    Thread Starter
    Hyperactive Member GlenW's Avatar
    Join Date
    Nov 2001
    Location
    Gateshead, England
    Posts
    479
    Originally posted by filburt1
    Try starting Windows in Safe Mode and doing it again.
    Tried it, no joy.

  4. #4
    Frenzied Member vbgladiator's Avatar
    Join Date
    May 2001
    Posts
    1,950
    The computer where you're trying to register the DLL might not have all of the DLL's dependancies. Make sure that whatever the DLL references is present on the computer you're trying to register it on.

  5. #5
    Junior Member
    Join Date
    Sep 2000
    Location
    Texas
    Posts
    29
    "The computer where you're trying to register the DLL might not have all of the DLL's dependancies. Make sure that whatever the DLL references is present on the computer you're trying to register it on."

    -- Also make sure that the pathing to the dependancies is set as well.

  6. #6

    Thread Starter
    Hyperactive Member GlenW's Avatar
    Join Date
    Nov 2001
    Location
    Gateshead, England
    Posts
    479
    Originally posted by vbgladiator
    The computer where you're trying to register the DLL might not have all of the DLL's dependancies. Make sure that whatever the DLL references is present on the computer you're trying to register it on.
    How do I do that?

  7. #7
    old fart Frans C's Avatar
    Join Date
    Oct 1999
    Location
    the Netherlands
    Posts
    2,926
    If the dll doen't have a DLLRegisterServer entry point, it is probably not a COM dll. Only COM dll's need to be registered.
    Other DLL's must be placed in a location in the PATH environment variable. Mostly the system/system32 directory is used.

    Oh, and it is definitely not a dependency problem. You would have got a different error message for that.

  8. #8

    Thread Starter
    Hyperactive Member GlenW's Avatar
    Join Date
    Nov 2001
    Location
    Gateshead, England
    Posts
    479
    I can't even reference this .DLL from within VB6.

  9. #9
    PowerPoster
    Join Date
    Mar 2002
    Location
    UK
    Posts
    4,780
    It probly is not an active X dll then.

    You will need to call it with Knowning exactly the procedure names in it, like how you would use an API call.

  10. #10

    Thread Starter
    Hyperactive Member GlenW's Avatar
    Join Date
    Nov 2001
    Location
    Gateshead, England
    Posts
    479
    Originally posted by Grimfort
    It probly is not an active X dll then.

    You will need to call it with Knowning exactly the procedure names in it, like how you would use an API call.
    Would the functions need to be declared like an API function then?

  11. #11
    old fart Frans C's Avatar
    Join Date
    Oct 1999
    Location
    the Netherlands
    Posts
    2,926
    Yes, you will need to declare the functions, just like any other API call.

  12. #12
    Junior Member
    Join Date
    Sep 2000
    Location
    Texas
    Posts
    29
    How about some more info on the dll. What is it, did it come from a s/w package, is it custom, where did you get it...?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width