I dont see any V9 for PC-BSD. The last stable release of PC-BSD is Version 8.2 as per their website. So using Beta software is not something that we can control if issues arise. They could have easily made changes to the software to cause this. Only they can answer such questions.
EasyBCD only adds entries to the boot menu for the various OS's out there. Other than that it has nothing at all to do with how the OS or system operates. This is an issue with PC-BSD and has to be taken up with them.
If EasyBCD was to blame you would get the error "OS not found press Ctrl+Alt+Del to restart" and you would then get brought back to the boot menu. Since you are only getting a boot error message this can only be the result of PC-BSD.
Did you have a stable and working install of PC-BSD 9 before you restarted and added it via EasyBCD? I never used version 7 either. I only used Version 8.1 of PC-BSD.
Alright that could be the issue then. You might have to redo the install of PC-BSD and have it not write the boot loader to the MBR but to that drive. Then add an entry for PC-BSD using EasyBCD.
The issue is 2 fold. PC-BSD doesnt use a standard boot loader. For the longest time they used the BTX loader which wasnt supported by anyone or anything let alone PC-BSD. We contacted them a long time ago to try and get support for their OS to use with EasyBCD for as far back as i remember.
Now they switched to what I can only assume is the FreeBSD loader. I still dont know, nor can confirm my suspicion on this with them cause my question has gone unanswered for the longest time. To make matters worse, they have now removed the EasyBCD guide from their Wiki. Showing that they dont want to have their OS installed along side of any others.
If we could talk to one of the Dev's and find out what boot loader they are using and how it operates I am sure that Mahmoud could code EasyBCD to work properly with PC-BSD. Until then not installing the loader and just creating a FreeBSD entry is all we can suggest for a fix.
The way we are doing installs on PC-BSD is to use the "MBR" loader only if the user clicks to install it from the GUI. This loads the standard freebsd /boot/boot0 MBR loader with the following command:
# gpart bootcode -b /boot/boot0 /dev/ada0
The only other time we do something like this is if you select GPT as the disk-scheme, in which case we load the protective MBR:
# gpart bootcode -b /boot/pmbr /dev/ada0
Do you remember when you did the install if you chose to use the GPT scheme? That would make a huge difference here I'm sure.
Also, we do still have the EasyBCD section in our handbook:
That option must have change. I remember I had to specifically check the box to UNdo the use of the MBR and have it install to the drive itself. Now you say that they have to check the box? So that has definately changed since I installed 8.1 not long ago.
The reason why I say EasyBCD was removed, is cause the only other entry I seen for it was deleted:
Some users were experiencing problems with GPT so we changed the default back to MBR for 9.0. We've had other users successfully dual-boot on two separate drives and have a mailing list thread started by roelof: