I'm running Windows 7 Pro, SP1 on a Dell Precision M2800 (I know it's out of date).
My VMWare Workstation version is 11.1.4 build 3848939. Right now I'm using it primarily for a VM with Windows 7 and a bunch of (latest) Rockwell/Keyence software.
I'm using CodeBlocks version 16.01 to compile C++. Packages I'm using in my code include various SDL libraries and the standard stuff.
The issue I'm having is repeatable for me:
I start both VMWare and CodeBlocks running on my host machine. I compile and test code in CodeBlocks while I wait for Rockwell to finish compiling/uploading/etc.. After a couple of times compiling and running programs with CodeBlocks, my host OS will lock up for a long time (more than an hour). I haven't waited long enough to see if it ever unlocks on its own.
The work-around I'm using right now is to just not use those programs at the same time. I'm not necessarily looking for a solution, (because I anticipate that everyone will just tell me to update Windows), although solutions are fine. I'm looking for information about the root cause. Anybody have ideas about why this might be happening?
Thanks in advance.
Related
I have a HP Pavilion dv6 which ran the x32 version of Windows 10, and so I wanted to install x64 OS. Also just a small side-note, the computer was set-up with Windows Insider. Anyway, I also have a Mac, which I created a USB boot drive with x64 Win10 (I originally used the Windows Media Creation software on my dv6), but whenever I tried to open the setup.exe file my dv6 would just say that the software is not compatible. That lead me to think that maybe Windows Insider was having an impact on the OS being slightly newer and not exactly compatible with the setup file... so I stopped Windows Insider updates and rollbacked to the latest Windows. But nope, the file still complained that it wasn't compatible. Skip past 2 days worth of me trying to create a boot drive and booting up my HP, whenever trying to boot up my dv6 with the image loaded on manually or by using Unetbootin, my dv6 would only complain that it's a Non-system disk or the USB drive doesn't contain an operating system.
Simply, I would just like to update my dv6 which now (sorry, I forgot to mention this earlier) after rollbacking now gets stuck in a loop of the green screen of death or blue screen of death and then "Recovering your computer" or something like that, from x32 to x64 os (and yes, I checked that it was capable of running x64 software).
Thanks,
Avoxel284
p.s. this is my first question, so sorry if I sound like some kind of noob or something...
p.s.s. i backed up my files, so all I need is to at least get it to some sort of OS.
I want to install some software on a pre-alpha XP build (codename Windows Whistler). However, 90% of the installers fail to run. I guess it is because of the kernel version, which I suppose is somewhere between 5.0 and 5.1 (as I remember even the software that should run under Windsows 2000 did not succeed to install).
How can I most correctly and efficiently change the values in registry so that I have a chance to test some software (I know there can be bugs because of missing features, I'm doing tests in the VM).
The same question about Windows XP x64 with kernel version 5.2 - where to change it so that basic software designed for Win XP x86 does install as it does on regular Win XP (or maybe there is some compatibility option in properties).
Thanks for your help.
UPD: Java Runtime Environment version 5 update xxx should work on Windows 2000 (and even on Windows 98 SE, I tested it). But it somehow refused to install on Whistler... Maybe they cut something important away during development to make builds faster to compile?
You can try Right Click on .exe -> Properties -> Compatibility -> Run this program in compatibilty mode for.. and then specify compatible versions of OS.
I want to make a Windows store application using the monogame libraries, but for this purpose, I need to install Windows 8.1. The installation fails and gives me the error
0xC1900101 - 0x40017
This error is quite large and alot of people have had or still have it. I made alot of research on it and it seems that this problem is caused by driver incompatibility. I tried the installation about 15 times now, every time updating some drivers, installing updates, etc.
On the installation, it stops at 84% on "Applying PC parameters" step.
So I believe that the problem is that one of my drivers in incompatible and I need to remove it so here are my specs/peripherals:
ASUS G75VW qs71 laptop (16GB RAM, i7 ivy bridge) (I don't think it is the problem, since my friend has the same and it worked for him)
- Logitech G930 Gaming Headset
- Razer Orochi Mouse (Not the 2013, but the 2012)
If some of these drivers are incompatible, please tell me how to remove them.
Thank you.
P.S. I'm not sure if this question is relevant for this site, but it is somewhat programming related and I need it to do programmation.
I have had basic tests for meteor on a Windows7 PC.
But there the application crashed too often.
Before this, I tested meteor on PC running Windows8. There, crashes happened much less often and generally they were recovered when I shutdown and rebooted the meteor.
Is Meteor unstable on windows7?
Or is there any way to avoid this?
The version packaged to the MSI installer that can be found on win.meteor.com is not official. If you want a more stable, try the virtualized option I've described on the site. I've been using that for a month without issues.
Please could you be specific about what problems you are seeing, for example, what do you mean by 'crash'.
You can certainly raise issues on SO, but if they appear to be specific to the windows port, please raise a ticket at: https://github.com/sdarnell/meteor
The only difference between Win7 and Win8 meteor, is that the installer sets the Win7 compatibility mode for the node.exe executable on Windows 8.
There are also relatively few differences between the windows port of meteor and the official linux/mac release. So there is a possibility that the issue is either environmental (e.g. you have different things installed on the two machines), or it may even be a core issue that just happens to appear more often Win7 due to timing issues (there was a case of this in 0.6.3).
I've been using clang successfully on Windows XP and Windows Vista using the 'experimental' builds for MinGW, but now that I try on my new Windows 7 64-bit laptop it simply crashes. Even if I just run "clang++" or "clang" it crashes, and I can't figure out how to get windows to give me more detailed crash info (I will edit that in if I can). I've redownloaded clang and reinstalled MinGW, and I've tried running clang.exe in compatibility mode, but it still doesn't work. This is the first time I am using it on 64-bit, I hope that's not the issue (if it is, I still have another computer I can use).
I've looked around and can't find anyone else having this same problem with clang crashing before even giving any output or processing any input, I really feel lost.
This has now happened multiple times on various system and I have found the solution. Reinstall MinGW using the prepackaged files, the 'latest' ones have a tendency to be unstable in relation to clang. Make sure you haven't also installed a newer version of gcc on top of the MinGW installation, as that will cause issues too.