Re: Comment Installer Windows 11 32 Bits
Nandan Barahona
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.
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'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.
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 am mostly posting this in case someone comes along and is not awarethat 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.
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 doesand 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 emulationwhich 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
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.
I'm following the instructions of someone whose repository I cloned to my machine. I want to use the make command as part of setting up the code environment, but I'm using Windows. I searched online, but I could only find a make.exe file, a make-4.1.tar.gz file (I don't know what to do with it next) and instructions for how to download MinGW (for GNU; but after installing it I didn't find any mention of "make").
Other recommended option is installing a Windows Subsystem for Linux (WSL/WSL2), so you'll have a Linux distribution of your choice embedded in Windows 10 where you'll be able to install make, gccand all the tools you need to build C programs.
On windows 10 or 11, you can run the command winget install ezwinports.make in the command line or powershell to quickly install it, restart the command line or powershell, Than you can use the command make.
Another alternative is installing MSYS2 from Chocolatey and using make from C:\tools\msys64\usr\bin. If make isn't installed automatically with MSYS2 you need to install it manually via pacman -S make (as pointed out by @Thad Guidry and @Luke).
If you're using Windows 10, it is built into the Linux subsystem feature. Just launch a Bash prompt (press the Windows key, then type bash and choose "Bash on Ubuntu on Windows"), cd to the directory you want to make and type make.
Note that you might not be able to select your environment. If the build system was created for Cygwin, it might not work in other environments without modifications (The make language is the same, but escaping, path conversion are working differently, $(realpath) fails on Windows paths, DOS bat files are started as shell scripts and many similar issues). If it's from Linux, you might need to use a real Linux or WSL.If the compiler is running on Linux, there is no point in installing make for Windows, because you'll have to run both make and the compiler on Linux. In the same way, if the compiler is running on Windows, WSL won't help, because in that environment you can only execute Linux tools, not Windows executables. It's a bit tricky!
Installation from GnuWin32 or via winget are good and easy options. But I only found make 3.8.1 there. This version lacks the very important option -O, which handles the output correctly when compiling multithreaded.
One solution that may helpful if you want to use the command line emulator cmder. You can install the package installer chocately. First we install chocately in windows command prompt using the following line:
The default install of GnuWin32 on Windows 11 was in Program Files (x86). I setup my environment variables PATH to point to the bin with the make.exe, but for whatever reason this location did not work.
I've been having this problem for a while and can't seem to fix it so after trying with Microsoft Community with little result I decided to try here. Don't really know if it's the place for more user-side problems but I figured I'd give it a try.
Basically, certain applications, seemingly all system ones (at the moment Groove Music, now called "Media Player" on the Store, Movies and TV and Photos), simply can't update to their latest versions because of the error i cited in the title, which happens after a couple seconds of the Store trying to install the app, after completing its download.
The main problem is related to the Photo app though. It originally wouldn't update and would weirdly only display the english language, while the rest of the system is in italian, so I tried resetting it and finally uninstalling it by removing its two main components from Windows' Settings to see if it would yield any result on the Store side.
What I ended up doing is leaving my system with neither a way of rapidly opening and viewing pictures or reinstalling the Photos app, which behaves exactly the same as the other two with the exception i'm trying to get it on my system instead of just updating it.
I already tried resetting the Store's cache and updating it but it didn't work. The troubleshooter also didn't give results and trying to remove and reinstall the Photo's app package through Powershell didn't work too.
An interesting thing is that the Photos app exists and works on my secondary user account, kinda leading to the conclusion my main account is at fault here. I don't understand what could be going on though. Thanks in advance and sorry for the weird spacing but my keyboard is also facing problems lol.
3- The DISM tool will report whether the image is healthy, repairable, or non-repairable. If the image is repairable, you can use the /RestoreHealth (Dism /Online /Cleanup-Image /RestoreHealth) argument to repair the image.
Solution 2
It might be that something went wrong with the update files itself. Clearing the folder where all of the
update files are stored will force Windows Update to download fresh files.
Here how to clear update database cache, reset windows update components to the default setup.
100% fresh install of Windows 10, reinstalled 6 times trying to fix this issue after exhausting every possible solution I could find including the first 3 solutions you posted. The error code 0x80070005 is proving impossible to fix on a non Windows N locked version even after purging 100% of the store and downloads and making sure my computer is completely up to date. I even went as far as to try installing EVERY SINGLE THING in Windows Update to try and see if that possibly helped so I could start narrowing it down but still nothing at all. This issue has been making me extremely angry for weeks now because my Dolby Atmos "enabled" headset can't function without Dolby Atmos. If I try to use it then I get constant screeching from a failure to process non Dolby Atmos encoding. I have to say, I have tried absolutely everything at this point and am losing my mind.
d3342ee215