Okay I am baffled.

I am running Suse, fresh install.

Let me first state that I have run Suse prior to this problem on my laptop (still newbie) and I was able to get Cedga running, up to the point of a video driver conflict. I am now trying Suse on my desktop PC.

Anyway my problem I first thought was with Cedga not working properly but in fact Suse is the culpret. I have no idea whats going on, but when I stick a CD "starcraft" in the drive (I have tried two different drives) I dont see the correct files on the CD. I have tried various ways of viewing the contents such as from 'My Computer', /dev/cdrecorder, or /media/cdrecorder. All show the same odd incorrect files.

Let me show you a comparison to what is seen in Windows and what is seen in Suse. I will also note this exact same CD reads perfectly on my laptop (running Suse as well).

Windows CD contents:
DIRECTX5
AUTORUN.INF
INSTALL.EXE
SC.ICO
SETUP.EXE
SMACK32.DLL
STARCRAFT.PDF

SUSE CD contents:
Desktop Folder
TheVolumeSettings Folder
Trash
Desktop DB
Desktop DF
Preview
Starcraft Archive
Starcraft Installer
Starcraft Manual.pdf

From what I can tell it seems almost as if the cd drive is listing my desktop only those files are not seen on my desktop except for trash. This leads me to believe that some how Suse is symbolicly linking my CD drive to some other location?

Does anyone know what I can try, or turn off to stop this from happening? This is really annoying and pretty much defeats the purpose of having a CD-ROM drive.

Please let me know your thoughts.
Thanks

Anyone?

Which version of suse are you using????
Can you show me your fstab file????? It's on /etc/
Have you tried with other cd?????

Okay

My version: SUSE 9.3 Professional (KDE Desktop)

FSTAB INFO:

cat /etc/fstab
/dev/hda2 / reiserfs acl,user_xattr 1 1
/dev/hda1 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/hdd1 /windows/D ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/hda3 swap swap pri=42 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
sysfs /sys sysfs noauto 0 0
/dev/cdrecorder /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0

Have I tried with another CD?

YES, I put in my Driver CD for my digital camera.
Contents are:
Network Trash Folder
PEX 2.0
PEX 2.0F
PEX 2.0G
PEX 2.0l
PEX 2.0J
PEX 2.0P
PEX 2.05
TheVolumeSettingsFolder <--also found on the StarCraft CD
Trash <-- Also found on the StarCraft CD
Desktop DB <-- Also found on the StarCraft CD
Desktop DF <-- Also found on the StarCraft CD

The PEX folders are probably the driver folders, I'm just taking a guess as I havnt checked it in Windows.


I will also note I have tried reinstalling while I waited for a response, with just the default packages incase it was some 'feature' I installed. Still no luck.

Please let me know,
Thanks

Edit your fstab file as root, and erase the 'noauto' option from the cdrecorder line. Like this:
Hope this work-

Sorry, right after you edit 'fstab' you have to restart your computer.

Hello,

I tried what you said and it seemed to work. YAY!

Only I have a new problem (not a result of changing the fstab). I have tried reinstalling about 4 or 5 times now trying to fix this crash that seems to happen. See when ever I reboot or shutdown the system will not load the GUI properly... instead it will load some sort of extreme minimal interface, which is slightly more than the command prompt but only has very basic tools and like grey and green colors. No textures or anything. This problem is new, my system didnt used to do this when I shutdown the first time I installed SUSE. It's only started happening recently.

Now I have tried loading SUSE Failsafe and I am able to type 'startx' and load the GUI fine. Thats how I was able to see the new fstab settings working. Any ideas?

Hope you can help,

Thanks a lot for all your help

You are welcome!!!!

Sorry, but i don't know what can you do to fix this new error.

Create a new thread with this error, maybe someone have the answer to your problem.

Good luck!!!!!!!!