![]() ![]() |
Hi Everyone,
Recently I tried to open Wonderware Inouch 7.1 application that was developed under Windows 2000 on a new workstation with with Windows XP and Intouch 7.1 loaded and Intouch could not recognize the application from Tools->Find Applications menu. Can anybody advice what might be the problem? Your help is appreciated, Thanks! :-)
wesley szymczyk
Recently I tried to open Wonderware Inouch 7.1 application that was developed under Windows 2000 on a new workstation with with Windows XP and Intouch 7.1 loaded and Intouch could not recognize the application from Tools->Find Applications menu. Can anybody advice what might be the problem? Your help is appreciated, Thanks! :-)
wesley szymczyk
![]() ![]() |
Hi Wesley,
Are there any service packs on XP, and for Intouch 7 used? Intouch 7.1 is a fairly old version, and is not listed in their matrix any more. Version 7.11 requires Patch 6 for WinXP SP1 and 2.
Regards,
Trevor Ousey
Are there any service packs on XP, and for Intouch 7 used? Intouch 7.1 is a fairly old version, and is not listed in their matrix any more. Version 7.11 requires Patch 6 for WinXP SP1 and 2.
Regards,
Trevor Ousey
![]() ![]() |
Please call your Wonderware distributor for this kind of stuff. Unless, of course, you are using an unlicensed version of InTouch, in which case
you should pay for it, and then call for help.
I have wondered for years why people ask specific tech support questions in a forum like this, rather than go bother the vendor. The vendor knows the product better than we do, has been paid to help you, and has the time and the desire to help you.
Can anybody explain this behavior to me?
Walt Boyes
Editor in Chief
CONTROL magazine
www.controlglobal.com
Blogging at Sound OFF! at controlglobal.com or direct at
http://waltboyes.livejournal.com
Putman Media
555 W. Pierce Rd #301
Itasca, IL 60143
+1-630-467-1301 x 368
wboyes@putman.net
you should pay for it, and then call for help.
I have wondered for years why people ask specific tech support questions in a forum like this, rather than go bother the vendor. The vendor knows the product better than we do, has been paid to help you, and has the time and the desire to help you.
Can anybody explain this behavior to me?
Walt Boyes
Editor in Chief
CONTROL magazine
www.controlglobal.com
Blogging at Sound OFF! at controlglobal.com or direct at
http://waltboyes.livejournal.com
Putman Media
555 W. Pierce Rd #301
Itasca, IL 60143
+1-630-467-1301 x 368
wboyes@putman.net
![]() ![]() |
Yes Walt, I can explain this. In general it's often much faster and far less painful to get just what you need from someone who knows. Enduring the bad muzak or propaganda on hold and having to jump through hoops and provide details that can't possibly be relevant and perhaps even dump and reload the program a few times to satisfy the lower echelons and get to someone who might actually have a clue about your problems is something most people find unpleasant in the middle of their development. After a few of these episodes, most will seek any time and cost efficient alternative. On that particular problem, it sounds like the vendor may be the only hope, but it doesn't hurt to ask around first. And it's real discouraging when you simply hit a wall and they tell you they'll get back to you. I submit that it is the current state of application support that causes that behavior. Especially in my case.
Regards
cww
Regards
cww
![]() ![]() |
Mr. Boyes,
I just read your reply, I thought that this forum is used to exchange technical information/experience by professionals or enthusiasts and not for personal comments/views (for whatever reason). I think that you found the explanation to my question in one of the responses. Anyway, Thank you for your input.
respectfully,
wesley szymczyk.
P.S. By the way, the problem is solved.
I just read your reply, I thought that this forum is used to exchange technical information/experience by professionals or enthusiasts and not for personal comments/views (for whatever reason). I think that you found the explanation to my question in one of the responses. Anyway, Thank you for your input.
respectfully,
wesley szymczyk.
P.S. By the way, the problem is solved.
![]() ![]() |
In reply to Wesley Szymczyk - Your question seemed quite reasonable to me. I have not previously replied on this topic because I had nothing useful to add. If I used Wonderware however, I would certainly have been quite
interested in knowing about this problem and what people did to solve it. This is why I read the Automation List. What by the way was your solution to this problem?
interested in knowing about this problem and what people did to solve it. This is why I read the Automation List. What by the way was your solution to this problem?
![]() ![]() |
Unfortunately many of the WonderWare affiliates know precious little about the products they sell and many engineers like myself have to rely on other users for help! Hence we ask forums.
Also this is not limited to just WonderWare but includes many other OEMs and their network of "support". You must have a really limited exposure to vendors if you naively think that they are experts in what they sell!!!!!!!
Also this is not limited to just WonderWare but includes many other OEMs and their network of "support". You must have a really limited exposure to vendors if you naively think that they are experts in what they sell!!!!!!!
![]() ![]() |
I have seen WW fail to update it's combo box display on the find
applications dialog on XP before. Try moving up one directory and see if
you can search farther down in the tree.
--
Michael R. Batchelor
www.ind-info.com
Guerrilla Maintenance Training (tm)
for Allen Bradley PLC5, SLC500, and CLX
training@ind-info.com
Industrial Informatics, Inc.
1013 Bankton Cir., Suite C
Hanahan, SC 29406
843-329-0342 x111 Voice
843-412-2692 Cell
843-329-0343 FAX
applications dialog on XP before. Try moving up one directory and see if
you can search farther down in the tree.
--
Michael R. Batchelor
www.ind-info.com
Guerrilla Maintenance Training (tm)
for Allen Bradley PLC5, SLC500, and CLX
training@ind-info.com
Industrial Informatics, Inc.
1013 Bankton Cir., Suite C
Hanahan, SC 29406
843-329-0342 x111 Voice
843-412-2692 Cell
843-329-0343 FAX
![]() ![]() |
Hi ya,
The problem you have is that if an Intouch 7.1 application has been developed on Win 2000 then it can only run on Win 2000. Also if you develop on XP it will only run on XP.
I found that the only way to run a Intouch application on XP after it was developed on Win2000 is to do the following in Windowmaker(you will need a development license):
1.create a new application on an XP machine
2. import all the windows and scripts from the old intouch application.
3.Then export the tag database from the old application and import this into your new app.
4.Go through each window and script and convert the tags to local.
There is a Windows 2000 compatiblity tool in XP which is supposed to allow you to run programs designed for a Win 2000 machine but I was never able to run old Intouch Applications using this.
The problem you have is that if an Intouch 7.1 application has been developed on Win 2000 then it can only run on Win 2000. Also if you develop on XP it will only run on XP.
I found that the only way to run a Intouch application on XP after it was developed on Win2000 is to do the following in Windowmaker(you will need a development license):
1.create a new application on an XP machine
2. import all the windows and scripts from the old intouch application.
3.Then export the tag database from the old application and import this into your new app.
4.Go through each window and script and convert the tags to local.
There is a Windows 2000 compatiblity tool in XP which is supposed to allow you to run programs designed for a Win 2000 machine but I was never able to run old Intouch Applications using this.
![]() ![]() |
Hi Joe,
I'm currently working on an Intouch 7.0 system running on Windows NT4. The guys at the installation want to update their PC's and the OS to XP. The question is will this proceedure work in my case too??? Thanks in advance.
Mike
I'm currently working on an Intouch 7.0 system running on Windows NT4. The guys at the installation want to update their PC's and the OS to XP. The question is will this proceedure work in my case too??? Thanks in advance.
Mike
![]() ![]() |
I did the step from NT4 SP6 with Intouch 7.1 to XP SP2 with Intouch 9.0.
I installed 9.0 on the XP machines, run the OS Configuration Utility to open the necessary Ports in the XP firewall, copied the old 7.1 app to the new machines, started WindowMaker which converted the app to 9.0.
Everything runs fine.
The only issue i have: Sometimes InTouch crashed when running both Maker and View. Now I shutdown the View app before starting Maker and vice versa. No crash since this time.
I installed 9.0 on the XP machines, run the OS Configuration Utility to open the necessary Ports in the XP firewall, copied the old 7.1 app to the new machines, started WindowMaker which converted the app to 9.0.
Everything runs fine.
The only issue i have: Sometimes InTouch crashed when running both Maker and View. Now I shutdown the View app before starting Maker and vice versa. No crash since this time.
![]() ![]() |
Hi There,
Try to install patch 6 from intouch, which you can download for free.
Good luck.
Try to install patch 6 from intouch, which you can download for free.
Good luck.
![]() ![]() |
Got the same problem.
thus i check out thw wonderware webpage..
Below are OS for intouch 7.0 only..
refer to below page for detail..
http://www.wonderwaremidwest.com/new/Tech/faqs/intouchfaq.htm#f
InTouch 7.1
Windows 95 SP1
Windows 98SE
Windows NT4 SP5
Windows NT4 SP6a (InTouch 7.1 requires Patch03 for this configuration)
Windows 2000 Professional (InTouch 7.1 requires Patch03 for this configuration)
Windows 2000 Professional SP1 (InTouch 7.1 requires Patch05 for this configuration)
Windows 2000 Professional SP2 (InTouch 7.1 requires Patch06 for this configuration)
Windows 2000 Professional SP3 (InTouch 7.1 requires Patch08a for this configuration)
Windows 2000 Server (InTouch 7.1 requires Patch03 for this configuration)
Windows 2000 Server SP1 (InTouch 7.1 requires Patch05 for this configuration)
Windows 2000 Server SP2 (InTouch 7.1 requires Patch06 for this configuration)
Windows 2000 Server SP3 (InTouch 7.1 requires Patch08a for this configuration)
Windows 2000 Advanced Server (InTouch 7.1 requires Patch03 for this configuration)
Windows 2000 Advanced Server SP1 (InTouch 7.1 requires Patch05 for this configuration)
Windows 2000 Advanced Server SP2 (InTouch 7.1 requires Patch06 for this configuration)
Windows 2000 Advanced Server SP3 (InTouch 7.1 requires Patch08a for this configuration)
thus i check out thw wonderware webpage..
Below are OS for intouch 7.0 only..
refer to below page for detail..
http://www.wonderwaremidwest.com/new/Tech/faqs/intouchfaq.htm#f
InTouch 7.1
Windows 95 SP1
Windows 98SE
Windows NT4 SP5
Windows NT4 SP6a (InTouch 7.1 requires Patch03 for this configuration)
Windows 2000 Professional (InTouch 7.1 requires Patch03 for this configuration)
Windows 2000 Professional SP1 (InTouch 7.1 requires Patch05 for this configuration)
Windows 2000 Professional SP2 (InTouch 7.1 requires Patch06 for this configuration)
Windows 2000 Professional SP3 (InTouch 7.1 requires Patch08a for this configuration)
Windows 2000 Server (InTouch 7.1 requires Patch03 for this configuration)
Windows 2000 Server SP1 (InTouch 7.1 requires Patch05 for this configuration)
Windows 2000 Server SP2 (InTouch 7.1 requires Patch06 for this configuration)
Windows 2000 Server SP3 (InTouch 7.1 requires Patch08a for this configuration)
Windows 2000 Advanced Server (InTouch 7.1 requires Patch03 for this configuration)
Windows 2000 Advanced Server SP1 (InTouch 7.1 requires Patch05 for this configuration)
Windows 2000 Advanced Server SP2 (InTouch 7.1 requires Patch06 for this configuration)
Windows 2000 Advanced Server SP3 (InTouch 7.1 requires Patch08a for this configuration)
![]() ![]() |
Hi,
Currently I'm experience a similar issue. I've migrated a 7.0 version to a 9.5 WW running on XP SP3, but when I go with the Viewer I can not establish communication between WW and ABTCP, neither using DDE nor suitlink. I can see that ABTCP, get connected with the different Topics it has configured but The runtime is not able to show the values.
Currently I'm experience a similar issue. I've migrated a 7.0 version to a 9.5 WW running on XP SP3, but when I go with the Viewer I can not establish communication between WW and ABTCP, neither using DDE nor suitlink. I can see that ABTCP, get connected with the different Topics it has configured but The runtime is not able to show the values.
Your use of this site is subject to the terms and conditions set forth under Legal Notices and the Privacy Policy. Please read those terms and conditions carefully. Subject to the rights expressly reserved to others under Legal Notices, the content of this site and the compilation thereof is © 1999-2013 Nerds in Control, LLC. All rights reserved.
Users of this site are benefiting from open source technologies, including PHP, MySQL and Apache. Be happy.
Fortune
Drink Canada Dry! You might not succeed, but it *__is* fun trying.

Control.com is the largest Automation community on the web. Learn how to advertise here now...
Servo, stepping motor control, analog & web HMI in one system!








