strange ini key in build app: AssemblyDepHWConfigFile="assemblyHWConfig.bin"

[Neil.Pate]

Hi experts,

Got a strange one here.

I have a project that is mainly PC code, but also include some FPGA code. The build of the PC executable goes without problems, but when I try and run it

When it comes to running the executable  the following dialogue is displayed as soon as the app is run:

It gets stranger... the app itself is still present in the Taskbar and in the Windows process list, and if the executable is run again I do not get the same error and it runs fine. If I close both apps, next time I run it I get the same error.

Oddly, I have found that if I delete the FPGA target from the project the build goes ok and the executable seems to run ok. The only difference as far as I can tell is that the executable that was built with the FPGA Target in the program also has the key AssemblyDepHWConfigFile="assemblyHWConfig.bin" in the apps ini file. If I delete this key the app does not throw an error and everything seems to work ok. The MD5 sums of the two build apps are totalyl different, but I would expect this as LV does some things behind the scenes which makes it quite tricky to get the same MD5 sum from the same project. Both executables are identical file size.

This file "assemblyHWConfig.bin" is not located anywhere on the PC!

The same error occurs on three different PCs (XP, Vista and Win7), all are running LabVIEW 2010f4.

So my question really is:

1) does anybody know what AssemblyDepHWConfigFile="assemblyHWConfig.bin" is doing in the ini file

2) is it safe to delete this line from the ini as it seems to be causing me grief

Thanks

n

[Stephen_C]

Hi nrp,

This is not an issue that I have encountered previously. Can you provide some more details about this issue?

You mentioned that the project contains some FPGA code, could you please let me know which hardware target is this intended for?

I am trying to gather as much information about the problem as I can, then I shall discuss this with my colleagues to see if anybody has any ideas or suggestions for you.

Many thanks,

[Neil.Pate]

Hi Stephen,

The target is a PCI-7813R with a cDAQ chassis attached (populated with an analogue input and analogue output module).

I have figured out the line in the ini files gets placed there if the Include My Computer hardware configuration option is selected in the executable build config.

If I unselect this option the executable runs fine.

n 

[Stephen_C]

Hi nrp,

Now that you are aware of which setting insets this ini key does it still represent a problem to you? Is including your hardware configuration required for your application?

The reason that I am asking is that I was not able to find a definitive answer to this at my end. If it is still troublesome for you I will endeavour to contact some technical support staff in another branch to see if they can help with this matter.

Kind regards,

[Neil.Pate]

Stephen,

I need to test the executable on the target platform, and this will only be next week.

At this point in time it looks like the build problem is always related to the key in the ini (even for trivial apps I create) so something is up...

It would be great to get to the bottom of this, just for curiosity sake, but it doesnt look like its going to be a showstopper for me, which is what is important at the moment.

thanks

n

[Neil.Pate]

Stephen,

I need to test the executable on the target platform, and this will only be next week.

At this point in time it looks like the build problem is always related to the key in the ini (even for trivial apps I create) so something is up...

It would be great to get to the bottom of this, just for curiosity sake, but it doesnt look like its going to be a showstopper for me, which is what is important at the moment.

thanks

n