[UNSUPPORTED] Open 7 act*vator by Nononsence [revised by HotCarl] ;-)

That is odd, I will look into it. I don't know how an unhandled exception managed to get past the goalie, but I'll figure it out for 1.0.9.
I assume since the exception was unhandled that there is no error event in O7A's error log? (in your temp folder, if you dont know which is your temp folder, open cmd.exe and type "echo %TEMP%" and hit enter)

Strange that I have no problems with it on my PC in the testing I have done. No matter, I will fix it before the next release.

Thanks for the bug report.

 

Well, I don't think that is it because I dont use a background worker on load...but thank you for the suggestion.
I went through and tested it to the best of my ability and found no exception, so I added some more error handling in some other places so I can trap it if it occurs again (as I cannot duplicate what you are experiencing, but I will keep trying to make it crash so I can find any faults).

 

I use a loop (hence the status bar & splash screen) because the background worker has caused issues for me on load in the past, like you noted above, so I dont use it there.

For Each objMgmt In LicenseStatus.Get

EDIT: And I have always had everything that is on load encapsulated in multiple try...catch statements, so I dont see how he could have gotten an unhandled exception on load...

 

I dont know why either, and no one else has had an issue (or at least no one has said anything...) so I am beginning to think that it is specific to his machine.

I forgot to ask if he was running a 64-bit copy of windows...because the only other time I have seen an error like that on load in VB.NET (that I couldnt explain) is when reading in a database on load...and I had to set the advanced compile options > target CPU to x86 to force it to run 32-bit mode on the 64-bit machine to get rid of it... But that would not matter in this case. *shrug*

 

Ahhh, that makes sense. Thanks for the clarification.

 

Thank you for the clarification. I bolded the reminder on the OP that says to ensure that you have the most recent .NET framework installed (v3.5) if you have Windows Server 2008 R2.

Seeing as how it is only Windows Server 2008 R2 family that does not ship with .NET framework, I don't think it is a big deal to require that those users update their .NET first...it is probably a good idea to have the most recent version anyway.

 

Possibly in the future if I ever decide to expand the supported operating systems for O7A. The PID checker only really needs to check Windows 7 and Server 2008 R2 keys...and it seems to do that just fine in my tests, although it could be nice to have it check for other types of keys as well (for FYI purposes for the end user).

Its up to you, if you want to share your source, then I would be happy to look at it (I don't like copy and pasting code, but I do like seeing how others have implemented certain ideas)...but I probably couldn't do anything with it until Friday because I as so darn busy this week (college, work, and Modern Warfare 2 just came out ).

But feel free to PM me a link and I will try to take a look at it asap. Thanks.

 

Right on, I will save it to the HD and look at it as soon as I can.