Running Installer, installer sometimes crashes.....

[GoogleCodeExporter]

So, I've been distributing my installer to my mod pack users that uses 
VCLStyles, and a couple of my users have reported "crashing" while installing, 
and it occurs at different times.

One user got this error....

----

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    LAMP_0.9.3.v7.tmp
  Application Version:    51.52.0.0
  Application Timestamp:    2a425e19
  Fault Module Name:    VclStylesInno.dll
  Fault Module Version:    1.2.6.1
  Fault Module Timestamp:    54409c91
  Exception Code:    c0000005
  Exception Offset:    0000a26e
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033
  Additional Information 1:    58b1
  Additional Information 2:    58b1f0a719820549d00d78799b478f60
  Additional Information 3:    ea81
  Additional Information 4:    ea8171ac1130827ff07dc52345e72812

----

Another user had crashing issues also every time he ran the installer, but it 
would occur at different points in the installer, however, he say's disabling 
"Steam" fixed the issue.  However, I'm not sure if that is completely the 
problem, because I've had random crashing issues also without anything running. 
 Not sure about error message becuse I just get a "app needs to close box".  I 
guess the error log is somewhere in windows.

This issue "seems" to have started occuring after you fixed the "List" scroll 
bar issue, the last release of your .dll.  However, it's always possible it 
might be something else, cause we made some small code changes.  However, given 
that the above error directly points to the VCLStyles .DLL I'm wondering if the 
error is related to your .dll?

Here's a copy of my full installer if you want to text it.

http://www.mediafire.com/download/sgs878ga9qs9eqt/LAMP_0.9.3.v7.exe

And attached is a copy of the .ISS file.

Original issue reported on code.google.com by leeunive...@gmail.com on 29 Oct 2014 at 1:49

Attachments:

• [without the button_32.iss](https://storage.googleapis.com/google-code-attachments/vcl-styles-plugins/issue-10/comment-0/without the button_32.iss)

[GoogleCodeExporter]

Also, around the same time this crashing started my friend had added this code 
to the .iss file.

AppId={{3E77C31A-C78C-431E-8B53-0EFA66142FC1}

Never had any crashing before that.  Do you think this code could be the 
problem?
I've actually been testing an installer without that code, and not a single 
crash yet.
I'm going to upload it for my users to try out to see if they have any 
crashing, since I can't reproduce it after many try's.

Original comment by leeunive...@gmail.com on 29 Oct 2014 at 1:54

[GoogleCodeExporter]

Ok , I just tried the installer a couple of times on different environments and 
not exception is raised. about the last changes made to the vcl styles plugin I 
don't made any critical change. Please keep me posted about any additional data 
to track the issue. 

Original comment by Rodrigo.Ruz.V@gmail.com on 29 Oct 2014 at 2:57

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Why your new comments appears deleted? Anyway can you try enabling the log  
(http://www.jrsoftware.org/ishelp/index.php?topic=setup_setuplogging) parameter 
in the iss script and if the installer crash again send the log file.  

Original comment by Rodrigo.Ruz.V@gmail.com on 29 Oct 2014 at 2:13

[GoogleCodeExporter]

Cause I think I made a mistake....  I thought I had commented out that AppID 
line, in the last setup I made, but it seems like apparently I didn't save it 
or something, not sure what happened, so I have to test again.

Original comment by leeunive...@gmail.com on 29 Oct 2014 at 3:29

[GoogleCodeExporter]

Okay, sure....

Original comment by leeunive...@gmail.com on 29 Oct 2014 at 3:29

[GoogleCodeExporter]

Okay, so here's the error code from the Windows Error Log.
Attached is the Log from the Installer.
One thing though, when I ran the installer without a crash, the log was just 
the text file, but then when the crash occured, there was a .tmp file there 
also (which I've included in the attachement).  And you'll see from the log 
it's like it didn't complete.

So, hopefully this is what you're needing.

 System 

  - Provider 

   [ Name]  Application Error 

  - EventID 1000 

   [ Qualifiers]  0 

   Level 2 

   Task 100 

   Keywords 0x80000000000000 

  - TimeCreated 

   [ SystemTime]  2014-10-30T08:28:04.000000000Z 

   EventRecordID 58301 

   Channel Application 

   Computer Dads 

   Security 

- EventData 

   LAMP_0.9.3.v7_TEST.tmp 
   51.52.0.0 
   2a425e19 
   VclStylesInno.dll 
   1.2.6.1 
   54409c91 
   c0000005 
   000030c9 
   1a38 
   01cff41b5c6b5c94 
   C:\Users\LEEUN_~1\AppData\Local\Temp\is-62ANV.tmp\LAMP_0.9.3.v7_TEST.tmp 
   C:\Users\LEEUN_~1\AppData\Local\Temp\is-CK59K.tmp\VclStylesInno.dll 
   aa734870-600e-11e4-82a6-0c8bfd21ef66 

Original comment by leeunive...@gmail.com on 30 Oct 2014 at 8:39

Attachments:

• Temp.zip

[GoogleCodeExporter]

For the "crashing" issue, I've removed an InnoCallback.dll which wasn't being 
used by the script, and so far I myself haven't had any crashes.  But, it would 
only occur for my like between 20-30 times when running the installer, and I've 
ran it likely 100 times.

Still waiting on a couple of my users to test who had crashes.  But, it's 
strange, one would think the error message would occur on that .dll, not yours.

Original comment by leeunive...@gmail.com on 1 Nov 2014 at 5:20

[GoogleCodeExporter]

Thanks for the update.

Original comment by Rodrigo.Ruz.V@gmail.com on 2 Nov 2014 at 3:33

[GoogleCodeExporter]

Okay, so my user who had the installer crash when "Stream" was running didn't 
have the issue.  He was able to install fine even with Stream running.  I'm 
still waiting on the one user who just reported a bunch of crashing.  But, it's 
looking hopeful so far.

Original comment by leeunive...@gmail.com on 2 Nov 2014 at 8:56

[GoogleCodeExporter]

CRAP....

I've had a crash....  This time around I was using your latest .dll
Crash log attached.

- System 

  - Provider 

   [ Name]  Application Error 

  - EventID 1000 

   [ Qualifiers]  0 

   Level 2 

   Task 100 

   Keywords 0x80000000000000 

  - TimeCreated 

   [ SystemTime]  2014-11-03T00:43:53.000000000Z 

   EventRecordID 58775 

   Channel Application 

   Computer Dads 

   Security 

- EventData 

   LAMP_0.9.3.v8.tmp 
   51.52.0.0 
   2a425e19 
   VclStylesInno.dll 
   1.2.9.5 
   5451a3c1 
   c0000005 
   000030c9 
   f9c 
   01cff6ff268cf326 
   C:\Users\LEEUN_~1\AppData\Local\Temp\is-DVFHG.tmp\LAMP_0.9.3.v8.tmp 
   C:\Users\LEEUN_~1\AppData\Local\Temp\is-DGC9D.tmp\VclStylesInno.dll 
   7b83bbcc-62f2-11e4-82a6-0c8bfd21ef66 

Original comment by leeunive...@gmail.com on 3 Nov 2014 at 12:49

Attachments:

• Temp2.zip

[GoogleCodeExporter]

BTW.....  One of my users reported constant crashing with and without Steam 
running with my latest installer, I've asked him for the log's, and I'm still 
waiting for another user that had crashing to test.

Original comment by leeunive...@gmail.com on 5 Nov 2014 at 9:42

[GoogleCodeExporter]

Okay, so one of my users said he didn't have a crash when installing.
But he went a looked at the Log Anyway, and he said the "last line" in the 7 
Line Log DID say this.

Access violation at address 0000006C. Write of address 0000006C.

Original comment by leeunive...@gmail.com on 6 Nov 2014 at 12:22

[GoogleCodeExporter]

Okay, so my other user who had previous crashing issues reports with the latest 
installer also no crashing on install.

So, two previous users report no crashing other than the above access 
violation, but I do have a "new" user who does report crashing apparently with 
the latest installer, he's the one I reported in post #13, still waiting on his 
logs.

BTW, my latest installer was using the "previous" .dll.  So, the two new good 
reports and the new bad report were using it (at least I think on this last 
guy).  I was testing the new .dll when I had my crash finally, and almost 
immediately when using the new .dll. while the previous .dll that my two users 
report no crashing anymore I ran it a 100 times at least, and no crash, while I 
would have one around every 20 or so runs before.

So, 3 of us report no crashing on your previous .dll and with InnoCallBack.dll 
removed.  I had a crash almost immediately on the new .dll.  My new user that 
reported crashing with and without Steam running "apparently" was using the 
version that we all no longer crashed on.  But, still trying to verify that 
with a log.  Sorry this so erratic, users are unreliable.  LOL

Original comment by leeunive...@gmail.com on 6 Nov 2014 at 1:11

[GoogleCodeExporter]

BTW, I wanted to mention that when I had my crash that I posted above, I was 
doing several things, like I had the VCLStyles Editor open, etc.

But, I haven't had a crash yet again still using the new .dll.

So, it "appears" that maybe your .dll is sensitive to maybe some things running 
sometimes, or certain things?

Original comment by leeunive...@gmail.com on 6 Nov 2014 at 1:16

[GoogleCodeExporter]

Thanks, for all the feedback, about your question the dll (plugin) is not 
affected by external running Apps. because only run on the memory address space 
of the calling process. 

Original comment by Rodrigo.Ruz.V@gmail.com on 6 Nov 2014 at 2:07

[GoogleCodeExporter]

You're welcome.
So have you looked at the Error logs I've uploaded?
Any thoughts?

And ya, previous crashes and some user crashes nothing was running, but, it 
simply seemed more common when things were running, so just mentioning just in 
case.

Original comment by leeunive...@gmail.com on 6 Nov 2014 at 2:26

[GoogleCodeExporter]

So, I crashed again.....
I've had to update my mod pack, and so I compiled the full mod pack, and then I 
ran it through the InnoSetup compiler, and I crashed again.

Note, I "seem" to always crash at the same point, and that is the page with the 
Scroll bar that you fixed.  Though, I may have crashed other times just can't 
remember, and my users have reported crashing at different points, not a 
particular spot.

Hope you can get this fixed....  I really like your skin.

Here's the Windows log and the Inno Log is attached.....

Faulting application name: LAMP_0.9.4.v1.tmp, version: 51.52.0.0, time stamp: 
0x2a425e19
Faulting module name: VclStylesInno.dll, version: 1.2.9.5, time stamp: 
0x5451a3c1
Exception code: 0xc0000005
Fault offset: 0x000030c9
Faulting process id: 0x24c0
Faulting application start time: 0x01cffa7c11b9b6a7
Faulting application path: 
C:\Users\LEEUN_~1\AppData\Local\Temp\is-KNPF9.tmp\LAMP_0.9.4.v1.tmp
Faulting module path: 
C:\Users\LEEUN_~1\AppData\Local\Temp\is-5AUJF.tmp\VclStylesInno.dll
Report Id: 710149e3-666f-11e4-82a8-0c8bfd21ef66
Faulting package full name: 
Faulting package-relative application ID: 

Original comment by leeunive...@gmail.com on 7 Nov 2014 at 11:24

Attachments:

• Log.zip

[GoogleCodeExporter]

Wow, I just crashed twice in a row when I ran the installer again through 
innocompiler.
Again, same page.

Here's the logs again.....

Faulting application name: LAMP_0.9.4.v1.tmp, version: 51.52.0.0, time stamp: 
0x2a425e19
Faulting module name: VclStylesInno.dll, version: 1.2.9.5, time stamp: 
0x5451a3c1
Exception code: 0xc0000005
Fault offset: 0x000030ff
Faulting process id: 0x2c58
Faulting application start time: 0x01cffa7de23b1236
Faulting application path: 
C:\Users\LEEUN_~1\AppData\Local\Temp\is-R7763.tmp\LAMP_0.9.4.v1.tmp
Faulting module path: 
C:\Users\LEEUN_~1\AppData\Local\Temp\is-ONRDG.tmp\VclStylesInno.dll
Report Id: 48d3e300-6671-11e4-82a8-0c8bfd21ef66
Faulting package full name: 
Faulting package-relative application ID: 

Original comment by leeunive...@gmail.com on 7 Nov 2014 at 11:31

Attachments:

• Log2.zip

[GoogleCodeExporter]

TRIPLE WOW.....  I just crashed for a third time in row.
I've never crashed so badly before, and I haven't ran the installer much at all 
since I switched to your last .dll, and so all the crashing I've had including 
the one before seems to be with that .dll.  But, who knows.

Faulting application name: LAMP_0.9.4.v1.tmp, version: 51.52.0.0, time stamp: 
0x2a425e19
Faulting module name: VclStylesInno.dll, version: 1.2.9.5, time stamp: 
0x5451a3c1
Exception code: 0xc0000005
Fault offset: 0x000030c9
Faulting process id: 0x8b0
Faulting application start time: 0x01cffa7e788e6972
Faulting application path: 
C:\Users\LEEUN_~1\AppData\Local\Temp\is-1T6LF.tmp\LAMP_0.9.4.v1.tmp
Faulting module path: 
C:\Users\LEEUN_~1\AppData\Local\Temp\is-0DV54.tmp\VclStylesInno.dll
Report Id: 26331c05-6672-11e4-82a8-0c8bfd21ef66
Faulting package full name: 
Faulting package-relative application ID: 

Original comment by leeunive...@gmail.com on 7 Nov 2014 at 11:39

Attachments:

• Log3.zip

[GoogleCodeExporter]

BTW, forgot to mention that that last crash occured while the program was 
actually "installing" files, not on that scroll page.

Original comment by leeunive...@gmail.com on 7 Nov 2014 at 11:42

[GoogleCodeExporter]

Well....  I don't know what's going on.
It's crashing every time now after a compile and run within Innosetup.
I even used the previous vclstyles .dll and it's still doing it.

I don't see anything also in the code that should be an issue.
I've compared previous iterations and for the life of me I don't see anything 
obvious.

Original comment by leeunive...@gmail.com on 7 Nov 2014 at 1:47

[GoogleCodeExporter]

I will create a special version of the plugin with an exception logging, to 
determine where the exception occurs. So wait for the new version ;)

Original comment by Rodrigo.Ruz.V@gmail.com on 7 Nov 2014 at 4:06

[GoogleCodeExporter]

Great thanks much... :)

Original comment by leeunive...@gmail.com on 7 Nov 2014 at 6:50

[GoogleCodeExporter]

Oh, and here's my entire "project" code if you want to compile the setup 
yourself and look over the code etc.  Your's is the "Final" one, the Zinstaller 
is an old one that works no crashing, and it has the same code as yours accept 
some minor differences and using ISSkins.  But it has other things "hidden" 
(why I went to you) like, the next button won't work if using the license page, 
have to go back a page, the info pages won't scroll accept with the mouse, and 
if you have a long info page and you go back to it, some of the previous page 
will be showing in the window.

http://www.mediafire.com/download/3af7185hpdhvyty/LAMP.zip

Original comment by leeunive...@gmail.com on 7 Nov 2014 at 6:55

[GoogleCodeExporter]

Oh, forgot to mention that due to some special "functions" in the code, you 
need to use InnoUltra 5.5.1 ANSI to compile it.

Original comment by leeunive...@gmail.com on 14 Nov 2014 at 2:22

[GoogleCodeExporter]

I just made several changes to the library. please check the new version 
(1.3.1.5) and let me know the results. 

Original comment by Rodrigo.Ruz.V@gmail.com on 15 Nov 2014 at 2:35

[GoogleCodeExporter]

K, I will check it....  thanks much.

Original comment by leeunive...@gmail.com on 15 Nov 2014 at 4:34

[GoogleCodeExporter]

OMG....  It might be a miracle.... :)
Several runs so far and I haven't had a crash.  Looks like you've done great 
work.
However, just to be sure, I need to keep running it over the next few days, and 
have all my users try it, especially those who had crashing.

Well done work though so far.  Great job.   :)  Thank you.

Original comment by leeunive...@gmail.com on 15 Nov 2014 at 5:39

[GoogleCodeExporter]

BTW, did you enable "logging" in the .dll or whatever, so I can tell my users?

Original comment by leeunive...@gmail.com on 15 Nov 2014 at 8:05

[GoogleCodeExporter]

No logging mechanism was enabled on this version.

Original comment by Rodrigo.Ruz.V@gmail.com on 15 Nov 2014 at 3:08

[GoogleCodeExporter]

Okay, good news....
With your latest installer from the 15th, 70 downloads of it, and only "1" user 
reports a "crash" of the installer, and that was because he had "Steam" on.... 
which was a problem for him before.  But he installed fine without Steam on.

So wonderful, looks like you've fixed this problem, unless you also have any 
idea about Steam?  But, that's fairly normal with installers sometimes.

Thank you much for your work....  Now just the radio button bug to fix, and it 
looks like we are set.

Original comment by leeunive...@gmail.com on 18 Nov 2014 at 3:03

[GoogleCodeExporter]

Thanks for the info, about the another issue I will try to check that tonight. 

Original comment by Rodrigo.Ruz.V@gmail.com on 18 Nov 2014 at 3:05

• Changed state: Fixed

[GoogleCodeExporter]

BTW, here's the log files of the guy who crashed with "Steam" running.
It includes his first two attemps with Steam running, sound off, then on, and 
then the third attempt with Steam off, install successful.

In case it helps to further improve something.

Original comment by leeunive...@gmail.com on 18 Nov 2014 at 6:01

Attachments:

• Steam_Crash.rar

[GoogleCodeExporter]

Danget... :(  Crashed again, twice in the same day, last two .DLL's.
Went a bit without a crash on the previous .dll.

*** Previous dll crash****
Faulting application name: LAMP_0.9.4.v5.tmp, version: 51.52.0.0, time stamp: 
0x2a425e19
Faulting module name: VclStylesInno.dll, version: 1.3.2.1, time stamp: 
0x5467735e
Exception code: 0xc0000005
Fault offset: 0x00003463
Faulting process id: 0x2630
Faulting application start time: 0x01d005610934ea9e
Faulting application path: 
C:\Users\LEEUN_~1\AppData\Local\Temp\is-BA2KB.tmp\LAMP_0.9.4.v5.tmp
Faulting module path: 
C:\Users\LEEUN_~1\AppData\Local\Temp\is-DRC50.tmp\VclStylesInno.dll
Report Id: 6a8e3980-7154-11e4-82ac-0c8bfd21ef66
Faulting package full name: 
Faulting package-relative application ID: 

---

Fault bucket 73673966730, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: LAMP_0.9.4.v5.tmp
P2: 51.52.0.0
P3: 2a425e19
P4: VclStylesInno.dll
P5: 1.3.2.1
P6: 5467735e
P7: c0000005
P8: 00003463
P9: 
P10: 

Attached files:
C:\Users\leeun_000\AppData\Local\Temp\WERA0C9.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LAMP_0.9.4.v5.tm_944
16c0ef2d9ef3171e4087351390cfa23313cc_914c7df2_1beb0d1f

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6a8e3980-7154-11e4-82ac-0c8bfd21ef66
Report Status: 0

**** Last .DLL Crash ****
Faulting application name: LAMP_0.9.4.v6.tmp, version: 51.52.0.0, time stamp: 
0x2a425e19
Faulting module name: VclStylesInno.dll, version: 1.3.2.5, time stamp: 
0x546ea4f0
Exception code: 0xc0000005
Fault offset: 0x000030e9
Faulting process id: 0x2068
Faulting application start time: 0x01d005bf94470546
Faulting application path: 
C:\Users\LEEUN_~1\AppData\Local\Temp\is-KEDRV.tmp\LAMP_0.9.4.v6.tmp
Faulting module path: 
C:\Users\LEEUN_~1\AppData\Local\Temp\is-KVES4.tmp\VclStylesInno.dll
Report Id: 9697ba79-71b3-11e4-82ac-0c8bfd21ef66
Faulting package full name: 
Faulting package-relative application ID: 

----

Fault bucket 73675308643, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: LAMP_0.9.4.v6.tmp
P2: 51.52.0.0
P3: 2a425e19
P4: VclStylesInno.dll
P5: 1.3.2.5
P6: 546ea4f0
P7: c0000005
P8: 000030e9
P9: 
P10: 

Attached files:
C:\Users\leeun_000\AppData\Local\Temp\WER58E7.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LAMP_0.9.4.v6.tm_61c
0437e75431a76897ba72b2a41296ec03cafe_444edde9_35c74674

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9697ba79-71b3-11e4-82ac-0c8bfd21ef66
Report Status: 0
Hashed bucket: 747fae333ce4f453a67199ac77b8d368

Original comment by leeunive...@gmail.com on 21 Nov 2014 at 7:42

[GoogleCodeExporter]

Logs....

Original comment by leeunive...@gmail.com on 21 Nov 2014 at 7:44

Attachments:

• fsfsfssf.png
• 11.21.2014_crash.zip
• 11.21-2.2014_crash.zip

[GoogleCodeExporter]

Here's also the "report archives" per the links in the above reports.

Original comment by leeunive...@gmail.com on 21 Nov 2014 at 7:51

[GoogleCodeExporter]

ah

Original comment by leeunive...@gmail.com on 21 Nov 2014 at 7:51

Attachments:

• ReportArchive.zip

[GoogleCodeExporter]

Okay, one of my users who's almost always had crashing, has done a bunch of 
detailed testing and saved the logs.....

Here you go...  
https://www.mediafire.com/folder/wtfvcq3w0ncnkjx,4r0y4gy1z5ha3kf,kkfkq8rb30jrcpu
,jb34u4u1mzddwf9,9doadw40tsgaeof,o2z9kyq5p8hzs2i,qfge25d16fa7ari/shared

Original comment by leeunive...@gmail.com on 22 Nov 2014 at 4:40

[GoogleCodeExporter]

Hey.... So any word on this continued crashing?

Original comment by leeunive...@gmail.com on 9 Dec 2014 at 12:24

[GoogleCodeExporter]

Sorry, for the delay but I don't receive any notifications on my mail about 
this issue because is marked as closed. 
  As you know I really invested a lot of time on this case. So finally I concluded which the issue can be caused for one of these 

1. The interaction of the plugin with the InnoUltra version. (The plugin only 
supports the official release of Inno setup).

2. Some third-party dll used on the installer can cause which the plugin crash. 

  So my advice is migrate the installer to an official inno setup release, and also avoid the use of third-party dlls when was possible.

  Unfortunately due which is a random exception, is very difficult identify which is causing of the issue.    

Regards
Rodrigo.

Original comment by Rodrigo.Ruz.V@gmail.com on 11 Dec 2014 at 3:34

[GoogleCodeExporter]

Thanks for your reponse.

The only problem with what you think is causing the "crashing" is that when 
your skin isn't used at all, no crashing occurs, and the error message only 
relates to your .DLL.  If it was something else, other things would be also 
indicated.

The reason for InnoUltra usage is that regular InnoUltra doesn't allow for the 
usage of certain functions and abilities, like music, the pic rotator, etc.  
InnoUltra allows for more customization.  Also, ISSkin's doesn't cause any 
crashing, though it has other window alignment issues which is why I went to 
VCLskins.

Also, just an FYI, InnoUltra is "common" used among the community because of 
the official setup limitations.  So, if there is any way you could one day 
again try to resolve the issue, it would be great.

But, I guess it seems you've gotten tired of working on the issue for now, so I 
appreciate you're at least trying and the other work you've done.  I guess I'm 
going to have to go "skinless" in order to not have crashing or other issues.

Thanks again for trying at least.....
It's too bad, really thought we had it fixed finally, not sure why it started 
again.
Anyway, take care.....

Original comment by leeunive...@gmail.com on 11 Dec 2014 at 4:15

[GoogleCodeExporter]

Hi, I'm aware which the crash is caused by the plugin, What I mean is the 
plugin fails because is not compatible with InnoUltra or another third-party 
dll used. Anyway I just uploaded a new version (1.3.4.0) which you can try out. 
On this new version some of the core components used by the plugin was updated. 

Original comment by Rodrigo.Ruz.V@gmail.com on 11 Dec 2014 at 7:12

[GoogleCodeExporter]

Okay....  So, I've used the updated .dll and also put in the Uninstaller code, 
no crashes on my end yet after several try's/installs.

I've released it to my users, so let's see if they report any crashes.
Let's hope it's all good finally.  :)

Original comment by leeunive...@gmail.com on 14 Dec 2014 at 7:06

[GoogleCodeExporter]

Hmmm....  So, didn't have a single crash with the previous .DLL one from the 
11th (or any users reporting a crash).
But this last .DLL from the 21st I crashed on the 2nd run.

Original comment by leeunive...@gmail.com on 23 Dec 2014 at 7:15

[GoogleCodeExporter]

Ugh....  It now crashed on the 3rd run with a new compile.....

Original comment by leeunive...@gmail.com on 23 Dec 2014 at 7:50

[GoogleCodeExporter]

Okay, so I recompiled again but with the previous 11th .DLL and I've ran the 
installer 3 times now, and not a single crash.

Oddly, the uninstaller is using the cached skin that the new DLL made allow to 
work on the "outside" border of the uninstall box, that the version on the 11th 
didn't have.

Do you want me to try the new DLL again and get you the error logs?

Original comment by leeunive...@gmail.com on 23 Dec 2014 at 8:17

[GoogleCodeExporter]

Hey....  Just wanted you to know that the latest .DLL Jan 18, several runs, 
several full compiles and installs, and not a single crash, no matter what I 
did or was doing.

This is good news....  Basically ALL previous crashed at some point, save long 
ago versions, and a couple a bit long ago.  All of late have been crashing at 
in some way more or less.

But this one, nothing.....  Great work....
Thank you so much.  :)

Original comment by leeunive...@gmail.com on 25 Jan 2015 at 4:21

[GoogleCodeExporter]

[deleted comment]