Windows 10: Is there a point in creating an image of your SSD and HD separately?

We used to be able to use Config.sys to make a VDisk and assign it a drive letter.

You do the current equivalent.

Then you start to install Windows on that drive letter.

Then install your programs.

When done you use an imaging program to backup that drive.

On a restart you restore that drive.

That is a clumsy way, I hope the new Fall Update Pro version has this more streamlined. That way will still need a memory copy from the drive to main memory. I'm hoping the new code will avoid that.

With an NVRAM, you would not need to restore. If a motherboard had support for backup power on the memory modules one could avoid a memory wipe.

I don't know what will be in that new fall update, but the promised non-volatile memory support seems to be a big deal in that new version.

 

If you want to go back far enough, I used to have a copy of Intel's 1970's CPU pricelist.
If I recall, the 8080 had a 10 millisecond cycle time and cost over $100 and it required a whole board full of support chips (memory controller, etc.).
That's when I decided to buy an Atari.

 

I kept my Atari 1040St well into 486 era. Used it mostly for Draphics 3D CAD which made files compatible with AutoCad but was much easier to use and specially much cheaper.

 

All threads, even in highly structured forums like this one, all seem subject to the inevitable decay of entropy.

As just pointed out in this very post.

 

That's because we are all waiting for new build.

 

I meant to self-refer to my post, but you just improved on the observation!

And I continue the marathon towards madness.