Not sure what you mean.
describe what your trying to do....
If you want some details to help out here is some info.
In Unix-style OSes everything is a file, hardware resources are no exception. On your computer you have some special files called device files. These reside in the /dev/ directory and represent different things. For instance /dev/zero is a file of infinate zeros, /dev/urandom is a file of infinate random information. /dev/null is a black hole, anything you put in /dev/null will be gone forever.
Well you have files that represent your IDE devices, usually harddrives and cdroms, but can be zip drives or other things that are connected to the IDE controllers.. These are /dev/hd## files. /dev/hda = primary master, /dev/hdb = primary slave, /dev/hdc = secondary master, /dev/hdd = secondary slave.
Usually cdrom drives are detected at install and have symbolic links (like a shortcut) from /dev/cdrom to the /dev/hd# file that they are represented by. But sometimes it doesn't work out that way perfectly.
In order to access a file you have "mount" it. This makes a filing system (wiether it be on a harddrive, cdrom, zip, floppy, or network share) a part of your overall directory system.
Usually the command would go like this:
mount /dev/hdc /cdrom
Some distros make a /cdrom directory or a /mnt/cdrom directory or just /mnt for you to use, but any empty directory can be used to mount a filing system to.
Mandrake uses automount system to try to automate it.
Either way the default mount points are controlled by the /etc/fstab configuration file. That file is how the OS knows which drive is which and the details on how and when to mount files.
It's hard to say which thing isn't working for you. I am not that familar with Mandrake's specific idosicrosies. However I would try to login as root and try to automount the cdrom that way.
(although as a rule you don't use Root unless you realy realy have to. For instance if you ment to type "rm -rf ./*" clear out a directory and you typed out "rm -rf /" instead, you wipe out your entire OS, and their is NO way to recover from that. also their is security issues.)
If logging in as root doesn't help, then manually mount the device with the mount command should do it.