I installed FireFly version 3.10 with Power Basic 9 as compiler in a computer running Windows 7 and when I try to compile a program I get this error message:
FireFly Visual Designer has stopped working
I clicked debug button and this message shows up from Program Compatibility Assistant :
This program has known compatibility issues with this version of Windows.
Program: Visual Studio.
Publisher: Microsoft,
Location: …\msdev.exe
I click the run button and I get this message from Microsoft Visual C++:
Unhandled exception in Firefly3.exe: 0xC00000005: Access violation.
How can I fix this problem?
I think a lot people here use Win 7 including myself.
When you did the install of FF, where did you select to install the "CodeStore Functions Library, Settings and Projects"?
For Vista and Win 7 you should select the "My Documents" folder, which is NOT the default setting.
Bob
I have win7 x64 and Visual Studio 2010. I haven't had any problems
Doug
Hi Rioja,
Might be some setup configuration corruption somehwere in your pc/windows. Your compiling a PB source code with PB9 initiated through FF3.10 triggers the VC++ v6 IDE msdev.exe to run.
Regarding compatibility issue with msdev.exe, this shoud be set to run in Win2000 mode. But this is another issue and not the issue you want to resolve here.
Check why msdev.exe is triggered to run, when it is not relevant to PB9.
EDITED:
I missed this the first time I read your post:
"I clicked debug button and this message shows up from Program Compatibility Assistant :"
Windows pop up a message and when you click the Debug button, Windows open the default debugger.
This happend to me before not with msdev.exe but with something like JITdebug.exe or something like that whenever I had one of the .NET Visual Studio installed.
In other words, whenever an error occur Windows prompt you to open the default debugger. This default debugger can be changed. See this link:
http://support.microsoft.com/kb/121434
The Debugger value in my WinXP Pro SP3 is:
drwtsn32 -p %ld -e %ld -g
If you install FireFly into a folder like C:\FF3 instead of the Programs folder you will avoid those problems.
Installing "CodeStore Functions Library, Settings and Projects" in the My Documents folder is to follow Microsoft's guideline regardless of which Windows you are using.
This guideline to put working, config, supplementary files in My Documents and outside of Program Files folder has been in place even before Win2000. It is only from Vista onwards that Microsoft "enforces" it.
To cater to "legacy" software that did not follow guidelines, Microsoft implemented file virtualization (and also registry virtualizaion) in Vista and Win7. File and registry virtualization, being a temporary measure, may or may not continue in future versions of Windows.
"Legacy" here refers to software that does not follow guidelines. It does not necessary means "old", can also be "newly" written ones.
Rioja's issue may or may not be caused by file virtualization. Because if it is, other error would already have pop up. I may be wrong.
When the default debugger is triggered by Windows, it means there is an error cause by an exe program and Windows want you to know and to debug it.
However, you can turn off the default debugger. See Solution 1 the following link. It applies to turning of any default debugger, not just Dr Watson:
http://techchand.org/88/how-to-remove-dr-watson-postmortem-debugger-error
For more insight into File Virtualization, see these links:
http://www.codeproject.com/Articles/66275/Windows-Vista-File-and-Registry-Virtualization.aspx
http://support.microsoft.com/kb/927387
Note that installing into root folder in C:\ is also not recommended and may or may not encounter problem in future versions of Windows.
I believe I see My Documents in Win98, I cannot remember whether I see it in Win95. This is how old the guideline has been.
Quote from: Cho Sing Kum on February 20, 2011, 12:06:01 AM
Installing "CodeStore Functions Library, Settings and Projects" in the My Documents folder is to follow Microsoft's guideline regardless of which Windows you are using.
Thanks for the info. I'm adding it to my to-read list.