@
mark_e_h - just checked my Win7-64 - null device is there, and it's status is 'working properly'
I updated the Win 7 RC to production version in mid 2009 - so its almost 4 years old. I've been running Calibre intensively since late 2011. I've never had this problem.
null.sys has hardlinks at
Code:
C:\Windows\System32\drivers\null.sys
C:\Windows\winsxs\amd64_microsoft-windows-null_31bf3856ad364e35_6.1.7600.16385_none_055adf2434ae116e\null.sys
I suspect something out there is clobbering the hardlink in the winsxs (side by side) directory - but I don't think its Calibre that's doing it - could be malware.
Windows goes to its side by side folders to deal with the
DLL Hell phenomena - System32 is mainly there for boot processing and legacy apps
If you install Link Shell Extension you will see (via an overlay glyph) that most of System 32 has multiple hardlinks. You can find out where the links are from the Link Properties sheet that LSE adds to Properties.
null.sys is a bit bucket driver, most os's have them in one form or another.
I have no idea why Calibre should be sensitive to it... anyone know?
BR