I have tried twice to download IBM Watson Studio Desktop Trial for Microsoft Windows 64-bit. It's 3.3 GB and on my slow internet connection it takes many hours. The 1st time, the download just stopped about halfway through. The 2nd time, the download was only at 1.7 GB but said it was done. When I clicked on IBMWatsonStudio_x64.exe it said the file was corrupt.
I'm a Data Scientist and am quite interested in trying IBM Watson Studio Desktop Trial for Microsoft Windows 64-bit but can't get past this 1st step. Help!
Your operating system should be Windows 10 Enterprise or Professional otherwise, it will not execute the installed file. If os is suitable for the installation, then you need to check your internet connection, it is better to have fast internet for such big files.
Related
I've some time lately trying to find a clear answer for updating some of my desktop applications to run on Windows 8.1 (Desktop/laptop and Surface). So far everything I am finding is pointing toward developing for the Windows Store where the application then could be downloaded.
Heres my development Environment:
Windows 7 Ultimate
MS Visual Studio 2012 Premium
MS Visual Studio 2013 Express
My test environment consist of:
Windows 8.1 Surface Tablet
Windows 8.1 Laptop
When I build something now (retargeted to the newer framework (4.5 (4.5.1 is installed)) and copy it over to these devices and try to run them I get an error that the indicates "This app can't run on your PC" "To find apps for this PC, open the Windows Store.". This isn't really what I want to do, I just want to make he applications we use on a day to day basis in my retail store availible to the new computers.
A couple of questions come to mind;
Does the development environment need to be a Windows 8.1 based environment?
Do I need to again buy a new version of Visual Studio (Visual Studio 2013)?
Am I stuck using the Windows Store to deploy applications?
If anyone could point me in the right direction as to where to read or provide some insight tho cross this hurdle would surely save alot of repeated reading about how great the store is.
A Surface tablet does not permit running desktop apps. You can only run apps that are downloaded from the Store. So scratch the idea that your Winforms app is going to work on the tablet. There isn't any good reason why it would not work on the laptop, they work fine on mine.
Does the development environment need to be a Windows 8.1 based environment?
Yes, for VS2013. For VS2012 it needs to be at least 8.0
Do I need to again buy a new version of Visual Studio (Visual Studio 2013)?
You didn't buy VS2013, you do need the correct version of Express. There are several. You need the "Express 2013 for Windows" edition, it only supports developing apps for the Store. You probably have the "Express 2013 for Windows Desktop" edition, it only supports desktop apps and supports Winforms. The retail edition supports all targets. The Express editions were split to keep them small.
Am I stuck using the Windows Store to deploy applications?
If you develop Store apps, yes. You get a temporary license to develop the app but it expires after a month. If you need more time then you get just another license. But the app needs to be certified to obtain a permanent license so it can run permanently on the Surface machine. And everybody else's.
I downloaded RAD 8 for websphere from Developer works website.
Amidst its installation, it prompted for disk 1,2&3. But i could find 'em nowhere in the RAD_SETUP folder.
Where to get those disks?
There's more ZIPs you need to get from Developer Works that are the installation disks.
When I run my application (WPF,VB.net 2008) on Windows XP, I get weird Windows Errors. When I installed VS2008 on the machines that got the error and debug. I got a loader lock exception, so I went into Debug and removed it. However, I still get the error when it is installed on the machine.
Is there a way to remove the Loader Lock Exception when the application is install. I do understands that it might not be the best solution, but it seems this happen only when I start an WindowsElementHost with a ReportViewer and this is causing the problem, so I don't really know what else to do with it.
All version of XP have that problem, as with 2003.
In Windows 7 and Vista I never run into that error while debugging and the installed product. The same thing applies with 2008 and 2008R2.
I've done a little bit of research and below you can find my guesses:
maybe it's a bug in the Report Viewer control itself and you should update to a later version. I've noticed that on December 2012 a new version was released (see this post), supposedly running on both .NET 3.5 and 4.0 (so it should work with VB 2008, see download page);
I've noticed that Report Viewer 2008 SP1 requires .NET 3.5 SP1 (see the download page) -- maybe an outdated version can trigger the exception you are seeing;
maybe Windows XP is not updated to the latest Service Pack or is the wrong edition -- again Report Viewer 2010 SP1 requires Windows XP SP3 (see download page) and Report Viewer 2012 does not run on Windows XP Starter Edition;
maybe it's a library used by Report Viewer that causes this exception (especially a mixed mode assembly) -- a dump or a stack trace would be helpful in this sense;
there is a comprehensive answer in this thread in the Visual Studio Tools for Office forum that lists several resources to understand this problem;
the previous link suggests that in some conditions it's safe to ignore this lock. If from your testing under Visual Studio with Loader Lock MDA disabled you see that there is no problem, you can disable the MDA in production machines using the instructions in this blog post -- basically it involves setting an environment variable and adding some lines to the app.config file (see also the documentation for Loader Lock MDA to see what the new lines should look like). I haven't tried it but I thought it may be useful for you as a last resort solution -- just be sure to test thoroughly your application to avoid undesired side effects.
To get more help, I suggest you so specify:
the version of Report Viewer you are using;
the version of .NET Framework you are targeting (in particular including Service Pack);
what Service Pack is installed for Windows XP;
any stack trace or debugging information you can gather.
So we've an old circa 2000 Powerbuilder App that we've been maintaining all this time. Its been working great until I tried to get it going on my new Windows 7 64-bit machine.
First, the old SQL 2000 client install we always have used won't install.
Second, after installed SQL 2008 connectivity tools, the app fails to connect to our database.
The error is "DBMS is not supported in your current installation"
Im worried that the 32bit PBMSS90.dll just cannot deal with the 64bit SQL drivers. I have no idea what to do at this point.
If you can offer any help, its greatly appreciated.
Thank you
Just load the 32-bit connectivity software for SQL Server. The 32-bit and 64-bit should be able to co-exist nicely, and PowerBuilder (and any other 32-bit software that accesses SQL Server) will be able to use 32-bit.
Good luck,
Terry.
Windows 7 comes with a virtual machine IIRC that can emulate all MS operating systems back to Windows 95. If this is an OS environment problem try loading your app in an XP virtual machine.
The problem I encountered is that the ancient Microsoft SQL Server driver we had been using (MSS) cannot be installed on a 64bit machine.
To make matters worse, the current SQL Native Client driver (SNC) is not at all compatible with the Powerbuilder 9.0 app we had.
The solution was to installed SNC and recompile the application in Powerbuilder 11.5 or later (in our case we used 12).
The application now runs, and connects to the database. There are a few issues to work out yet, as MSS and SNC regard char type variables differently, but the major hurdle was covered.
Thanks for your help.
I would like to install Visual Studio 2008 and MS SQL Server 2008 on Ubuntu OS which I have in my PC.
Wine is great, but using it for either Visual Studio or MS SQL Server is probably pushing it. Both are behemoths that tend (especially VS) to use the latest MS APIs. More to the point, both VS and MSSQL are listed as Garbage in Wine's db, meaning compatibility is very poor.
I would recommend you take a serious look at the available tools on GNU/Linux, such as MonoDevelop, Mono, Eclipse, MySQL, etc. You can use cross-platform build technologies, such as nant to build the same apps on both platforms.
If that isn't an option, then you will have to resort to virtualization, as noted by sean.
This answer might help you. Visual Studio and SQL Server are for Windows OS variants. You'll need some sort of VM to run on Ubuntu.
If you have some sort of Windows OS disks available to you (XP / Vista / 2008), then you could consider installing Windows under VirtualBox, and installing your software inside that VM. That used to work really well for me when I was still on Ubuntu.
I've been developing using Visual Studio in Ubuntu since version 10.04, and there is a solution, although I would recommend that you run the 64 bit version of Ubuntu and have at least 4Gb of ram available.
Install the latest version of VirtualBox (download from the website, rather than using the ubuntu repository), and install Windows as a virtual machine. You need to allocate a virtual disk and then, when the virtual machine starts for the first time, either install Windows from a CD/DVD, or select a CD image to use within VirtualBox.
You will also see, with the later versions of VirtualBox, something called "seamless mode". This essential hides the virtual machine, so that instead of running in a window, it will integrate with the Ubuntu desktop. That way, you can run Visual Studio in what looks to be native to Ubuntu.
I have tried both VMWare Player and VirtualBox and found VirtualBox to be better for my setup. Although VMWare Player has something called VMWare tools, which provides an API layer to better translate Windows calls to your video card, this can be temperamental if you're using an ATI card (speaking from experience with a Mobility Radeon HD 4600). Nvidia provide much better driver support in Linux than ATI do.
Hope this helps!
I think is better to simply dual boot to write your .net code. It will put your hardware to better use, and you will be able to focus more since all the programs on which you waste your time will be on the linux side :D (at least that's the upside for me)
To use Visual Studio 2008 and MS SQL Server 2008 in any Linux..
Just try sharpdevelop: http://www.icsharpcode.net/opensource/sd/