- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hard to say. MS does not support any VS version earlier than 2005 on Vista. I don't know if CVF is in the list of images it knows about, but if you had VS98 installed you'd get warnings. I know I recently tried VS2003 on Vista and had some problems with Fortran, though I was able to work around them. Maybe I'll try CVF as well and see what happens.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is probably a good time to quote Kyle every time Kenny gets killed "You B%$#@".
Just kidding.
We have some transition problems here. IVF doesn't work well on VS2005 much less VS2007 or whatever the number will be (maybe VS2009??). Vista won't support (well) VS2003, which has been virtualy rock solid for me. To date I have been using Windows XP (32-bit) so VS2003 and IVF have been great. I do want to migrate to Windows Vista and/or to Windows XP 64-bit.
I could use the command line compiler with a MAKE utility under the 64-bit O/S but I am not totaly sure IVF command line works OK on 64-bit system. So I may have to resort to cross compiling on a 32-bit O/S for a 64-bit Windows target system. But this means I lost the integration environment where the editor, compiler system, debuggerand system under test machine are all the same machine.
What would really be helpful is not to know you had problems with VS2003 under Vista.
Rather it would be nice to know what your work-arounds were to the problems.
True, Vista ain't your problem, VS2003 on Vista ain't your problem.
Your problem is your customers are stymied. They won't stay put for long so Intel needs to do something about this and soon. In 30 days Vista will launch, and us overworked software developers will get barraged with complaints as to why our code won't work on Vista. Can you see what your problem is now?
Jim Dempsey
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The bad news first - CVF simply falls over on Vista. It installs without a complaint, but as soon as you bring up Developer Studio, it dies. Windows helpfully offers to send the detsails to Microsoft but does not note it as something with a known compatibility problem. I am not at all surprised by this.
The issue I had with VS2003 was, other than telling Vista that, yes, I really wanted to run it, thank you very much, the Fortran debug expression evaluator did not install correctly. To fix that, I opened Visual Studio using "Run as Administrator" and when I brought up the debugger, it took care of it. Minor, really. That's for Fortran - I had some real problems with Intel C++ that I know are being looked into. I'll admit that I didn't try a lot of things, but everything I thought to try worked fine.
As for VS2005, the only real issues I know of will be fixed in VS2005 SP1, which should be out at around the same time Vista hits the retail shelves. In a few minutes, I'm going to try VS2005 on my Vista system (which I just wiped and reinstalled) and see how it goes.
I see no reason why IVF shouldn't work from the command line in Vista64, though that's an environment I'm not readily equipped to test (at least not personally.) And VS2005 should work there too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, this is fun... Even VS2005 brings up the compatibiliy warning! According to this page, full support for VS2005 on Vista will come in "the first quarter of 2007".
More in a bit...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, VS2005 and IVF work, but you have to always start VS2005 as an administrator (hint from the MS doc I mentioned above.) In addition to the debug thing, for some reason the compiler can't get a license unless you do this. Odd, as it works fine in comnmand line mode.
You can set the shortcut for VS to always run as administrator.
What schools that don't give students privs are going to do, I don't know. Perhaps there is some lower privilege level that will work.
Oh, and it turns out that "Run as administrator" helps with CVF too... It started ok when I did that and I was able to build a simple application.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
>> the compiler can't get a license unless you
Do you mean IVF cannot locate its own license, the *.lic file?
If so, then this should be a relatively easy thing for Intel to fix. e.g. set an environment variable to specify the path to a non-administrator accessible folder containing the .lic file.
I don't know how your .lic file lookup works but have you tried copying the .lic file to the current directory of the project? (I don't have Vista so I cannot try this myself).
If this is the licenses to VS then MS should have a fix.
The gate keeper must have something that can be used to appease them.
Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The license file is the one for the compiler. It may be more than "can't find the file" - there is already a mechanism in place for it to do so. It seems to be more a permissions thing, and no, copying the .lic won't help. I'm sure we'll figure it out, but as MS is going to recommend running VS with privileges anyway, perhaps that will sort out the license problem as well (as I noted, it works when VS is run as administrator.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Q: Is there any difference between Visual Studio 2005 RTM and Visual Studio 2005 SP1 on Vista?
A: No. The only change is a warning that Visual Studio 2005 should be run with elevated privileges on Windows Vista.
Vista does have a large database of applications for which it gives detailed warnings and links to explanatory web pages. CVF's dfdev.exe is not among them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is Virtual Vista available on Vista Server? If so then a user on a server can have administrative privledges only within the Virtual Vista system but not on the server itslelf. Not having Vista Server, i am unable to test that.
Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have installed CVF on Vista and have been experiencing something similar to whatSteve Lionel mentioned in his first post. As soon as I launch Developer Studio it dies. The message I get is Microsoft Developer Studio has stopped working with a button to end the program.
I switched the short cut properties to run as administrator mentioned in a later post and I still get this error. Any ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The first thing I did with my laptop with Vista was to install XP so I could dual boot. I tried to install VS/VC++ 6 on Vista but it was a no go. I assumed that CVF wouldn't install on Vista so I installed iton XP. I later returned to getting CVF to install on Vista. No problem, sure you get compatibility warnings and of course you 'run as administer' even if you have administrator privileges. I then installed VC++ 6 and it too worked. As far as I can tell CVF 6.6C runs fine on Vista in VS 6. The only annoyance is that CVF doesn't like being started from Start but VC++ does and then you can open whatever workspace you want. The sequence CVF followed by VC++ was important in getting the latter to install. YMMV.
Gerry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
http://social.msdn.microsoft.com/forums/en-US/windowsgeneraldevelopmentissues/thread/cd740951-dd2c-46eb-856f-6e653a2e3d07/
Then I installed CVF6.6a followed by CVF6.6b & CVF6.6c pach updates.
As Gerry mentioned above CVF does not start by executing DFDEV.exe or clicking the MSDev link corresponding to CVF6.6. However everything works fine if you start the VS C++ 6.0 Dev Studio executable first, then open your visual fortran project.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
http://social.msdn.microsoft.com/forums/en-US/windowsgeneraldevelopmentissues/thread/cd740951-dd2c-46eb-856f-6e653a2e3d07/
Then I installed CVF6.6a followed by CVF6.6b & CVF6.6c pach updates.
As Gerry mentioned above CVF does not start by executing DFDEV.exe or clicking the MSDev link corresponding to CVF6.6. However everything works fine if you start the VS C++ 6.0 Dev Studio executable first, then open your visual fortran project.
Hi cmood,
I encountered very similar problems as described when I'm using windows 7. I tried your mtd in windows 7 and I manage to open a workspace thru vs c++ 6.0 dev studio. However, during compilation, it says error there df.exe is not able to spawn. In command prompt, I also can't compile using f90. It says dfort.lib error. It used to work when I only had CVF installed.
Any ideas?
Thanks alot!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The bad news first - CVF simply falls over on Vista. It installs without a complaint, but as soon as you bring up Developer Studio, it dies. Windows helpfully offers to send the detsails to Microsoft but does not note it as something with a known compatibility problem. I am not at all surprised by this.
Plz can you help me out...
i m much familier with CVF only.. this all IVF 11.1 and VS2008 seems difficult for me to work wih...
CVF 6.6 installs properly.. even opens up very properly.. but when it comes to compile and built .. dvelopement studio dies.. without any replies from MS about compatibilty issuees...
Can u again guide me about virtualpc, what this is all about..???
waiting eagerly for ur kind reply....

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page