Drag and drop crash with 12.90.0004

[Enternal]

WOW, I never thought to mention that. I've been running your official version 12.90.0000 ever since this problem arose, but yes...your recompiled version OF THE SAME FILE crashed!! Have you recently updated your compiler?

Bill

EXACTLY! If Don really did indeed recompiled 12.90.0000, then it's an issue with the compiler or something on his system. Obviously the code was working before but then something funky went on. Damn Gremlins... Those pesky Gremlins probably left a ratchet somewhere in Don's system while he was away.

[admin]

Well, then we are screwed. This is version 12.90.0000, the one that was supposed to still work!

So it's not the source code. Logic would say that my compiler started to have a problem some days ago. Or maybe my system. A recent Windows Update maybe?

...

Okay, here is a likely culprit. On 13-Sep-2013 my system installed this Windows update (I allowed Windows to do this automatically):
http://support.microsoft.com/?kbid=2876217
On that page you can see that a new Ole32.dll has been installed. AFAIK information from this crucial system file can influence the behavior of the compiler. And yes, this file is important for drag and drop.

I now have this version of the file:
ole32.dll, 1.289.728 bytes, 05.08.2013 15:30:32, ver 5.1.2600.6435 (xpsp_sp3_qfe.130803-0418), C:\WINDOWS\system32\

[Enternal]

Well, then we are screwed. This is version 12.90.0000, the one that was supposed to still work!

So it's not the source code. Logic would say that my compiler started to have a problem some days ago. Or maybe my system. A recent Windows Update maybe?

...

Okay, here is a likely culprit. On 13-Sep-2013 my system installed this Windows update (I allowed Windows to do this automatically):
http://support.microsoft.com/?kbid=2876217
On that page you can see that a new Ole32.dll has been installed. AFAIK information from this crucial system file can influence the behavior of the compiler. And yes, this file is important for drag and drop.

I now have this version of the file:
ole32.dll, 1.289.728 bytes, 05.08.2013 15:30:32, ver 5.1.2600.6435 (xpsp_sp3_qfe.130803-0418), C:\WINDOWS\system32\

OOOOHHH!!!!! A few days ago, I was using OllyDbg 1.10 to play around and see if I can dig something out as to why XYplorer crashed. Somewhere in the data that I played with, it did mention ole32.dll as being a problem the moment XYplorer crashed. Of course since I know nothing about debugging and was just merely playing around with OllyDbg, I don't think I can reproduced what I clicked and such. Soo.... sorry I'm kinda useless as well.

[Marco]

Don,
could that dll update have other effects too? Here's what Borut experiences on XP SP3, http://www.xyplorer.com/xyfc/viewtopic. ... 148#p92148
I suspect there might be some connection.

[Borut]

I can confirm that I have the incriminated ole32.dll, 1.289.728 bytes, 05.08.2013 15:30:32, ver 5.1.2600.6435 on my machine(s) too.

However, no D&D problems. Only these extract-copy problems, which Marco pointed to. Thanks Marco, similar thoughts occurred to me too!

So, the Gremlins are taking over Redmond, or what?

[Enternal]

OK!!! I restored the old version of ole32.dll and I put it next to XYplorer.exe. XYplorer no longer crash.

ole32.dll is probably the reason for all our problems as well as Borut. I will try zipping up the old ole32.dll and post it here for everyone to try first and see how it goes.

[admin]

OK!!! I restored the old version of ole32.dll and I put it next to XYplorer.exe. XYplorer no longer crash.

ole32.dll is probably the reason for all our problems as well as Boruts. I will try zipping up the old ole32.dll and post it here for everyone to try first and see how it goes.

Wow, that proves the connection!

But I have that new ole32.dll as well andI have no crash (just like Borut)!

[Enternal]

OK!!! I restored the old version of ole32.dll and I put it next to XYplorer.exe. XYplorer no longer crash.

ole32.dll is probably the reason for all our problems as well as Boruts. I will try zipping up the old ole32.dll and post it here for everyone to try first and see how it goes.

Wow, that proves the connection!

But I have that new ole32.dll as well andI have no crash (just like Borut)!

Ok, just unload the ole32.exe file in the zip and put it next to XYplorer.exe and see if it resolves the problem for serendipity, Borut, n2tpa, and jcmn.

ole32.zip

Now Also Store Creation/Modification Date of ole32.dll

(632.17 KiB) Downloaded 134 times

EDIT: But yeah, I still don't understand why your and Borut drag and drop did not crash.

[admin]

Uploaded v12.90.0015- I tried something. Please run the debug thing again and show the lines you see (only one or two lines this time). Of course, you should use the new (evil) ole32.dll for this test.

[Borut]

But I have that new ole32.dll as well andI have no crash (just like Borut)!

Is a certain ole32.dll file version identical for all WinXP language editions? Don and I both have German WinXPs. Marco Italian. Enternal?

Anyway, I will not make experiments with mixed ole32.dll sources, not even in the XYplorer folder. Perhaps during the night.

[Enternal]

Uploaded v12.90.0015- I tried something. Please run the debug thing again and show the lines you see (only one or two lines this time). Of course, you should use the new (evil) ole32.dll for this test.

Wait, was it supposed to crash because it did not. I also checked the old version and they still crashed (to make sure the old good ole32.dll is not loaded in memory. also did a computer restart). Anyways:

Code: Select all

03:35:09.312 - dtf5: 
03:35:09.328 - dtf6: 
03:35:09.390 - dtf5: 
03:35:09.437 - dtf6: 

But I have that new ole32.dll as well andI have no crash (just like Borut)!

Is a certain ole32.dll file version identical for all WinXP language editions? Don and I both have German WinXPs. Marco Italian. Enternal?

Anyway, I will not make experiments with mixed ole32.dll sources, not even in the XYplorer folder. Perhaps during the night.

Good point. I'm not sure if they're identical at all. We could check using hashes so the evil ole32.dll MD5 is 59B408E5B8489B0B36A0D783D150EDCC.

[admin]

It did not crash? With the evil ole32.dll? Then I fixed it.

[Enternal]

It did not crash? With the evil ole32.dll? Then I fixed it.

AMAZING!!!

Out of curiosity, what exactly did you do?

[admin]

!!!WHOA!!!

What a triumph of logic! It was exactly the line between "dtf5" and "dtf6" (debug thing). So I thought "ole32" is evil, so away with it!

Here is the crucial section:

Code: Select all

  ' 20130920: try fix drag bug
  ReleaseStgMedium tSTGM
  ''olelib.ole32.ReleaseStgMedium tSTGM

I hope it now still works in Win7/8.

[Enternal]

!!!WHOA!!!

What a triumph of logic! It was exactly the line between "dtf5" and "dtf6" (debug thing). So I thought "ole32" is evil, so away with it!

Here is the crucial section:

Code: Select all

  ' 20130920: try fix drag bug
  ReleaseStgMedium tSTGM
  ''olelib.ole32.ReleaseStgMedium tSTGM

I hope it now still works in Win7/8.

Wait. So it was not ole32.dll? Or it was the code for the Outlook drag and drop?