I cannot see your image, due to incorrect google drive permissions.

However, this sounds like your ATAPI driver does not correctly work with your drive.

I'd try going down the (long) list of generic atapi drivers, to see which, if any, work with your drive.

I'd also isolate it all by itself on a channel, to remove other possible causes of failure, then document my findings here.

I have tried the drives on channel 1 as CS with nothing on channel 2 and still had this behavior. I have tried generic drivers and brand drivers for lg and mitsumi, which are the brands of drives im using.

Does this drive work in another machine?

Does it audibly spin up the disc?

Is this a factory pressed disc, or a CDR?

etc.

The bit after the name looks like corruption, maybe try a different cable

I have no other machine to put ide drives in, this has happened with 2 different drives. Its a factory ms win98 cd, i never hear either drive spin up. Hopefully its the cable, will try a different one after work.

I also tried two other drives, and they wouldnt open. I figured they were just garbage, could a bad cable/driver stop the tray from opening?

A bad cable can, but it's unusual.

The most likely culprit is 'drive belt broke, or turned into sticky goo over a decade ago', when confronted with 'tray wont open.'

https://youtu.be/21AnFs3DaKI?is=CHWZrYMqG6hY6EH6

'Disc does not spin' can be a related failure: the disc wont spin if the tray does not fully get pulled in, and hit the endstop sensor. That can fail to happen if the belt has failed.

The belt capstan+motor continues for a small bit after the tray is pulled in, as the mechanism then pulls down the spindle hub on the disc, hits end of travel in the mechanism, and engages the switch. This tells the drive that the tray has *fully* inserted, and that it is safe to spin up the media, and attempt to find the track with the laser sled.

If the belt has degraded or broke, there is not enough grip to pull down the spindle hub, and the endstop sensor does not trigger, so the drive never enters 'ready' state.

As mentioned though, your drive is giving bad ID string reads, which suggests a bad cable, or other electronic mode of failure.