USB CD Support

It sounds like it will be easier that ethernet was so you shouldn’t need to jump through all the hoops I did. Be interesting to see how it performs.

A quick heads up before I go to bed…

During the maybe most productive day in hubersn Software development history, I finally managed to get my BeagleBoard in action. With the help of the excellent Wiki article “How to get started with a BeagleBoard”, it is really easy – there were two or three minor niggles in the description which I will fix ASAP.

Having a running BeagleBoard, I decided to try out CDFS and the CDFaker module. And since I didn’t have an isoimage to mount, I also decided to try to get CDVDBurn on the BeagleBoard to create one. The surprise was that everything worked. CDVDBurn created an isoimage of my complete BeagleBoard boot USB stick (and fast it was!), CDFaker mounted it, and CDFS showed the content. Getting CDFS to work was a bit fiddly because there seem to be resources missing, I had to copy them over from the IYONIX.

Wow. I am not sure why CDVDBurn works (it is compiled with a specially-patched GNAT 3.03 which is in turn based on GCC 2.7.2), but I surely won’t complain.

Anyway, many thanks to all the developers who made the BeagleBoard port possible.

Nice work! If anyone testing this fancies updating the Instal_CC on ARMv7 (local drive not CDFS) bug report (by trying an install direct from the CD-ROM) it may be useful.

Has any work been done recently on adding support for USB CD/DVD drives?

Unfortunately, progress is nearly nil from my side of things. “Real world” work pressure meant that I have only a few hours per month to work on RISC OS stuff.

Currently, I have a USB-capable CDVDBurn that seems to run on the BeagleBoard. It might or might not work with any USB CD/DVD/Blu-Ray drive you will throw at it. And you need a recent RISC OS image, Jeffrey did a lot of USB fixing to get it to work properly. The current version is only slightly more advanced than the one sent out to testers in 2010.

The CDFaker module seems to work fine on BeagleBoard, this is at the moment the only released CD-related piece of software for the Beagle.

My efforts to produce a USB-capable CDFSSoft module have stalled for reasons described above.

I hope this will get better in July, but I hoped the same for the last few months.

If someone is interested to help testing, mail me. Yes, I know there are still some unanswered CD related emails in my inbox.

Hi Steffen,
I’m interested in helping in any way I can!

I’ve just dropped you an Email.

Steffen:

I have a USB DVD writer, a USB analyser (sadly only full speed, but I also have a full speed only hub), and a BeagleBoard. This may put me in some position to help: either in logging the transactions that Windows makes with the drive, or in logging the transactions that my BeagleBoard and your experimental software make with the drive.

Let me know what I can do.

Hi Dave,

sorry, a lot of people have offered help, but sadly I don’t even have enough free time to let me help! I promised Jeffrey a new test package which illustrates the problems I have encountered during development of CDVDBurn, mainly the error handling, but I have not yet got around to package it up properly :-(

Jeffrey volunteered to try to produce a CDFSSoftUSB driver, and I’ll do my best to provide the necessary information. I hope to have a bit more free time mid-October.

And there was me feeling bad for not doing anything these past few weeks!

A while ago Steffen did send me a bunch of docs and one of Acorn’s old samples for how to write a SCSI CD driver. From the sound of things it should be pretty easy to write a SCSI/USB CD driver, but since I let myself get distracted by ArcEm I haven’t actually started work on anything yet.

I think I’m now in the right kind of mood to start work on the CD driver; hopefully I’ll start reading through the docs and looking at source code sometime this week. Unfortunately things are starting to get a bit hectic at work, so I’m not sure how much time/energy I’ll have to be able to devote to it over the next few weeks.

OK, Jeffrey, maybe I can help you instead of Steffen :-)

I’m also up for helping in any way I can, just let me know if I can help at all!

The OMAP3 & 4 ROM images on the downloads page have now been rebuilt to contain the first version of the new SCSI/USB CD driver. Don’t be too surprised if it doesn’t work for you – so far it’s only been confirmed to work with one drive model. However I’ve now got my hands an IDE/SATA to USB adapter, so between myself and Steffen (and anyone else here) it shouldn’t be long before we iron out all the bugs.

A few general usage notes:

• Since the CDFS modules don’t support hot-plugging of drives, the driver may need a bit of poking to get it to detect any USB device connects/disconnects. I’ve found that the easiest way to do this is to go into Configure and increase or decrease the number of CD-ROM drives by 1. Saving the settings will then cause CDFS to redetect all the drives. But in general as long as your drive is connected at boot time, and you’ve got at least one CD drive configured, it should be detected OK.
• You can check whether the drive has been detected by looking at the output of *-cdfs-cddevices (which I think is the correct syntax for issuing a filing system specific command; if not, just do *cdfs *cddevices instead). If the drive doesn’t show up then it’s worth checking *devices (for the list of detected SCSI devices), or failing that, *usbdevices.
• CD speed get/set isn’t supported yet. The required commands have changed a bit over the years, so I’ll need to do some more experimentation to come up with code which works with all drive types.
• The inactivity timer multiplier setting won’t work on all drive types
• Audio playback & volume control might not be fully working (the drive I was testing with didn’t have any audio out connectors, so although I could see that the drive was playing the disc I couldn’t verify it was fully working)

Once I’ve had a change to test the module with all the IDE/SATA drives I’ve got I’ll probably upload a debug version of the module somewhere so people can help track down any issues with their drives. Plus I know that four of my IDE drives work with the ATAPI driver, so getting them to work with the SCSI driver would be a good step towards any future merge of the two drivers (or the production of a SCSISoftATAPI driver).

Sadly it doesn’t work with my LG GE20NU11 drive. *usbdevices sees it; *devices sees 0:0.0 as “Read-only Unknown HL-DT-ST DVDRAM GE20NU11 CN01” But any click on the CD-ROM icon gives “CD-ROM drive not found”.

Clearly this drive is much more than a CD-ROM drive.

Anything else I can try that would help?

Also sadly doesn’t work with my Samsung DVD Writer model No SE-S084C/TSBS.

USBInfo gives:

New USB Device found:
vendor_id = 13fd
product_id = 0842
vendor_name = TSSTcorp
product_name = USB Mass Storage Device
class = 8_2_80
usbinfo = 0.60 (08 Apr 2011)
USBDevices sees 6 0 0 TSSTCorp USB Mass Stirage Device.
CDFS command gives No CD-Rom Devices recognised.

Anyway as Jeffrey says early days yet but great to see some progress.

Doug

I haven’t really fixed anything yet, but there’s now a debug version of CDFSSoftSCSI over here: http://www.phlamethrower.co.uk/misc2/cdfs.zip

It’s using DADebug for debug output, so make sure you load that first otherwise you won’t get any of the debug output. After loading the new CDFSSoftSCSI you’ll also need to reinitialise the CD modules (e.g. by messing with the number of drives in Configure). If you’ve done it right, *dadprint should spit out a load of lines like the following, from where CDFSDriver is searching for drives:

CDFSSoftSCSI: driver_code: Op Identify (30) on 2:1.2
CDFSSoftSCSI: driver_code: Op Identify (30) on 2:2.2
CDFSSoftSCSI: driver_code: Op Identify (30) on 2:3.2

If a SCSI device is present on any of the device IDs then the module should also spit out the inquiry response data. For CD/DVD/etc. drives the first byte of the data should be 05; this is how the module currently identifies CD drives. So if you’ve got a device connected but there’s no inquiry response data shown, or the first byte of the response data isn’t 05, then it’s possibly an issue where the device isn’t fully spec compliant. (And if you do have strange inquiry response data for a drive, then posting it here would help).

It’s also possible that something else has already “claimed” the SCSI device ID that the device is attached to. E.g. looking at the CDFaker sources I can see that once it claims a device ID it won’t release it, even if a valid SCSI device starts using that ID. This means CDFSSoftSCSI might not even get called for the device.

Note that *dadreset can be used to clear the debug log.

For even more debugging, there’s also the ‘inquiry’ BASIC program. This loops through all the SCSI device IDs and issues inquiry comands in a similar way to CDFSDriver, and prints out the results. It tries three different buffer sizes for the response data – 36 bytes (which is what CDFSDriver currently uses), 96 bytes, and 512 bytes. So if you get response data for some sizes but not others then it suggests that it is a problem with the device not being fully spec compliant.

I’ve also had a chance to do some quick testing with my IDE/SATA → USB adapter. One drive (‘98 CD-ROM from a RiscPC, model OPC-K101/4) worked OK, but the other (’04 DVD-RW, model TS-H552) causes the SCSI/USB stack to get stuck when issuing commands. The drive+adapter works OK when connected to my PC, so it must be a bug in RISC OS somewhere – so I’ll be concentrating on fixing that bug before I start tearing apart my machines to gain access to my other drives.

I have quite a few CDROM drives (at least 6 IDE) If you are anywhere near (I’m in London next week) you are welcome to them.

Hi Jeffrey

Output from my Samsung DVD writer.

dadprint
Debug start
CDFSSoftSCSI:
CDFSSoftSCSI: ** Debug Session Started ************************************
CDFSSoftSCSI: DebugLib is © Pace Micro Technology plc. 1997-2001
CDFSSoftSCSI: System: DebugLib 0.65
CDFSSoftSCSI: remotedb 0.10
CDFSSoftSCSI: PDebug 0.07
CDFSSoftSCSI: Task: CDFSSoftSCSI
CDFSSoftSCSI: Time: Wed Nov 23 08:35:26 2011
CDFSSoftSCSI: Levels: Not specified.
CDFSSoftSCSI: ******************************************************************
CDFSSoftSCSI: driver_code: Op Identify (30) on 0:0.0
CDFSSoftSCSI: driver_code: Op Identify (30) on 0:1.0
CDFSSoftSCSI: Inquiry response data:
CDFSSoftSCSI: 00: 05
CDFSSoftSCSI: 01: 80
CDFSSoftSCSI: 02: 00
CDFSSoftSCSI: 03: 32
CDFSSoftSCSI: 04: 5b
CDFSSoftSCSI: 05: 00
CDFSSoftSCSI: 06: 00
CDFSSoftSCSI: 07: 00
CDFSSoftSCSI: 08: 54
CDFSSoftSCSI: 09: 53
CDFSSoftSCSI: 0a: 53
CDFSSoftSCSI: 0b: 54
CDFSSoftSCSI: 0c: 63
CDFSSoftSCSI: 0d: 6f
CDFSSoftSCSI: 0e: 72
CDFSSoftSCSI: 0f: 70
CDFSSoftSCSI: 10: 43
CDFSSoftSCSI: 11: 44
CDFSSoftSCSI: 12: 44
CDFSSoftSCSI: 13: 56
CDFSSoftSCSI: 14: 44
CDFSSoftSCSI: 15: 57
CDFSSoftSCSI: 16: 20
CDFSSoftSCSI: 17: 53
CDFSSoftSCSI: 18: 45
CDFSSoftSCSI: 19: 2d
CDFSSoftSCSI: 1a: 53
CDFSSoftSCSI: 1b: 30
CDFSSoftSCSI: 1c: 38
CDFSSoftSCSI: 1d: 34
CDFSSoftSCSI: 1e: 43
CDFSSoftSCSI: 1f: 20
CDFSSoftSCSI: 20: 54
CDFSSoftSCSI: 21: 53
CDFSSoftSCSI: 22: 30
CDFSSoftSCSI: 23: 32
CDFSSoftSCSI: Detected DriveType_MMC
CDFSSoftSCSI: driver_code: Op DiscHasChanged (21) on 0:1.0
CDFSSoftSCSI: driver_code: Op DiscChanged (16) on 0:1.0
CDFSSoftSCSI: SCSI_Op: type 8000000 dev 0:1.0 scblen 6 buffer 00000000 buflen 0 timeout 0 retries 0
CDFSSoftSCSI: SCB: 00 00 00 00 00 00
CDFSSoftSCSI: OK, 0 data bytes
CDFSSoftSCSI: driver_code: Op ReadData (0) on 0:1.0
CDFSSoftSCSI: Reading 1 blocks (2048 each) from 00000010 to 200f697c. Data mode 0
CDFSSoftSCSI: Performing PhotoCD correction
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:1.0 scblen 10 buffer 2047f2c0 buflen 12 timeout 0 retries 0
CDFSSoftSCSI: SCB: 43 00 01 00 00 00 00 00 0c 00
CDFSSoftSCSI: OK, 12 data bytes
CDFSSoftSCSI: Applying offset of 00000000
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:1.0 scblen 12 buffer 2047f2c0 buflen 2352 timeout 0 retries 0
CDFSSoftSCSI: SCB: be 00 00 00 00 10 00 00 01 78 00 00
CDFSSoftSCSI: OK, 2340 data bytes
CDFSSoftSCSI: Device didn’t read all the data!
CDFSSoftSCSI: driver_code: Returning error 803426 Bad response from device
CDFSSoftSCSI: driver_code: Op EnquireDataMode (9) on 0:1.0
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:1.0 scblen 10 buffer 2047f2c0 buflen 8192 timeout 0 retries 0
CDFSSoftSCSI: SCB: 52 00 00 00 00 10 00 20 00 00
CDFSSoftSCSI: OK, 28 data bytes
CDFSSoftSCSI: READ TRACK INFORMATION of 00000010:
CDFSSoftSCSI: READ TRACK INFO only returned 28 bytes!
CDFSSoftSCSI: driver_code: Returning error 803426 Bad response from device
CDFSSoftSCSI: driver_code: Op EnquireTrack (13) on 0:1.0
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:1.0 scblen 10 buffer 2047f2c0 buflen 12 timeout 0 retries 0
CDFSSoftSCSI: SCB: 43 00 00 00 00 00 01 00 0c 00
CDFSSoftSCSI: OK, 12 data bytes
*
*-cdfs-cddevices
Drive Dev LUN Card Product Capacity Firmware
00 1 0 0 CDDVDW SE-S084C 4 Mbytes TS02
*usbdevices
No. Bus Dev Class Description
1 1 1 9/ 0 EHCI root hub
2 1 2 9/ 0 Standard Microsystems Product ID 9514
3 2 1 9/ 0 MUSBMHDRC root hub
4 1 3 FF/ 0 Standard Microsystems Product ID EC00
5 1 4 0/ 0 Logitech USB Receiver
6 1 5 0/ 0 Sunplus Innovation Technology. USB to Serial-ATA bridge
7 1 6 0/ 0 TSSTcorp USB Mass Storage Device
Hope this is of some help.

Doug

Hope this is of some help.

Yes, that’s great, thanks. I think I can see what the problem is.

Hi Jeffrey

I’m going to condense the information, to save posting very long and repetitive logs here. Drive is an LG GE20NU11.

The “inquiry” BASIC programme gives these lines for 0:0.0 to 0:0.7:

Probing 0:0.0
36 byte inquiry: Error &2010E SCSI driver reservation error
96 byte inquiry: Error &2010E SCSI driver reservation error
512 byte inquiry: Error &2010E SCSI driver reservation error

These lines for 0:1.0 to 0:7.7:

Probing 0:1.0
36 byte inquiry: Error &20106 No hardware at this device ID
96 byte inquiry: Error &20106 No hardware at this device ID
512 byte inquiry: Error &20106 No hardware at this device ID

And these lines for 1:0.0 onwards:

Probing 1:0.0
36 byte inquiry: Error &20105 Invalid SCSI device ID
96 byte inquiry: Error &20105 Invalid SCSI device ID
512 byte inquiry: Error &20105 Invalid SCSI device ID

The DADebug *dadprint only gave disc changed or Op_Identify lines; no response data at all, ever.

Hope this helps.

Dave – Does the drive show up in *devices at all? Because judging by what you’ve posted above, it looks like the drive isn’t being detected by SCSISoftUSB (the driver reservation errors would most likely be from SCSIFS claiming your USB stick/hard disc). If the drive isn’t showing up in *devices, can you post the *usbdevinfo and *usbconfinfo output for it, as that will help work out why SCSISoftUSB doesn’t like it.

Doug – (and anyone else) – there’s now a new driver up on my site which should fix the problem that was stopping your drive from working, along with a couple of other bugfixes. I’ve also tweaked the debug output a bit so inquiry response dumps, etc. won’t take up so much space.

Hi Jeffrey

Tried the new module but it still doesn’t read a disc with “Target Error – Illegal Request” messages.

Output as per below:

CDFSSoftSCSI: ******************************************************************
CDFSSoftSCSI: driver_code: Op Identify (30) on 0:0.0
CDFSSoftSCSI: Inquiry response data:
CDFSSoftSCSI: 05 80 00 32 5b 00 00 00 54 53 53 54 63 6f 72 70 43 44 44 56 44 57 20 53 45 2d 53 30 38 34 43 20 54 53 30 32
CDFSSoftSCSI: Detected DriveType_MMC
CDFSSoftSCSI: driver_code: Op DiscHasChanged (21) on 0:0.0
CDFSSoftSCSI: driver_code: Op DiscChanged (16) on 0:0.0
CDFSSoftSCSI: SCSI_Op: type 8000000 dev 0:0.0 scblen 6 buffer 00000000 buflen 0 timeout 0 retries 0
CDFSSoftSCSI: SCB: 00 00 00 00 00 00
CDFSSoftSCSI: OK, 0 data bytes
CDFSSoftSCSI: driver_code: Op ReadData (0) on 0:0.0
CDFSSoftSCSI: Reading 1 blocks (2048 each) from 00000010 to 200f697c. Data mode 0
CDFSSoftSCSI: Performing PhotoCD correction
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:0.0 scblen 10 buffer 2047e660 buflen 12 timeout 0 retries 0
CDFSSoftSCSI: SCB: 43 00 01 00 00 00 00 00 0c 00
CDFSSoftSCSI: OK, 12 data bytes
CDFSSoftSCSI: Applying offset of 00000000
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:0.0 scblen 12 buffer 2047e660 buflen 2352 timeout 0 retries 0
CDFSSoftSCSI: SCB: be 00 00 00 00 10 00 00 01 78 00 00
CDFSSoftSCSI: OK, 2340 data bytes
CDFSSoftSCSI: Device didn’t read all the data!
CDFSSoftSCSI: driver_code: Returning error 803426 Bad response from device
CDFSSoftSCSI: driver_code: Op EnquireDataMode (9) on 0:0.0
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:0.0 scblen 10 buffer 2047e660 buflen 8192 timeout 0 retries 0
CDFSSoftSCSI: SCB: 52 00 00 00 00 10 00 20 00 00
CDFSSoftSCSI: OK, 28 data bytes
CDFSSoftSCSI: READ TRACK INFORMATION of 00000010:
CDFSSoftSCSI: Should be data mode 1
CDFSSoftSCSI: driver_code: Op GetParameters (4) on 0:0.0
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:0.0 scblen 10 buffer 2047e660 buflen 8192 timeout 0 retries 0
CDFSSoftSCSI: SCB: 5a 08 3f 00 00 00 00 20 00 00
CDFSSoftSCSI: OK, 256 data bytes
CDFSSoftSCSI: ModeDataLength doesn’t add up! Drive reports 252 bytes, but should be 262
CDFSSoftSCSI: driver_code: Op SetParameters (5) on 0:0.0
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:0.0 scblen 10 buffer 2047e660 buflen 8192 timeout 0 retries 0
CDFSSoftSCSI: SCB: 5a 08 0d 00 00 00 00 20 00 00
CDFSSoftSCSI: OK, 16 data bytes
CDFSSoftSCSI: ModeDataLength doesn’t add up! Drive reports 14 bytes, but should be 22
CDFSSoftSCSI: SCSI_Op: type a000000 dev 0:0.0 scblen 10 buffer 2047e660 buflen 16 timeout 0 retries 0
CDFSSoftSCSI: SCB: 55 10 00 00 00 00 00 00 10 00
CDFSSoftSCSI: Error 201c5 Target error – Illegal request
CDFSSoftSCSI: driver_code: Returning error 201c5 Target error – Illegal request
CDFSSoftSCSI: driver_code: Op EnquireTrack (13) on 0:0.0
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:0.0 scblen 10 buffer 2047e660 buflen 12 timeout 0 retries 0
CDFSSoftSCSI: SCB: 43 00 00 00 00 00 01 00 0c 00
CDFSSoftSCSI: OK, 12 data bytes
CDFSSoftSCSI: driver_code: Op DiscChanged (16) on 0:0.0
CDFSSoftSCSI: SCSI_Op: type 8000000 dev 0:0.0 scblen 6 buffer 00000000 buflen 0 timeout 0 retries 0
CDFSSoftSCSI: SCB: 00 00 00 00 00 00
CDFSSoftSCSI: OK, 0 data bytes
CDFSSoftSCSI: driver_code: Op EnquireDataMode (9) on 0:0.0
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:0.0 scblen 10 buffer 2047e660 buflen 8192 timeout 0 retries 0
CDFSSoftSCSI: SCB: 52 00 00 00 00 10 00 20 00 00
CDFSSoftSCSI: OK, 28 data bytes
CDFSSoftSCSI: READ TRACK INFORMATION of 00000010:
CDFSSoftSCSI: Should be data mode 1
CDFSSoftSCSI: driver_code: Op GetParameters (4) on 0:0.0
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:0.0 scblen 10 buffer 2047e660 buflen 8192 timeout 0 retries 0
CDFSSoftSCSI: SCB: 5a 08 3f 00 00 00 00 20 00 00
CDFSSoftSCSI: OK, 256 data bytes
CDFSSoftSCSI: ModeDataLength doesn’t add up! Drive reports 252 bytes, but should be 262
CDFSSoftSCSI: driver_code: Op SetParameters (5) on 0:0.0
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:0.0 scblen 10 buffer 2047e660 buflen 8192 timeout 0 retries 0
CDFSSoftSCSI: SCB: 5a 08 0d 00 00 00 00 20 00 00
CDFSSoftSCSI: OK, 16 data bytes
CDFSSoftSCSI: ModeDataLength doesn’t add up! Drive reports 14 bytes, but should be 22
CDFSSoftSCSI: SCSI_Op: type a000000 dev 0:0.0 scblen 10 buffer 2047e660 buflen 16 timeout 0 retries 0
CDFSSoftSCSI: SCB: 55 10 00 00 00 00 00 00 10 00
CDFSSoftSCSI: Error 201c5 Target error – Illegal request
CDFSSoftSCSI: driver_code: Returning error 201c5 Target error – Illegal request
CDFSSoftSCSI: driver_code: Op EnquireTrack (13) on 0:0.0
CDFSSoftSCSI: SCSI_Op: type 9000000 dev 0:0.0 scblen 10 buffer 2047e660 buflen 12 timeout 0 retries 0
CDFSSoftSCSI: SCB: 43 00 00 00 00 00 01 00 0c 00
CDFSSoftSCSI: OK, 12 data bytes

Doug

“Doug – (and anyone else) – there’s now a new driver up on my site”

I am getting my Aopen DVDreader to show up on 0.0.0 using the BASIC inquiry program.
Probing 0:0.0
36 byte inquiry: 36 bytes returned OK – ….)…AOPEN. .COM.2.2.AAH.SL .
96 byte inquiry: 56 bytes returned OK – ….)…AOPEN. .COM.2.2.AAH.SL .1.0.0.0.0.AOpEn.7.1.1.5.
512 byte inquiry: 0 bytes returned OK

It is an ide on a USB adapter at *USBDevices 7.1.2
When clicking on its icon, I get ‘CD-Rom drive not found’ and DADPrint outputs a line for all but 0.0.0 with the line
‘CDFSSoftSCSI: driver_code: Op Identify (30) on 0:0.1’ (-3:7.7)
and no mention of 0.0.0

Ron Iyonix 5.16

Ronald – What other CD drivers do you have loaded? It sounds like one of them is claiming 0:0.0 before CDFSSoftSCSI is given a look-in. Having the ATAPI driver loaded should be fine (it’s never given me any problems), but I believe CDFaker can cause problems because it will most likely claim 0:0.0 and then never release it. Maybe I should start having a think about a proper solution for dealing with device hot-plugging and reservation of device IDs by non-SCSI drivers.

Doug – I’ll have another read of the docs and see if I can get a new driver out tonight.

Well, to my amazement, after some strangenesses while booting up (and needing to reboot), tonight the driver is working and allowing me to read my old Photodesk CD! I’ve not even downloaded your new driver yet!

I have no idea what persuaded things to behave differently, however I can observe that on Tuesday, as noted in my posting above, 0:0.0 was the CD/DVD drive (presumably 0:1.0 was the HDD, although I don’t have a record so that really is only a presumption), whereas tonight 0:0.0 is the HDD and 0:1.0 is the CD/DVD drive.

More good news: it read a DVD+R too. “Dismount” and “Eject” work.

To my astonishment, it has even made some sense of a DVD-RAM disc, though I don’t know how it’s formatted.