error 339

Which hub software is the best? Where can I find script XXX? Discuss it here...(no, this is not for advertising your hub...)

Moderator: Moderators

Locked
(420Matrix)(Neo)
Posts: 3
Joined: 2003-05-26 13:43
Location: USA
Contact:

error 339

Post by (420Matrix)(Neo) » 2003-05-27 11:32

When i try to run dc hub software it will not run the hub software it keeps telling me error 339 component DcSysTray.ocx or one of its dependicies is not correctly registered a file is missing or corrupt. NOW I HAVE tried uninstalling it reinstalling NMDC and then the hub software and still get the error 339 code im getting pissed off :x about this because for a whole year the program has always worked now suddenly it does not want to work anymore and that is Bullshit :evil: come on all you DC experts out there someone must know a way to correct this problem please help thanks in advance

TheParanoidOne
Forum Moderator
Posts: 1420
Joined: 2003-04-22 14:37

Post by TheParanoidOne » 2003-05-27 11:45

I have never used hub software and probably never will, but the frequency of this problem means that even I know the answer to this.

It has something to do with installing the client.

Use the Search feature with the ocx as the search term. Oh, and chill. Anger and frustration will get you nowhere.
The world is coming to an end. Please log off.

DC++ Guide | Words

GargoyleMT
DC++ Contributor
Posts: 3212
Joined: 2003-01-07 21:46
Location: .pa.us

Post by GargoyleMT » 2003-05-27 19:00

This is really a hub question *nudge, nudge* And this is really a problem for Jon Hess, since it's not related to DC++ at all :wink:


But anyhow. DcSysTray.ocx should be in your Windows directory (winnt or otherwise) in the System32 subdirectory. The following are the registry entries from my system in Regedit format:

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}]
@="SysTrayCtl.cSysTray"

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}\Control]
@=""

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}\Implemented Categories]

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}\Implemented Categories\{0DE86A52-2BAA-11CF-A229-00AA003D7352}]

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}\Implemented Categories\{0DE86A53-2BAA-11CF-A229-00AA003D7352}]

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}\Implemented Categories\{0DE86A57-2BAA-11CF-A229-00AA003D7352}]

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}\Implemented Categories\{40FC6ED4-2438-11CF-A3DB-080036F12502}]

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}\InprocServer32]
@="C:\\WINNT\\System32\\DCSysTray.ocx"

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}\MiscStatus]
@="0"

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}\MiscStatus\1]
@="148881"

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}\ProgID]
@="SysTrayCtl.cSysTray"

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}\ToolboxBitmap32]
@="C:\\WINNT\\System32\\DCSysTray.ocx, 30000"

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}\TypeLib]
@="{60CC5D62-2D08-11D0-BDBE-00AA00575603}"

[HKEY_CLASSES_ROOT\CLSID\{60CC5D60-2D08-11D0-BDBE-00AA00575603}\VERSION]
@="1.0"

[HKEY_CLASSES_ROOT\TypeLib\{60CC5D62-2D08-11D0-BDBE-00AA00575603}]

[HKEY_CLASSES_ROOT\TypeLib\{60CC5D62-2D08-11D0-BDBE-00AA00575603}\1.0]
@="System Tray Icon Control"

[HKEY_CLASSES_ROOT\TypeLib\{60CC5D62-2D08-11D0-BDBE-00AA00575603}\1.0\0]

[HKEY_CLASSES_ROOT\TypeLib\{60CC5D62-2D08-11D0-BDBE-00AA00575603}\1.0\0\win32]
@="C:\\WINNT\\System32\\DCSysTray.ocx"

[HKEY_CLASSES_ROOT\TypeLib\{60CC5D62-2D08-11D0-BDBE-00AA00575603}\1.0\FLAGS]
@="2"

[HKEY_CLASSES_ROOT\TypeLib\{60CC5D62-2D08-11D0-BDBE-00AA00575603}\1.0\HELPDIR]
@="C:\\WINNT\\System32"

Save them to a file with a .reg extension and import them.

Sidenote, you are running the setup as a user with Administrative rights, correct? That could be the source of your problem. Or not.

Note, this is Windows 2000 which has as different default windows directory than XP. Please correct the above paths before importing it into your system.

Paul_Don
Posts: 146
Joined: 2003-01-29 06:41
Location: uk
Contact:

Post by Paul_Don » 2003-05-27 21:03

or u could try installin nmdc client first then running the hub client

GargoyleMT
DC++ Contributor
Posts: 3212
Joined: 2003-01-07 21:46
Location: .pa.us

Re: error 339

Post by GargoyleMT » 2003-05-28 18:31

(420Matrix)(Neo) wrote:NOW I HAVE tried uninstalling it reinstalling NMDC and then the hub software and still get the error 339 code
I interpreted this line as meaning that he's uninstalled and reinstalled the Neo-Modus Client (as well as hub)... That's what I told him to do last time (and what past posters have said)... hopefully he's tried that. ;-) (And will follow up when he's got it resolved.)

Locked