I need to programmatically (c++) start my desktop application once per week. With a parameter, on user context.
In Windows I have implemented this using TaskScheduler. This is close to what I have used: https://learn.microsoft.com/en-us/windows/desktop/taskschd/c-c-code-example-creating-a-task-trigger
I need to add same functionality for osx port. Can someone point to the Api that is exposing this functionality? I am targeting osx 10.12
I have an XP 32 bit installation on VirtualBox, but whenever I want to increase the cores of the cpu to more than one core, the OS won't boot! What's going on?
These two links might help:
How to change XP VM on virtualbox to have two CPUs without having to reinstall XP
VirtualBox - XP guest does not see multiple cores/multiple processors
You can try ways provided in these two links. If they does not work, you might need to reinstall.
I found the problem! At least in my case.
The problem was that I had "Virtual Machine Platform" feature enabled in Windows features.
I had looked and looked but many nothing said about this, some people said to just turn off Hyper-V which I did but same problem. So I decided to disabled everything that had to do with "virtual" then it worked!
Also I downgraded to WSL1
Don't turn off Hyper-V, otherwise it may give you some problems like slowing down your VM (atleast it did for me).
Disable Virtual Machine Platform
Enable Hyper-V as this allows you to run WSL and Virtual machine together
And if you really want WSL also enable "Windows Subsystem for Linux"
Downgrade to WSL1
Can you install win 7 in virtualbox that already runs in virtualbox of a nother win 7? Question also implies for any other operating system.
Each virtual machine is technically "independent" of one another, and with VirtualBox, you could easily do this, since it is supported on both Windows and Linux host operating systems (emulated or not). You could simply use Windows as your "base-host" OS, run Linux in a VM, and then use that operating system as the new base-host for Bochs.
check this out
HERE
Your question is not fully clear to me. If you mean running a virtualized Windows 7 within a native Windows 7, this is perfectly possible, as any other OS/OS combination. It will just eat up a lot of ressources. If you mean running a virtualized Windows 7 within another virtualized Windows 7, then you will run into trouble and you would better run the 2 virtualized Windows 7 in parallel on a single native OS.
I have installed carbide c++ 2.7 , S60 3rd edition FP2, activePerl on Drive C. carbide c++ detects that the sdk is installed and I can create Symbian OS C++ projects too. When I build the projects, all the executables are created and when I run the emulator debug, the emulator starts and then after few seconds it terminates. I followed the instruction come with sdk on how to install the sdk on vista( well same should apply for win 7 ryt?).. please help me.. Even I cannot run Hello world program.. :D
I've had the same problem on Windows 7 using SDK Emulators, the issue was that my sound chip was Realtek. If you disable all sound outputs via Sound option from Control Panel and start the Emulator then it will work. After it loads fully just re-enable your sound devices.
That's at least how it worked in my case.
As some of you may have noticed, a few hours ago Microsoft released Windows 7 RTM to those of us with a Technet or MSDN subscription.
I unfortunately didn't have the opportunity time-wise to test the new OS. I'm asking of anyone who used it with Visual Studio 2008 during RC what was your experience? Did you feel the RC offered a stable environment for it? Did it behave well under Windows 7? In short, can I rely on Windows 7 as my soon-to-be development platform?
On another note, did anyone did any tests the new crt? What were the results?
EDIT: As an afterthought, I'm interested indeed in both 32bit and 64bit experiences, since the OS will go to just one of these machines.
x58 chipset and i7 processing unit, Windows 7 RC x64, I had a lot of issues with programs locking up and crashing (not responding, invoking windows "Ill find out whats wrong! .. not) when you try to close the form. It kills development time.
Especially visual studio 2008, countless crashes and lock ups or delays. It does run good most of the time, but it has its moments.
My experience is that its not 100% solid.
I thought that it was weird, because its built in the Vista SP1 core, and my hardware runs Vista very solid, no hitches -ever-.
And yes, it was a fresh install of Win7, not an upgrade. I'm installing Server R2 though, so I'll see how that works out! :D
edit
I couldn't put my finger on it. Under Vista SP1/SP2 it runs rock solid. The video drivers worked great however for my GTX295, motherboard BIOS is up to date.
I don't think that the problem was driver related per-se, but I can't say. The symptoms purely came across as a software related issue with the OS and how it handles the Windows.
The Event logs are not a help, because a generic form crashing doesn't produce any real detail for me to burn through and say "Ah ha!".
I must say though, it was mostly Visual Studio and forms run under the debugging host process. Anything else was pretty okay, so it could be more or less just a compatibility issue
edit
After a fresh install of Windows Server R2 RC, after the initial installation and a driver install for a wireless adapter, the system fails to boot up properly (or atleast "detects" an problem), so you have to manually tell it to boot Windows up normally, which works.
After doing some Windows updates, same thing, but this time the OS fails even when trying to boot up normally and just does a reboot (probably a blue screen, but surpressed by my BIOS)
My experience with R2 was blazingly fast, both in performance and a drop in satisfaction and warm fuzzies about it working good
It seems that either way you go, on the newest of new hardware, it has its issues. Bummer.
The best way to write Win7 compatible programs is to use Win7 as a development platform. I use Win7 x64 with Visual Studio 2008 almost half a year and it looks pretty stable and has some helpful features (e.g. snap). At this moment all my programs are ready for certification and compliant with all Win7 requirements. I use VirtualBox to test my programs in Windows XP/Vista environment and VirtualBox works without any problems on Win7 too.
My hardware is Intel Q6600 processor on ASUS P5KC motherboard. ATI video card was unstable until some build of drivers, now it works fine. NVidia video card has no problems all the way.
I've been using Visual Studio 2008 under the RC for a while now. No issues at all. For that matter, I don't remember having any under the Beta either.
Windows 7 is good to go for development, as far as I'm concerned.
We've been piloting Windows 7 internally for some time now and have had very few if any troubles with it. I've personally been using it with Visual Studio 2008 (Full and Express) and have been very pleased with the OS overall. I recommend it. (It is fair to note, however, that we use beefy hardware, generally dual or quad core, 4GB RAM and good video cards for our pilot).
I been using windows 7 (x86) for few month now, never had a single problem with that.
Visual Studio 2008, Adobe products, Netbeans and everything else running just fine.
Win7 RC1, VS 2008 SP1 here. The only issue so far is graphical glitches in drawing VisualSVN icons in the Solution Explorer if I scroll the projects tree using mouse wheel.
Also sometimes Tortoise SVN cache crushes. But it might not be related to Windows 7.