the unforgiven said:
I would be happy to uninstall the application, but......
the real problem is, I don't know what application is causing the
problem. It seems the only solution is to disable that unknown program
from running.
I've tried running service pack 1 from safe mode and atapi.sys is
still open!
Do you get it? How many times do we have to tell you this?
Is Microsoft so helpless that they can't install ANY of the bug fixes
when atapi.sys is open? How pathetic!
Maybe Microsoft can take responsibility for the useless solutions they
provide to their customers. I'm not holding my breath. I've seen full
well, over the past decade, that Microsoft cares very much about
destroying their competition, but otherwise, they don't give a damn
about quality.
Mike Brannigan's flippant response is a perfect example. As though
it's not Microsoft's fault that they can't patch your system because
some rogue program has a file open. It should be very simple for the
Service Pack program to kill the process that has the file open. But
it's easier to put the burden on the hapless customer who isn't given
a clue as to what remedial measures he can take. So, Mike Brannigan,
take your stupid answers, and your lack of concern for your customers,
and shove it!
The original poster has a known application that is not what you would
consider to be "well behaved" in that it is not written to allow itself to
be stopped to release any locked files etc. This is a failure in the
application since other applications that perform the same task (as I
illustrated) can be closed and the opened again without any need for a
system restart or safe mode. So my advice was valid and correct. In that
the original posters problem is an application one, with 2 causes of action
contact the vendor for support or change the application.
I've tried running service pack 1 from safe mode and atapi.sys is
still open!
Do you get it? How many times do we have to tell you this?
As regards your specific problem. You also obviously have an application
issue. However you appear to not be able to identify which of your
applications is causing you your problem.
Since we are capable of replacing this file (and have done so successfully
on millions of systems) in the SP then you have some application that is
preventing this.
You will have to troubleshoot this issue by starting your system in safe
made and then trying to locate the device driver to application that is
causing this issue for you.
Maybe Microsoft can take responsibility for the useless solutions they
provide to their customers. I'm not holding my breath. I've seen full
well, over the past decade, that Microsoft cares very much about
destroying their competition, but otherwise, they don't give a damn
about quality.
Which "useless solution" ? since this is obviously a third party
application issue/driver problem, I suggest you look at those applications
and drivers you have installed to your system for a resolution.
Mike Brannigan's flippant response is a perfect example. As though
it's not Microsoft's fault that they can't patch your system because
some rogue program has a file open. It should be very simple for the
Service Pack program to kill the process that has the file open. But
it's easier to put the burden on the hapless customer who isn't given
a clue as to what remedial measures he can take. So, Mike Brannigan,
take your stupid answers, and your lack of concern for your customers,
and shove it!
You simple cannot just "kill a process" in an ad hoc manner just because to
has a file open etc.
Doing so may lead to a fatal system crash, particularly when you are dealing
with a device driver/device issue as we are here. This is not a simple
application holding a file open. As in the case of the original poster and
the Daemon Tools application. It is not the application that is the issue
but the device it creates that then will not respond to a stop control
signal.
Finally the fact that I spend countless hours in these newsgroups in my own
time answering questions for posters such as your self and the original
poster is my contribution to mine own and my companies customers
--
Regards,
Mike
--
Mike Brannigan [Microsoft]
This posting is provided "AS IS" with no warranties, and confers no
rights
Please note I cannot respond to e-mailed questions, please use these
newsgroups
