- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm using CVF v6.6 in Windows 2000 professional.
My program runs more or less correctly until I try to use the debugger to check on a couple of things. As soon as I hit the debugger icon I get a Windows message: "DFDEV.exe has generated errors and will be closed by Windows ... An error log is being created."
Windows does not say what this file is called nor where it is to be found. I've had a look in the Event Viewer but it is not there. However, since it closes the CVF Developer Studio it looks pretty serious.
Please can anyone suggest what might cause such an error and where the error log might be located?
With many thanks in advance,
Mike
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Michael
I'm having the same problem - executables seem to run but all attempts at debugging crash.This happened after installation of IVF 8.0 and makes one wonder about the compatibility. Since I have the luxury of an extra PC that has CVF without IVF, I may just use itto check out what's going on. If I find anything out, will post it here in this thread.
John Carman
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The problem with DFDEV.EXE (which is the CVF shell over MSDEV.EXE - all it does is present the CVF splash screen) is common and can usually be solved by deleteing the file in your project with the .OPT file type. Developer Studio will recreate it.
Installing Intel Visual Fortran will have no effect on this at all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve
Good to hear from you again; your fix works fine.
I only experienced this problemafter installing IVF on the same box with CVF 6.6 - Not even VS .Net 2002 caused the problem, so something must get stepped on somewhere.I had another old Win98 box at home that still had CVF 6.6 on it and that had no problem debugging.
In my case, it's also possible thesecurity "gurus" at work did something in the registry to cause this; they are forever mucking about to make us secure! The whole project sits on a 256MB Compact Memory card andtravels between the homePCs and work on that medium. Next step is to apply your document and migrate the mess to IVF.
John

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