Vista odity

FinalBuilder Discussion
1

Here's an odd thing...   Any ideas are welcome (and I've already heard "Revert back to XP" lol).

FB5 and Delphi 2006 is installed on an XP Pro Guest VM under VMWare 6 with Vista X64 as host.

My Delphi projects are on my host computer under a shared folder (with full access).

I've mapped the project folder shares as drives on the XP Guest.

Prior to moving moving to Vista as a host, I had XP.  All worked great. 

Now... under Vista, when I build, I get a link error from Delphi under FB5.

The kicker....  I can open up Delphi and build all / compile and not a problem at all.

As a test, I created a folder off the XP guest's C drive and told FB5 to set that as the output path.

That resolved the issue for now and I can live with that.

I do have NOD32, if that matter.  

Lance

2

Hi Lance,

Sorry to hear you’re having problems. Unfortunately, I’m a little confused. Can I just check my understanding of the problem:

- FinalBuilder is running Delphi from inside the XP VM.

- The VM is building files located on the Vista host, accessed via a network share which is mapped as a drive (ie there are no UNC paths involved.)

- When XP was the host, this same setup (same VM?) worked fine.

- Now that Vista is the host, this does not work any more.

Am I following you properly?

Which machine has NOD32 on it, the host or the guest? If you try disabling it, does it make a difference? Do you have “Full Access” enabled for the shares in Vista? Could you please post the log ouput from the failed Delphi action?

Unfortunately, it sounds like this is more likely to be a Delphi command line compiler issue than anything we can deal with, but we’re happy to investigate somewhat. Thanks for your patience.

Regards,

Angus

3

Angus,

thanks for the reply.  After futzing with this for a while, I finally noticed an error message in the VM that I've never seen.  Errors dealing with the network.

While I don't understand why the Delphi IDE would never have a problem, FB would have a problem.  A couple times it made it through one project, but would stop on another.

What ended up happening is that the NIC built into the new MSI board.... well...  stinks.

I disabled and added an Intel NIC.   Things are back to being rock solid.

FB and my build machine is back working like a champ

4

Hi Lance,

That’s really interesting. I wouldn’t have guessed that a hardware problem could manifest itself in such a strange way.

Glad it’s all working fine now.

Regards,

Angus