Windows 10: Installing Win10 on an old Compaq laptop

I have the ISO -- which I got from the MCT.

I will look into restoring Win7 and mounting the ISO.

Will get back -- most likely tomorrow.

 

DVDs are the least reliable means of installing Windows, historically. Maybe the ISO was bad or the DVD didn't get burned 100% correctly. That's why I recommend downloading the ISO file again and using it directly.

 

In the long post I noted that upgrade from 7 was the only way I managed to get the install to complete,

I'd try an upgrade from 7 - it may utilize the drivers that Windows 7 has cached instead of the Windows 10 generics, which are known to cause a lot of problems, being installed in place of working, older drivers.

That's why I made the long post - I've seen a lot of other posts concerning problem installs on older laptops, and 100% CPU use/overheating/stalling during various stages of setup is a common and tricky problem probably due to chipset drivers missing.

One thing that many folk don't realize is that during much of the setup process it can be observed, either by alt-tabbing to the underlying OS being upgraded from and using the Task Manager to see what's happening in terms of resources and processes, or during WinPE parts of the upgrade using Shift+F10 to get the command prompt, and then using Task Manager as above. You can even use Technet Sysinternals Process Explorer if you have it available on the hard drive.

Task manager can browse to an installed 7-ZipFM and open it as a file manager if you want to see what's going onto the disk, and notepad and regedit are also available.

Mark, you omit to mention how much memory you have installed, unless I've missed it - at least 2GB, I'd hope.

 

So, I wonder, @Fafhrd....

First of all, can you DISM /export-driver in Windows 7? So, you get the Windows 7 drivers in a folder, we'll say DriversW7. Then you run the Windows 10 setup.exe with:

E:\setup.exe /installdrivers e:\DriversW7

Because notice this output from setup.exe /? from Windows 10:





I wonder if that would be the way to accomplish the clean install?

 

It may be a possibility, haven't tried anything like it - but I know that with older Intel systems, the right chipset drivers applied post-install make a lot of difference to CPU behaviour, from enabling sleep etc, to cooling the system down. If they could be installed at setup time it would be ideal.

In the Windows Embedded Standard 7 systems you could create an answer file based on driver information obtained from running TAP.exe on the old system and taking the xml from the Panther directory created to feed into the system builder, then automagically all the drivers would be added to your new build. The extensive Panther folder files created for Windows 10 are typically obfuscated Microsoft stuff, and so much of it!
Of course the WDDM model is so much more strongly enforced in Windows 10 than it was in 7.

However, the problem is probably a "design feature" by Microsoft - they don't want older hardware to be used for their new OSs any more than their OEM partners do - they want us to buy new kit, especially obsolescent-when-purchased mobile or portable systems. That's why the demands of WinPE 10 are much greater that those of WinPE 8.1:

Windows 10 Recovery Tools - Bootable Rescue Disk - Page 36 - Windows 10 Forums

Note the shared system video memory had gone from 256MB to 1GB for the basic display adapter from 8.1 to 10 - for Win PE, when WinPE runs as a Ramdisk - why?

I suppose I am saying that the problem is with WinPE/Setup not having the right drivers available for WinPE to run properly, let alone get the main Windows 10 drivers right. I'd like to use the windows 8 WAIK to run the setup, but there's changes in the Install.wim of 10 - it cannot be applied directly to an empty volume and run from that like was possible with 7 and 8.

Windows 10 on this Acer Laptop installed leaving an almost unusable windows 10 with continuous 100% CPU usage due to IRQ conflicts on shared IRQs between modem, Wireless adapter, ethernet adapter, and the basic display driver on the unsupported Intel integrated Graphics module and I haven't seen that since the bad-old-days of Windows 9x. Once I had disabled the non-essentials (modem, wireless) I could use the laptop.

Late here and I need to get up early tomorrow - continue later.

As you may understand, having struggled to manage to get Windows 10 running on this almost hopelessly underspecced test machine, I am loath to wipe it to try out another possible failure *Smile, but I will do it when I have some free time. Using the switches in setup are certainly one way to go. Another may be to build a franken-install.wim or esd for Windows 10 with the Windows 8 boot.wim in place of the Windows 10 one.

 

OK, understand. I'll get back after the restore and trying the install with the mounted ISO.

 

You'll need to use a third party tool to mount the iso within Windows 7 - it does not allow native mounting of virtual CD/DVD-roms from Iso Files.

Just one additional 3rd party process using up resources unnecessarily.

Better to extract the files from the Iso\sources folder to a folder on the hard drive, and setup from there. You could use 7-zip to extract the sources folder from the iso - you need nothing else to run the setup contained in the folder.

 

Well ... that was an exercise in futility!

Should have run the in-place upgrade FIRST -- because when I finally got around to doing it, the update tool complained and said Win10 can't run on the Compax due to the "NX problem".

Had I run the upgrade first, I would have saved a lot of trouble.

 

hmm. *Wink

 

You're right -- I should have checked ahead of time, and in your second post, you did say that doing an upgrade was the only thing that worked. I was just hoping to avoid the Upgrade because that totally trashed another laptop, and in that case, only a clean-install worked.

 

I was trying to give the benefit of my experiences, to possibly save you from grief and wasting time, but the only way to really learn is to make your own mistakes and learn from them, since YMMV.

There are apparently ways to circumvent the NX problem , I've read, but that seems, to me, to be "an exercise in futility" in an OS that's designed to be upgraded over time and again.

My specs show my Pentium 4 that happily runs Windows 10, but many P4s do not have the NX feature.

There are several threads here that document folks' experience with Windows 10 on "old hardware" or "old Computer(s)" for those that wish to experiment to pick up pointers and ideas.

NavyLCDR has made some interesting suggestions which I may try out in due course, probably when Redstone long term version is released, if Microsoft has not made the setup process more stringent by then! *Sad

 

I have a tablet that needs extra drivers for the touchscreen and screen rotation to work so next time I need to re-install Windows on it I am going to try to figure out a way to get those drivers to load either in WinPE to do the install from, or at least during initial install. As it is now, I am stuck with having the keyboard connected (which is for landscape mode) and then having to sit the entire assembly up sideways in profile mode to install the touchscreen and screen rotation drivers.

 

Dism can be used to inject drivers for an offline image:
Add and Remove Drivers to an Offline Windows Image
Also into the boot.wim (WinPE image)
How To: Use DISM to Manually Inject Drivers int... | Ivanti User Community