DOS batch file query

Topic

New Reply

Not sure if this is the right place, to ask, but I’m looking for
help in closing a .txt file that opens during my automated back-ups.

I need to find a way to close it from within the DOS batch file
which is controilling the process.

Any suggestions please.

Reply | Quote

Replies

The “obvious” answer would be to get the program that opens this TXT file to close it. Then the backup could back up everything successfully…

You really need to say a bit more about the TXT file.

John

Reply | Quote

Thanks

I had tried to look at the txt file – created by PestPatrol running in command line mode – but couldn’t see any option to close it from within PestPatrol.

There is an option to stop it displaying however, so i can get round it that way, but it is not as convenient.

Colin

Reply | Quote

Can you stop PestPatrol while you’re doing the backups?

John

Reply | Quote

There about 6 to 8 individvidual Batch files which run each nite, doing defrags, spyclean, empty recycle etc. Each batch file does similar tasks, so the one I’m concerned with runs Ad-Aware, Spybot & Pest-Patrol each night, then archives the log files. Each of these progs is run in command-line format

I use winzip to carry out the back-up elements, also controlled froma a command line interface.

I’ve already edited the bat file to stop the .txt file opening in the first place.

Colin

Reply | Quote

Perhaps PSKill will do the job for you?

Reply | Quote

I’ll have a look

Colin

Reply | Quote

Their web page suggests it is for NT/2000.

Is it safe for XP ?

Reply | Quote

Yes, but I don’t think it will do what you want.

PSKILL “terminates processes on local or remote systems”…

John

Reply | Quote

Yes, but I don’t think it will do what you want.

PSKILL “terminates processes on local or remote systems”…

John

Reply | Quote

Colin, Windows XP is just Windows 2000.1 if you look at the version numbers. I was wondering, though, if you wrote the batch file that is opening the log file. If so, what is the syntax that is causing it to open?

Reply | Quote

Colin, Windows XP is just Windows 2000.1 if you look at the version numbers. I was wondering, though, if you wrote the batch file that is opening the log file. If so, what is the syntax that is causing it to open?

Reply | Quote

Their web page suggests it is for NT/2000.

Is it safe for XP ?

Reply | Quote

I’ll have a look

Colin

Reply | Quote

Mark

I thought he wanted to close a file, not terminate a process!

John

Reply | Quote

To be sure, John…killing notepad is one way to close the file!

Reply | Quote

Where did NOTEPAD come into this? I thought it was PestPatrol which was creating the TXT file and holding it open!

John

Reply | Quote

Yes, but… it sounds like the .txt file is likely being “opened” by the default program associated with .txt files — and for 95% of users, that would be NotePad.

OK, so it is a slight assumption, but I’ll bet it is correct. PestPatrol itself does not likely “open” the .txt file. Instead it more likely uses the associated program. Therefore, slamming shut NotePad should be successful.

Reply | Quote

Colin hasn’t actually said what is in this TXT file. I have assumed that it is a form of LOG file (like the notorious SQL.LOG file) which is written to while PestPatrol is running (either a scan or as a resident “watcher”, perhaps).

It would be fairly easy to see if NOTEPAD is running by looking at the Processes tab of Task Manager.

However, I don’t have PestPatrol, so this is fairly speculative…

John

Reply | Quote

Agreed entirely.

I don’t use Pest Patrol either, so I am speculating as well. If this process is occurring before Windows is shut down, perhaps even the program is obviously displayed.

Either way, the offending program should be able to be identified — and then “TaskKilled” (I would hope).

Reply | Quote

Agreed entirely.

I don’t use Pest Patrol either, so I am speculating as well. If this process is occurring before Windows is shut down, perhaps even the program is obviously displayed.

Either way, the offending program should be able to be identified — and then “TaskKilled” (I would hope).

Reply | Quote

Colin hasn’t actually said what is in this TXT file. I have assumed that it is a form of LOG file (like the notorious SQL.LOG file) which is written to while PestPatrol is running (either a scan or as a resident “watcher”, perhaps).

It would be fairly easy to see if NOTEPAD is running by looking at the Processes tab of Task Manager.

However, I don’t have PestPatrol, so this is fairly speculative…

John

Reply | Quote

Yes, but… it sounds like the .txt file is likely being “opened” by the default program associated with .txt files — and for 95% of users, that would be NotePad.

OK, so it is a slight assumption, but I’ll bet it is correct. PestPatrol itself does not likely “open” the .txt file. Instead it more likely uses the associated program. Therefore, slamming shut NotePad should be successful.

Reply | Quote

Where did NOTEPAD come into this? I thought it was PestPatrol which was creating the TXT file and holding it open!

John

Reply | Quote

To be sure, John…killing notepad is one way to close the file!

Reply | Quote

Mark

I thought he wanted to close a file, not terminate a process!

John

Reply | Quote

Perhaps PSKill will do the job for you?

Reply | Quote

There about 6 to 8 individvidual Batch files which run each nite, doing defrags, spyclean, empty recycle etc. Each batch file does similar tasks, so the one I’m concerned with runs Ad-Aware, Spybot & Pest-Patrol each night, then archives the log files. Each of these progs is run in command-line format

I use winzip to carry out the back-up elements, also controlled froma a command line interface.

I’ve already edited the bat file to stop the .txt file opening in the first place.

Colin

Reply | Quote

Can you stop PestPatrol while you’re doing the backups?

John

Reply | Quote

Thanks

I had tried to look at the txt file – created by PestPatrol running in command line mode – but couldn’t see any option to close it from within PestPatrol.

There is an option to stop it displaying however, so i can get round it that way, but it is not as convenient.

Colin

Reply | Quote

The “obvious” answer would be to get the program that opens this TXT file to close it. Then the backup could back up everything successfully…

You really need to say a bit more about the TXT file.

John

Reply | Quote