2006-01-12 10:59 PM - last edited on 2023-05-25 06:19 PM by Rubia Torres
2006-02-08 09:10 PM
2006-02-08 10:46 PM
2006-02-09 12:17 AM
Aussie wrote:i have a gut feeling that it happens when a tiger-based file path type gets written into a file . . . which gives archiCAD the shits when it tries to resolve it - regardless of the system it's running in.
This has been happening for some time now. I dont have any solutions though
2006-02-09 04:58 AM
~/archiben wrote:Yes I work remote but I do get the same message when working over main office LAN - even over a gigabit networkAussie wrote:
another hunch is that the type of file path that gets screwed up is one whereby the local network has been accessed remotely - which has happened in our case and i know could be possible in john's case (you work remote, right?) . . . what about anybody else?
~/archiben
2006-02-09 05:07 AM
Aussie wrote:my hunch is that a remote file path gets written into the file and somehow sticks around - even after saves with the local area net . . .
Yes I work remote but I do get the same message when working over main office LAN - even over a gigabit network
2006-02-09 08:25 AM
2006-03-10 03:17 AM
2006-04-20 06:25 AM
2006-04-20 10:27 AM