![]() ![]() |
Jul 25 2006, 09:22 AM Post
#21 | |
| Group: Members Posts: 8 Joined: 3-June 04 From: East Coast Member No.: 21804 |
OK so none of what I did worked. I ended up deleting CMDOW as part of my SAV install...it deleted just before RunOnceEx calls the Symantec msi. This still keeps the RunOnceEx hidden but my cleanup.cmd is NOT hidden...its only up for maybe 5 seconds though so I don't mind.
|
| | |
Jul 8 2007, 05:10 AM Post
#22 | |
| Group: Members Posts: 1 Joined: 8-July 07 Member No.: 145880 OS: XP Pro x86 | hello express, et.al. i am memofromturner, a new member. i have read through several replies to your original post, but not all. just wanted to add that i received the identical response from my nod32 v2.5.18. i googled the file, and found this link to be quite informative: http://www.commandline.co.uk/cmdow/, ritchie lawrence's command line utils, etc. according to sir lawrence [get it?], it has a veritable plethora of handy usages. hope it sheds new light on this topic. sincerely, memofromturner |
| | |
Jul 26 2009, 03:36 AM Post
#23 | |
| Group: Members Posts: 1 Joined: 26-July 09 Member No.: 253918 OS: none |
Hello I have NOD32 and today it have alarmed me, that the CMDOW.EXE have been infected with WIN32/CMDOW.143 Is it proper or i need to delete it or take in carantene or what? Sorry about writing mistakes, i'm learning English. Thnaks, fsz2 This post has been edited by fsz2: Jul 26 2009, 04:10 AM |
| | |
![]() ![]() |
| Lo-Fi Version | Time is now: 21st November 2009 - 11:19 PM |