I need to install Visual Foxpro 6 on my Windows 8 laptop.
I have the Visual Studio 6 CDs. I go through the installation and everything completes installing. However, after the progress bar completes and goes away, the green installation screen displays a message like "Configuring your setup" or "completing setup". But this screen never goes away. It just hangs until I "Close Program" it.
When I start VFP6, it opens but the Command window never displays. I do see the white VFP6 desktop, but it doesn't respond and I have to Close Program.
I tried copying the VFP6 files from the CD to the drive, but the same thing happens when I try to run VFP6, it doesn't respond and I have to Close Program.
I'm able to run VFP9 on this Win8 PC just fine. But I can't get VFP6 to install or run.
Is there a solution?
I would suspect that VFP 6 is not even CLOSELY supported for Windows 8. Another person I help periodically was running VFP 8 on a Windows 8 machine and it fails. Apparently that was his consensus finding across the board for others he has communicated with. I wouldn't even bother trying VFP 6 on Windows 8.
Related
Tried shutting down my laptop, a windows 7 os on Sunday afternoon. Then I got a notification telling me that a program was still running, forced the system to shut down because I was in a rush. Then on Monday morning, I powered up my system and tried opening visual studio code editor by clicking on the shortcut on the desktop. When I click, the loading circle spins for some seconds then stops. Nothing else happens. It doesn't open. Did this several times. I have uninstalled and installed visual studio code 4 times,but it's still the same thing. Even after downloading and installing its meant to open / run automatically, but instead it doesn't. Please what can I do? This is really frustrating.
I've been using Rad Studio for some old projects on another Windows XP (32 bit) based PC. So, I wanted to move my projects new computer. But, after the setup, bds.exe didn't open. Same setup file works on Windows 10 PC (64 bit), but I am not able to open on Windows XP computer.
When I tried to open its closing immediately and giving just-in-time debug option from visual studio 2005. Also, it’s giving some error codes. But, I couldn’t find any solution for this issue.
When I wanted to open firstly following screen comes up.
Then, if I click no it’s closing. If I click yes following screen comes up.
Note: Closing Just-in-time debug doesn’t help to open bds.exe .
We are getting a application failed to initialize error 0xc000007b. I looked around it seems to maybe be the .NET framework, I also read a possible virus.
Our application is Visual Basic .NET 2010, running on Windows XP, Windows Update is turned on.
What fixes the problem, seems to be temporary, is take my backup copy of the .exe and replace the .exe on the machine, it runs for a few hours. Keep in mind I am 12 hours away or more from the machine, I remote to it using TeamViewer.
Will event viewer or something else give me a better idea of what happened? or more information about the error and it's cause?
I'm far from a Visual Basic guru, so I'm very puzzled as to why this application is throwing this error after running for approximately 2 years.
Can windows update cause this? Does .NET framework update itself automatically?
Thanks for any help.
Well if your program was not recompiled, I'd doubt it's the program itself, but if you have the source code you can try running it through the debugger to see what's going on, and where. Personally I'd try just reimaging your xp system and seeing if that fixes the issue.
Also, isn't xp out of support? I suppose windows updates could affect it. I've seen updates cause older applications to break, so it is a possibility. You can look at the recent updates and roll them back.
I have written a user interface in Visual Basic that sends commands to AutoDesk Inventor to create 3D CAD assemblies. Towards the end of my program, the CAD file is saved and a SaveDialog box comes up. It was working perfectly fine for a while, but now there is an error. Here is the relevant code segment:
SaveDialog.Filter = "Inventor Part | *.ipt|Step File | *.stp"
SaveDialog.DefaultExt = "ipt"
SaveDialog.ValidateNames = True
SaveDialog.ShowDialog()
On the last line shown, I get a run-time error as follows:
"The program can't start because api-ms-win-crt-runtime-l1-1-0.dll is
missing from your computer. Try reinstalling the program to fix this
problem."
After closing this error message, the SaveDialog box comes up anyway and works perfectly fine. Of course, on the compiled version the error box never actually shows up and the program simply hangs up indefinitely.
I have search for solutions to this problem for two days. I used Dependency Walker and found a list of other dlls that are reportedly missing, most of them under the MSHTML.DLL
I figure there is probably something that is not referenced correctly in my program, but I'm not sure where to look. Thanks for any help!
The problem is that the KB2999226 (Universal CRT) which is part of the Visual C++ Redistributable failed to install. Is your automatic updates turned OFF?
Solution
Install Windows Updates:
Go to Start - Control Panel - Windows Update
and click on Check for updates. Install all available updates. After the updates are installed, restart your computer. After the restart repeat the steps above again until no more updates are available.
Download the Visual C++ Redistributable:
For Windows 64-bit
http://download.microsoft.com/download/9/3/F/93FCF1E7-E6A4-478B-96E7-D4B285925B00/vc_redist.x64.exe
For Windows 32-bit
http://download.microsoft.com/download/9/3/F/93FCF1E7-E6A4-478B-96E7-D4B285925B00/vc_redist.x86.exe
Run the vcredist_x64.exe (64-bit) or vcredist_x86.exe (32-bit) and select Uninstall. Run the .exe again and select Install
I'm using Visual Studio 2013 Express on Windows 7 to build a desktop application using .NET services with DirectX 11. I've started testing on 2 different Windows 8 machines. One also has VS2013E on it, and uses Windows 8 Pro. The other does not have Visual Studio, and uses Windows 8.1. On the first machine, all I had to do was move my executable onto the machine and it worked fine. On the second, I see no evidence that it attempts to run. In fact, I added a MessageBox.Show(...) as the very first line in my code to see if my code was breaking anywhere, but still, nothing happens. Any ideas on what I'm missing?