I've bought windows 8 upgrade for my windows 7 pc. I've payed, downloaded, but unfortunatly, for the entusiasm of that moment, I haven't burned a dvd or usbkey for having the iso. Now, after two week I had a bsod after a synchronization with skydrive, and after this, my pc is "broken" (I've tryed everything) ...
So, now I want to do a reset but I haven't got the install dvd (I've already tried with a refresh but nothing usefull happens) . I've searched everywhere on web but is not clear what I have to do... (I'm not able to find any official download for win8 pro) I've bought my upgrade, but I can't reinstall it? It's strange and it sounds a little silly...
Any hint?
I had the same problem. Because you own the license, you can download a Windows 8 pro from "the internet" and install it with your key. Just be sure to download a official iso with a valid hash (it doesn't matter if you get it from unofficial sources).
Of course you can also call Microsoft for support, but the former solution is so easy.
Related
I had been using Platform-IO up to 2019 but when I reopened a project things started getting worse and worse. Tasks disappeared and it took a while to be able to compile again. Now Platform-IO has disappeared completely and I was getting deprecation warnings in the "Toggle developer tool' console.
Now after a complete reinstall of VS, Platform-IO etc. the IDE is still not functioning and I regret ever using it. It is like you jump into your car begging it to start. For professional use (able to restart your car every day without a mechanics) this solution needed to be solid and reliable which it does not seem to be. I will have to switch to another IDE I guess. The name Microsoft should have make me hesitate ...
I am using Windows 7 Professional and NO I WILL NOT UPGRADE THE OS.
Is there any means to install a functioning VS-Code / Platform-IO on Windows 7 or is it just an idea of an IDE ?
Sorry to appear mean but "Making you more productive" sounds like a scorn.
I recently tried installing Platform IO on a Win 7 PC of a colleague and experienced similar issues like you. Seems like current Platform IO versions / builds are not compatible and therefore not runnable on Windows 7.
Only idea comes to my mind is using legacy / previous releases of VS Code and Platform IO (manual plugin installation with a legacy release) to get a runnable environment on Win 7, but I didn't test it since I ended up installing a recent Ubuntu next to Win 7. (Seemed like a better solution to me).
Here you can find all of the older releases of VS Code & Platform IO:
https://code.visualstudio.com/docs/supporting/faq#_previous-release-versions
https://code.visualstudio.com/updates/v1_64
https://github.com/platformio/platformio-core/releases
Good luck ;)
I am really new to Windows Phone 8 App development. I would be grateful to you if you can answer my question. I have a machine with Intel(R) Core(TM) i3 processor and when checked I found out that my virtualization setting enabled.
I installed Windows Pro 8.1 in to my machine and then it indicates that my Hyper Visor is default switched off and I had to run it. But when I run it after making some of the changes by restarting the machine, suddenly for some unknown reason it undoes every change made finally leaving the machine with no Hyper Visor running.
I come across the same process when I am to run the Windows Phone emulator to test Windows Phone 8 Apps.
I hope my issue is clear to you all, can someone help me to fix this issue or tell me the exact reason behind this?
I would look at my Windows Event log and see if you perhaps there's a problem with Hyper-V being incompatible with a driver or something like that. It may be failing to reboot and the doing a system restore to get the machine back to a bootable state (by rolling back Hyper-V). I've had problems with Hyper-V and my HP laptop's blue tooth drivers:
Here's the thread where I found out about that:
HP Bluetooth / Hyper-V woes
Updating the driver to the newest version on HP's site fixed my computer for a while, but then I had problems with Windows Update hosing my machine with an update to the Bluetooth driver.
I seem to have fixed it for good by going to RA Link's website and downloading a version of the driver that's newer than the one on HP's website. I'm not at my personal computer right now, but if you'd like I can see if I can find the driver version that seems to have fixed my Bluetooth/hyper-v problems for good.
-Eric
So I finally got my two Kinect v2's in the mail, and was looking forward to get some raw data from them and see how much they interfere with each other. I went to go download the SDK, and for some reason I had never noticed the Windows 8 requirements... As in Windows 7 isn't supported.
This feels pretty bogus and unnecessary, but fine I can't do anything about that. Before I waste some money to upgrade my machine to an OS that I really don't want, is there any way to get the Kinect v2s to talk to a Windows 7 machine (or maybe even Ubuntu)? I don't need any of the fancy skeletal detection or anything; I just want raw xyz-rgb data. I was reading about OpenNI (and their new Apple overlords), and I was hoping that by some miracle their last open source distributions would be forwards compatible with the Kinect v2s?
TL;DR: Are there any free SDKs that can interface with a Kinect v2 on Windows 7-64bit?
look at libfreenect2
It looks like its not ready yet but there are people working on it. So you might want help them along.
Update 2014-10-28
The Project is live and kicking and works fine
Just dropping by to say that I successfully 'installed' the Kinect 2 SDK to windows 7 and it is being recognized by driver4vr.
I'm not precisely sure which files where required so I'll just post my process.
Install VirtualBox (and enable CPU virtualization in bios to support 64bit OS)
Install win 8.1 x64 in VirtualBox
Monitor the VirtualBox c-drive for changes (I used spy-the-spy)
Download and install the Kinect 2 SDK in VirtualBox
Check spy-the-spy for all files added, and copy them to your Windows 7 OS on the same location. (It also installs some VC redistributables, so skip the files already there)
Reboot windows 7 and enjoy Kinect 2.0 on the final decent MS OS.
The Windows 8 is MINIMUM requirement to developing kinect v2
you do not need use Skeleton(kinect V1) or Body(Kinect V2) to track body or skeleton .
you need use to MultiFrameSource Class
I was recently following a tutorial in a "Kinect Hacking" book that I purchased on Amazon. The first thing I was asked to do, is to check to see if my Kinect plug would fit into my laptop's which it did. I was then asked to download OpenNI from the following link: http://www.openni.org/Downloads/OpenNIModules.aspx
The only problem is that the link given above redirects to a "unknown page" (which is probably due to a recent site update...Anyway, I download OpenNI from here instead: http://www.openni.org/openni-sdk/ (for Windows), and it installed fine, though after then asked to additionally install Sensor Kinect from the following link: https://github.com/avin2/SensorKinect (that link did work) and executing the .exe file, I received an error message saying to: "Please install OpenNI version 1.2.0.4 or higher!"
So...what should I do?
Thanks in advance! (I haven't had any help on the OpenNI forums, so I posted here).
P.S I'm running Windows 8
Apparently I'm not the only one with this problem, and after some research I found that the new OpenNI isn't compatible with the SensorKinect, so in order to fix this I have to download the version that is slightly dated, luckily a site called "ZigFu" has all the necesary plugins built onto one: http://zigfu.com/en/downloads/browserplugin/
Does anyone know if Powerbuilder 10 is compatible with Windows 8 (Both the IDE and the runtime module)?
It seems like 11.5 is officially supported, but I couldn't find any info on PB 10's compatibility on Windows 8.
If it isn't, any tips on the migration process from 10->Further version? (Anything particular we have to watch out for?)
You should have no problem with running PB10 applications on Windows 8, appart perhaps not being not fully compliant with Win8 standards (concerning the placement of application data files, access rights on files, and so on mostly related to UAC file virtualization).
Neither you should have big problems with running the IDE, but maybe some minor issues (I think about an issue on the retrieval argument editor on PB11.5 that could also address PB10).
This is one of those things where you just have to try it yourself. The number of PowerBuilder developers with Windows 8 is likely very small.
I am supposed to be getting a Surface Pro 2 when they come out Oct 22nd which will run Windows 8.1. Hopefully there won't be any issues.
I am not sure about PB10 but I have used PB 10.5 in Win8 with no problem.
We have serious issues with running a PB10 application on Windows 8 computers.
Application runs fine until user enters text in datawindow fields, the application "stopped working". The problem is that it happens randomly, 10 fields can be entered without a problem but at the next field the "stopped working" pops up en the application is closed the next time it might happen after entering 2 fields.
The same application runs already for years on many computers unders XP, Vista, Windows 7 without any issue.
Until now we still have no clou what is causing it. Also we have no idea where to start searching.
The application is developed andf deployed under XP.
Next week we are going to setup a development environment under Windows, hopefully this will give us some more light on the issue.
Two things you need to realize:
PB10 was built (and support development stopped) before before Win8 was conceived, so obviously Sybase couldn't do anything in PB to help with Win8 compatibility. You're relying on MS's ability to maintain a backward compatible environment. IME, they do a pretty good job (better than my experience upgrading in the Unix world, but I'd imagine YMMV), but it's never perfect.
PowerBuilder is powerful enough to allow you to build an application that will break under any operating system. PB10 may have been supported on XP, but I guarantee you that I could have written something that violated an XP rule, or corrupted memory, or whatever, and would have been broken under XP. (I've seen memory corruptions that didn't manifest themselves until after an OS upgrade or some other change; so "broken" may not even manifest symptoms yet.) Is that Sybase's fault? I don't think so. They're the rope manufacturer; if you hang yourself....
Bottom line is what's already been said: no matter what the manufacturer or anyone else says, the only answer worth anything is the results of your own testing. My "Hello World" app may run in Win8 just fine, but your app that taps into the TCP/IP stack, leverage protected mode calls, sending printing language codes directly to the point-of-sale bar code printer, etc....
Good luck,
Terry.