Hello everyone, I am in the process of setting up NAD using the step-by-step guide provided by InTouch on how to set up NAD for Modern InTouch Applications. However, I am facing an issue where it takes over 8 hours for the client to open in WindowViewer, even though none of the IO has been configured yet. It seems to be running slow, despite having a local copy on the computer. Can anyone suggest any solutions to improve the performance of WindowViewer? I also attempted to follow the tech note from InTouch (TN IT104) on improving InTouch NAD performance, but I am hesitant as I have multiple win.ini files and don't want to disrupt the current setup. Thank you for any help or suggestions!
What type of network are you using? In my experience, 8 hours is an unusually long time for network processes. It's a good idea to check the System Management Console log for any error messages. Ensure a strong connection with an ethernet cable tester and use switches instead of hubs. Also, remember not to enable NAD on the development server itself; it should only be enabled on clients.
While using SCADA, the SMC may display a "disconnected" error message, even though it eventually connects successfully. The NAD feature is enabled only on the client but doesn't open properly. It's unlikely to be a network issue since another NAD computer is functioning without any problems. The configuration of the network drive may be the issue, as the application manager only shows "X:" instead of the complete path name.
If you're experiencing network issues, it may be specific to a particular client. Check your port lights to ensure they are green, not amber, and test the network cable connecting the client to the switch. Avoid using hubs in the network route from client to server. Update the application path in the Application Manager to use the full path for each user's network drive, as it is a best practice. While this may not be the cause of the current issue, it can help improve network performance.
It sounds like a tough situation you are in! Have you considered checking the specifications of your computer? Sometimes when systems tend to run slow, it could be due to insufficient hardware resources. The performance of WindowViewer can be quite dependent on the operating system, processor speed, and RAM available. Make sure they all meet the requirements of the software. Additionally, if you have multiple win.ini files, it's crucial to identify the one that your InTouch is using. If you're not sure, a safe bet would be to apply the tech note improvements to each win.ini file, as the unnecessary modifications should be ignored. Don't forget to back up the existing files first in case you need to revert the changes. Good luck!
Hi there, it sounds like a frustrating situation you're dealing with. Are you sure that the hardware requirements have been met for the setup? WindowViewer can be quite a heavy application and it needs a fair amount of processing power and available memory. Keep your resources in mind, if it's a resource-intensive app running on a resource-constrained machine, it's bound to take a while. About the tech note, it might help to backup all the win.ini files before you attempt to modify them. This way, you can always revert to the original if something isn't working as expected. If all else fails, it might be valuable to reach out to InTouch's support for more direct assistance.
Hi there, I've encountered similar situations in the past. I suggest checking the graphics settings first, as overloading on graphics can slow down WindowViewer considerably. Reducing bitmap usage might help. Also, ensure unnecessary apps/services aren't running in the background. Regarding the multiple win.ini files, I advised creating a backup of the original files before making any modifications. That way, you can revert if something goes wrong. If possible, you might want to consider asking for professional IT assistance when tinkering with win.ini files. Lastly, sometimes a simple system reboot resolves such issues. If you haven't tried it yet, give it a shot. Best of luck!
Hey there! It sounds really frustrating to deal with such slow performance, especially in the initial setup phase. Have you checked if there are any background processes running that might be hogging resources? Sometimes antivirus software or unnecessary startup programs can significantly slow things down. Also, it might be worth temporarily disabling those win.ini files—just make sure to back them up first! Another tip could be to look into network settings if you're accessing resources remotely; optimizing those can sometimes make a big difference. Good luck!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: 1. Why is my WindowViewer client taking over 8 hours to open even without any configured IO? - The slow performance of WindowViewer could be due to various factors such as system resources, network issues, or configuration settings.
Answer: - You can try following the tech note from InTouch (TN IT104) on improving InTouch NAD performance or explore other solutions suggested by the community or technical support.
Answer: - It is recommended to carefully review the tech note instructions and consider the potential impact on your current setup before making any changes to improve performance. Backing up your configuration is also advisable.
Answer: - In case of multiple win.ini files, it is essential to identify the correct file to make the necessary modifications for improving WindowViewer performance. Consulting with technical support or experienced users can provide guidance in handling such situations.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.