Post reply

Topic Summary

Posted by: KM

« on: July 10, 2006, 09:05:16 pm »

Insert Quote

i should hope it's not - as the patch doesn't use that filename

the one in the temporary directory, try renaming it (but should be safe to delete)... although in the temporary directory it shouldn't effect anything not run from the temporary directory

Posted by: SamSeeSam

« on: July 10, 2006, 06:44:38 pm »

Insert Quote

ws2_32.dll dated (5/11/98)
(7/9/06)

Windows first looks in the same folder for any dll's that any programs might need. If the DLL is not there then windows looks into the system directory for it. So that's why there are two ws2_32.dll's
the 98 one is the microsoft one adn the other one is KM's patch

Posted by: Reidh69

« on: July 10, 2006, 03:51:56 pm »

Insert Quote

Quote from: KM on July 10, 2006, 12:17:56 pm

it is something not related to the patch if disabling the patch didn't fix it, the next thing i would think is somethign else has replaced the ws2_32.dll file in the system directory, however i'm not sure of any program that would do that (as it is extremely bad practice, for the precise reason that it would break things)

first search your hard drive for any files named ws2_32.dll, you should only see the one in the system directory not any others so useful to check for that, then that one in the system directory should show in the file properties as being by microsoft

in theory literally any dll that winmx uses could have been tampered with by a program and cause that problem, but ws2_32.dll is the most likely one to check (if for no reason than the fact that if it isn't that one then there are a lot of places to look in...)

I have one ws2_32.dll dated (5/11/98) in the System folder and one dated (7/9/06) in the Temp folder.

Posted by: Reidh69

« on: July 10, 2006, 03:49:15 pm »

Insert Quote

Quote from: Bearded Blunder on July 10, 2006, 05:15:30 am

Have you run Windows Update & got all the critcal updates & patches? There are now a LOT for win98, it may be that one or other of them might resolve this issue..

I have done that...
I did it before downloading the latest WinMX+patch...

Posted by: KM

« on: July 10, 2006, 12:17:56 pm »

Insert Quote

it is something not related to the patch if disabling the patch didn't fix it, the next thing i would think is somethign else has replaced the ws2_32.dll file in the system directory, however i'm not sure of any program that would do that (as it is extremely bad practice, for the precise reason that it would break things)

first search your hard drive for any files named ws2_32.dll, you should only see the one in the system directory not any others so useful to check for that, then that one in the system directory should show in the file properties as being by microsoft

in theory literally any dll that winmx uses could have been tampered with by a program and cause that problem, but ws2_32.dll is the most likely one to check (if for no reason than the fact that if it isn't that one then there are a lot of places to look in...)

Posted by: Bearded Blunder

« on: July 10, 2006, 05:15:30 am »

Insert Quote

Have you run Windows Update & got all the critcal updates & patches? There are now a LOT for win98, it may be that one or other of them might resolve this issue..

Posted by: Maxe

« on: July 10, 2006, 01:42:26 am »

Insert Quote

Just a thought and I might be completely off track with this but could it be this user is using the same or similar program (PGP I think it was) that someone mentioned in the help room the other day. Apparently it locks down winsock and won't allow a replacement dll to take over.

Posted by: Reidh69

« on: July 09, 2006, 11:34:51 pm »

Insert Quote

failure to initialize winsock is still popping up.

Posted by: KM

« on: July 09, 2006, 11:09:55 pm »

Insert Quote

hmm, interesting... first time i've heard of that one, renaming it does mean it's something patch related (btw it won't connect, because you just disabled the patch... lol)

try installing winmx 3.53 (instead of 3.54) and putting this file in to the winmx directory, it's an alternate version of the patch but only works on 3.53

failing that the next thing to try would be 2.2, but that doesn't have the fake filtering...

Posted by: Reidh69

« on: July 09, 2006, 09:38:13 pm »

Insert Quote

it won't connect....? :roll:

Posted by: Reidh69

« on: July 09, 2006, 09:26:39 pm »

Insert Quote

I rename Oledlg.dll and it started up..
now waiting to connect..

Posted by: Reidh69

« on: July 09, 2006, 09:05:02 pm »

Insert Quote

no... I haven't..

no...

Posted by: KM

« on: July 09, 2006, 08:56:05 pm »

Insert Quote

did you try renaming oledlg.dll to something else? did it suddenly stop erroring?

Posted by: Reidh69

« on: July 09, 2006, 08:36:22 pm »

Insert Quote

no, I do not have any add-ons installed..
that is the only copy of winMX I have on my computer..

Posted by: Bearded Blunder

« on: July 09, 2006, 08:24:56 pm »

Insert Quote

You aren't trying to run with BendMX or other add ons installed are you? That's the only time I've seen that error with WinMX running under Win 98.

Also please check the properties of the shortcut you're using to start WinMX, use the "Find Target" button, it's not impossible to end up with 2 winmxprogram folders, please make sure you have the right one patched (ideally delete any spare ones too & start with a fresh clean install).