Can i use dev c++ 4.9.9.2 on Windows Server 2008 R2, i mean that i tried using it on windows 8 but it didn't run. And we are restricted to use this IDE only from our university.
Server 2008 R2 is 64-bit OS.
According to their site, Dev C++ 4.9.9.2 only supports Windows 9x, NT, or 2000. Given that the Windows Server operating system series started in 2000 (with Windows Server 2000), and that Dev C++ 5 doesn't support it (even though it supports XP, a later released OS), I would surmise that it is not supported on Windows Server 2008 R2. However, you should be able to run it if you use Compatibility Mode.
You can use the following steps: (from How to Run Older Programs under Windows 8 -- For Dummies but copied down in case of link rot. This technique also works in Windows Vista/7/Server 2008 R2)
Right-click the program's icon and choose Properties.
When the Properties dialog box appears, click the Compatibility tab
and then click the Run Compatibility Troubleshooter button.
In its robotic way, Windows 8 tries to guess what version of Windows
your program needs, and then it applies the changes. If the program
begins working, you're through.
If the program still has trouble, though, move to Step 3.
In the Compatibility Mode section, select the Run This Program in
Compatibility Mode For check box and select the program's desired
Windows version from the drop-down list.
Check your program's box or look at its manual to see what version
of Windows it expects.
Click OK and then try running your program again to see whether it
works better.
If your older program doesn't run, it's time to upgrade to a newer version.
Related
I am developing a VB.Net based Windows8.1(10) Store application.
After published, I've found out that my App crashes on Windows8.1 while it works fine on Windows10.
So, I want to debug my App on the Windows8.1. However, I cannot find how to do so.
When I [Run] the App to [Simulator], it runs on clone of my computer, but I want to run it on other version of Windows.
Visual Studio 2015 is now installed on Windows10.
Thanks.
Disclaimer: I work on Visual Studio, though not on the Universal/Modern App area.
This is not a supported scenario and there is no feature present in Windows that emulates or simulates previous versions of the "Modern" runtime environment.
The Simulator feature is actually a local-loopback Remote Desktop (Terminal Services) session and existed to make it easier to debug Modern applications given that they could only run in a fullscreen mode, however as this is no-longer the case (as apps are now floating windows) the utility of the Simulator is limited, and as you're discovering is not relevant to your problem.
The only solution I can recommend is to use Hyper-V (or another desktop virtualisation product, such as VirtualBox or VMWare if you don't want a hypervisor installed) to install a dedicated Windows 8.1 environment followed by installing the Visual Studio Remote Debugger.
Given the rapid adoption of Windows 10 (as it is provided as a recommended update to the majority of Windows 8.1 users) I don't personally recommend explicitly targeting the Windows 8.x "Modern" app environment unless you know you will have users or if it's a contract requirement.
I had SQL Server 2005 working when I upgraded to Windows 10. Now it won't work. I read that it is not compatible with Windows 8, according to Microsoft. Windows 10 is but the matured version of Windows 8, to me. Is there any way I can get SQL Server 2005 to work with Windows 10?
Have you tried to apply / re-apply SP4? I'm not saying it will work but it works in Windows 8. Not sure what you upgraded from.
This may help .. https://www.youtube.com/watch?v=cj859zcWhEM
uninstall inFlow before upgrading to Windows 10 and then re-install (because of compatibility issues with SQL Server 2005). This is pretty easy and can be done from the START menu by searching “Programs and Features” and once open, choosing to uninstall inFlow Inventory.
Not sure which version of SQL you’re using? You can check the version of SQL Server through the START menu by searching “Programs and Features.” In that window, look for “Microsoft SQL Server” and check the version (it will either be 2005 or 2008 R2). If you’re in 2008 R2 or 2012 you’re golden, no extra steps required).
So bottom line: if you’re planning to take advantage of the upgrade from Windows 7 to Windows 10 that’s great, but take a few minutes to double check your SQL Server version (as noted above) before you upgrade. Most of us won’t be affected but if you don’t, the upgrade could break inFlow and that’s no fun at all!
On a Windows 8 machine with VS Express 2010, VS 2012, I've installed Visual Studio 2013 Ultimate Preview.
In the end of the installation, an error message appears, giving me this link to activate Hyper-V.
So i entered BIOS, I found a similar option for enabling Virtualization, and set it to Enable.
After finishing restart, I downloaded coreinfo.exe, opened the console as Admin, and checked for asterisk in the row where it said I should check. So there was, which means my computer supports SLAT.
When I go to Control Panel -> Programs -> Windows Features on/off, there is no Hyper-V there as is shown in the link that there will be, and I should select it and press OK to install/activate it.
Will this be fixed by reinstalling Visual Studio 2013 Ultimate Preview now?
Make sure you are running Windows 8 Pro 64-bit as the Hyper-V feature is a Pro Edition feature.
I'm using the Crystal Report 10 viewer ActiveX control in an Access App I've written. Works great in Office 2003 on 32bit versions of Windows. The problem arrises when I try to run the program in 64 bit Windows (with 32bit Office). I get the following error:
Run-time error '429': ActiveX component can't create object
I get this error on the following line of my VBA code.
Set rdApp = CreateObject("Crystalruntime.application.10")
How can I get this to work in 64bit?
I don't have any specific experience with Crystal Report, but I do have some experience with installing components on a 64-bit Windows environment that were intended for 32-bit Windows, so here are some general suggestions of things to try:
Before installing, try loosening the security privileges - I have Windows Server 2008; on this OS, they're under Start | Administrative Tools | Local Security Policy. Many old installers are thwarted by these controls. You'll want to return them to their defaults after the install.
Make sure that you run the installer with admin privileges (right-click; run as Administrator).
Examine the installation log for Crystal Report - it may indicate a failure registering a component. In one instance, I was able to get the installation working by running the command to register the failed component manually, on an administrator-privileged command line (the command was in the log).
If acceptable, try to create a Windows Virtual Machine running a virtual Windows XP, and try the installations there (this might be a bit tedious, due to your need for MS Office).
Take a look at VMWare's ThinApp - this is intended for packaging applications for administrators, but this was the solution we ended up using to shield one of our 32-bit apps from Windows 64-bit perils
Hope this helps; we struggled for awhile trying different things to get our legacy apps working on a 64-bit environment.
How can I use my old VB6 customized SQLServer database application in Windows 7?
I can not upgrade my old VB6 EXE file.
VB6 Apps:
You can run 32-bit VB6 apps in windows 7.
The full scope of support is detailed here: http://msdn.microsoft.com/en-us/vstudio/ms788708.aspx
There is a thread here that covers some bits and bobs you may need to cover off: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/vb6-executable-will-not-run-in-win-7-64-bit/05c506d7-2ae9-4abd-91d6-9481b4b243e0
The main thing to realize is that you may have to manually install some of the pre-requisits you would have expected to be there by default on other windows versions.
SQL Server 7:
This may be more insteresting. You can certainly run a newer version of SQL Server and set the compatability level of your database as required - this may be sufficient.
I'd be surprise if you were able to install SQL Server 7 itself on Windows 7
I don't know about SQL Server 7, but VB6 will definitely run on Windows 7.