McAfee clean.bat not working

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:CfO3h.1100$244.1093@trnddc01
> From: "Tom Del Rosso" <td_01 RemoveThis @att.net.invalid>
>
>> I just tried running the latest CLEAN.BAT on several XP PCs in safe
>> mode, and it just doesn't start, but has no error messages.
>> SCAN.EXE runs in DOSCLEAN.BAT so apparently Kixstart is not working.
>>
>> I'm not sure how to diagnose a Kixstart problem. Has anyone seen
>> this type of failure?
>>
>
> You did not state which one of my tools you are using and the
> Interpreter is KiXtart, not "Kixstart".
>
> plaese FULLY explain which tool you are using and what you are trying
> to do.

You're the author? Well then many thanks for making this available.

Which tool? The McAfee clean tool. Sorry, but I thought that was clear
from the names of the batch files.

The DAT files downloaded with no error. Upon booting in
safe-mode-with-command-prompt and running clean.bat, all it does is emit one
beep, then hangs in a blank command window. However DOSclean.bat works,
therefor SCAN.EXE works, and apparently KiXtart doesn't work.

I'm basically reiterating. Sorry, but I don't know what details I'm leaving
out. (I get that a lot because I try to avoid verbose questions - not
because I can't write a complete paragraph.) If I start the interpreter in
debug mode maybe there would be something else to observe. If this is not a
known problem then I'll just go back and try that.

I could add that clean.kix is headlined "01-28-2006 // v3.77" but it was
just downloaded a few weeks ago.


--

Reply in group, but if emailing add another
zero, and remove the last word.
 >> Stay informed about: McAfee clean.bat not working 

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:CfO3h.1100$244.1093@trnddc01
> From: "Tom Del Rosso" <td_01.RemoveThis@att.net.invalid>
>
>> I just tried running the latest CLEAN.BAT on several XP PCs in safe
>> mode, and it just doesn't start, but has no error messages.
>> SCAN.EXE runs in DOSCLEAN.BAT so apparently Kixstart is not working.
>>
>> I'm not sure how to diagnose a Kixstart problem. Has anyone seen
>> this type of failure?
>>
>
> You did not state which one of my tools you are using and the
> Interpreter is KiXtart, not "Kixstart".
>
> plaese FULLY explain which tool you are using and what you are trying
> to do.

You're the author? Well then many thanks for making this available.

Which tool? The McAfee clean tool. Sorry, but I thought that was clear
from the names of the batch files.

The DAT files downloaded with no error. Upon booting in
safe-mode-with-command-prompt and running clean.bat, all it does is emit one
beep, then hangs in a blank command window. However DOSclean.bat works,
therefor SCAN.EXE works, and apparently KiXtart doesn't work.

I'm basically reiterating. Sorry, but I don't know what details I'm leaving
out. (I get that a lot because I try to avoid verbose questions - not
because I can't write a complete paragraph.) If I start the interpreter in
debug mode maybe there would be something else to observe. If this is not a
known problem then I'll just go back and try that.

I could add that clean.kix is headlined "01-28-2006 // v3.77" but it was
just downloaded a few weeks ago.


--

Reply in group, but if emailing add another
zero, and remove the last word.
 >> Stay informed about: McAfee clean.bat not working 

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:CfO3h.1100$244.1093@trnddc01
> From: "Tom Del Rosso" <td_01.RemoveThis@att.net.invalid>
>
>> I just tried running the latest CLEAN.BAT on several XP PCs in safe
>> mode, and it just doesn't start, but has no error messages.
>> SCAN.EXE runs in DOSCLEAN.BAT so apparently Kixstart is not working.
>>
>> I'm not sure how to diagnose a Kixstart problem. Has anyone seen
>> this type of failure?
>>
>
> You did not state which one of my tools you are using and the
> Interpreter is KiXtart, not "Kixstart".
>
> plaese FULLY explain which tool you are using and what you are trying
> to do.

You're the author? Well then many thanks for making this available.

Which tool? The McAfee clean tool. Sorry, but I thought that was clear
from the names of the batch files.

The DAT files downloaded with no error. Upon booting in
safe-mode-with-command-prompt and running clean.bat, all it does is emit one
beep, then hangs in a blank command window. However DOSclean.bat works,
therefor SCAN.EXE works, and apparently KiXtart doesn't work.

I'm basically reiterating. Sorry, but I don't know what details I'm leaving
out. (I get that a lot because I try to avoid verbose questions - not
because I can't write a complete paragraph.) If I start the interpreter in
debug mode maybe there would be something else to observe. If this is not a
known problem then I'll just go back and try that.

I could add that clean.kix is headlined "01-28-2006 // v3.77" but it was
just downloaded a few weeks ago.


--

Reply in group, but if emailing add another
zero, and remove the last word.
 >> Stay informed about: McAfee clean.bat not working 

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:CfO3h.1100$244.1093@trnddc01
> From: "Tom Del Rosso" <td_01 DeleteThis @att.net.invalid>
>
>> I just tried running the latest CLEAN.BAT on several XP PCs in safe
>> mode, and it just doesn't start, but has no error messages.
>> SCAN.EXE runs in DOSCLEAN.BAT so apparently Kixstart is not working.
>>
>> I'm not sure how to diagnose a Kixstart problem. Has anyone seen
>> this type of failure?
>>
>
> You did not state which one of my tools you are using and the
> Interpreter is KiXtart, not "Kixstart".
>
> plaese FULLY explain which tool you are using and what you are trying
> to do.

You're the author? Well then many thanks for making this available.

Which tool? The McAfee clean tool. Sorry, but I thought that was clear
from the names of the batch files.

The DAT files downloaded with no error. Upon booting in
safe-mode-with-command-prompt and running clean.bat, all it does is emit one
beep, then hangs in a blank command window. However DOSclean.bat works,
therefor SCAN.EXE works, and apparently KiXtart doesn't work.

I'm basically reiterating. Sorry, but I don't know what details I'm leaving
out. (I get that a lot because I try to avoid verbose questions - not
because I can't write a complete paragraph.) If I start the interpreter in
debug mode maybe there would be something else to observe. If this is not a
known problem then I'll just go back and try that.

I could add that clean.kix is headlined "01-28-2006 // v3.77" but it was
just downloaded a few weeks ago.


--

Reply in group, but if emailing add another
zero, and remove the last word.
 >> Stay informed about: McAfee clean.bat not working 

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:CfO3h.1100$244.1093@trnddc01
> From: "Tom Del Rosso" <td_01.RemoveThis@att.net.invalid>
>
>> I just tried running the latest CLEAN.BAT on several XP PCs in safe
>> mode, and it just doesn't start, but has no error messages.
>> SCAN.EXE runs in DOSCLEAN.BAT so apparently Kixstart is not working.
>>
>> I'm not sure how to diagnose a Kixstart problem. Has anyone seen
>> this type of failure?
>>
>
> You did not state which one of my tools you are using and the
> Interpreter is KiXtart, not "Kixstart".
>
> plaese FULLY explain which tool you are using and what you are trying
> to do.

You're the author? Well then many thanks for making this available.

Which tool? The McAfee clean tool. Sorry, but I thought that was clear
from the names of the batch files.

The DAT files downloaded with no error. Upon booting in
safe-mode-with-command-prompt and running clean.bat, all it does is emit one
beep, then hangs in a blank command window. However DOSclean.bat works,
therefor SCAN.EXE works, and apparently KiXtart doesn't work.

I'm basically reiterating. Sorry, but I don't know what details I'm leaving
out. (I get that a lot because I try to avoid verbose questions - not
because I can't write a complete paragraph.) If I start the interpreter in
debug mode maybe there would be something else to observe. If this is not a
known problem then I'll just go back and try that.

I could add that clean.kix is headlined "01-28-2006 // v3.77" but it was
just downloaded a few weeks ago.


--

Reply in group, but if emailing add another
zero, and remove the last word.
 >> Stay informed about: McAfee clean.bat not working 

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:CfO3h.1100$244.1093@trnddc01
> From: "Tom Del Rosso" <td_01 RemoveThis @att.net.invalid>
>
>> I just tried running the latest CLEAN.BAT on several XP PCs in safe
>> mode, and it just doesn't start, but has no error messages.
>> SCAN.EXE runs in DOSCLEAN.BAT so apparently Kixstart is not working.
>>
>> I'm not sure how to diagnose a Kixstart problem. Has anyone seen
>> this type of failure?
>>
>
> You did not state which one of my tools you are using and the
> Interpreter is KiXtart, not "Kixstart".
>
> plaese FULLY explain which tool you are using and what you are trying
> to do.

You're the author? Well then many thanks for making this available.

Which tool? The McAfee clean tool. Sorry, but I thought that was clear
from the names of the batch files.

The DAT files downloaded with no error. Upon booting in
safe-mode-with-command-prompt and running clean.bat, all it does is emit one
beep, then hangs in a blank command window. However DOSclean.bat works,
therefor SCAN.EXE works, and apparently KiXtart doesn't work.

I'm basically reiterating. Sorry, but I don't know what details I'm leaving
out. (I get that a lot because I try to avoid verbose questions - not
because I can't write a complete paragraph.) If I start the interpreter in
debug mode maybe there would be something else to observe. If this is not a
known problem then I'll just go back and try that.

I could add that clean.kix is headlined "01-28-2006 // v3.77" but it was
just downloaded a few weeks ago.


--

Reply in group, but if emailing add another
zero, and remove the last word.
 >> Stay informed about: McAfee clean.bat not working 

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:CfO3h.1100$244.1093@trnddc01
> From: "Tom Del Rosso" <td_01 RemoveThis @att.net.invalid>
>
>> I just tried running the latest CLEAN.BAT on several XP PCs in safe
>> mode, and it just doesn't start, but has no error messages.
>> SCAN.EXE runs in DOSCLEAN.BAT so apparently Kixstart is not working.
>>
>> I'm not sure how to diagnose a Kixstart problem. Has anyone seen
>> this type of failure?
>>
>
> You did not state which one of my tools you are using and the
> Interpreter is KiXtart, not "Kixstart".
>
> plaese FULLY explain which tool you are using and what you are trying
> to do.

You're the author? Well then many thanks for making this available.

Which tool? The McAfee clean tool. Sorry, but I thought that was clear
from the names of the batch files.

The DAT files downloaded with no error. Upon booting in
safe-mode-with-command-prompt and running clean.bat, all it does is emit one
beep, then hangs in a blank command window. However DOSclean.bat works,
therefor SCAN.EXE works, and apparently KiXtart doesn't work.

I'm basically reiterating. Sorry, but I don't know what details I'm leaving
out. (I get that a lot because I try to avoid verbose questions - not
because I can't write a complete paragraph.) If I start the interpreter in
debug mode maybe there would be something else to observe. If this is not a
known problem then I'll just go back and try that.

I could add that clean.kix is headlined "01-28-2006 // v3.77" but it was
just downloaded a few weeks ago.


--

Reply in group, but if emailing add another
zero, and remove the last word.
 >> Stay informed about: McAfee clean.bat not working 

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:CfO3h.1100$244.1093@trnddc01
> From: "Tom Del Rosso" <td_01.RemoveThis@att.net.invalid>
>
>> I just tried running the latest CLEAN.BAT on several XP PCs in safe
>> mode, and it just doesn't start, but has no error messages.
>> SCAN.EXE runs in DOSCLEAN.BAT so apparently Kixstart is not working.
>>
>> I'm not sure how to diagnose a Kixstart problem. Has anyone seen
>> this type of failure?
>>
>
> You did not state which one of my tools you are using and the
> Interpreter is KiXtart, not "Kixstart".
>
> plaese FULLY explain which tool you are using and what you are trying
> to do.

You're the author? Well then many thanks for making this available.

Which tool? The McAfee clean tool. Sorry, but I thought that was clear
from the names of the batch files.

The DAT files downloaded with no error. Upon booting in
safe-mode-with-command-prompt and running clean.bat, all it does is emit one
beep, then hangs in a blank command window. However DOSclean.bat works,
therefor SCAN.EXE works, and apparently KiXtart doesn't work.

I'm basically reiterating. Sorry, but I don't know what details I'm leaving
out. (I get that a lot because I try to avoid verbose questions - not
because I can't write a complete paragraph.) If I start the interpreter in
debug mode maybe there would be something else to observe. If this is not a
known problem then I'll just go back and try that.

I could add that clean.kix is headlined "01-28-2006 // v3.77" but it was
just downloaded a few weeks ago.


--

Reply in group, but if emailing add another
zero, and remove the last word.
 >> Stay informed about: McAfee clean.bat not working 

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:CfO3h.1100$244.1093@trnddc01
> From: "Tom Del Rosso" <td_01.TakeThisOut@att.net.invalid>
>
>> I just tried running the latest CLEAN.BAT on several XP PCs in safe
>> mode, and it just doesn't start, but has no error messages.
>> SCAN.EXE runs in DOSCLEAN.BAT so apparently Kixstart is not working.
>>
>> I'm not sure how to diagnose a Kixstart problem. Has anyone seen
>> this type of failure?
>>
>
> You did not state which one of my tools you are using and the
> Interpreter is KiXtart, not "Kixstart".
>
> plaese FULLY explain which tool you are using and what you are trying
> to do.

You're the author? Well then many thanks for making this available.

Which tool? The McAfee clean tool. Sorry, but I thought that was clear
from the names of the batch files.

The DAT files downloaded with no error. Upon booting in
safe-mode-with-command-prompt and running clean.bat, all it does is emit one
beep, then hangs in a blank command window. However DOSclean.bat works,
therefor SCAN.EXE works, and apparently KiXtart doesn't work.

I'm basically reiterating. Sorry, but I don't know what details I'm leaving
out. (I get that a lot because I try to avoid verbose questions - not
because I can't write a complete paragraph.) If I start the interpreter in
debug mode maybe there would be something else to observe. If this is not a
known problem then I'll just go back and try that.

I could add that clean.kix is headlined "01-28-2006 // v3.77" but it was
just downloaded a few weeks ago.


--

Reply in group, but if emailing add another
zero, and remove the last word.
 >> Stay informed about: McAfee clean.bat not working 

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:CfO3h.1100$244.1093@trnddc01
> From: "Tom Del Rosso" <td_01.RemoveThis@att.net.invalid>
>
>> I just tried running the latest CLEAN.BAT on several XP PCs in safe
>> mode, and it just doesn't start, but has no error messages.
>> SCAN.EXE runs in DOSCLEAN.BAT so apparently Kixstart is not working.
>>
>> I'm not sure how to diagnose a Kixstart problem. Has anyone seen
>> this type of failure?
>>
>
> You did not state which one of my tools you are using and the
> Interpreter is KiXtart, not "Kixstart".
>
> plaese FULLY explain which tool you are using and what you are trying
> to do.

You're the author? Well then many thanks for making this available.

Which tool? The McAfee clean tool. Sorry, but I thought that was clear
from the names of the batch files.

The DAT files downloaded with no error. Upon booting in
safe-mode-with-command-prompt and running clean.bat, all it does is emit one
beep, then hangs in a blank command window. However DOSclean.bat works,
therefor SCAN.EXE works, and apparently KiXtart doesn't work.

I'm basically reiterating. Sorry, but I don't know what details I'm leaving
out. (I get that a lot because I try to avoid verbose questions - not
because I can't write a complete paragraph.) If I start the interpreter in
debug mode maybe there would be something else to observe. If this is not a
known problem then I'll just go back and try that.

I could add that clean.kix is headlined "01-28-2006 // v3.77" but it was
just downloaded a few weeks ago.


--

Reply in group, but if emailing add another
zero, and remove the last word.
 >> Stay informed about: McAfee clean.bat not working 

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:CfO3h.1100$244.1093@trnddc01
> From: "Tom Del Rosso" <td_01 DeleteThis @att.net.invalid>
>
>> I just tried running the latest CLEAN.BAT on several XP PCs in safe
>> mode, and it just doesn't start, but has no error messages.
>> SCAN.EXE runs in DOSCLEAN.BAT so apparently Kixstart is not working.
>>
>> I'm not sure how to diagnose a Kixstart problem. Has anyone seen
>> this type of failure?
>>
>
> You did not state which one of my tools you are using and the
> Interpreter is KiXtart, not "Kixstart".
>
> plaese FULLY explain which tool you are using and what you are trying
> to do.

You're the author? Well then many thanks for making this available.

Which tool? The McAfee clean tool. Sorry, but I thought that was clear
from the names of the batch files.

The DAT files downloaded with no error. Upon booting in
safe-mode-with-command-prompt and running clean.bat, all it does is emit one
beep, then hangs in a blank command window. However DOSclean.bat works,
therefor SCAN.EXE works, and apparently KiXtart doesn't work.

I'm basically reiterating. Sorry, but I don't know what details I'm leaving
out. (I get that a lot because I try to avoid verbose questions - not
because I can't write a complete paragraph.) If I start the interpreter in
debug mode maybe there would be something else to observe. If this is not a
known problem then I'll just go back and try that.

I could add that clean.kix is headlined "01-28-2006 // v3.77" but it was
just downloaded a few weeks ago.


--

Reply in group, but if emailing add another
zero, and remove the last word.
 >> Stay informed about: McAfee clean.bat not working 

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:CfO3h.1100$244.1093@trnddc01
> From: "Tom Del Rosso" <td_01.TakeThisOut@att.net.invalid>
>
>> I just tried running the latest CLEAN.BAT on several XP PCs in safe
>> mode, and it just doesn't start, but has no error messages.
>> SCAN.EXE runs in DOSCLEAN.BAT so apparently Kixstart is not working.
>>
>> I'm not sure how to diagnose a Kixstart problem. Has anyone seen
>> this type of failure?
>>
>
> You did not state which one of my tools you are using and the
> Interpreter is KiXtart, not "Kixstart".
>
> plaese FULLY explain which tool you are using and what you are trying
> to do.

You're the author? Well then many thanks for making this available.

Which tool? The McAfee clean tool. Sorry, but I thought that was clear
from the names of the batch files.

The DAT files downloaded with no error. Upon booting in
safe-mode-with-command-prompt and running clean.bat, all it does is emit one
beep, then hangs in a blank command window. However DOSclean.bat works,
therefor SCAN.EXE works, and apparently KiXtart doesn't work.

I'm basically reiterating. Sorry, but I don't know what details I'm leaving
out. (I get that a lot because I try to avoid verbose questions - not
because I can't write a complete paragraph.) If I start the interpreter in
debug mode maybe there would be something else to observe. If this is not a
known problem then I'll just go back and try that.

I could add that clean.kix is headlined "01-28-2006 // v3.77" but it was
just downloaded a few weeks ago.


--

Reply in group, but if emailing add another
zero, and remove the last word.
 >> Stay informed about: McAfee clean.bat not working 

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:CfO3h.1100$244.1093@trnddc01
> From: "Tom Del Rosso" <td_01.TakeThisOut@att.net.invalid>
>
>> I just tried running the latest CLEAN.BAT on several XP PCs in safe
>> mode, and it just doesn't start, but has no error messages.
>> SCAN.EXE runs in DOSCLEAN.BAT so apparently Kixstart is not working.
>>
>> I'm not sure how to diagnose a Kixstart problem. Has anyone seen
>> this type of failure?
>>
>
> You did not state which one of my tools you are using and the
> Interpreter is KiXtart, not "Kixstart".
>
> plaese FULLY explain which tool you are using and what you are trying
> to do.

You're the author? Well then many thanks for making this available.

Which tool? The McAfee clean tool. Sorry, but I thought that was clear
from the names of the batch files.

The DAT files downloaded with no error. Upon booting in
safe-mode-with-command-prompt and running clean.bat, all it does is emit one
beep, then hangs in a blank command window. However DOSclean.bat works,
therefor SCAN.EXE works, and apparently KiXtart doesn't work.

I'm basically reiterating. Sorry, but I don't know what details I'm leaving
out. (I get that a lot because I try to avoid verbose questions - not
because I can't write a complete paragraph.) If I start the interpreter in
debug mode maybe there would be something else to observe. If this is not a
known problem then I'll just go back and try that.

I could add that clean.kix is headlined "01-28-2006 // v3.77" but it was
just downloaded a few weeks ago.


--

Reply in group, but if emailing add another
zero, and remove the last word.
 >> Stay informed about: McAfee clean.bat not working