Username:

Password:

Pages: [1]
  Print  
Author Topic: Hyper lobby  (Read 2037 times)
ODB_Stinger
Newbie
*
Offline Offline

Posts: 1


View Profile WWW
« on: June 13, 2007, 11:22:19 am »

I keep getting error 339 when I try to launch HL. I have tried to run as admin, and run in safe mode. Here is the post I put in Hyperfighter.sk. It is probably vista related but some people run it on vista. Can anyone help?


Run -time error "339":

Component "mswinsck.ocx' or one of its dependencies not correctly registered: a file is missing or invalid.

My system:

Make: HP a1483w

CPU: Athlon 64 X2 (T) 4200+ 2.2 GHz Socket 939
2000 MT/s (mega transfers/second)

Memory: 2 GB PC-3200 184 pin, DDR SDRAM

HDD: 250 GB SATA

Board: Asus A8N-LA

Video: Nvidia Gforce 6600 512MB PCI Express x16

OS: Windows Vista Home Premium 32Bit

Games: IL2

HL Version: 3.9.111

Internet Explorer version: 7

verinfo.txt file contens:

Win NT: 6.0.1770 -
hlpro.exe 3.9.0.111
aping.exe 1.0.0.18
dexec.exe 1.0.0.8
mswinsck.ocx 6.1.97.82
msvbvm60.dll 6.0.97.97
asycfilt.dll 6.0.6000.16386
comcat.dll 6.0.6000.16386
ctl3d.dll No Version Info available!
ctl3dnt.dll No Version Info available!
oleaut32.dll 6.0.6000.16386
olepro32.dll 6.0.6000.16386
stdole2.tlb 6.0.6000.16386

 
Logged

 
TX-CUDA
BLACK 8
TX-Member
Hero Member
*****
Offline Offline

Posts: 1730



View Profile
« Reply #1 on: June 13, 2007, 07:48:58 pm »

.....have you tried doing a Google search for mswinsck.ocx to see what it might be a component of? I just looked via Google and there are several links relating to this file missing condition. Might try looking at those as just glancing it appears that you can manually install the file yourself. I'm no expert but I have had luck in the past when confronted with missing files.REMEMBER: Always create a system restore point BEFORE you add anything like this just in case!!TX-CudaMinister of Information
Logged

TX-Cuda
Minister of Information
<img src="http://miniprofile.xfire.com/bg/bg/type/2/txcuda340.png" border=0>
TX-Rahman
BLACK 4
Administrator
Hero Member
*****
Offline Offline

Posts: 1715



View Profile WWW
« Reply #2 on: June 17, 2007, 10:51:41 pm »

That's the Microsoft Winsock which is tied to your network.  You may want to go into device manager and uninstall the network drivers then have the system redetect and reinstall.  This will reinstall and reregister your winsock drivers as well.Regards,TX-RahmanRegards,TX-Rahman"BLACK 4"
Logged

Regards,
TX-Rahman
"BLACK 4"
Pages: [1]
  Print  
 
Jump to: