Trying to figure out a CD_ROM problem
 

To set up my problem, I'll mention that I am using an old Dell Studio 1537 laptop running Manjaro (which brought life back to this old machine!)

So, I was trying to install Simcity 4 Deluxe using Wine, which is a two disk install. It would go through the install fine, until wanting the second disk. I would get the first disk ejected, put the second disk in and....nothing. I would look in the file manager and that disk is not there, at all. I would quit the install and the disk is still not showing in the file manager. I would push the physical eject button on the laptop and nothing. The only way I could eject the disk was to use 'eject' in terminal. I then rebooted the machine and just put that second disk in and...nothing. It does not show up at all to be mounted, and again, the only way to eject was in terminal. Other disks would mount and show up fine, even installing Windows software in Wine, so, I figured the drive is working ok. Thinking that the disk itself is bad, I put it in a Windows machine and there was no problems looking at the files on the disk there.

Of course, I left the laptop at home and am writing this at work (sometimes I am a real bonehead), but I would appreciate any help and also your patience as I will have to wait till later to try any ideas presented.

Thanks

Hi....

From Allen Choong's blog (credit goes to him)...

"1. Firstly, run the winecfg.
2. Go to Drives tab.
3. Click Show Advanced button.
4. Click Add, for example, add a D: drive.
5. Now, we can Browse the path of our mounted ISO images.
6. The important part is the Type:, we need to change to CD-ROM.
7. Apply."

Hopefully, that resolves the issue. :)

Regards...

Yes, I'll try that. But it still confuses me why the disk wouldn't mount at all without trying to install, while other disks would.

Yes, I'll try that. But it still confuses me why the disk wouldn't mount at all without trying to install, while other disks would.

Perhaps it has a non-standard filesystem that Linux doesn't know how to handle? Just guessing.

Looking into the kernel message buffer right after you insert the disk (dmesg command, or /var/log/syslog(?) file) should provide clues.