APPCRASH working on network drive

[lwalker]

I've got this crash while working in a network drive and using two panels.
My workstation is a W7 64Bits.

This is the crash report that windows generated:

Firma con problemas:
Nombre del evento de problema: APPCRASH
Nombre de la aplicación: XYplorer.exe
Versión de la aplicación: 10.40.0.0
Marca de tiempo de la aplicación: 4e8b0112
Nombre del módulo con errores: OLE32.DLL
Versión del módulo con errores: 6.1.7601.17514
Marca de tiempo del módulo con errores: 4ce7b96f
Código de excepción: c0000005
Desplazamiento de excepción: 0004a4bb
Versión del sistema operativo: 6.1.7601.2.1.0.256.48
Id. de configuración regional: 3082
Información adicional 1: 0a9e
Información adicional 2: 0a9e372d3b4ad19135b953a78882e789
Información adicional 3: 0a9e
Información adicional 4: 0a9e372d3b4ad19135b953a78882e789

[PeterH]

Maybe you should give some info "what you worked"?

[admin]

Moving files maybe?

(The bug looks similar to the other crash bug reported recently -- fix is coming).

[lwalker]

Moving files maybe?

(The bug looks similar to the other crash bug reported recently -- fix is coming).

Great!

pd: of course, I was moving files. (I was working on some of my job things, but I think this is not important for solving the bug )

[lwalker]

sorry, I forgot to mention that, after this crash, all the configuration options are lost. So XYplorer behaves as the first time it was instaled.

pd. "As the first time" is true for everything. My trial period has been reseted too, to the 30 days period! (I suppose you'd want to solve this too )

[admin]

sorry, I forgot to mention that, after this crash, all the configuration options are lost. So XYplorer behaves as the first time it was instaled.

pd. "As the first time" is true for everything. My trial period has been reseted too, to the 30 days period! (I suppose you'd want to solve this too )

(What you say there looks like an impossible thing from my POV, but:) Let's see whether you get it again.

[lwalker]

(What you say there looks like an impossible thing from my POV, but:) Let's see whether you get it again.

I'm a developer too, and I can say that in computers there is not such a thing as "impossible"

Anyway, I'll let you know if it happens to me again.

[admin]

A crashed app is dead. How could it delete and change particular files in a particular folder in this unlively state?

[lwalker]

A crashed app is dead. How could it delete and change particular files in a particular folder in this unlively state?

Well... guessing... (I don't have the code. Besides, I'm a C# developer, so not much knowledge of C/C++ "way of do things")

·Maybe the state was been saved (I was not changing options, but maybe the autobackup feature does something in the background...) and became corrupted. I suppose you have some code to reset state if its unreadable...

·I don't know where you store the registration info... maybe it's in the registry, and maybe the "zone" asigned to xyplorer became corrupt because of the crash... maybe you save the "undo" info in some place related with the registration, so the whole information package became corrupted... again, it's impossible to guess without the code

Just to give you more information to look for the bug: I think i've not turned off the computer since I instaled xyplorer (I allways hibernate, and only restart it if some software ask me to do it after installation). So guessing again... maybe the first settings+trial expiration date were "just" never saved... (In the configuration window I used, of course, the "OK" button, but who knows...)

If you think there are some usefull logfiles that I could send to you to solve this problem, tell me and I'll send them to you.

[admin]

maybe the first settings+trial expiration date were "just" never saved...

That's the only explanation.