CVF and C++ don't work on my new VISTA machine!

[longthong]

VISTA Home Premium Version 6.0 build 6001 SP1
CVF Professional Edition 6.6C
VC++ 5.0 (I am an old retired engineer on a fixed income)

I was excited when both programs installed cleanly on my new DELL desktop. Then I ran them. They both bombed out in Developer Studio. Ferinstance if I make a new console project (hello world) in CVF I get an error message "Microsoft Studio has stopped working, DEBUG/CLOSE PROGRM". I get the same message if I try to run a sample program. The DEBUG/CLOSE options both simply close the window. I, being the only user, have administrator privileges. I turned UAC off and tried various ways of invocing the compiler. None worked. Since all I do on computers is progam this is a very disapointing turn of events. Is anyone out running CVF or VC++ on Vista? I could sure use some help. Thanx.
DT

[Steven_L_Intel1]

Right click on the Developer Studio shortcut and select Run as Administrator. You can change the Compatibility setting for the shortcut to always run as administrator. I played with this for a VERY short time a couple of years back and it seemed to work.

[Peter]

Quoting - longthong

VISTA Home Premium Version 6.0 build 6001 SP1
CVF Professional Edition 6.6C
VC++ 5.0 (I am an old retired engineer on a fixed income)

I was excited when both programs installed cleanly on my new DELL desktop. Then I ran them. They both bombed out in Developer Studio. Ferinstance if I make a new console project (hello world) in CVF I get an error message "Microsoft Studio has stopped working, DEBUG/CLOSE PROGRM". I get the same message if I try to run a sample program. The DEBUG/CLOSE options both simply close the window. I, being the only user, have administrator privileges. I turned UAC off and tried various ways of invocing the compiler. None worked. Since all I do on computers is progam this is a very disapointing turn of events. Is anyone out running CVF or VC++ on Vista? I could sure use some help. Thanx.
DT

Is it a 64 bit or 32 bit computer, because CVF does not work on a 64 bit computer.

[TimP]

Quoting - Peter

Is it a 64 bit or 32 bit computer, because CVF does not work on a 64 bit computer.

That is not entirely correct, although the original post makes one suppose it is 32-bit Vista; whether it is 64-bit hardware is not relevant, if a 32-bit WIndows is installed. No doubt, the advantage of Vista are greater in the 64-bit version, when using 64-bit ifort.
It's possible MSVC5 (which would support only 32-bit mode) may present problems on Vista. Normally, at least MSVC7.1 would be used on Vista. There are free 32-bit versions (VS Express), but of course those post-date CVF.

[Peter]

Quoting - tim18

That is not entirely correct, although the original post makes one suppose it is 32-bit Vista; whether it is 64-bit hardware is not relevant, if a 32-bit WIndows is installed. No doubt, the advantage of Vista are greater in the 64-bit version, when using 64-bit ifort.
It's possible MSVC5 (which would support only 32-bit mode) may present problems on Vista. Normally, at least MSVC7.1 would be used on Vista. There are free 32-bit versions (VS Express), but of course those post-date CVF.

hmmm....It was my experience that CVF doesn't run on 64 bit machine. So I had to buy latest IVF. Initially I had some problems installing and running program, thanks to Steve for helping out.
Yes it looks like a 32-bit Vista, however I want tosee what the starter of the post says!

[TimP]

Quoting - Peter

hmmm....It was my experience that CVF doesn't run on 64 bit machine. So I had to buy latest IVF. Initially I had some problems installing and running program, thanks to Steve for helping out.
Yes it looks like a 32-bit Vista, however I want tosee what the starter of the post says!

If you install CVF on a 64-bit OS, of course it still builds only 32-bit applications. The autorun stuff on the top level of the CD requires 16-bit execution support, not available on 64-bit OS, so you must browse down to the 32-bit installer, as well as dealing with the stricter permissions. As the original post implied no major difficulty running the installer, that tended to indicate a 32-bit OS. I didn't ever try to match up CVF with a Visual Studio MSVC on 64-bit, given that no VS for which CVF was designed would run well on 64-bit Windows. And then, I didn't push my luck beyond command line operation. So, if you wanted best functionality from CVF, you wouldn't move beyond 32-bit XP.
It remains to be seen whether Windows 7 will give those who want legacy 32-bit operation an incentive to be more adventurous.

[Peter]

Quoting - tim18

If you install CVF on a 64-bit OS, of course it still builds only 32-bit applications. The autorun stuff on the top level of the CD requires 16-bit execution support, not available on 64-bit OS, so you must browse down to the 32-bit installer, as well as dealing with the stricter permissions. As the original post implied no major difficulty running the installer, that tended to indicate a 32-bit OS. I didn't ever try to match up CVF with a Visual Studio MSVC on 64-bit, given that no VS for which CVF was designed would run well on 64-bit Windows. And then, I didn't push my luck beyond command line operation. So, if you wanted best functionality from CVF, you wouldn't move beyond 32-bit XP.
It remains to be seen whether Windows 7 will give those who want legacy 32-bit operation an incentive to be more adventurous.

Little bit digression from the original post. What is interesting is installing CVF on a 64 bit Os. Thats a good info, thanks Tim ! I anyways have IVF.

I don't know what do you mean by best functionality, however I used CVF on a Vista 32 bit without any problems. The extent that I've used is running a monstrous CFD code, which worked great ! I personally like Vista, whereas lot of people like XP better. Vista is just challenging, not unreliable.

[longthong]

Quoting - Peter

Little bit digression from the original post. What is interesting is installing CVF on a 64 bit Os. Thats a good info, thanks Tim ! I anyways have IVF.

I don't know what do you mean by best functionality, however I used CVF on a Vista 32 bit without any problems. The extent that I've used is running a monstrous CFD code, which worked great ! I personally like Vista, whereas lot of people like XP better. Vista is just challenging, not unreliable.

Peter: If you "used CVF on a Vista 32 bit machine without any problems" I would sure like to know how you did it. I am having massivs problems and no luck. I am seriously considering a dual boot with WIN98 except I don't know how to do it.

Steve: I tried running as administrator to no avail.

Everybody: My Vista is 32 bit running on a dell inspiron530.

DT

[Peter]

Quoting - longthong

Peter: If you "used CVF on a Vista 32 bit machine without any problems" I would sure like to know how you did it. I am having massivs problems and no luck. I am seriously considering a dual boot with WIN98 except I don't know how to do it.

Steve: I tried running as administrator to no avail.

Everybody: My Vista is 32 bit running on a dell inspiron530.

DT

DT,

The problems, I believe comes from integration of MSVS with CVF. When I first installed CVF on my laptop (32-bit Vista) it was just installedin one go.It looks like you've installed succesfully, but do you haveMicrosoft Windows SDK installed ? If you have that installed look at the folllowing.

I would like to know step by step how you are creating a project, compiling and debugging.

The best information can be found at Program FilesMicrosoft Visual StudioDF98CVF_GS.

It is likely that you'l have less problems if you installed MS Visual C++ prior to installing CVF.

** I do not recommend using two operating systems because the some new computers are not compatible with Win98. You dont have to take my word for this. It just happened to me! You can check with Dell technical support before you want to install Win98.

[Peter]

DT,

Another piece of info. I've just installed CVF on a 64 bit Vista succesfully (less than 10 mins ) and ran a nice CFD code. I dont have any problems upto this point.

Also I created a simple Hello world project without any problems !!

Did you use typical installation or custom installation ?

[TimP]

Quoting - Peter

** I do not recommend using two operating systems because the some new computers are not compatible with Win98. You dont have to take my word for this. It just happened to me! You can check with Dell technical support before you want to install Win98.

Getting well off the topic, Win98 has been off support for so long that it is unlikely to work on current hardware platforms. However, XPSP3 has been fully off support for only a short time, and has a reasonable chance of working with current hardware and with CVF.

[longthong]

Quoting - Peter

DT,

The problems, I believe comes from integration of MSVS with CVF. When I first installed CVF on my laptop (32-bit Vista) it was just installedin one go.It looks like you've installed succesfully, but do you haveMicrosoft Windows SDK installed ? If you have that installed look at the folllowing.

I would like to know step by step how you are creating a project, compiling and debugging.

The best information can be found at Program FilesMicrosoft Visual StudioDF98CVF_GS.

It is likely that you'l have less problems if you installed MS Visual C++ prior to installing CVF.

** I do not recommend using two operating systems because the some new computers are not compatible with Win98. You dont have to take my word for this. It just happened to me! You can check with Dell technical support before you want to install Win98.

Peter: Here is one way I can make it fail:
double click the cvf icon
file/new/project
fortran console application/HELLO/c:MyFortranHELLOA Hello world sample project
get error message "The project directory no longer exists. Please choose a different directory"
I go back and check the sharing to make sure it is shared I reshare it for everyone, repeat and getthe sameresults.

My VC and CVF systems are completely seperate and each have their own VS. They both act the same however. CVF's VS is 2000. VC's VS is 97. VC has MFC and, yes, CVF has win32 SDK.

That is bad news about win98 being incompatable with my new computer. Maybe I should just dunp VISTA and bay another

Your news about CVF_GS is good news . I never new this pdf existed. I think I will print it.

Thanx for everything.
DT

[Steven_L_Intel1]

CVF's VS is '98 (VC6).

[Peter]

Quoting - longthong

Peter: Here is one way I can make it fail:
double click the cvf icon
file/new/project
fortran console application/HELLO/c:MyFortranHELLOA Hello world sample project
get error message "The project directory no longer exists. Please choose a different directory"
I go back and check the sharing to make sure it is shared I reshare it for everyone, repeat and getthe sameresults.

My VC and CVF systems are completely seperate and each have their own VS. They both act the same however. CVF's VS is 2000. VC's VS is 97. VC has MFC and, yes, CVF has win32 SDK.

That is bad news about win98 being incompatable with my new computer. Maybe I should just dunp VISTA and bay another

Your news about CVF_GS is good news . I never new this pdf existed. I think I will print it.

Thanx for everything.
DT

Dt,

Why would one do that unless you are a "beginner". I am assuming you are not.
What happens is when you say
fortran console application/Hello, visual studio creates a folder (project) and then
c:MyfortranHelloA sample fortran programmeans there is already a directory named Hello and you are creating another directory A sample fortran program. So now there is a difference b/t existing folder and creating a new folder. You are actually trying to create a folder 'Hello' in a directory (or folder) 'Hello' which never existed.

Here is what you can do. First create a folder for all your projects of the same kind, say
C:MyfortranMy Projects
so now going back to
fortran console application/Hello creates a folder in a directory given by you in
C:MyfortranMy Projects

Simple enough??

Regarding Win98 i wont venture going back (i tried and realised it is waste of my time) to older OS or versions of software. I believe, like I said earlier, Vista is lil bit counter-intuitive, but not unreliable !! Once you get used to it you'l like it.

CVF_GS is a good manual, but I never had to refer itfor installing CVF on my computer. Because installing CVF is that easy! The manual , honestly takes time to read and understand for an average person (who has computer internals knowledge 5/10).

I hope you'l be able to run your hello world project succesfully.

Let me know if you did and have any specific questions??

[longthong]

Quoting - Peter

Dt,

Why would one do that unless you are a "beginner". I am assuming you are not.
What happens is when you say
fortran console application/Hello, visual studio creates a folder (project) and then
c:MyfortranHelloA sample fortran programmeans there is already a directory named Hello and you are creating another directory A sample fortran program. So now there is a difference b/t existing folder and creating a new folder. You are actually trying to create a folder 'Hello' in a directory (or folder) 'Hello' which never existed.

Here is what you can do. First create a folder for all your projects of the same kind, say
C:MyfortranMy Projects
so now going back to
fortran console application/Hello creates a folder in a directory given by you in
C:MyfortranMy Projects

Simple enough??

Regarding Win98 i wont venture going back (i tried and realised it is waste of my time) to older OS or versions of software. I believe, like I said earlier, Vista is lil bit counter-intuitive, but not unreliable !! Once you get used to it you'l like it.

CVF_GS is a good manual, but I never had to refer itfor installing CVF on my computer. Because installing CVF is that easy! The manual , honestly takes time to read and understand for an average person (who has computer internals knowledge 5/10).

I hope you'l be able to run your hello world project succesfully.

Let me know if you did and have any specific questions??

Dear Peter: Nope. I still get the same results. Here is exactly what I did:

1. Make a new directory on my C drive "C:MyFortran"
2. Open CVF and choose "file/new/Fortran Console Application.
3. At this point the Project Name Box is empty and the Location Box sez "C:|MyFortran"
4. I type "hello" in the name box and is appropriatly appended to location box to read "C:MyFortranHello"
5. The "create New Workspace Button" is selected automatically
6. I hit OK and select "a hello world application" in the next dialog
7. The next dilog is a summary of the input and it sez that the project directory is "C;MyFortranhello"
8.I hit OK and get the same old nasty error message "The project directory no longer exists. Please choose a different directory"!

I check the folders on the C: drive and C:MyFortranhello does exist at this point and it contains "hello.dsw"
I double click this and VS opens CVF with navigation pane saying "Workspace 'Hello' 0 Project(s)" and no files.

This is the simplest thing one can do and it doesn't work.

I was never a begginer. I am just "old."

DT

[Peter]

DT,

Strange !. It looks like you are not able to create any f90 source file. You can check this by creating a .f90 file and write a hello world program, for that you want to select an 'Empty project' instead of 'A simple hello world project' . Let me know what happens


Was your installation a 'customized' or 'typical' one ??

[longthong]

Quoting - Peter

DT,

Strange !. It looks like you are not able to create any f90 source file. You can check this by creating a .f90 file and write a hello world program, for that you want to select an 'Empty project' instead of 'A simple hello world project' . Let me know what happens


Was your installation a 'customized' or 'typical' one ??

Peter;
Sorry I have taken so long to reply to your post. I have made some progress. I returned the new DELL Vista machine. Can't handle Vista. But I am stuck with the new Vista laptop because the return time frame has expired. So I loaded VF on this laptop. I took all of the default options except I did not load the environmental variables for command line execution and I did a custon installto install everything. I then created a console project "hello" and selected "A(n) "hello" simple project". It worked! But when I tried to comple, build and run (!) I got this error message.

THIS PROGRAM HAS KNOWN COMPATABILITY ISSUES

[] Don't show this message again.

If I check for solutions online it tells me it doesn't have any and suggests a Microsoft site. When I hit that button I get a page not found message. So much for Microsoft. However, if I "run program" it works! Compiles, builds and runs. Checking the box eliminates the messages in all future runs.

I'm not out of the woods yet, however. When I try to run a sample problem by clicking a .dsw file I get an error message:

MICROSOFT STUDIO HAS STOPPED WORKING
etc. etc.

This occurs also if I go to the folder my new "hello" project is stored in. But "recent workspaces" in visual studio works. I think this gives me a way around my problems with Vista.

Incidently, I installed VC and everything apears to work fine. Again I took all the defaults (including folders) and made a complete install. Thanx for all the help. I will keep you posted.

DT

PS I couldn't figure out how to emmbed a picture (.bmp) inthese posts?

[Peter]

Quoting - longthong

Peter;
Sorry I have taken so long to reply to your post. I have made some progress. I returned the new DELL Vista machine. Can't handle Vista. But I am stuck with the new Vista laptop because the return time frame has expired. So I loaded VF on this laptop. I took all of the default options except I did not load the environmental variables for command line execution and I did a custon installto install everything. I then created a console project "hello" and selected "A(n) "hello" simple project". It worked! But when I tried to comple, build and run (!) I got this error message.

THIS PROGRAM HAS KNOWN COMPATABILITY ISSUES

[] Don't show this message again.

If I check for solutions online it tells me it doesn't have any and suggests a Microsoft site. When I hit that button I get a page not found message. So much for Microsoft. However, if I "run program" it works! Compiles, builds and runs. Checking the box eliminates the messages in all future runs.

I'm not out of the woods yet, however. When I try to run a sample problem by clicking a .dsw file I get an error message:

MICROSOFT STUDIO HAS STOPPED WORKING
etc. etc.

This occurs also if I go to the folder my new "hello" project is stored in. But "recent workspaces" in visual studio works. I think this gives me a way around my problems with Vista.

Incidently, I installed VC and everything apears to work fine. Again I took all the defaults (including folders) and made a complete install. Thanx for all the help. I will keep you posted.

DT

PS I couldn't figure out how to emmbed a picture (.bmp) inthese posts?

DT,

You almost got there ! except you go check for the solutions online and download two softwares/updates from MS website. They are supposed to make MSVS or IVF compatible with Vista. Then you'l be all set. That happens to everybody!

Go to add files, give some name, say 'bmp' >click on 'create folder'> a folder will be created.click on 'bmp', upload the file from your hard disk> once you uploaded the file say image.bmp, click on it and select add as an attachment or add to the editor.

[longthong]

Peter et al,

CVF is running smoothly. The only thing I can't do is open a sample project by clicking its' .dsw file in the sample directory. I can open a sampe project from within VS with file/open and click the .dsw file. That's good enough. Thanx to everybody for the help. This forum is ppriceless.
DT

[Les_Neilson]

Quoting - longthong

Peter et al,

CVF is running smoothly. The only thing I can't do is open a sample project by clicking its' .dsw file in the sample directory. I can open a sampe project from within VS with file/open and click the .dsw file. That's good enough. Thanx to everybody for the help. This forum is ppriceless.
DT

Try right mouse click on the dsw file and select properties. On the "General" tab there is an "Opens with:" option with a "Change" button. Click the button and you should be able to specify that you want Visual Studio to open the file.
Then when you double click the dsw file VS should start automatically.

Les