Hi, I've searched the forum for this problem but nothing helped.
I'm using v.4.8 on the runtime I get
F Could not open file /usr/local/pwrp/t1/bld/common/load/ld_boot_lacrim-virtual-machine_0517.dat
F Could not open file /usr/local/pwrp/t1/bld/common/load/ld_node_lacrim-virtual-machine_0517.dat
F Could find my own node in /usr/local/pwrp/t1/bld/common/load/ld_node_lacrim-virtual-machine_0517.dat

I've shorted names to <16 but it didn't help. Is it because ld_boot_lacrim-virtual-machine_0517.dat is too long? If yes, then please tell me how to change it.
Thanks

Hi Grzegorz,

The 'long nodename' bug should be fixed in 4.8.

Do you have the correct bus identity ? The busid is configured in the BusConfig object in the directory volume and has to correspond to the environment variable $PWR_BUS_ID which seems to be 517. The default value of PWR_ US_ID is fetched from /etc/proview.cnf but can be changed with a 'export PWR_BUS_ID=...' before Proview runtime is started.

/Claes

In the config file of proview which You told me to check is correct 517. I have something strange in the runtime window, in the filed version I have either nothing or something in hmm ASCII code, like %%strange letters etc. Do You have any idea what could be wrong or have some other things which I should check?

I'm not following you now. Do you still have the errors with ld_node and ld_boot files or have you past this problem ?

/Claes

No. The problem is still the same, 517 is in the /etc/proview.conf
I'm describing some things that might be important

Ok, the strange characters doesn't ring any bell. If we continue with the error messages, you get this message if the files doesn't exist, or you don't have read permissions. Have you checked the busid in the BusConfig object for this node in the directory volume ?

/Claes