Is it possible to take a complete restorable snapshot of a running or suspended DirectX program while NOT within a virtualization program, like VirtualBox? If so, how? While the program is running natively, the snapshot would have to include enough of the OS and hardware state to restore the program without messing up the stability of the OS when it is restored a few minutes or more later.
I would like to do this on XP with DirectX 5 to 9, but ideas or solutions for Windows 7 using DirectX 5 to 11 or Linux using Wine are welcome. I am not sure how good support is for DirectX 8 or less on the most recent Windows OSs.
For those who want to comment on the virtualization approach, I can not get solid DirectX 7 or before hardware rasterization emulation, and I do not know how to trick a pre-coded program into using reference or software rasterizers. In other words, I would like to get 3DMark2001 and like working in VirtualBox. I know snapshots are easier using virtualization software, but that could only work for me with DirectX 8 or later.
Comments on the stability of snapshots, using virtualization software or native OS, are welcome too.
Related
I use Codewarrior
- V4.7 for HCS12X
- V6.3 for HCS08
in Windows XP.
Moving CW to Windows 10 seems impossible.
It won’t install, and dongle licensing does not work.
I have tried to figure this out on the NXP site, but I find it extremely difficult and confusing.
Which Codewarrior is needed for HCS12X and HCS08 in 32 and 64 bit Windows 10?
Yeah it is nearly impossible. I've struggled lots with this problem. There is an unofficial "hack" someone made - won't link it because my browser says the site is unsafe. However, it would seem that hack only works up to Windows 8, not on Windows 10. I have both IDEs (HCS08 and HCS12) running perfectly on a Windows 7 machine, with dongle license.
We managed to get it running so-so on Windows 10 by doing a dirty hard copy of the hacked installation folder to Windows 10. Various mysterious bugs followed though, so not the best idea.
Another option is to run the Windows XP mode emulator from Microsoft, but it is no longer supported for Windows 10.
So ultimately there are two options left if you are stuck with Windows 10:
Move development to the worst IDE ever released, Codewarrior for Eclipse. Please note that the future of this IDE is uncertain after the NXP merger. They might decide to put their money on their other trash IDE, LPCxpresso.
Port your project to another compiler or MCU.
I would recommend to install it in a VMWare or virtualBox container using Windows 7 as OS.
This makes it possible, that your installation will work even in some years.
I'm using such a container (with WinXP) for an old Visual Basic 6 installation and HEW-IDE.
You should use at least Win7, to avoid the network problems with WinXP (SMB1 can't be connected anymore).
There is a Codewarrior Classic 6.3 community project for RS08, S08, ColdFire V1 for Windows XP, 7, 8, 8.1, and 10. Basically, the installer is repacked will all service packs and patches for USBDM and PEMicro tools.
If you have an obsolete programming tool you will need to use CW 6.3 on XP. Also, if you have these specific family of parts S08: RN, RNA, PA, PT, Kinetis (including Tower), ColdFire V2 you must use the bloated eclipse version CodeWarrior 11
For S12 or S12X CodeWarrior Classic 5.2 for Windows 7 - Windows 10
But when they released 5.2 they removed most of the older derivatives from it, but you can add them back using this procedure CodeWarrior 5.2
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
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.
I have a few programs I'd really like to test on Windows 8 for ARM. I don't have any Windows 8 ARM hardware though. Is it possible to install Windows 8 in some kind of ARM emulator or some such?
Yes, I know that if it compiles on WinRT it is suppose to "just work", but I'd really like to test it not only to see if it works, but also relative performance(as much can be guessed from an emulator)
There is no way, how to start you x86 PC in an "ARM mode", or launch Simulator in ARM mode. WinRT was designed to bridge the differences or these platforms so you don't need to worry about it and you can just develop. All I can think of right now is try to contact local Microsoft representative in your area - if they have any ARM tablet for testing, they might help you in this, but again if your app is not really flawed or computing power demanding, don't worry about the ARM platform :)
This now appears to be sorta possible (haven't tested yet) with the new App Ceritification Kit for WinRT, which appears to include ARM emulation.
EDIT: This isn't an emulator, it will only run on an ARM WinRT device. I guess there is no ARM emulator, despite that page mentioning ARM and emulation
I think this is a common problem for all developers using Windows CE 6.0 operating systems on specific hardware. I have a client that needs a custom operating system for its ICOP PDX-089T PC with Touch panel, that is based on DM&P SoC CPU Vortex86DX-1GHz.
I do not have the hardware with me, so every time I make a change I have to send at least the NK.bin file, or the whole ghost image to the client to make the tests for.
Is there any way to build a custom Windows CE emulator to add it to Visual Studio 2005 for testing or may be a custom virtual machine to launch it through VMWare or Virtual PC?
I tried some guidelines from the internet to build one, but every effort in making one resulted in hanging up my PC.
Does anybody have similar needs and some solution?
Note: The emulator I need is for Vortex86DX processor and ICOP board.
Microsoft abandoned the x86 Emulator some time ago, choosing to support only an ARM emulator (the BSP ships in the box with Platform Builder 6.0). This means that you can't create an emulator for the x86 processor, though I'm hard-pressed to think of a scenario where you'd really need to and where just getting hardware isn't a better solution for anyway.
There is a BSP for doing Virtual PC OS builds that would run on x86. It's not had much activity in some time, and I've never tried it, so YMMV.