05-13-2020, 06:08 AM
Thanks for the reply and thanks for the help... I had you with coffee this morning. It's been a long day.
I've another question. It has come up maybe a person ought to keep Windows 7. It has it's uses... just shouldn't be run on the internet, or even connected to it. Apparently there are lots of holes in it since the support shut down in January.
I actually put Windows to use tonight. A person can search into 'partitions' > 'Create and format hard disk partitions' > rt. clk. on 'Disk 0' in the graphic of disk partitions and see a choice of 'Convert to GPT Disk'... meaning the HDD is MBR. So, after too much knocking around the net I know definitely what partitioning form I should use (middle choice, Arch Wiki link in first post)... /, swap, /home.
So IF, in the end, Windows stays, I know to use Windows Shrink to gain the unallocated space needed for Linux Lite. The existing Windows partition structure is /sda1, 2, 3... 1.46GB Recovery (no actions allowed)... 448.66GB C: Boot, Page File, Crash Dump (many actions allowed)... 14.66GB Primary 'no name' (only 'delete' action active in list). /sda3 is, I believe, the data/function a person would use to Recover. We've got a USB working copy of it.
I applied a 1000MB shrink of /sda2... the C: Drive... and it went fine. It is sitting at the end of /sda2 with sda/3 afterwards. I'm thinking maybe Windows wants to be all grouped up. I'm pretty sure I've got (or can re find) info on moving partitions using Windows. I know it can be done with GPartEd. But is it really necessary? IF Windows 7 stays, can Windows live with a lump of Linux in between and /sda3 at disk end?
I know the first Linux partition needs to be 'extended' with /, swap, /home as logicals... /sda4... then 5, 6, 7.
Always before with Win/Linux dual boots I've had Linux after all of Windows. It just worked out that way, really, but I'm thinking there may be a function logic in not having a Window partition hanging out at disk end.
Some views would be appreciated.
Mike
Just to say... The way I'd deal with Shrink and push /sda3 to disk end would be to make the shrink then reboot, run a disk/system check, reboot another time or two... just to make sure Windows was well aware of form and functional with it.
I've another question. It has come up maybe a person ought to keep Windows 7. It has it's uses... just shouldn't be run on the internet, or even connected to it. Apparently there are lots of holes in it since the support shut down in January.
I actually put Windows to use tonight. A person can search into 'partitions' > 'Create and format hard disk partitions' > rt. clk. on 'Disk 0' in the graphic of disk partitions and see a choice of 'Convert to GPT Disk'... meaning the HDD is MBR. So, after too much knocking around the net I know definitely what partitioning form I should use (middle choice, Arch Wiki link in first post)... /, swap, /home.
So IF, in the end, Windows stays, I know to use Windows Shrink to gain the unallocated space needed for Linux Lite. The existing Windows partition structure is /sda1, 2, 3... 1.46GB Recovery (no actions allowed)... 448.66GB C: Boot, Page File, Crash Dump (many actions allowed)... 14.66GB Primary 'no name' (only 'delete' action active in list). /sda3 is, I believe, the data/function a person would use to Recover. We've got a USB working copy of it.
I applied a 1000MB shrink of /sda2... the C: Drive... and it went fine. It is sitting at the end of /sda2 with sda/3 afterwards. I'm thinking maybe Windows wants to be all grouped up. I'm pretty sure I've got (or can re find) info on moving partitions using Windows. I know it can be done with GPartEd. But is it really necessary? IF Windows 7 stays, can Windows live with a lump of Linux in between and /sda3 at disk end?
I know the first Linux partition needs to be 'extended' with /, swap, /home as logicals... /sda4... then 5, 6, 7.
Always before with Win/Linux dual boots I've had Linux after all of Windows. It just worked out that way, really, but I'm thinking there may be a function logic in not having a Window partition hanging out at disk end.
Some views would be appreciated.
Mike
Just to say... The way I'd deal with Shrink and push /sda3 to disk end would be to make the shrink then reboot, run a disk/system check, reboot another time or two... just to make sure Windows was well aware of form and functional with it.