WLM latest version sign in problem
 

Hi all

I have the latest WLM installed on the network slave computer, this one is wired to my pc via a crossover ethernet network.

Yesterday I had a bsod and since then we have had this problem, I have checked as my pc has Zonealarm (free) wether it was the firewall, since I have had the same error with my firewall closed and all tasks relevant deactivated I can assume it is not that.

I have checked the time and date of both computers, which is bang on time, and have checked and cleared all cookies and reg keys relevant to MSN, I also have defragmented both computers, and reinstalled WLM on this one, after uninstalling and clearing computer from WLM reg keys the lot, then deleting folders, and temp files, and rebooting the computer, this again no luck.

I am doing my head in finding the problem as on my pc WLM signs in just fine it is just this one.

This machine has no firewall installed as it is only used for WLM and Yahoo and the odd email, forum work my gf uses it for.

Any help would be nice, just if needed specs of this machine and a screeny of the error are below.

P3 547mhz
128mb Ram
20gb HD main 80gb HD slave for data backup
8mb Matrox Millenium AGP
Windows XP Pro Sp2

Re: WLM latest version sign in problem
 

I take it you went through these steps?
http://www.mybilgisayar.net/Live-New...live-messenger
http://www.fanatic.net.nz/2005/08/30...-80048820.html
How did you stop ZA? Did you tell it not to run at start up and then reboot?

Re: WLM latest version sign in problem
 

I shutdown zonealarm on my pc ( this one has no firewall on it ) and ended tasks relevant to both AVG and Zonealarm.

I have reformatted this pc also.

IN the DLL file thing I notice a few of the final ones come up not available I assume this is because of the newish build of WLM i am using.

---------- Post added at 14:51 ---------- Previous post was at 14:20 ----------

I sorted it !!!!!!!!

I shutdown all the computers and reset the modem then rebooted mine refreshed the network wizard and then did the same on the slave one with the issue and it worked!!!!