John,
I believe that your experience on 64-bit is common as the paths that the studio uses are sometimes hard coded and some moving of DLLs is necessary if they are not already where WT thinks they should be. If you were to install the server on the 64-bit OS, you would likely have to do the same tricks as always. I don't have 7 on a 64-bit platform yet to test this out. As for working in XPmode, again, I don't have access to that so I can't test, but does it help if you manually assign the file extension inside the VM using the default documents control panel? In XPmode (non-seamless) you would right click on a TAF and select Open With > Choose Program and then re/select Witango Studio along with the Always checkbox. This is just a guess, but it might build the connection so that 7 can 'see' it. You may have to restart the XPmode after this change, if the "publishing" only happens at boot. Robert _____ From: John McGowan [mailto:[email protected]] Sent: Monday, November 23, 2009 9:50 AM To: [email protected] Subject: Re: Witango-Talk: Windows 7 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 ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
