Cant get embedded CD burn feature to identify that there i..

G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.embedded,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.setup_deployment (More info?)

Having just installed SP2, I cant get the CD burn feature to work. I dont
think SP2 is relevant, - I didnt enable or use this feature before I
installed it, I used Easy CD Creator 5 which wont work with SP2 so I
uninstalled it, installed Nero 5 which wouldnt work either (because it is I
THINK an OEM version), uninstalled that and applied the registry patch when
all my CD drives disappeared.

The problem is that the burning process gets as far as the (second, the
actual) burn stage when it pretends that it can't see the CD which is
obviously in the Archos DEX DVD drive and which Windows explorer could see
as being there and having a CD-R in it.

I went to Control Panel, Administrative Tools, Services, Double-clicked
"IMAPI CD Burning", clicked Start, and set "Startup type" as "Manual" (or
"Automatic") Neither made any difference.

The burn feature puts an icon in startup tray telling me that there are
files waiting to be written to CD and then when I name the file on the CD
which Windows Explorer identifies as a fit and proper CD, it tells me that
there is still no CD in writer. On one CD, Explorer even identifies a few
small files which were already
written to it on one of the CDs I tried. It even pretends it is going to
burn them in the next step or so:

It is at that stage that the OS suddenly thinks that, - although it can see
the drive, - there is no disc in that drive.

(There is nothing, obviously, in Device Manager about the driver being wrong
or the device having anything wrong with it)..
 
G

Guest

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

A number of CD-r owners are finding they cannot get that to work. A better driver, or a different cd drive seem to be the only fix.

--

Mark L. Ferguson
FAQ for MS Antispyware version 1.0.509
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
marfers notes for windows xp http://www.geocities.com/marfer_mvp/chatNotes.htm
..
"news.microsoft.com" <fountainpen@amexol.net> wrote in message news:eh4osJSZFHA.2664@TK2MSFTNGP15.phx.gbl...
> Having just installed SP2, I cant get the CD burn feature to work. I dont think SP2 is relevant, - I didnt enable or use this
> feature before I installed it, I used Easy CD Creator 5 which wont work with SP2 so I uninstalled it, installed Nero 5 which
> wouldnt work either (because it is I THINK an OEM version), uninstalled that and applied the registry patch when all my CD drives
> disappeared.
>
> The problem is that the burning process gets as far as the (second, the actual) burn stage when it pretends that it can't see the
> CD which is obviously in the Archos DEX DVD drive and which Windows explorer could see as being there and having a CD-R in it.
>
> I went to Control Panel, Administrative Tools, Services, Double-clicked "IMAPI CD Burning", clicked Start, and set "Startup type"
> as "Manual" (or
> "Automatic") Neither made any difference.
>
> The burn feature puts an icon in startup tray telling me that there are files waiting to be written to CD and then when I name the
> file on the CD which Windows Explorer identifies as a fit and proper CD, it tells me that there is still no CD in writer. On one
> CD, Explorer even identifies a few small files which were already
> written to it on one of the CDs I tried. It even pretends it is going to burn them in the next step or so:
>
> It is at that stage that the OS suddenly thinks that, - although it can see the drive, - there is no disc in that drive.
>
> (There is nothing, obviously, in Device Manager about the driver being wrong or the device having anything wrong with it)..
>
>
>
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.embedded,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.setup_deployment (More info?)

Try Nero 6.6 to see if it makes a difference and be sure to have Easy CD 5
uninstalled.

http://ww2.nero.com/enu/index.html



"news.microsoft.com" <fountainpen@amexol.net> wrote in message
news:eh4osJSZFHA.2664@TK2MSFTNGP15.phx.gbl...
> Having just installed SP2, I cant get the CD burn feature to work. I
> dont think SP2 is relevant, - I didnt enable or use this feature before I
> installed it, I used Easy CD Creator 5 which wont work with SP2 so I
> uninstalled it, installed Nero 5 which wouldnt work either (because it is
> I THINK an OEM version), uninstalled that and applied the registry patch
> when all my CD drives disappeared.
>
> The problem is that the burning process gets as far as the (second, the
> actual) burn stage when it pretends that it can't see the CD which is
> obviously in the Archos DEX DVD drive and which Windows explorer could see
> as being there and having a CD-R in it.
>
> I went to Control Panel, Administrative Tools, Services, Double-clicked
> "IMAPI CD Burning", clicked Start, and set "Startup type" as "Manual" (or
> "Automatic") Neither made any difference.
>
> The burn feature puts an icon in startup tray telling me that there are
> files waiting to be written to CD and then when I name the file on the CD
> which Windows Explorer identifies as a fit and proper CD, it tells me that
> there is still no CD in writer. On one CD, Explorer even identifies a few
> small files which were already
> written to it on one of the CDs I tried. It even pretends it is going to
> burn them in the next step or so:
>
> It is at that stage that the OS suddenly thinks that, - although it can
> see the drive, - there is no disc in that drive.
>
> (There is nothing, obviously, in Device Manager about the driver being
> wrong or the device having anything wrong with it)..
>
>
>
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.embedded,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.setup_deployment (More info?)

I have an app running under XPE which burns CDs using the IMAPI
interface, so I know it's possible. It's likely that your CD burning
app (sounds like you are trying to use Nero 5) is using some OS feature
that your XPE configuration doesn't include.

For example, I had problems using the Shell interface ICDBurn
(GetRecorderDriverLetter() function) in my app since I hadn't included
all of the shell components. Also, I've had interesting problems with
some 3rd party apps that don't work well without Winlogon (instead of
Minlogon). Even more strange, some XP services require Terminal
Services, since they make calls such as WTSEnumerateSessions to get
access to the active session (i.e., when fast user switching is
enabled)!

Resolving problems with a 3rd party app under XPE can be tricky, since
you have to determine which XPE components the app (for which you
probably don't have the source code) are required. There are several
tactics you can use: you can attempt to figure out directly which APIs
are required (using tools such as Depends, FileMon, etc.) *or* you can
use a trial-and-error approach (keep adding components until the app
works.)
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.embedded,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.setup_deployment (More info?)

> Try Nero 6.6 to see if it makes a difference and be sure to have Easy CD 5
> uninstalled.

I don't have Nero 6.6: I have tried Burnatonce which also doesn't work.

Does this mean that I can't use the XP embedded feature and if so, does
anyone know why?
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.embedded,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.setup_deployment (More info?)

sounds like you are trying to use Nero 5)

interesting problems with
> some 3rd party apps that don't work well without

No, all I am trying to do is use the embedded burning app in XP. Archos
(which provided me with easy cd creator, - which I have now deleted as it
doesn't work with SP2), said just to use the embedded burning feature in XP.

Am still trying to use the embedded feature but I am wondering if I should
install a Sony SCSI burning app which came with the drive in the interim (CD
Extreme) or will this cause more problems than it might solve? Especially if
IT doesn't work with SP2 (Sony wont say if it will or wont)
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.embedded,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.setup_deployment (More info?)

Download the trial version of Nero from the following link :) Just see if
it helps.

http://ww2.nero.com/enu/index.html



"news.microsoft.com" <fountainpen@amexol.net> wrote in message
news:eBY62RiZFHA.580@TK2MSFTNGP15.phx.gbl...
>
> sounds like you are trying to use Nero 5)
>
> interesting problems with
>> some 3rd party apps that don't work well without
>
> No, all I am trying to do is use the embedded burning app in XP. Archos
> (which provided me with easy cd creator, - which I have now deleted as
> it doesn't work with SP2), said just to use the embedded burning feature
> in XP.
>
> Am still trying to use the embedded feature but I am wondering if I should
> install a Sony SCSI burning app which came with the drive in the interim
> (CD Extreme) or will this cause more problems than it might solve?
> Especially if IT doesn't work with SP2 (Sony wont say if it will or wont)
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.embedded,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.setup_deployment (More info?)

> Download the trial version of Nero from the following link :) Just see if
> it helps.
>
> http://ww2.nero.com/enu/index.html

Well that SEEMED like a good idea but downloading Nero Burning CD ROM
created an app on my system called NEROMIX which doesnt seem to burn CDs
(except possibly music files which it does seem to play). The Ahead site is
exceptionally confusing with buttons leading down dark paths and not giving
either they describe or what you need.

So I cant really tell whether this assisted at all or not. Surely there is
a better way of testing what is wrong with the embedded CD burning feature
of XP? I have already downloaded burnatonce (wihch didn't work either)
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.embedded,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.setup_deployment (More info?)

Sorry, I had thought the trial version included the toolkit which apparently
it doesn't anylonger. Your CD seems to me to be having driver conflicts so
a couple things you can do is 1.) download and install the latest driver for
your CD from the manufacturers site. 2.) run Nero's driver and registry
cleaning tool after uninstalling all burn programs (link belolw) 3.)
uninstall your CD in device manager and reboot. Upon reload, windows will
reinstall the CD with the new driver and you should have better operation.
Also, NeroMix has a preference menu that allows setting input and output
devices. I'm unfamiliar with this program but from there you may be able to
set and test your CD from.

http://www.nero.com/en/Driver_Clean_Tool_and_RegistryChecker.html
http://www.nero.com/en/NeroMIX_QuickStart_Guide.html

hope this helps..



"news.microsoft.com" <fountainpen@amexol.net> wrote in message
news:ODIwV6lZFHA.3648@TK2MSFTNGP14.phx.gbl...
>> Download the trial version of Nero from the following link :) Just see
>> if it helps.
>>
>> http://ww2.nero.com/enu/index.html
>
> Well that SEEMED like a good idea but downloading Nero Burning CD ROM
> created an app on my system called NEROMIX which doesnt seem to burn CDs
> (except possibly music files which it does seem to play). The Ahead site
> is exceptionally confusing with buttons leading down dark paths and not
> giving either they describe or what you need.
>
> So I cant really tell whether this assisted at all or not. Surely there
> is a better way of testing what is wrong with the embedded CD burning
> feature of XP? I have already downloaded burnatonce (wihch didn't work
> either)
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.embedded,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.setup_deployment (More info?)

I've encountered the same problem actually. It happened when I integrated a
registry change into my build which disabled all autoplay features. An
adverse side effect was the system would no longer recognize when a blank
writeable cd was in the drive, unless that cd was present at bootup. The
registry key was:

H_KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Cdrom\Autorun

If it is set to 0 autorun is disabled, set it to 1 to re-enable it and see
if your problem persists. If it was already set to 1, then I'm at a loss.
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.embedded,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.setup_deployment (More info?)

I think this is getting closer to the real problem here, though I Have no
other problems with the CD drive or any autorun feature: The point is that
the embedded burning feature doesn't even look at the CD device (which is as
I say working properly)

It goes, in a millisecond, straight to the erroneous NO DISK IN DRIVE error
report. It simply doesnt check anything.

Then today I tried to run iTunes and was given an error message telling me
that some CD burning software had made some change to the registry so that
iTunes could no longer read CDs and would I just reinstall iTunes to correct
this mistake

I can't help but feel that this is somehow relevant? Surely there is some
MVP out there somewhere who knows how to search the MS Knowledge base to
identify what would do this? There is probably an MS Patch somewhere for it
as well.

Does anyone think it would help if I posted to EVEN MORE Microsoft
newsgroups?

"RHughes" <RHughes@discussions.microsoft.com> wrote in message
news:A5E147D6-E5FF-4517-8B62-37A524B2275E@microsoft.com...
> I've encountered the same problem actually. It happened when I integrated
> a
> registry change into my build which disabled all autoplay features. An
> adverse side effect was the system would no longer recognize when a blank
> writeable cd was in the drive, unless that cd was present at bootup. The
> registry key was:
>
> H_KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Cdrom\Autorun
>
> If it is set to 0 autorun is disabled, set it to 1 to re-enable it and see
> if your problem persists. If it was already set to 1, then I'm at a loss.
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.embedded,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.setup_deployment (More info?)

As I said, you're describing the exact issue I ran across. The system would
not check to see that there was in fact a writable cd in the drive, and throw
up an error as a result. Have you checked the registry key I posted earlier?
If for nothing more than my own curiosity I'd like to know how it is set.


"news.microsoft.com" wrote:

> I think this is getting closer to the real problem here, though I Have no
> other problems with the CD drive or any autorun feature: The point is that
> the embedded burning feature doesn't even look at the CD device (which is as
> I say working properly)
>
> It goes, in a millisecond, straight to the erroneous NO DISK IN DRIVE error
> report. It simply doesnt check anything.
>
> Then today I tried to run iTunes and was given an error message telling me
> that some CD burning software had made some change to the registry so that
> iTunes could no longer read CDs and would I just reinstall iTunes to correct
> this mistake
>
> I can't help but feel that this is somehow relevant? Surely there is some
> MVP out there somewhere who knows how to search the MS Knowledge base to
> identify what would do this? There is probably an MS Patch somewhere for it
> as well.
>
> Does anyone think it would help if I posted to EVEN MORE Microsoft
> newsgroups?
>
> "RHughes" <RHughes@discussions.microsoft.com> wrote in message
> news:A5E147D6-E5FF-4517-8B62-37A524B2275E@microsoft.com...
> > I've encountered the same problem actually. It happened when I integrated
> > a
> > registry change into my build which disabled all autoplay features. An
> > adverse side effect was the system would no longer recognize when a blank
> > writeable cd was in the drive, unless that cd was present at bootup. The
> > registry key was:
> >
> > H_KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Cdrom\Autorun
> >
> > If it is set to 0 autorun is disabled, set it to 1 to re-enable it and see
> > if your problem persists. If it was already set to 1, then I'm at a loss.
> >
> >
>
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.embedded,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.setup_deployment (More info?)

We are definitely on the right path, though this particular key is set to
REG_DWORD 0x00000001 (1) as you suggest it should be.

But clearly something in the registry such as this is exactly what is
causing the burn feature to not make the app look to the drive before
telling me that there isn't a disc in it.

And suddenly iTunes has started acting erratically: First it wouldn't see a
drive and demanded reinstallation of the software which I did. Now it wont
read from the CD and import the tracks to iTunes library: It only looks at
and imports the track identification, not the track itself. And along the
way before it started developing this problem, it read half a CD and then
started telling me that it could import Track 15 no longer as there was
suddenly no disc in the drive!!

Whatever is affecting the burn feature is now also affecting iTunes

Surely there is some software somewhere for checking the registry?

H_KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Cdrom\Autorun
>> >
>> > If it is set to 0 autorun is disabled, set it to 1 to re-enable it and
>> > see
>> > if your problem persists. If it was already set to 1, then I'm at a
>> > loss.
>> >
>> >
>>
>>
>>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.embedded,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.setup_deployment (More info?)

I also have this same exact problem on about 50 computers. Our OS install is
fresh and the systems are brand new. We added the writeable drives after
installation and the first problem was that none were seen as "Recorders". So
I edited the registry
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\CD Burning\Drives and
on the appropriate drive, change the value to 2.

This enabled the "Recorder" tab in drive Properties and I was able to select
Enable there. But still now when I "write these files" to the blank CD, I
receive a message stating there is not a blank CD in the drive. But there is,
and we've tried several different vendors of media.

I know I can install a third party software but we are on a AD site and we
don't want to have to install the software for everyone. Besides that, the
built in burning app should work. And I just have to know why it doesn't :)

So if anyone has any more ideas, please feel free to post them!

"news.microsoft.com" wrote:

> We are definitely on the right path, though this particular key is set to
> REG_DWORD 0x00000001 (1) as you suggest it should be.
>
> But clearly something in the registry such as this is exactly what is
> causing the burn feature to not make the app look to the drive before
> telling me that there isn't a disc in it.
>
> And suddenly iTunes has started acting erratically: First it wouldn't see a
> drive and demanded reinstallation of the software which I did. Now it wont
> read from the CD and import the tracks to iTunes library: It only looks at
> and imports the track identification, not the track itself. And along the
> way before it started developing this problem, it read half a CD and then
> started telling me that it could import Track 15 no longer as there was
> suddenly no disc in the drive!!
>
> Whatever is affecting the burn feature is now also affecting iTunes
>
> Surely there is some software somewhere for checking the registry?
>
> H_KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Cdrom\Autorun
> >> >
> >> > If it is set to 0 autorun is disabled, set it to 1 to re-enable it and
> >> > see
> >> > if your problem persists. If it was already set to 1, then I'm at a
> >> > loss.
> >> >
> >> >
> >>
> >>
> >>
>
>
>