Hi, yesterday I clean installed 5728 x86 German Ultimate with two IDE HDs, three partitions, one C drive with RC1 x86 German, and 5728 on E.

I enable Data Execution Prevention before I installed BootPro 2.1 for all programs, it runs fine. I saw the update available, downloaded and installed it by removing the older version. When I agreed to launch it simply crashes.
I added an exception to DEP for 3.0 and then it launches fine. Known issue?

Greetings Stefen

Your'e a star sniem. Thank you very much for posting this. We will get that fixed.

Oh and welcome to PROnetworks

Grav!ty wrote:

Your'e a star sniem. Thank you very much for posting this. We will get that fixed. Oh and welcome to PROnetworks

Oh, thanks .

Your software is btw a must have for Vista users

Grav!ty wrote:

Thank you very much for posting this. We will get that fixed.

FYI, does repro with 3.1. But as this wasn't mentioned in the changelog I'm not surprised

I am running Windows Vista Build 5728, and notice this problem too. I am using VBP VistaBootPro 3.1 Beta. I just wanted to post more information, so others will realize the problem/solution.

With DEP fully enabled (Turn on DEP for all programs and services except those I select)..........

Upon startup of VBP, I get:
---------------------------
'XPExplorerBar_nat.dll' not found!
---------------------------
Can't find native library! Please install the native library to your local directory or to your system(32) directory.
---------------------------
OK
---------------------------


After I click OK, I get:
---------------------------
Unhandled Exception
---------------------------
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidProgramException: Common Language Runtime detected an invalid program.

at XPExplorerBar.TaskPane..ctor()

at VistaBootPRO.VistaBootPRO.AAJO(rM()

at VistaBootPRO.VistaBootPRO..ctor()

at AuO2K52XBYDY56C92XWV.AAJO(rM.AAJO(rM()

--- End of inner exception stack trace ---

at E9Z6L.ACsfw0BeQi4hYNTA.ACsfw0BeQi4hYNTA(String[] )

at Bx0dBWouRcx6NTrFZ34ruNckOfq9.ADJATbVDkW.AAa3nV5OB92LEZqr(String[] )

--- End of inner exception stack trace ---

at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)

at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)

at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)

at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
---------------------------
OK
---------------------------

After I click OK, nothing happens.

SOLUTION: Add "VistaBootPRO.exe" to the DEP exceptions list. (This should not involve a restart). VBP then works normally.

Thank you for the program - I hope you get this fixed quickly.

sniem wrote:

Hi, yesterday I clean installed 5728 x86 German Ultimate with two IDE HDs, three partitions, one C drive with RC1 x86 German, and 5728 on E. I enable Data Execution Prevention before I installed BootPro 2.1 for all programs, it runs fine. I saw the update available, downloaded and installed it by removing the older version. When I agreed to launch it simply crashes. I added an exception to DEP for 3.0 and then it launches fine. Known issue? Greetings Stefen

Hi JacobKlein and welcome to PROnetworks. Thank you both very much, sniem and JacobKlein for reporting this to us. It is very few folk who enable DEP for all programs, but we have found what is causing this error

The compression code we have been using on the *_nat.dll files is the culprit and will be changed in the next release. In the mean time it is totally safe to add the program as an exclusion to the DEP monitored programs list

We had very limited time to make the most crucial changes to the application to fix the issues we did from Version 3.0 to Version 3.1 as the two programmers coding the application are both on a well deserved break at the moment