If you suspect something on the network then physically move the computer to another area of the network so that it would use a different path through different switches. A bad port on a switch could explain this. So could a failing network card on the workstation.
Some other things to try:
- plug in a USB wifi stick and pull the ethernet cord, see if that makes a difference; that would rule out any networking issues or network card issues
- create a new Windows account on that machine and let the user try from that account; that would rule out anything in that profile
- check for free disk space on the workstation; low disk space would severely slow down FM
I shall let you know how it goes…
The user accounts for your windows are they roaming profiles? what version of windows are you on?
check all file paths with get functions. sometimes the assumed local paths might be not that local at all.
I am not in the office so cannot check on a client machine - but the issue is also occurring when using remote desktop on a machine that is Running Windows Server 2008.
Yes they are using roaming profiles - why do you ask?
In this case moving from one layout to another using a script does not make use of any get functions and few are used out side of scripts - can you explain more why this might be an issue?
- thanks for your input.
- Richard and
Roaming profiles can be very difficult to optimize if once slowness reported. A new user account helps or could help for a while as we experienced with Windows 7.
Check if you are running a supported flavor of Windows.
The get functions just tell you where the files are managed from your Pro installation.
get (temporaryPath) might indicate that it is on a networked volume - get (desktopPath ) , get ( PreferencesPath )
all can be helpful to see what kind of installation you are dealing with.