Please report all bugs for the VistaBootPRO program in this thread. Each bug will be reviewed and fixed in upcoming builds. Please specify the OS the bug occurs in and only report bugs for the most recent version of VistaBootPRO.

Thank you for your support in making VistaBootPRO better than ever!!!

Current Version - 3.1
VistaBootPRO

Note: We appreciate all feedback. Non-bug content and comments will however be moved to a more appropriate area.



++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

When you run Vista with a custom font size such as 110 DPI (115% of normal) many items are cut off and cannot be read easily. (My monitor's native display resolution is 1600x1200.) The program runs perfectly and is easily ised at the normal DPI setting.

JanJ wrote:

When you run Vista with a custom font size such as 110 DPI (115% of normal) many items are cut off and cannot be read easily. (My monitor's native display resolution is 1600x1200.) The program runs perfectly and is easily ised at the normal DPI setting.

Thank you for bringing this to our attention JanJ. We will see if we can fix this in a future version

JanJ wrote:

When you run Vista with a custom font size such as 110 DPI (115% of normal) many items are cut off and cannot be read easily. (My monitor's native display resolution is 1600x1200.) The program runs perfectly and is easily ised at the normal DPI setting.

Yes, thank you JanJ and welcome to PROnetworks!! We really appreciate all reports on this program; please stop by our Introduction Area so we can give you a PRO welcome! Enjoy the site!

jrfree1 wrote:

martyfelker wrote: VistaBootPRO says Vista has not been installed when first loaded but then works fine. Is this because I have dual boot (Vista Bootloader) with Winxpx64 on first partition? Since I use BootITNG (great program) I installed Vista on second partition but it THINKS it is C:. Anyway what's with the load message? Actually, I believe the message you are getting says "VistaBootPRO has detected that either Microsoft Windows Vista is not currently installed, or you may have an irregular drive configuration" In your case it sees an irregular drive configuration so there should be no problems running the program.

i have the same error using vista 5744 and VBP 3.1
i didn't think my drive configuration was unusual *shrug*
1x80GB hard drive split into 3 partitions, xp32 (20gb), xp64 (20gb) and vista64 (approx 38gb)

There is an issue that is more (IMO) a BIOS issue than a specific Vista or VBPro issue........... we really need to the Hardware guys on/into this to see what the "sticking point" is. We have had numerous issues with IDE/SATA in justa about EVERY configuration you can come up with. Grav!ty has a thread here somewhere with some insights into IDE/SATA configs and dual booting XP and Vista........ I'll find it in a sec.... or eventually.....lol

opening the app anyway, it appears to be working properly but i'm a little nervous about changing anything after the message :p
i tried the advanced option to allow unsigned drivers in vista x64, but that didn't work

Pyr0 wrote:

i have the same error using vista 5744 and VBP 3.1 i didn't think my drive configuration was unusual *shrug* 1x80GB hard drive split into 3 partitions, xp32 (20gb), xp64 (20gb) and vista64 (approx 38gb)

Thats weird, I've tested that in 5 or 6 different installations of XP. Did you get that in XP X64 or XP X32? or in Vista X64?

Pyr0 wrote:

opening the app anyway, it appears to be working properly but i'm a little nervous about changing anything after the message :p i tried the advanced option to allow unsigned drivers in vista x64, but that didn't work

That function has been changed by MS Pyr0, so in Vista X64 it overrides the setting that we use. Although the setting we use actually takes, it does not work now in X64 and we are looking at how to get that sorted out.

The only way to disable driver signing in Vista X64 is to do it from the boot menu by hitting F8 and then selecting to turn it off. On reboot it reverts back to not allowing unsigned drivers unless you do that again.

i tried VBP in vista x64, haven't tried in any other os yet

yeah i hate having to remember to press F8 every reboot

I installed VBP on Win2K3 but it doesn't run, giving the following message: "Can't find native library! Please install the native library to your local directory or to your system(32) directory". When I click OK it gives me a bunch of unhandled exception errors and aborts. I checked it out and XPExplorerBar_nat.dll is in C:\PROnetworks\VistaBootPro 3.1 directory. Copying it to System32 doesn't help either...
Vista is installed on another physical hard disk.
I have 3 physical hard disks: 40Gb ATA, 120Gb ATA, 300GB SATA. Vista is on the 40GB ATA, but it placed the BCD on 120Gb drive somehow. And 2K# is on the 300GB SATA.
When I run VBP on vista, it tells something like "non-standard drive configuration" and "can't fine vista" (it probably looks for it on the 120Gb drive where BCD ias located)
Then I edited the boot store from VBP and added an entry to the drive where 2K3 is located, but when I choose the 2K3 entry during boot it gives the missing ntloader message and doesn't boot. The 2K3 is perfectly operational however if I change the boot drive priority to SATA from BIOS. Any help would be very much appreciated