Mobileread
Fail-"Python Nul file missing"
#1  mark_e_h 05-13-2013, 02:27 AM
Suddenly, when I start Calibre I get a message "Python function terminated unexpectedly NUL file missing...Error code 1"

After looking around here, I have uninstalled Calibre. Removed all left over files (Calibre, Calibre2). Also tried Revo Uninstaller Pro. Reinstalled the latest, and older versions.

Nothing has worked. HELP!! Any suggestions please....


.Windows 7, x64 (I've tried both 64 and 32 bit versions)

This might help:


===


C:\Users\Mark>calibre-debug -g 2>&1 > log.txt
Traceback (most recent call last):
File "site.py", line 132, in main
File "site.py", line 109, in run_entry_point
File "site-packages\calibre\debug.py", line 208, in main
File "site-packages\calibre\gui2\main.py", line 415, in main
File "site-packages\calibre\gui2\main.py", line 85, in init_qt
File "site.py", line 50, in load_module
File "site-packages\calibre\gui2\ui.py", line 24, in <module>
File "site.py", line 50, in load_module
File "site-packages\calibre\utils\ipc\server.py", line 18, in <module>
File "site.py", line 50, in load_module
File "site-packages\calibre\utils\ipc\launch.py", line 21, in <module>
RuntimeError: NUL file missing in windows. This indicates a corrupted windows. Y
ou should contact Microsoft for assistance.
Reply 

#2  DoctorOhh 05-13-2013, 03:27 AM
Quote mark_e_h
Suddenly, when I start Calibre I get a message "Python function terminated unexpectedly NUL file missing...Error code 1"

...

File "site-packages\calibre\utils\ipc\launch.py", line 21, in <module>
RuntimeError: NUL file missing in windows. This indicates a corrupted windows. You should contact Microsoft for assistance.
This is not a calibre problem it is a problem with your Windows Operating System. A review of entries in this Google search might help.
Reply 

#3  PeterT 05-13-2013, 09:27 AM
See http://www.mobileread.com/forums/sho...d.php?t=166163 or http://www.mobileread.com/forums/sho...d.php?t=173360
Reply 

#4  mark_e_h 05-13-2013, 04:59 PM
Quote DoctorOhh
This is not a calibre problem it is a problem with your Windows Operating System. A review of entries in this Google search might help.
Well, I guess in the technical sense it's a Windows problem. As the Google search shows, Calibre is a widely used app, and most of the people with the problem are experiencing it with Calibre.

The "fixes" suggested in the postings don't seem particularly relevant, at least in my case. So I guess I think that Calibre development needs to provide some of the help with the resolving the problem. This has randomly occurred more than once on my system. In the past a system restore was able to resolve it, but not this time.


.
Reply 

#5  itimpi 05-13-2013, 05:09 PM
I am afraid it IS a problem with your Windows system. There should be a NUL device on a standard Windows 7 installation, and somehow yours seems to have disappeared. It is just that if it goes missing then Calibre will show it up.
Reply 

#6  mark_e_h 05-13-2013, 06:57 PM
Quote
I am afraid it IS a problem with your Windows system. There should be a NUL device on a standard Windows 7 installation, and somehow yours seems to have disappeared. It is just that if it goes missing then Calibre will show it up.
That would make it easy. Its right there, in:

C:\Windows\System32\drivers\null.sys

To confirm this, the C:/boot drive is a SSD - the original system is now on the F: drive (it was copied over when the system was new, a year ago.). The same file, same length (6,144), same create date, same permissions, etc...

I presume this is the correct file, in the correct place?? What am I missing??

I was referred to this site, with registry changes:
http://siebn.de/other/nulldevice/

It's not clear that the changes apply to a Win7 x64 system, though I guess I could apply them and backoff if there is a problem. Seems a little risky.

Any other suggestions would be greatly appreciated.

.



.
Reply 

#7  PeterT 05-13-2013, 07:19 PM
So just reinstall windows then. Far less risky
Reply 

#8  mark_e_h 05-13-2013, 08:01 PM
ok -

null.sys was there
registry was in place.


Solution (at least for me)

go to:
system > administrative tools > Device Manager
under View - "show hidden devices"
under "Non-Plug and Play Drivers" find Null
In my system, Null was offline - error 22.

Try restarting - well this is Windows, so it won't work. Don't know why.

right mouse and uninstall Null
reboot
Null is now gone from device manager (though the file is still on the system)

Get down to "Non-Plug and Play Drivers", right mouse, and "scan for hardware changes"

Null now returns.... Calibre works. All is well - until the next time....



.
Reply 

#9  BetterRed 05-13-2013, 11:11 PM
@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
Reply 

Today's Posts | Search this Thread | Login | Register