help please!
20 June 2005, 08:04 PM
#1
Scooby Regular
Thread Starter
help please!
when trying to run things this appears.
c:\windows\system32\autoexec.nt. the system file for running ms-dos and microsoft widows applications.choose close to terminate the application
c:\windows\system32\autoexec.nt. the system file for running ms-dos and microsoft widows applications.choose close to terminate the application
21 June 2005, 12:08 PM
#3
Scooby Regular
Thread Starter
Originally Posted by Hanslow
Is that the exact text that appears? Does it appear in a dialog? What things are you trying to run when you get the message?
yes thats the exact text, trying to run my scanner (canon fb630u) it worked ok the last time i used it. it also happens when i try to load the software disc for it to!
ps at the top of the box the blue line bit it says,16 bit windows subsystem.
21 June 2005, 12:15 PM
#4
Scooby Regular
Join Date: Mar 2001
Location: Derbyshire
Posts: 4,496
Likes: 0
Received 0 Likes
on
0 Posts
Have a read of this.
It could potentially be a trojan that has messed with these files so worth running a virus check just to make sure it isn't resident.
It could be that something (trojan or valid app) is, or has, written to one of the config files specified in the knowledge base article above.
It could potentially be a trojan that has messed with these files so worth running a virus check just to make sure it isn't resident.
It could be that something (trojan or valid app) is, or has, written to one of the config files specified in the knowledge base article above.
21 June 2005, 06:47 PM
#5
Scooby Regular
Thread Starter
Originally Posted by Hanslow
Have a read of this.
It could potentially be a trojan that has messed with these files so worth running a virus check just to make sure it isn't resident.
It could be that something (trojan or valid app) is, or has, written to one of the config files specified in the knowledge base article above.
It could potentially be a trojan that has messed with these files so worth running a virus check just to make sure it isn't resident.
It could be that something (trojan or valid app) is, or has, written to one of the config files specified in the knowledge base article above.
thanks hanslow did this and its working you are a genius thanks again
Glad you are all sorted 