.INF files and devices installation

andrzejtomys

Reputable
Dec 18, 2015
2
0
4,510
Problem with "*.INF" file with the old TDK DVDRW0404N ATA Device. After x32 WinXP system crashing and installing Win 7 x64 one - device correctly appears on the Device Manager ONLY as properly installed. Anyway NO ACCESS to it is possible,
I'd found ( http://www.driverscape.com/download/tdk-dvdrw0404n-ata-device ) "declared as a "driver" (2006-06-21) v. 6.1.7600.16385 Win 7 x64 77.34 K in internet. It contains the only three files: - cdrom.inf, - cdrom.PNF and - cdrom.sys. No executable application "*.exe" e.g. (Driver.exe) exists in such a “driver”.
How to "install" device without executable file, taking account, that Device Manager delivers info, that the driver is OK! and actual, while device is not accessible ? Similar problem frequently appears with different devices. Tell me please, HOW to implement “*.INF”, “*.sys” files to install devices along with Win 7 Prof x64?
What does “*.PNF” file in installation procedure?
Where the executable file "Device.exe" could be found to perform installation with positive effect?
Could anybody help?
Andrzej
awb@op.pl
 
Solution
Device Manager -> Problem device -> Properties -> Driver tab ->Update driver ->Browse my computer - at that point it will be looking for .inf files in whatever folder you browse to, and it will probably automatically pick up the cdrom.inf file from the folder where it is residing and it will install the driver when you select it.... Or quite possibly, it will say that the driver it already has is the best one available. cdrom.sys is a standard windows driver for optical drives. It is quite possible that the drive itself is bad. Or, if it actually works after trying to install the driver, then it has replaced a core windows driver, and it is possible that no other device, which requires cdrom.sys, will work in the future, until you...
Device Manager -> Problem device -> Properties -> Driver tab ->Update driver ->Browse my computer - at that point it will be looking for .inf files in whatever folder you browse to, and it will probably automatically pick up the cdrom.inf file from the folder where it is residing and it will install the driver when you select it.... Or quite possibly, it will say that the driver it already has is the best one available. cdrom.sys is a standard windows driver for optical drives. It is quite possible that the drive itself is bad. Or, if it actually works after trying to install the driver, then it has replaced a core windows driver, and it is possible that no other device, which requires cdrom.sys, will work in the future, until you restore the original windows driver.
 
Solution