|
Post by al on Nov 26, 2018 16:43:34 GMT 1
I've just started evaluating VDOS with a networked Foxprox accounts application prior to moving over fully to Win10.
When the application is running and has files open, but is minimised to do something else, it sometimes won't open back up from the taskbar. The little window image comes up if you hover on the icon, and hovering over that produces the full window but it is not clickable into and disappears if you come off the image. There seems to be no way to kick it back into life other than using task manager to close it.
I haven't been able to replicate the problem, it seems to take some time sitting in the background before the fault develops and there doesn't seem to be a common process running at the same time that causes it. At first I thought it was Windows sleep settings related, loosing the network connection to the server but I've turned those up to max so it gets no rest. I have seen it happen now on three different machines. The log files just show idles until the file ends.
Many years ago on Novell IPX we never liked leaving applications minimised with files open as things tended to go astray, but with TCP/IP that has never been a problem.
Are there any particular config.fp and/or config.txt settings that are known to be reliable for foxprox?
|
|
|
Post by Jos on Nov 26, 2018 17:35:26 GMT 1
|
|
|
Post by al on Nov 27, 2018 9:16:35 GMT 1
Jos,
Thanks for the quick reply, it is my intention to get a network licence once the PCs are sorted so if that's all it is then fine.
|
|