Then reinstall every software properly from official or well knows sources in acceptable places (a temp folder is not.). My advice when things go that way is to keep calm, save all the data, reinstall the system (including formatting the hard disk), install a good antivirus (avira or avast or correct free possibilities), ask the antivirus to scan the saved data and restore it. So what is to blame is not the fact that a running instance of wireshark tries to load a DLL from a weird folder, but the fact that is could be installed in that folder and that its installation (or the installation of any other program) has put a system.dll there. That being said, Windows rules specify that a DLL file is first searched in the folder that contains the executable. ![]() ![]() Hmm, how did you install wireshark on your system? IMHO, what is bad is the existence of a system.dll file in c:\Document and settings\administrator\locals.\temp (I cannot remember exactly how the local temp folder is named in XP).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |