After applying the "no driver check" option using vistabootpro 3.3.0.0 on my vista ultimate x64 SP1 (build 6001 SP1) I found out this option does not work, driver checking still is enabled.
Yes, I rebooted, it's denoted obvious enough in VBP.
During this test a "Test Mode" watermark is displayed in all four corners, no problem so far.

Then, after re-enabling the "driver checking" in vistabootpro 3.3.0.0 nothing obvious changed, BUT the watermarks still are in place after reboot.
Tried several times over to correct the setting in VBP (though it's NOT marked as disabled driver checking), nevertheless the watermarks stay in place.

Then I tried booting in safe mode, mode without driver checking, and normal in a row assuming one of them restores the normal setting.
To no avail....

Also tried
Bcdedit.exe /set nointegritychecks OFF
To no avail....

In my opinion VBP doesn't restore one of the normal settings as it should, it only messed up vista.
Even tried reversing to a restore point before installation of vistabootpro, also to no avail.

Any solutions for this ?

I also noted VBP complaining about "vista not installed or on hidden drive" at every startup of VBP, despite starting it from within vista itself

Regards


Note:
typing bcdedit /enum all gets me following list
(after re-enabling drivers signing that is, and watermarks still in place)

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {80cb88f6-f63a-11dc-88ce-fa6341db669a}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
bootdebug No
nointegritychecks No
testsigning Yes
osdevice partition=C:
systemroot \Windows
resumeobject {80cb88f6-f63a-11dc-88ce-fa6341db669a}
nx OptIn
pae ForceDisable
vga No
quietboot No
sos No
debug No

Resume from Hibernate
---------------------
identifier {80cb88f6-f63a-11dc-88ce-fa6341db669a}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device partition=C:
path \ntldr
description Earlier Version of Windows

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

________________________________________________________
No I'm not stupid, I just want to know what's all the fuzz about the errors other people have made earlier :-p

Ok, solved it, it all comes down to

bcdedit /set testsigning off

I don't know if vistabootpro messed up something else while being so busy, no other obvious things changed so far.

That was the first AND the last time I've used vistabootpro, that's for sure !!

Hope this info helps someone else too.

greetz

mmm...applications don't just run commands on their own and VistaBootPRO definetly cannot run the command to turn on test signing. You must have done that by some other means. It's usually best to ask for information before trying something like that one is unfamilar with.

Grav!ty wrote:

It's usually best to ask for information before trying something like that one is unfamilar with.

Well, then explain this to me, I'm open to any other explanation if any:
- Vistabootpro was the ONLY app I tried to fool around with for disabling driver signing
- only AFTER using the option to allow unsigned drivers from within vistabootpro the "test mode" watermark came up in the corners
- Vistabootpro didn't succeed at all in disabling the blocking of unsigned drivers
- turning the option to check driver signing back on from within vistabootpro (restore original setting AND reboot) DIDN'T get rid of the watermarks at all

The only option to turn the watermarks off was by manually using the bcdetit /set testsigning off, something that (imho) ONLY could have been modified from within vistabootpro since NO other app as vistabootpro was ever tried (and no, not even bcdedit, found that trick later and after damage was already done)

Any suggestions ?

Like Grav!ty explained VistaBootPRO does not contain ANY code that sets test signing to on. However, that does not mean it didn't trigger something within Windows itself to turn that option on. Again, VBP doesn't contain the command to do that so there isn't a way for it to run that command.

Drivers and Windows are a very touchy situation. Disabling driver signing could have easily caused Vista to revert back to test signing. In fact, I have had situations where I have used Bcdedit and it caused Vista to un-activate itself.

Also, for the 'hidden drive' message it is stating that it can't find a certain file to check for Vista. This is being removed in later versions as the code checking all the information is faster than the information being passed in by Windows. It is nothing to worry about and certainly has no effect on your system or the application (except the annoying message)

Hope that helps explain things a little more.

Jason