Your eyes are fine, something happens when I paste anyones line in. There all perfect fo awhile then the error msg. & everyone points out the same thing. The only thing I can think of, is NOD was not full screen when I pasted. Hmm! Why should that matter?

Right now I've no clue. I'm new to nod so I'm not sure how it works. I use to use Peter Norton's stuff. I've had lots of problems with resources and the works. A friend recommended nod so here I be. I've formatted and started over clean...Help me please.

What I'm looking for is step-by-step mode please. Its a new program that I'm doing a lot of reading on. It seems to be great and spywarrior seems to like it too.

If you want to perform full scan of your system with the default configuration , open Control Center -> In-depth analysis

About the scheduled scan , you have two options - a silent one which will run the background and a visible one . Of course , a scheduled scan is not a must , you can manually run such scan when you want.

To do a silent scan:
Open Control Center -> NOD32 System tools -> Scheduler/Planner
Click Add button . As a task choose "NOD32 on-demand scanning" and follow the instructions to choose the date/type . At the end if you use default configuration choose the profile of Control Center-In depth analysis .

To do a visible scan , which will run NOD32.exe
Open Control Center -> NOD32 System tools -> Scheduler/Planner
Click Add button . As a task , choose Execution of an external application . Find NOD32 on-demand's scanner path and the file (C:\Program files\ESET\nod32.exe) and as a commands you can paste these:

Should this fail, how crippled is NOD, because of the commad line fail? Crippled is perhaps too strong a word, but hopefully you understand my meaning.

Click to expand...

It's not at all, just means that you can not run a commandline scan, and this I have never come across before.

If it was mine, I'd be placing a image back on or formatting the system and starting again, this times Windows only, then NOD32 and keep it that way for a few days until you are satisfied that NOD32 works correctly, then image the drive, and keep adding programs (imaging between) until you find the culprit that caused all this.