Welcome Guest Search | Active Topics | Sign In | Register

Windows XP Unhandle Exception: This version of Windows is not supported Options
enriquecorpus
Posted: Tuesday, March 27, 2018 10:29:59 PM
Rank: Newbie
Groups: Member

Joined: 3/27/2018
Posts: 3
Hi Guys,
I just want to ask if how can i catch the unhandled exception that i am getting when trying to open the EO browser on windows XP.
The error message says: This version of Windows is not supported. That is fine, if we cant run the browser in XP machines, its just we need to disable to unhandled exception error popup. I tried adding the handler which i found i some thread ' AddHandler EO.Base.Runtime.Exception, AddressOf Me.EOBaseRuntime_Exception_Handle' but still no luck. Here is the image of the exception message Unhandled Exception
eo_support
Posted: Wednesday, March 28, 2018 7:52:38 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,258
Hi,

You won't be able to silence this exception and make it work. The current version does not support Windows XP because it relies on system APIs that does not exist on XP, not because we don't want to make it work on XP.

Thanks
enriquecorpus
Posted: Friday, April 6, 2018 12:58:35 AM
Rank: Newbie
Groups: Member

Joined: 3/27/2018
Posts: 3
eo_support wrote:
Hi,

You won't be able to silence this exception and make it work. The current version does not support Windows XP because it relies on system APIs that does not exist on XP, not because we don't want to make it work on XP.

Thanks


Hi,

Thanks for the reply. Yep, i get it. Its ok if the browser wont run on xp. What I only need is to disable/hide or catch the exception message was there any methods that I can use for that?

Cheers.
eo_support
Posted: Friday, April 6, 2018 8:02:50 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,258
You would silence the exception the same way as you silence any other exception in your application. For example, you have a clear call path to the exception point, then you can put a try catch block around it. If you do not have a clear call path, then you will need to look into your application and see where/how to handle it. For example, for WPF application, you can look into the DispatcherUnhandledException. None of these have anything particular with our product, so you will need to work out the details yourself.


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.