Many Windows .dll files are "dynamic" files that are created by the system based on device driver info and other details of the specific user setup. A common fix for .dll file corruption is just to delete the .dll and let Windows create a new one the next time you open something that uses it. A very few .dll files have fixed content and are "generic" enough to be copied from one machine to another, but even when the filename is the same the needed file content may differ from one machine to another.

Installing an appropriate device driver will usually provide the correct .dll files, or the information needed by the system to create them - and to edit them in response to system changes.

WinME System Information (Start|Programs|Accessories|System Tools|System Information, or Start|Run|Msinfo32.exe) may possibly identify the manufacturer and model number of the CD device, even if it's not operable. (WinME SI also has a sort of mini System Restore in the "History" section that might let you roll-back to an operable earlier condition, if the history files haven't been deleted.)

If you can get a manufacturer and model number for the CD device, either the mfr's or your OEM computer maker's website should have a current driver, and installing a new driver should create any needed .dll file(s).

Any CD-ROM device more than about 2 years old needs new drivers anyway, since changes to the CD-ROM DISK specification(s) have made changes to the drivers necessary to maintain compatibility with the several "flavors" of disks extant now.

If the .dll isn't on install disks, and isn't easily found on the web, it means that the system has to create it when you install something else. I'd go for a new CD device driver.

John