Registering VB4 OCX's in XP?

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Cookie
    #1

    Registering VB4 OCX's in XP?

    I have a program that requires these OCX's and DLL's:
    COMDLG16.OCX, THREED16.OCX, OC25.DLL, VB40016.DLL
    These are all in the programs path.

    Program is written in VB 4.0
    Program must be runned on XP Home Edition.

    When starting the application it gives the error:
    Can't load (or register) custom control: "COMDLG16.O CX"

    When I try \path\regsrv32 \programpath\CO MDLG16.OCX
    XP gives me this error:
    The file "COMDLG16.O CX" is not an executable file and there is
    no registration-helper registered.
    (this is translated from dutch)
    Same error if I try unregister the OCX (regsrv32 -u)

    How can I solve this?
    Thanks

    Cookie
    --
    \|||/
    (. .)
    *--------ooO-(_)-Ooo--------*
    | |
    | cookie@yucom.be |
    | |
    *---------------------------*

    Tags: threed16.ocx
    • Stephane Richard
      #2
      Re: Registering VB4 OCX's in XP?

      unfortunately there's no miracle solution...
      vb4 came in 16 and 32 bits...if you're not using third party controls you
      should be able to bring your 16 bit project to 32 bits and then you should
      be able to register your OCX's in XP....XP and 16 bits is a bad idea to
      begin with :-).

      Once converted to 32 bits, things should go smoothly.
      --
      Stéphane Richard
      Senior Software and Technology Supervisor
      http://www.totalweb-inc.com

      For all your hosting and related needs
      "Cookie" <cookie@yucom.b e> wrote in message
      news:3F507638.1 050808@yucom.be ...[color=blue]
      > I have a program that requires these OCX's and DLL's:
      > COMDLG16.OCX, THREED16.OCX, OC25.DLL, VB40016.DLL
      > These are all in the programs path.
      >
      > Program is written in VB 4.0
      > Program must be runned on XP Home Edition.
      >
      > When starting the application it gives the error:
      > Can't load (or register) custom control: "COMDLG16.O CX"
      >
      > When I try \path\regsrv32 \programpath\CO MDLG16.OCX
      > XP gives me this error:
      > The file "COMDLG16.O CX" is not an executable file and there is
      > no registration-helper registered.
      > (this is translated from dutch)
      > Same error if I try unregister the OCX (regsrv32 -u)
      >
      > How can I solve this?
      > Thanks
      >
      > Cookie
      > --
      > \|||/
      > (. .)
      > *--------ooO-(_)-Ooo--------*
      > | |
      > | cookie@yucom.be |
      > | |
      > *---------------------------*
      >[/color]


        Comment

        • Mike Curry
          #3
          Re: Registering VB4 OCX's in XP?

          Try using the 32 bit version of the ocx

          "Cookie" <cookie@yucom.b e> wrote in message
          news:3F507638.1 050808@yucom.be ...[color=blue]
          > I have a program that requires these OCX's and DLL's:
          > COMDLG16.OCX, THREED16.OCX, OC25.DLL, VB40016.DLL
          > These are all in the programs path.
          >
          > Program is written in VB 4.0
          > Program must be runned on XP Home Edition.
          >
          > When starting the application it gives the error:
          > Can't load (or register) custom control: "COMDLG16.O CX"
          >
          > When I try \path\regsrv32 \programpath\CO MDLG16.OCX
          > XP gives me this error:
          > The file "COMDLG16.O CX" is not an executable file and there is
          > no registration-helper registered.
          > (this is translated from dutch)
          > Same error if I try unregister the OCX (regsrv32 -u)
          >
          > How can I solve this?
          > Thanks
          >
          > Cookie
          > --
          > \|||/
          > (. .)
          > *--------ooO-(_)-Ooo--------*
          > | |
          > | cookie@yucom.be |
          > | |
          > *---------------------------*
          >[/color]


            Comment

            • Cookie
              #4
              Re: Registering VB4 OCX's in XP?

              Mike Curry wrote:[color=blue]
              > Try using the 32 bit version of the ocx[/color]

              doesn't help...
              BTW: it is solved already:
              I had to use regsrv16 instead of regsrv32
              .....doh...

              Cookie

              --
              \|||/
              (. .)
              *--------ooO-(_)-Ooo--------*
              | |
              | cookie@yucom.be |
              | |
              *---------------------------*

                Comment

                • Cookie
                  #5
                  Re: Registering VB4 OCX's in XP?

                  Stephane Richard wrote:[color=blue]
                  > unfortunately there's no miracle solution...
                  > vb4 came in 16 and 32 bits...if you're not using third party controls you
                  > should be able to bring your 16 bit project to 32 bits and then you should
                  > be able to register your OCX's in XP....XP and 16 bits is a bad idea to
                  > begin with :-).
                  >
                  > Once converted to 32 bits, things should go smoothly.[/color]

                  It's not my project so don't have to source to recompile...
                  It's solved by using regsrv16 instead of regsrv32
                  Thanks anyway...

                  --
                  \|||/
                  (. .)
                  *--------ooO-(_)-Ooo--------*
                  | |
                  | cookie@yucom.be |
                  | |
                  *---------------------------*

                    Comment

                    Previous template Next
                    Working...