![]() Simply passing antivirus or any other automatic malware detection software without fully understanding what they can do and what can be their limits is not very different than first alternative (just pray). ![]() Note that Wireshark 1.12.13 was working fine on Windows XP as far as I can remember, even if it was no more officially supported. carefully examine all installed pieces of software to build a map of all used files and folders (good luck with that.) As shown on the Wireshark Wiki LifeCycle page, the last version to support XP is 1.10, and the last release of that was 1.10.14, available for download here.do nothing and pray hoping nothing worse happens.You can help us by donating at master wireshark Find file Clone README GNU General Public License v2. It may or not be possible if this computer has programs that you are no longer able to reinstall and that you do not want to lose, but it is the more robust and simple way to recover a sane environment. wireshark Project ID: 7898047 Star 710 87,029 Commits 29 Branches 902 Tags 268.6 GB Project Storage Topics: wireshark tshark packet capture 1 more Wireshark's official code repository. One Answer: As shown on the Wireshark Wiki LifeCycle page, the last version to support XP is 1.10, and the last release of that was 1.10. ![]() 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. |