Windows 10: Win 10 Workable on old hardware?

I own a Toshiba NB100-10Y (netbook ) with following hardware:
CPU: Intel(R) Atom(TM) CPU N270@1.60GHz
RAM: 798MHz 2GB RAM

Is this:
1. enough to clean install Window 10 Home Edition 32-bit and
2. will it be workable?

thanks for any anser, gabriël

:)

 

Printer and PC won't talk

First suggestion does not work. 2nd suggestion: after clicking properties there is no 'compatibility' tab and I shouldn't be looking in win 7/8 as I'm now running win 10.

Need a workable idea very badly. T hNKS.

 

Quiet Hours

The search box brings NO RESULTS!!! - Win 10 is, quite frankly, appalling.

Even in settings search box there is ............... nothing found.

I have now spent hours pissing around making Win 10 workable, and it's still abyssmal. Do Microsoft see these exchanges?

 

I would really doubt it since your system was originally delivered with Win XP. Since its so old I'm sure Toshiba will not provide W10 drivers for things like the "Touch pad", "USB Ports" etc.

 

I was afraid of that myself.
thank you for that confirmation.

 

I upgraded an older Lenovo laptop with a bit higher specs than yours which didn't have any drivers provided by Lenovo. The generic Windows 10 drivers worked and the machine is a bit snappier with 10 than 7.

I created an Acronis image prior to upgrading just in case.

 

I have installed W10 on PCs very similar to yours. Just do as cyberSAR says (make a partition backup first).

 

The Atom processor is likely to be OK, but the graphics may be a challenge, since the latest drivers may be from Windows Vista. see the second from last comment here:
How does Windows 10 run on older hardware? : windows

 

I tried to install 10 on an old laptop with 2gb of ram but it would not even install.

 

It can be a challenge, but those who have managed to install it seem to be in agreement, me included, that 10 runs as well as the original XP the machines were designed for on these old systems with 2GB.

The hurdles to overcome are no compatible chipset and graphics drivers, power management issues, and CPU overheating during installation, and worn out laptop hardware, like batteries and optical drives. The fan and cooling vents need to be properly cleaned in advance, and additional fan cooling is helpful during setup. Add to this the potential for IRQ conflicts from old unused legacy hardware like modems, infrared and pcmcia cards, and because these problems have never been tested for at Redmond, the lack of error codes these problems throw up during setup. - "Something went wrong" and " Something happened"fall into this category.

Things to do in preparation include remove the battery, plug in the power adapter, remove the internal wifi card, turn off and unplug the network cable, upgrade from a fully updated x86 Windows 7 where possible with older hardware devices disabled if not possible to remove them. Otherwise clean install, but this will use only generic drivers, rather than those scanned for in the Panther setuplogs.

Download and extract the x86 setup source files onto the hard disk, and avoid having any USB or any external devices - scanners, printers etc., - connected. Run the GatherOSState program from the sources folder and keep the genuineticket.xml file safe. Go into the BIOS and remove any extra memory preallocation for onboard graphics - just allow the bare minimum required - and make sure that the first hard drive is the default boot drive.

Set the locale to USA, and if you can, keyboard and language and time for the installation, so that number formats/time differences don't get in the way, and do a clean boot (Msconfig) without antivirus or any 3rd party software software or customizations running - disable touchpad enhancement software, and just allow Ps/2 mouse.

Finally run the setup upgrade as administrator, and prepare for a long patient wait...

 

Windows 10 partition/drive missing after merging - Windows 10 Forums

 

I finally took the plunge and did a clean install on my netbook toshiba.
It isn't a speed monster but it is totally workable; am ver plesed with it.

 

Hi there
actually as an interesting exercise you could install W10 (32 bit) on a VM with that machine - use VBOX or an old version of vmware player (32 bit version).

XP itself doesn't use a lot of RAM so you could allocate 1GB RAM to your Windows 10 Virtual machine.

Performance won't be stellar but it would give you a taste to see if you like W10.

Cheers
jimbo