I have standalone Foxpro 2.6a for DOS executable running on 2 sites connected by Kilostream link. All PC's (W2000) are mapped to server where executable resides. On the site where the application resides, accessing and logging on to the application is virtually instantaneous, however, on the remote site, the load time is in excess of 1 minute 30 seconds.
When users accessed the application from a remote site using W95, 98 the log in time would be approx 30 seconds and this was attributed to the slow speed of the kilostream link. However, a further 1 minute delay simply because the PC's are now W2000 seems excessive.
I have tried to optimise the remote site environment by having local configuration files, emuulating W95, 98 mode through Icon properties and maximising Extended and Expanded memory, but the best 'fix' I can get is still taking approx 1 minute to load.
Does anyone have a winning solution for solving the delay or suggestions on what to try as may be causing the excessive delay.
PS: Once loaded the response time on the remote site for doing transactions is slower but only for a delay of 1 second or so. It is simply the load up which causes users heartache.
Thanks!
When users accessed the application from a remote site using W95, 98 the log in time would be approx 30 seconds and this was attributed to the slow speed of the kilostream link. However, a further 1 minute delay simply because the PC's are now W2000 seems excessive.
I have tried to optimise the remote site environment by having local configuration files, emuulating W95, 98 mode through Icon properties and maximising Extended and Expanded memory, but the best 'fix' I can get is still taking approx 1 minute to load.
Does anyone have a winning solution for solving the delay or suggestions on what to try as may be causing the excessive delay.
PS: Once loaded the response time on the remote site for doing transactions is slower but only for a delay of 1 second or so. It is simply the load up which causes users heartache.
Thanks!