Multi Commander > Support and Feedback

Error 4000

<< < (6/8) > >>

Mathias (Author):
From the log I can see that first call to windows to write the data fails. So windows allows the file to be open for writing but when it starts to write data to the file it does not like it.  Something is stopping it from writing the data. This is not normal.  The internal error code is not shown in the log. And it is not one of the standard errors.
I will add the internal windows error code to the log in the next beta.
But if you are handy you can see it using Process Monitor, But that tool is not easy to use.

But why Windows does not allow the file data to be written is strange.
The question remains.. what is unique on the few systems that have this issue ?

78-45-33:
ProcMon is part of Sysinternals Suite, I already got it.

First I'm not a programmer at all; but only strange things I see in ProcMon log is buffer overflow and
invalid device request.

I saved the ProcMon log, could You take a look into it?  I'll upload it to yr website.
No hurry ofcourse as I can sent files other ways to the ext.HDD.

T.i.a.

Mathias (Author):
buffer overflow you see there are normal. it is not the bad kind. :)
But If you saved the log you can upload it and I can take a look.

78-45-33:
PML log uploaded

Mathias (Author):

--- Quote from: 78-45-33 on September 21, 2013, 22:30:42 ---PML log uploaded

--- End quote ---
Did not see anything it it.. To much noise.

But there is a new Beta out (build 1516) It will output the internal window error code when it fails to write data.

Navigation

[0] Message Index

[#] Next page

[*] Previous page