- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When the program ends and displays the message "...Exit window?", if you click No, the window freezes.
The same program works just fine in Vista x64/XP.
I have Windows 7 Ultimate x64 and compiler 11.1.035.
Any suggestion?
R//G
[Edit by Steve Lionel (Intel) - for information on this problem and to obtain a fix, please readIntel Visual Fortran QuickWin applications freezing]
The same program works just fine in Vista x64/XP.
I have Windows 7 Ultimate x64 and compiler 11.1.035.
Any suggestion?
R//G
[Edit by Steve Lionel (Intel) - for information on this problem and to obtain a fix, please readIntel Visual Fortran QuickWin applications freezing]
Link Copied
- « Previous
- Next »
128 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Works fine now. Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I may need to start a new thread about this, but has this freezing behavior been seen in any other types of FORTRAN executables?
I have a FORTRAN DLL that is called from a VB.NET program that has been freezing on a few Windows 7 64-bit machines. We have not been able to reproduce the issue here (both were developed on Win7 x64).
The DLL is not Quickwin, but it does have callbacks to the VB.NET program for screen output (shown on screen via a VB Rich Text Box).
Thanks for any help.
I have a FORTRAN DLL that is called from a VB.NET program that has been freezing on a few Windows 7 64-bit machines. We have not been able to reproduce the issue here (both were developed on Win7 x64).
The DLL is not Quickwin, but it does have callbacks to the VB.NET program for screen output (shown on screen via a VB Rich Text Box).
Thanks for any help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes it would be best to start a new thread with a title that refelects it. Can you include details on what you are seeing and even a test case that reproduces if possible. I have not seen or heard of these problems with Visual Basic caused by the compiler and this issue applies to Quickwin library only.
Thanks,
Thanks,
------
Wendy

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
- « Previous
- Next »