Am unable to install sas 9.3 in my window 10. Am getting below error message
You've attempted to install software intended for one operating system on a
machine using a different operating system. You should either install on a
machine using the operating system you downloaded for or return to the download
site and download the appropriate software
Pls advise how to resolve this problem
Your license limits you on what operating systems you can install your SAS distribution.
If you were to open your software order email, what operating systems are listed there? Alternate, open the SAS license file that you choose during the installation, it should also be listed there.
SAS 9.3 is not compatible with Windows 10. You will not be able to install it natively, and there are no known workarounds. Windows 10 support begins with 9.4M3 and above.
Related
I am wanting to write unmanaged C++ code that reads from and writes to the event log. I am working with VS2017 and Windows 10. Everything I have read states that there is a utility ECManGen that is used to create the manifest file that is then run through the message compiler (mc). I have the latest Windows 10 SDK installed. According to what I have read, the executable is in the Bin directory under the SDK. I have scanned my entire drive and have not been able to find the utility. Has the utility been deprecated for something else? Is there somewhere I can obtain the utility? It does not seem to be available for download from Microsoft as a component.
ecmangen was removed from the Windows 10 SDK starting with version 10.0.16299.15. If you install an older version of the SDK (side-by-side installation is supported, so you can keep the newer versions as well), it will be available again.
I recently installed windows 8.1 on my virtual machine. My SAS version is 9.3.
I have a 64 Bit system, x64 based processor on my Windows 8.1
I checked this link which tells me that enhanced editor on SAS 9.3 is not supported on Windows 8/8.1 (excluding Pro or Enterprise).
http://support.sas.com/kb/44/495.html
And this link tells me which SAS components go with each respective Windows Edition:
http://support.sas.com/supportos/list
Is there a way around this ? Using SAS without the enhanced editor is like playing with a fetus instead of a child (Apologies if anyone is offended, This situation disturbs me a lot)
SAS has not supported 'Home' versions since Windows XP; while Win7 Home was capable of running SAS, it isn't officially supported either.
You may be able to get Enterprise Guide working; in my Pro 8.1 installation I ran into the same error, and never got the EE working but did get EG working.
Your best bet is to upgrade SAS to release 9.4; it's a free upgrade. And BTW, they just released the first maintenance version (9.4M1), so be sure to get that.
Since you're using operating systems inside a virtual machine, couldn't you just boot up another version of Windows in your virtual machine(e.g. Windows 7) that is compatible with SAS? From my understanding of virtualization, you can run multiple different operating systems at the same time. It's the whole point of virtualization.
MY code will be deployed on FreeBSD. Would I be able to code using VS2010 in Win7? can this be done on Linux using gcc? or do I need to have freebsd installed on my laptop.
I plan on buying a new ultrabook and not sure FreeBSD will support the drivers or wireless. What the best practice here? VMs?
Thanks mods.
You can just write code in Visual Studio, however you will not be able to compile and run it in Windows, unless you are only using standard libraries.
To compile and test your code you need a FreeBSD somewhere.
I have never used FreeBSD on a laptop, so I can't say if dualbooting it with Windows is a good idea.
The best thing would be if you had access to a test server with the same configuration as your production server (i.e. same FreeBSD version, same packages, etc.). Then you could write code in VS, check it into a repository, SSH to the server, update a local copy of the source there and build.
If that is not an option, I recommend setting up a virtual environment. Download VirtualBox, obtain FreeBSD and install it on the VM. Set up port forwarding for SSH and then the process is pretty much the same as with a separate server. You may have to make some additional tweaks depending on the nature of the work you'll be doing.
Here is a setup I have used in cases where I am not using any OS specific library.
On your Windows 7 machine develop your application as usual without using MFC/ATL etc. If you are linking to external libraries/APIs you will have to use one which is portable across Windows and Linux (e.g. Boost libraries). Do not use pre-compiled headers (stdfax.h) or any other option which is Windows specific.
Get VirtualBox and install your favorite OS (FreeBSD in this case) and your favorite tool chain (gcc clang)
Share the disk/folder you are developing your app in the Windows file system so that it is visible in VirtualBox. In Ubuntu they end up in the /media/sf_Folder.
Compile in FreeBSD in VirtualBox. You will need to have an alternative make system setup in parallel in addition to the stuff Visual Studio creates. Make sure you do not have any conflicts in the way the directories used by the build system (to store object files etc.) between FreeBSD and Windows. You can try out this http://code.google.com/p/make-it-so/ to convert your VS solutions to gcc makefiles.
This way you can continue to use your favorite IDE and also rebuild on your target *ix OS on the same machine.
gcc + gvim + ( ( ctags with omnicppcomplete ) or ( clang with clang_complete ) and STL + Boost.
My company is thinking of dumping InstallShield and move to something else, mainly because of the poor experience it had with it, mostly on Linux.
Our product is a C++ application (binaries, shared libraries) targeted at Windows and Linux (Red Hat).
The installer itself isn't required to do anything special, just dump some binaries and shared libraries and sometime execute an external process. Things like version upgrading through the installer isn't necessary, this is handled after the installer finishes.
I thought of suggesting using NSIS on Windows and RPM on Linux.
What are the recommended installer systems to use when deploying to Windows/Linux? Something that is cross platform to prevent maintaining two installers is a definite plus.
For Windows I would definitively use NSIS. It's very lightweight, easy to code and very simple to understand. Using msis would just be a killer - it generates guid for every file so you can get upgrades for free and stuff but truth being said, you never end up using any of these.
Regarding Linux I would go for RPM and Deb. They're probably the two biggest packaging system so you'll be targeting most of the Linux users. I've never tried RPM but creating a Deb package is fairly straightforward.
See also:
What to use for creating a quick and light setup file?
Packaging to use to deploy cross-platform?
And even:
Creating installers for complex cross-platform programs
There's a tool called BitRock Installer which can create installers for Windows, Linux and OS X.
However, I think that if you target RedHat it would be better to provide native packages for that platform (that is .rpm).
For C++ projects, I'd go with cmake/cpack, if you are also willing to change your build system. Great support, strongly cross-platform. cpack has various generators, NSIS is one..
Take a look at InstallJammer. It will handle both platforms from the same build project, and you can have the installer register the package with the RPM database as well if that's your requirement.
You may want to consider our tool BitRock InstallBuilder , it can generate installers for Windows and Linux from a single project file and also RPMs. Is your application based on Qt? Our clients include the makers of Qt, Nokia (previously Trolltech) and they use it to package their Qt Creator product. We encourage to give InstallBuilder a try and contact our support with any questions or suggestions you may have.
How do Window's programmers profile their native C++ code?
On Unix/Linux you have gprof [thanks Evan] & valgrind (I personally used this one, although it's not a real profiler), and recently I'm on Mac and Solaris, which means I moved to dTrace. Now when I've had the need to profile on Windows in the past, like at my previous job, I used Intel's vtune, which is great, however it's commercial, and I don't have a license for private use, so I'm left wondering what's the standard (free is better) tool windows programmers commonly use?
Thanks in advance
You should give Xperf a try - it's a new system wide performance tool that can drill down to a particular application and what exactly it's doing inside itself as well as what's it's asking of the OS.
It's freely available on the Windows SDK for Windows Server 2008 and .NET Framework 3.5 ISO:
Install the SDK by downloading the ISO image, or using the Web based
installer.
Find the xperf MSI in the SDK's "bin" directory. It will be named
xperf_x86.msi, xperf_x64.msi, or
xperf_ia64.msi, depending on the
architecture for which you install the
SDK.
You can then install the xperf tools from the MSI directly, or copy
the xperf MSI file to another location
and install it from there. For
example, you could keep the MSI files
on a USB key.
Source: Pigs Can Fly blog on MSDN.com
Just verified that the xperf msi will not install except on windows Vista or Windows 2007.
-Adam
I got AMD Code Analyst. It's free, and you don't need an AMD CPU ;)
It's a little basic compared to something like Intel's VTune, but the price is right.
This link talks about Linux, but I use the same technique in MSVC and in C#.