cannot see or access CD-ROM drive

[Slobodan Brcin \(eMVP\)]

Hi Ann,

devcon.exe can be used to reenumerate hardware.

Usually if you did not previously used similar type of hardware it should install automatically. But sometime certain existing
values in registry can make problems in this case deleting them from offline registry is the one way I know of. Then during the boot
PnP will find new hardware and do clean install.

Best regards,
Slobodan

 

[Slobodan Brcin \(eMVP\)]

Hi Ann,

I do not know why you see these errors, but have you:
1. Resolved all dependencies?
2. What service pack and QFE components do you use?
3. setupapi.log contain usually more information's than FBAlog with these kind of problems.

Regards,
Slobodan

I did not have those.

Here are some interesting sections I found in FBAlog.txt:

1:23:29 AM - [PnpEnumThread: InstallDevice] SetupDiCallClassInstaller
Error: 0xe0000217, Device: Microsoft ACPI-Compliant Embedded Controller
.
.
.
1:24:09 AM - [FBAAddDevInstanceId]
PCI\VEN_8086&DEV_1079&SUBSYS_10798086&REV_03\5&A1F36AB&0&210210
1:24:14 AM - [FBAAddDevInstanceId]
IDE\CDROMMITSUMI_CD-ROM_SR244W___________________T01A____\5&20AE57A1&0&0.1.0
1:24:15 AM - [InstallEnumeratedDevices] SetupDiCallClassInstaller Error:
0xe000020d
1:24:15 AM - [FBAAddDevInstanceId]
PCI\VEN_8086&DEV_1079&SUBSYS_10798086&REV_03\5&A1F36AB&0&200210
1:24:19 AM - [FBAAddDevInstanceId]
SCSI\DISK&VEN_SEAGATE&PROD_ST336607LC&REV_0006\6&16BB7547&0&000
1:24:19 AM - [InstallEnumeratedDevices] SetupDiCallClassInstaller Error:
0xe000020d
1:24:19 AM - [FBAAddDevInstanceId]
SCSI\PROCESSOR&VEN_ESG-SHV&PROD_SCA_HSBP_M17&REV_1.00\6&16BB7547&0&060
1:24:35 AM - [FBAAddDevInstanceId] USB\ROOT_HUB\4&AA4272E&0
1:24:36 AM - [FBAAddDevInstanceId] USB\ROOT_HUB\4&24434A96&0
1:24:36 AM - [FBASkipDevice] USB\ROOT_HUB\4&AA4272E&0
1:24:36 AM - [FBASkipDevice]
IDE\CDROMMITSUMI_CD-ROM_SR244W___________________T01A____\5&20AE57A1&0&0.1.0
1:24:36 AM - [FBAAddDevInstanceId] USB\ROOT_HUB\4&33DAAAF6&0
1:24:37 AM - [FBASkipDevice] USB\ROOT_HUB\4&24434A96&0
1:24:37 AM - [FBASkipDevice] USB\ROOT_HUB\4&AA4272E&0
1:24:37 AM - [FBAAddDevInstanceId] USB\ROOT_HUB20\4&3176BA1E&0
1:24:38 AM - [FBAAddDevInstanceId]
DISPLAY\DEFAULT_MONITOR\5&1C603F11&0&80000000&05&0C
1:24:39 AM - [FBASkipDevice]
IDE\CDROMMITSUMI_CD-ROM_SR244W___________________T01A____\5&20AE57A1&0&0.1.0
1:24:39 AM - [FBASkipDevice]
IDE\CDROMMITSUMI_CD-ROM_SR244W___________________T01A____\5&20AE57A1&0&0.1.0
1:24:39 AM - [FBAAddDevInstanceId] FDC\GENERIC_FLOPPY_DRIVE\5&35AD0CB2&0&0
1:24:55 AM - [FBALaunch] rundll32.exe
C:\WINDOWS\system32\sti_ci.dll,InstallWiaService (ExitCode: 0x0)
1:24:55 AM - [LegacyInstallThread] SetupDiCallClassInstaller Error:
0xe000020d, Class: [DVD/CD-ROM drives]
1:24:55 AM - [LegacyInstallThread] SetupDiCallClassInstaller Error:
0xe000020d, Class: [Disk drives]
1:24:56 AM - [LegacyInstallThread] SetupDiCallClassInstaller Error:
0xe000020d, Class: [Ports (COM & LPT)]
1:24:56 AM - [FBAAddDevInstanceId] ACPI\PNP0501\1
.
.
.
There definitely seems to be a problem with the CD. As I said, it works
just fine on a regular XP Pro boot on the same machine.

Ann

Hi Ann,

If you have El-torito support and El-torito CD please remove it from XPe build.

Best regards,
Slobodan

 

[KM]

Ann,

"devcon rescan" ?

 

[Ann Adamson]

I meant in my distributed image -- I'm not allowed to redistribute
devcon.exe.

If I plug in a USB Hard Drive in the field, will it automatically be
detected without rebooting?

 

[Ann Adamson]

1. Yes
2. SP1 + QFE's
3. I will have a look at that one next time.

Ann

Hi Ann,

I do not know why you see these errors, but have you:
1. Resolved all dependencies?
2. What service pack and QFE components do you use?
3. setupapi.log contain usually more information's than FBAlog with these kind of problems.

Regards,
Slobodan

I did not have those.

Here are some interesting sections I found in FBAlog.txt:

1:23:29 AM - [PnpEnumThread: InstallDevice] SetupDiCallClassInstaller
Error: 0xe0000217, Device: Microsoft ACPI-Compliant Embedded Controller
.
.
.
1:24:09 AM - [FBAAddDevInstanceId]
PCI\VEN_8086&DEV_1079&SUBSYS_10798086&REV_03\5&A1F36AB&0&210210
1:24:14 AM - [FBAAddDevInstanceId]
IDE\CDROMMITSUMI_CD-ROM_SR244W___________________T01A____\5&20AE57A1&0&0.1.0
1:24:15 AM - [InstallEnumeratedDevices] SetupDiCallClassInstaller Error:
0xe000020d
1:24:15 AM - [FBAAddDevInstanceId]
PCI\VEN_8086&DEV_1079&SUBSYS_10798086&REV_03\5&A1F36AB&0&200210
1:24:19 AM - [FBAAddDevInstanceId]
SCSI\DISK&VEN_SEAGATE&PROD_ST336607LC&REV_0006\6&16BB7547&0&000
1:24:19 AM - [InstallEnumeratedDevices] SetupDiCallClassInstaller Error:
0xe000020d
1:24:19 AM - [FBAAddDevInstanceId]
SCSI\PROCESSOR&VEN_ESG-SHV&PROD_SCA_HSBP_M17&REV_1.00\6&16BB7547&0&060
1:24:35 AM - [FBAAddDevInstanceId] USB\ROOT_HUB\4&AA4272E&0
1:24:36 AM - [FBAAddDevInstanceId] USB\ROOT_HUB\4&24434A96&0
1:24:36 AM - [FBASkipDevice] USB\ROOT_HUB\4&AA4272E&0
1:24:36 AM - [FBASkipDevice]
IDE\CDROMMITSUMI_CD-ROM_SR244W___________________T01A____\5&20AE57A1&0&0.1.0
1:24:36 AM - [FBAAddDevInstanceId] USB\ROOT_HUB\4&33DAAAF6&0
1:24:37 AM - [FBASkipDevice] USB\ROOT_HUB\4&24434A96&0
1:24:37 AM - [FBASkipDevice] USB\ROOT_HUB\4&AA4272E&0
1:24:37 AM - [FBAAddDevInstanceId] USB\ROOT_HUB20\4&3176BA1E&0
1:24:38 AM - [FBAAddDevInstanceId]
DISPLAY\DEFAULT_MONITOR\5&1C603F11&0&80000000&05&0C
1:24:39 AM - [FBASkipDevice]
IDE\CDROMMITSUMI_CD-ROM_SR244W___________________T01A____\5&20AE57A1&0&0.1.0
1:24:39 AM - [FBASkipDevice]
IDE\CDROMMITSUMI_CD-ROM_SR244W___________________T01A____\5&20AE57A1&0&0.1.0
1:24:39 AM - [FBAAddDevInstanceId] FDC\GENERIC_FLOPPY_DRIVE\5&35AD0CB2&0&0
1:24:55 AM - [FBALaunch] rundll32.exe
C:\WINDOWS\system32\sti_ci.dll,InstallWiaService (ExitCode: 0x0)
1:24:55 AM - [LegacyInstallThread] SetupDiCallClassInstaller Error:
0xe000020d, Class: [DVD/CD-ROM drives]
1:24:55 AM - [LegacyInstallThread] SetupDiCallClassInstaller Error:
0xe000020d, Class: [Disk drives]
1:24:56 AM - [LegacyInstallThread] SetupDiCallClassInstaller Error:
0xe000020d, Class: [Ports (COM & LPT)]
1:24:56 AM - [FBAAddDevInstanceId] ACPI\PNP0501\1
.
.
.
There definitely seems to be a problem with the CD. As I said, it works
just fine on a regular XP Pro boot on the same machine.

Ann

Hi Ann,

If you have El-torito support and El-torito CD please remove it from

XPe
build.

Best regards,
Slobodan

I do have those components, and my CD drive does show up as a volume in
diskpart when booted on XP Pro. I will double check the log files today.

Ann,

First of all, diskpart allows you to manage fixed (non-removable) disks
and
volumes.
Second, check your FBALog.txt - any errors there?

Also, make sure you've got "Class Installer - DVD/CD-ROM drives" and
"CoDevice Installer - DVD/CD-ROM drives" component included.

KM

I have a system running XPE with minlogon and command shell.
I think I have all the components I need to access the CD Rom

drive,
but

the
drive does not appear to
be there. If I run diskpart and do a 'list volume' the CD drive does
not
appear in the list.

Yes, I have:
CD-ROM Drive
CDFS
Primary IDE Channel
Secondary IDE Channel
PnP (User Mode)
Removable Storage Service
.
.
.
etc.

Any ideas?

Thanks,
Ann Adamson

 

[KM]

Ann,

It may.

You can always do your own "devcon" or some functions of the tools using WinDDK.
I don't think SetupDi APIs are good for the "scanning" functionality but CM_ APIs is the way to go (not recommended from DDK docs,
though).
E.g., try this code:

BOOL ScanForHardwareChanges()
{
DEVINST devInst;
CONFIGRET status;

//
// Get the root devnode.
//

status = CM_Locate_DevNode(&devInst, NULL, CM_LOCATE_DEVNODE_NORMAL);

if (status != CR_SUCCESS) {
printf("CM_Locate_DevNode failed: %x\n", status);
return FALSE;

}

status = CM_Reenumerate_DevNode(devInst, 0);

if (status != CR_SUCCESS) {
printf("CM_Reenumerate_DevNode failed: %x\n", status));
return FALSE;
}

return TRUE;
}

http://support.microsoft.com/defaul...port/kb/articles/Q259/6/97.ASP&NoWebContent=1

 

[Slobodan Brcin \(eMVP\)]

Hi Ann,

This is given in source that you can use. Find rescan function and make your program with it. (30-50 lines of code) basically
copy/paste job, build it and you have program.
This is it, but you did not tell us if devcon actually helped you, if not then it is irrelevant.

Best regards,
Slobodan

 

[Slobodan Brcin \(eMVP\)]

You gave same but more complete answer than me and more importantly before me. It looks bad for me ;-)

Regards,
Slobodan

 

[Ann Adamson]

I think I found the problem. I was working with a platform Macro component
that I generated by importing the TAP .pmq file from my machine. When it
imports the .pmq, the CD Rom matches up with the Component "CD-ROM Drive".
However, there are like 15 of these components in the database. The one
that gets pulled in is "CD-ROM Drive [Version 5.1.2600,R620]" but there are
a bunch of others "CD-ROM Drive [Version 5.1.2600.1106,R1806]". All these
seperate ones, if you look at them, have different Concordance ID's but the
same PnPID. Weird. Anyway, when I boot with just this one device component
it pulls in, it seems like the OS cannot find a match for my Mitsumi CD-ROM.
I haven't dug down to decipher why the "Mitsumi CD-ROM Drive" component was
not matched when I imported the .pmq, but I've since added it manually, and
I hope this resolves the problem.

But, why the 14 or 15 different standard "CD-ROM Drive" Components? These
all appear to come from the SP1 repository, and they all reference the same
files. It seems like to get fairly generic CD support, you'd have to pull
them all in so you can be assured to get a match.

A REAL problem is that in Component Designer, I can't see the details on the
PnPID's or Concordance ID's when I try to select a CD-ROM device (or any
other device) entry when adding a dependency, so there isn't even a good way
to make sure I'm getting what I need!! Ughh!

Ann

 

[Slobodan Brcin \(eMVP\)]

Hi Ann,

But, why the 14 or 15 different standard "CD-ROM Drive" Components? These
all appear to come from the SP1 repository, and they all reference the same
files. It seems like to get fairly generic CD support, you'd have to pull
them all in so you can be assured to get a match.

I cried and yelled but almost nobody listened about this. Whole concept with automatic componentizing drivers from inf files is
"little" wrong. One inf file should produce one component but instead it usually yield one component per different device ID. And
the best part of this is that all these component are usually same.

If you are interested in topic you can read thread:
http://groups.google.com/groups?hl=...f=1&selm=#78YE#[email protected]

And you can give your comments on the topic.

Best regards,
Slobodan

I think I found the problem. I was working with a platform Macro component
that I generated by importing the TAP .pmq file from my machine. When it
imports the .pmq, the CD Rom matches up with the Component "CD-ROM Drive".
However, there are like 15 of these components in the database. The one
that gets pulled in is "CD-ROM Drive [Version 5.1.2600,R620]" but there are
a bunch of others "CD-ROM Drive [Version 5.1.2600.1106,R1806]". All these
seperate ones, if you look at them, have different Concordance ID's but the
same PnPID. Weird. Anyway, when I boot with just this one device component
it pulls in, it seems like the OS cannot find a match for my Mitsumi CD-ROM.
I haven't dug down to decipher why the "Mitsumi CD-ROM Drive" component was
not matched when I imported the .pmq, but I've since added it manually, and
I hope this resolves the problem.

But, why the 14 or 15 different standard "CD-ROM Drive" Components? These
all appear to come from the SP1 repository, and they all reference the same
files. It seems like to get fairly generic CD support, you'd have to pull
them all in so you can be assured to get a match.

A REAL problem is that in Component Designer, I can't see the details on the
PnPID's or Concordance ID's when I try to select a CD-ROM device (or any
other device) entry when adding a dependency, so there isn't even a good way
to make sure I'm getting what I need!! Ughh!

Ann

I have a system running XPE with minlogon and command shell.
I think I have all the components I need to access the CD Rom drive, but the
drive does not appear to
be there. If I run diskpart and do a 'list volume' the CD drive does not
appear in the list.

Yes, I have:
CD-ROM Drive
CDFS
Primary IDE Channel
Secondary IDE Channel
PnP (User Mode)
Removable Storage Service
.
.
.
etc.

Any ideas?

Thanks,
Ann Adamson

 

[Ann Adamson]

I will take a look. It is kind of a nightmare, and, as I said, the tools
are not very friendly to this.

I'm also going to post another issue/concern on a seperate thread about
importing .pmqs with Target Designer vs. Component Designer -- they often
produce different results, which is nightmarish!

Hi Ann,


I cried and yelled but almost nobody listened about this. Whole concept

with automatic componentizing drivers from inf files is

"little" wrong. One inf file should produce one component but instead it

usually yield one component per different device ID. And

the best part of this is that all these component are usually same.

If you are interested in topic you can read thread:
http://groups.google.com/groups?hl=...f=1&selm=#78YE#[email protected]

And you can give your comments on the topic.

Best regards,
Slobodan

I think I found the problem. I was working with a platform Macro component
that I generated by importing the TAP .pmq file from my machine. When it
imports the .pmq, the CD Rom matches up with the Component "CD-ROM Drive".
However, there are like 15 of these components in the database. The one
that gets pulled in is "CD-ROM Drive [Version 5.1.2600,R620]" but there are
a bunch of others "CD-ROM Drive [Version 5.1.2600.1106,R1806]". All these
seperate ones, if you look at them, have different Concordance ID's but the
same PnPID. Weird. Anyway, when I boot with just this one device component
it pulls in, it seems like the OS cannot find a match for my Mitsumi CD-ROM.
I haven't dug down to decipher why the "Mitsumi CD-ROM Drive" component was
not matched when I imported the .pmq, but I've since added it manually, and
I hope this resolves the problem.

But, why the 14 or 15 different standard "CD-ROM Drive" Components? These
all appear to come from the SP1 repository, and they all reference the same
files. It seems like to get fairly generic CD support, you'd have to pull
them all in so you can be assured to get a match.

A REAL problem is that in Component Designer, I can't see the details on the
PnPID's or Concordance ID's when I try to select a CD-ROM device (or any
other device) entry when adding a dependency, so there isn't even a good way
to make sure I'm getting what I need!! Ughh!

Ann

I have a system running XPE with minlogon and command shell.
I think I have all the components I need to access the CD Rom drive,

but
the

drive does not appear to
be there. If I run diskpart and do a 'list volume' the CD drive does not
appear in the list.

Yes, I have:
CD-ROM Drive
CDFS
Primary IDE Channel
Secondary IDE Channel
PnP (User Mode)
Removable Storage Service
.
.
.
etc.

Any ideas?

Thanks,
Ann Adamson

 

[KM]

Aha! And this is considering your a more "platform" guy than me
Seriously, I seem to have gotten faster Internet connection here

 

[Slobodan Brcin \(eMVP\)]

Seriously, I seem to have gotten faster Internet connection here

Yes and we all know how N times faster Internet connection is very important for text posts

Regards,
Slobodan

 

[KM]

Ha Got your sarcasm
I was actually referring to the search and other good tools.

Konstantin