IOCTL_CDROM_GET_CONFIGURATION with FeatureProfileList

NTDEV
1

Hi All
I am writing a filter driver for CD-ROM and would like to understand the
output that is returned for IOCTL_CDROM_GET_CONFIGURATION. All the
features are reported according to the documentation except
feature 0x0 - FeatureProfileList. As far as I know, the output should
contain the FEATURE_DATA_PROFILE_LIST structure, but the profiles that
appear in the list are illegal. Is there any way to understand the
output for this feature?
Thanks,
Gregory

2

Hello Gregory,

This ioctl is a wrapper around the mmc get configuration command. For
extensive documentation about get configuration, including profiles, check
the mmc specification from t10 - the draft is free for download

Take the revision 4:

MultiMedia Command Set - 4 (MMC-4)
{Date: 2005/05/04, Rev: 05a, Status: INCITS Approval, Project: 1545-D, File:
mmc4r05a.pdf (3502318 bytes)}
MMC-4 describes the fourth-generation command set for multi-media devices.
It has the next major inclusion of support for DVD: +R, +MRW and was
rewritten to update the standard according to field behaviour.

MMC-5 is only in development and not yet suitable for software
implementation use.

Best regards,

David Burg

David Burg
Software Development

Nero AG
Im Stoeckmaedle 18 fax: +49 (0)7248 928 299
76307 Karlsbad email: xxxxx@nero.com
Germany http://www.nero.com

Subject: IOCTL_CDROM_GET_CONFIGURATION with FeatureProfileList
From: Gregory Dardyk
Date: Tue, 26 Jul 2005 12:43:19 +0200
X-Message-Number: 3

Hi All
I am writing a filter driver for CD-ROM and would like to understand the
output that is returned for IOCTL_CDROM_GET_CONFIGURATION. All the
features are reported according to the documentation except
feature 0x0 - FeatureProfileList. As far as I know, the output should
contain the FEATURE_DATA_PROFILE_LIST structure, but the profiles that
appear in the list are illegal. Is there any way to understand the
output for this feature?
Thanks,
Gregory

----------------------------------------------------------------------

3

Hi Gregory,

You are correct – the output should indeed be a
FEATURE_DATA_PROFILE_LIST. As you know, all output has the
GET_CONFIGURATION_HEADER first, so it bytes should look something like:

00000000 - 00 00 00 30 - …0 // Data length = 0x0030
00000004 - 00 00 00 0A - … // Current Profile = 0x000A
00000008 - 00 00 03 28 - …( // Feature Code = 0x0000, Length =
0x28 (+4)
0000000C - 00 2B 00 00 - .+… // Profile 0x002B (not current)
00000010 - 00 1B 00 00 - … // Profile 0x001B (not current)
00000014 - 00 1A 00 00 - … // Profile 0x001A (not current)
00000018 - 00 14 00 00 - … // Profile 0x0014 (not current)
0000001C - 00 13 00 00 - … // Profile 0x0013 (not current)
00000020 - 00 11 00 00 - … // Profile 0x0011 (not current)
00000024 - 00 10 00 00 - … // Profile 0x0010 (not current)
00000028 - 00 0A 01 00 - … // Profile 0x000A ( CURRENT )
0000002C - 00 09 00 00 - … // Profile 0x0009 (not current)
00000030 - 00 08 00 00 - … // Profile 0x0008 (not current)

Can you give an example of what you are seeing, what byte ranges you
don’t believe are correct, and what you would expect to see in those
ranges (if not obvious)?

Thanks,
.

-----Original Message-----
From: Gregory Dardyk [mailto:xxxxx@safend.com]
Sent: Tuesday, July 26, 2005 3:43 AM
Subject: IOCTL_CDROM_GET_CONFIGURATION with FeatureProfileList

Hi All
I am writing a filter driver for CD-ROM and would like to understand the
output that is returned for IOCTL_CDROM_GET_CONFIGURATION. All the
features are reported according to the documentation except
feature 0x0 - FeatureProfileList. As far as I know, the output should
contain the FEATURE_DATA_PROFILE_LIST structure, but the profiles that
appear in the list are illegal. Is there any way to understand the
output for this feature?
Thanks,
Gregory