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.
Related
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.
I am trying to work out the least disruptive way of beginning to experiment with Windows 8 development. I currently have a Windows 7 Ultimate PC (plenty of disk space, RAM and i7 CPU), and I have a copy of Windows 8 (not 8.1).
I have considered various options:
Convert my whole machine to Windows 8. (Not ideal right now, as I am in the middle of other work, but I may have to do this eventually).
Dual boot Windows 7 & 8. (Can't get this to work. Windows 7 is already installed, and though I can get Windows 8 to install on the second HD, I can't get its boot menu to see Windows 7. I suspect this would be easier if I installed Windows 8 first, but that would be a huge pain.)
Run either OS using a virtual machine. (I haven't looked into this yet, and I have no idea what is involved.)
As a final option, I wondered if it is possible to develop Windows 8 applications on a Windows 7 PC and remote debug on an attached Windows 8 device? (I'd prefer to do this, as it is a way I have worked often in the past while doing console development.)
Does anyone have any experience of any of this - positive or negative? It takes ages to experiment with this stuff, with the constant threat of recking my existing work environment. I'd really appreciate any advice or pointers to articles that deal with any of this stuff.
Microsoft do their loyal developers no favours. I've paid hundreds for modern hardware, Windows versions and Visual Studio, and still it seems difficult to say the least to develop for their latest OS.
Kind wishes ~ Patrick
Option 4 is not possible. In similar situation I went with option 2 and gratually migrate myself completly to windows 8.
If you have problems with boot try to ask on superuser.com or better search the web for guideline.
If you want to develop applications for Windows 8 don't go with option 3.Please see this post on installing Visual studio in VM.
Regarding option 2,verbatim from Microsoft
You must install the older operating system first, and then install the more recent operating system. If you don't (for example, if you install Windows Vista on a computer already running Windows 7), you can render your system inoperable. This can happen because earlier versions of Windows don't recognize the startup files used in more recent versions of Windows and can overwrite them.
But as #Antonio said there may be roundabout for option 2.
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've been using ArcGIS 10.1 on my MacBook Pro (2011 model) via Boot Camp for a few months. A few days ago, I just installed Parallels 9 in order to use ArcGIS and my Mac programs at the same time and I've run into an issue with the license needing to be repaired. When I try to open ArcMap via Parallels, I get an error message saying something to the effect of "the license is in need of repair". When I installed Parallels 9, I chose to import my Boot Camp so I didn't have to reinstall anything. My guess is that ArcGIS thinks Parallels is a different computer and that's why the license is failing? Any ideas on how to resolve this issue? I can get a hold of another ArcGIS license so if it's a matter of using another license, I should be ok. Thanks.
You can not use ArcGIS on Bootcamp and VM with the same license key (single use license! - concurrenct use license with separat license server of course no problem). The license key is generated with some internal ids of your computer (eg ethernet MAC and other - you can match the ethernet MAC id in Parallels but thats not enough). You have to chose where you want to work with ArcGIS: bootcamp or VM (before licensing). Thats really annoying...
I had the same issue. Extremely annoying since it is without a doubt impossible to run both your BootCamp and VM versions at the same time. I never resolved it with traditional fixer.
If you are a student (hopefully you are) usually the person/department in charge of license distribution understand the need for both (rasters can be very sluggish on the VM side, but not always) when you are really putting the machine to the test.
SO, that is how i ultimately "solved" the issue. However, I believe the route issue to be the MAC address authentication, as I am experiencing the same problem in ArcGIS 10.2 when I tried to copy my VM from my MBP optical drive to my MBP sad - none of my tools are working.
When I first loaded the copied VM (by opening the VM file directly, not through Parallels) I was prompted if I wanted to use the same "......" (can't remember the actual term, but something along the lines of MAC id, or network address, etc.). Unfortunately I said no make a new one - WRONG ANSWER.
I'm trying to get it sorted now - just saved VM file, completely wiped Parallels, reboot, reinstall; and now I'm on the message boards trying to get this install right) [helpful ideal VM settings for ArcGIS specifically: http://maps.uky.edu/support/docs/BP_ArcGIS_on_Macv5.pdf ).
All that being said the first time I had this issue (month of nightmares, and late GIS homework) I had imported my VM from Bootcamp, which seems logical, but at that time (Parallels 8 and ArcGIS 10) it was still a license error I was receiving, but for some unremembered reason I was convinced it was because the VM calls its hard drive the "C" drive which it clearly is not - parallels merely translates this virtual C drive between the 2 OSs and their respective boot drives.
( I have not tried this next part yet) it might be worth trying to install your VM on the Mac side and then use the Windows or Parallels Migration Tool to create a Win migration file and then go to your BootCamp side (IMPORTANT - DEACTIVATE YOUR ESRI LICENSE BEFORE UNINSTALLING ARCGIS - if you don't do then you'll be mired in the "this license has reached its maximum allowable installations" or whatever they say).
If your Bootcamp side still has your ArcGIS, deactivate, then uninstall that version. Then try to import your migration file, but I've lost some of my Windows skills since switching to Mac, so I would do some research on that part. In theory since, your VM version was pointing to (for all intents and purposes) your "C" drive on the Mac side, hopefully the BootCamp install won't get as tripped up by the double installs as the VM did.
Just a thought, I realize as I finish this that you posted in October, so likely you've moved on, but if any of what I said is wrong, or if you found the best way to have it all, I would really appreciate your response.
I am trying to install Sheridan controls (ActiveThreed 2.01) on Win7 64-bit, but evidently it is a 16-bit installer so it won't execute.
What would be the best way to get round this problem?
Can anyone comment on whether http://homepage3.nifty.com/takeda-toshiya/msdos/index.html would be helpful?
It took me months of googling to find a solution for this issue. You don't need to install a virtual environment running a 32-bit version of Windows to run a program with a 16-bit installer on 64-bit Windows. If the program itself is 32-bit, and just the installer is 16-bit, here's your answer.
There are ways to modify a 16-bit installation program to make it 32-bit so it will install on 64-bit Windows 7. I found the solution on this site:
http://www.reactos.org/forum/viewtopic.php?f=22&t=10988
In my case, the installation program was InstallShield 5.X. The issue was that the setup.exe program used by InstallShield 5.X is 16-bit. First I extracted the installation program contents (changed the extension from .exe to .zip, opened it and extracted). I then replaced the original 16-bit setup.exe, located in the disk1 folder, with InstallShield's 32-bit version of setup.exe (download this file from the site referenced in the above link). Then I just ran the new 32-bit setup.exe in disk1 to start the installation and my program installed and runs perfectly on 64-bit Windows.
You can also repackage this modified installation, so it can be distributed as an installation program, using a free program like Inno Setup 5.
You can't run 16-bit applications (or components) on 64-bit versions of Windows. That emulation layer no longer exists. The 64-bit versions already have to provide a compatibility layer for 32-bit applications.
Support for 16-bit had to be dropped eventually, even in a culture where backwards-compatibility is of sacred import. The transition to 64-bit seemed like as good a time as any. It's hard to imagine anyone out there in the wild that is still using 16-bit applications and seeking to upgrade to 64-bit OSes.
What would be the best way to get round this problem?
If the component itself is 16-bit, then using a virtual machine running a 32-bit version of Windows is your only real choice. Oracle's VirtualBox is free, and a perennial favorite.
If only the installer is 16-bit (and it installs a 32-bit component), then you might be able to use a program like 7-Zip to extract the contents of the installer and install them manually. Let's just say this "solution" is high-risk and you should have few, if any, expectations.
It's high time to upgrade away from 16-bit stuff, like Turbo C++ and Sheridan controls. I've yet to come across anything that the Sheridan controls can do that the built-in controls can't do and haven't been able to do since Windows 95.
I posted some information on the Infragistics forums for designer widgets that may help you for this. You can view the post with the following link:
http://forums.infragistics.com/forums/p/52530/320151.aspx#320151
Note that the registry keys would be different for the different product and you may need to install on a 32 bit machine to see what keys you need.
I am mostly posting this in case someone comes along and is not aware
that VB2005 and VB2008 have update utilities that convert older
VB versions to it's format. Especially since no one bothered to
point that fact out.
Points taken, but maintenance of this VB6 product is unavoidable. It would also be costly in man-hours to replace the Sheridan controls with native ones. Simply developing on a 32-bit machine would be a better alternative than doing that. I would like to install everything on Win7 64-bit ideally. – CJ7
Have you tried utilizing the code upgrade functionality of VB Express 2005+?
If not,
1. Make a copy of your code - folder and all.
2. Import the project into VB express 2005.
This will activate the update wizard.
3. Debug and get the app running.
4. Create a new installer utilizing MS free tool.
5. You now have a 32 bit application with a 32 bit installer.
Until you do this, you will never know how difficult or hard it
will be to update and modernize the program.
It is quite possible that the wizard will update the Sheridan controls
to the VB 2005 controls. Again, you will not know if it does
and how well it does it until you try it.
Alternatively, stick with the 32 Bit versions of Windows 7 and 8.
I have Windows 7 x64 and a program that will not run. However,
the program will run in Windows 7 32 bit as well as Windows 8 RC 32 bit.
Under Windows 8 RC 32, I was prompted to enable 16 bit emulation
which I did and the program rand quite fine afterwords.
I had 32-bit software with a 16-bit installer that I couldn't unzip. I solved it with otvdm which allows you to run windows 1.x, 2.x, 3 programs on win64. In fact, otvdmw allows you to select the program to run (otvdm is command-line).
16 bit installer will not work on windows 7 it's no longer supported by win 7 the most recent supported version of windows that can run 16 bit installer is vista 32-bit even vista 64-bit doesn't support 16-bit installer....
reference http://support.microsoft.com/kb/946765
Bottom line at the top: Get newer programs or get an older computer.
The solution is simple. It sucks but it's simple. For old programs keep an old computer up and running. Some times you just can't find the same game experience in the new games as the old ones. Sometimes there are programs that have no new counterparts that do the same thing. You basically have 2 choices at that point. On the bright side. Old computers can run $20 -$100 and that can buy you the whole system; monitor, tower, keyboard, mouse and speakers. If you have the patience to run old programs you should have the patience to find what you are looking for in want ads. I have 4 old computers running; 2 windows 98, 2 windows xp. The my wife and I each have win7 computers.