G
gbd1956
Thanks guys/ladies,my previous posted problem is now solved.After
scanning w/anti virus,ad-aware,spybot s&d,determined that the
"newdot.dll error message I was getting had messed with my winsock
stack,and luckily,I already had a winsock fix disc;so I ran it and it
fixed the problem.I also read on a site that if you are running
Windows XP,you don't need a disc,you can go to cmd prompt and type "
netsh winsock reset catalog,and this will fix it.I tried this and it
said it was successful,but it didn't restore my winsock stack.Just
something to inform others on;I would just create a disc.
Thanks again for all yall's help.....Yep, I said yall's,Im from the
south................
scanning w/anti virus,ad-aware,spybot s&d,determined that the
"newdot.dll error message I was getting had messed with my winsock
stack,and luckily,I already had a winsock fix disc;so I ran it and it
fixed the problem.I also read on a site that if you are running
Windows XP,you don't need a disc,you can go to cmd prompt and type "
netsh winsock reset catalog,and this will fix it.I tried this and it
said it was successful,but it didn't restore my winsock stack.Just
something to inform others on;I would just create a disc.
Thanks again for all yall's help.....Yep, I said yall's,Im from the
south................