Archived from groups: microsoft.public.windowsxp.hardware (More info?)

After exhausting all avenues for fixing my cd-rw error
(including flashing new firmware-successfully,
uninstalling re-installing all drivers, repairing
registry, etc.), I have concluded new xpsp2 atapi.sys and
or cdrom.sys drivers from msft are probably "corrupt", to
use msft's own phrase.

Some Proof:

1) there is suddenly an epidemic of similiar read/write
errors on cd-rw, cd-rom, dvd in this newsgroup since sp2
was released

2) the only drivers running most cd-rw, cd-rom (IDE type)
are newly installed digitally signed msft atapi/ide files
in sp2. Ive tried to "roll them back" to sp1, but xp won't
let me so far.

3) msft's own Knowledge Base Article - 324129 How to
troubleshoot issues that occur when you write data to a CD-
R or CD-RW Optical Disc in Windows XP says:
"The following error message may occur when you try to
write to a CD-R or CD-RW if the driver is corrupted:
There is no disc in the drive. Please insert a writable CD
into drive."

4) most third party apps, like nero seem to work fine,
presumably because they don't use the msft atapi driver


When's the last time you used xp cd writing wizard to burn
a disk??? Don't be surprised if you get asked to "insert"
when there is already a disk in. Next, xp will
automatically change the drive to a cd-rom next boot etc.

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

OK, after reading your rant figured I would do as you say and try using XP
SP2's built-in burning feature to write files to a CDRW. Grabbed several
files of different types and used the send to option in the right click
menu. Didn't work! Then remembered that seeing there are two burners in my
machine but only one designated for use by XP <blush> had put the blank CDRW
in wrong drive!

Changed the blank to the proper drive, hit back on the XP dialogue box then
once the disk had been detected hit the next button and burned the files to
the RW without issue. Was able to open the files from the just burned CD so
know that the burn was without problems.

So I would say no the SP2 Atapi.sys is not corrupt.

FWIW,
Len

"kendal" <anonymous@discussions.microsoft.com> wrote in message
news:13fa01c48c38$100c3830$a601280a@phx.gbl...
> After exhausting all avenues for fixing my cd-rw error
> (including flashing new firmware-successfully,
> uninstalling re-installing all drivers, repairing
> registry, etc.), I have concluded new xpsp2 atapi.sys and
> or cdrom.sys drivers from msft are probably "corrupt", to
> use msft's own phrase.
>
> Some Proof:
>
> 1) there is suddenly an epidemic of similiar read/write
> errors on cd-rw, cd-rom, dvd in this newsgroup since sp2
> was released
>
> 2) the only drivers running most cd-rw, cd-rom (IDE type)
> are newly installed digitally signed msft atapi/ide files
> in sp2. Ive tried to "roll them back" to sp1, but xp won't
> let me so far.
>
> 3) msft's own Knowledge Base Article - 324129 How to
> troubleshoot issues that occur when you write data to a CD-
> R or CD-RW Optical Disc in Windows XP says:
> "The following error message may occur when you try to
> write to a CD-R or CD-RW if the driver is corrupted:
> There is no disc in the drive. Please insert a writable CD
> into drive."
>
> 4) most third party apps, like nero seem to work fine,
> presumably because they don't use the msft atapi driver
>
>
> When's the last time you used xp cd writing wizard to burn
> a disk??? Don't be surprised if you get asked to "insert"
> when there is already a disk in. Next, xp will
> automatically change the drive to a cd-rom next boot etc.
>
>

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

"kendal" <anonymous@discussions.microsoft.com> wrote in message
news:13fa01c48c38$100c3830$a601280a@phx.gbl...
> After exhausting all avenues for fixing my cd-rw error
> (including flashing new firmware-successfully,
> uninstalling re-installing all drivers, repairing
> registry, etc.), I have concluded new xpsp2 atapi.sys and
> or cdrom.sys drivers from msft are probably "corrupt", to
> use msft's own phrase.
>
> Some Proof:
>
> 1) there is suddenly an epidemic of similiar read/write
> errors on cd-rw, cd-rom, dvd in this newsgroup since sp2
> was released
>
> 2) the only drivers running most cd-rw, cd-rom (IDE type)
> are newly installed digitally signed msft atapi/ide files
> in sp2. Ive tried to "roll them back" to sp1, but xp won't
> let me so far.
>
> 3) msft's own Knowledge Base Article - 324129 How to
> troubleshoot issues that occur when you write data to a CD-
> R or CD-RW Optical Disc in Windows XP says:
> "The following error message may occur when you try to
> write to a CD-R or CD-RW if the driver is corrupted:
> There is no disc in the drive. Please insert a writable CD
> into drive."
>
> 4) most third party apps, like nero seem to work fine,
> presumably because they don't use the msft atapi driver
>
>
> When's the last time you used xp cd writing wizard to burn
> a disk??? Don't be surprised if you get asked to "insert"
> when there is already a disk in. Next, xp will
> automatically change the drive to a cd-rom next boot etc.
>
>

Check that the IMAPI CD-Burning COM Service is set to Automatic.

Q

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

I checked that already:IMAPI CD-Burning COM Service is set
to Automatic
I checked that already:Right click device>recording tab on
I checked that already : registry drive key is set to 2
I checked that already: change drive from memorex 48maxx
to Lite-on 52x with firmware flash
I checked that already: Upgrade Firmware to latest from
Lite-on
I checked that already: Drivers all atapi/ide drivers re-
installed
I checked that alreadyhysically disconnect-re-connect
drive
I checked that already:Nero burns fine

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Galoot, I support what you claim about the ms special xp2
cos' I am also one of the victims of trying to fixed those
same repeated errors surfacing. It make me go NUT until I
have to reversed back my OS. Let ms dust settle first
before you enter, it save you the trouble of meddling your
pc to fix it.
>-----Original Message-----
>IN THE NEWSGROUPS AND PAPERS THERE IS A LOT OF PROBLEMS
>WITH THE SP2 THAT JUST CAME OUT IF THAT THE ONE YOU ARE
>TALKING ABOUT AND IF YOU CAN GO BACK IN TIME AND GET RID
>OF IT THAT MIGHT HELP AND STAY AWAY FROM IT UNTIL GOOD O
>BILL GET IT RIGHT (THAT A JOKE BECAUSE MICROSOFT JUST
>DON'T CARE ANYMORE ABOUT PUTTING OUT BAD PROGRAM) O WELL
>
>LOL
>
>GALOOT
>
>
>>-----Original Message-----
>>After exhausting all avenues for fixing my cd-rw error
>>(including flashing new firmware-successfully,
>>uninstalling re-installing all drivers, repairing
>>registry, etc.), I have concluded new xpsp2 atapi.sys
and
>>or cdrom.sys drivers from msft are probably "corrupt",
to
>>use msft's own phrase.
>>
>>Some Proof:
>>
>>1) there is suddenly an epidemic of similiar read/write
>>errors on cd-rw, cd-rom, dvd in this newsgroup since sp2
>>was released
>>
>>2) the only drivers running most cd-rw, cd-rom (IDE
type)
>>are newly installed digitally signed msft atapi/ide
files
>>in sp2. Ive tried to "roll them back" to sp1, but xp
>won't
>>let me so far.
>>
>>3) msft's own Knowledge Base Article - 324129 How to
>>troubleshoot issues that occur when you write data to a
>CD-
>>R or CD-RW Optical Disc in Windows XP says:
>>"The following error message may occur when you try to
>>write to a CD-R or CD-RW if the driver is corrupted:
>>There is no disc in the drive. Please insert a writable
>CD
>>into drive."
>>
>>4) most third party apps, like nero seem to work fine,
>>presumably because they don't use the msft atapi driver
>>
>>
>>When's the last time you used xp cd writing wizard to
>burn
>>a disk??? Don't be surprised if you get asked
to "insert"
>>when there is already a disk in. Next, xp will
>>automatically change the drive to a cd-rom next boot etc.
>>
>>
>>.
>>
>.
>