Here is my experience with Installing the 5.5 Dev studio on Windows 7 Professional (64bit).
I installed the dev studio in XPSP3 Compatibility mode, (with default options), and the install went fine. Then I went ahead and tried to run the studio in the same compatibility mode after the install and got a missing DLL error. So, at that point I assumed that it wasn't going to run in Win7, and went ahead and installed XP Mode to run witango in a virtual environment. That all went fine, except that I couldn't get the file association of TAF and TCF files to link up with the Virtual machine. I could run the Dev Studio in seamless mode, but could not double click on a taf or tcf and have it start up automatically. When you google this sort of behaviour all the "experts" say. Yeah, it should work. XP Mode automatically "publishes" applications from the guest to the host, allowing those extensions to be recognized and automatically fire up a virtual application. However, there doesn't seem to be any way to do it manually if the "magic / automatic" method is failing. So, since I really need to be able to click on a taf in win7 and edit the file, I went back to the drawing board, and re-read Roberts post here. So, I re-installed Dev Studio on Win7 directly, but this time, instead of going with default options, I manually changed the install path to Program Files (x86) instead of the default "Program Files" directory. Now I'm able to start up the Witango editor without that missing DLL error. So, I guess that means that the ProgramFiles vs. ProgramFiles x86 directories are more important that superficial organization. I'd love to keep the dev studio isolated from the rest of my system by using XP Mode, so if anybody has any advise on how to manually setup that file association from the host to the guest, please advise. /John On Mon, Oct 12, 2009 at 9:12 AM, Robert Shubert <[email protected]>wrote: > For those of you that are wondering about Windows 7 support of the aging > Witango 5.5 code, I did some tests over the weekend and found that it seemed > to work OK. > > > > My test system is an older Pentium 4 based computer. I am running Windows 7 > Professional RTM in 32-bit mode. > > > > I downloaded the Witango 5.5 for Windows installers directly from > www.witango.com (5.5.8 and 5.5.20) > > > > In both cases, the only real issue I had was that I needed to execute the > installer in Windows XP SP3 compatibility mode. > > > > The studio seems to run fine. I have not spent a lot of time programming with > it, but I did already notice a few graphical and interaction problems as you > might expect since the studio is using very old Windows calls. I was able to > load an ODBC data source. I did not attempt to load COM objects. > > > > The server also installed without a problem, including adding the service to > the system. Windows 7 uses IIS 7.5 which is very different from IIS 6 in > terms of configuration. The Witango 5.5 client ISAPI plug-in is compatible > with IIS 7.5s ISAPI module and worked without issue. I did have to setup the > module mappings manually. > > > > Modifying the configuration files can not be done as a user, so I suggest > installing the server as Administrator. The studio should be installed as the > user that will use it. > > > > So far, I’ve only had a few minutes working in the studio and using the > server – so may not have run into a show-stopper yet. I don’t plan to use > this test system in day-to-day, but I will report my findings as I get to use > it more. > > > > If anyone has any questions, please feel free to ask. > > > > Robert > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > -- /John ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
