MX Linux Forum

Posted: **Mon Dec 16, 2024 9:44 am**

Hello,
I have an issue with linux installation
in het video here on how to create a post it says that quick system info is in the menu, I see a tab below with options, but I can't click it, I use firefox, (also tryed on chrome)
therefore I post here some info, and will update if I find out how to post it correctly:
Dell Vostro 3559
Operating System
Windows 10 Home 64-bit
CPU
Intel Core i5 @ 2.30GHz 62 °C
Skylake-U/Y 14nm Technology
RAM
16,0GB Dual-Channel DDR3 @ 798MHz (11-11-11-28)
Motherboard
Dell Inc. 047TR1 (U3E1)
Graphics
Generic PnP Monitor (1366x768@60Hz)
Intel HD Graphics 520 (Dell)
Storage
465GB Seagate ST500LT012-1DG142 (SATA ) 27 °C
465GB TOSHIBA External USB 3.0 USB Device (USB (SATA) ) 26 °C
Optical Drives
PLDS DVD+-RW DU-8A5LH

I downloaded mx linus two times:
1 https://sourceforge.net/projects/mx-lin ... o/download
2 https://sourceforge.net/projects/mx-lin ... o/download

I donwloade rufus: with download one I got the message: withdraw bootloader detected (is this important?)
2 I canot select this in rufus

Then I try to test linux on my system with a live system, but got the message as submitted

I hope you can help :) Thanx

Posted: **Mon Dec 16, 2024 11:03 am**

newbee85 wrote: Mon Dec 16, 2024 9:44 am Hello,
I have an issue with linux installation
in het video here on how to create a post it says that quick system info is in the menu, I see a tab below with options, but I can't click it, I use firefox, (also tryed on chrome)
therefore I post here some info, and will update if I find out how to post it correctly:

Not sure haven't used windows and Rufus for a while.
But in case they offer to use "ISO/dump" mode, I'd prefer this one.
Also BalenaEtcher is writing ISO-in dump mode onto the USB.
Not sure why you trying to use an 3 month old ISO, where we have a brand new
official ISO snapshot available: MX-23.4_December_KDE.iso.
https://sourceforge.net/projects/mx-lin ... Snapshots/
Also don't forget to verify the downloaded ISO, either with the sha512 checksum file or even better with the provided signature file.

Posted: **Mon Dec 16, 2024 1:39 pm**

fehlix wrote: Mon Dec 16, 2024 11:03 am
newbee85 wrote: Mon Dec 16, 2024 9:44 am
Also don't forget to verify the downloaded ISO, either with the sha512 checksum file or even better with the provided signature file.
how do you do you do that?

maybe I need to ad: like my nickname suggest, I'm completely new to linux

I will try again with the link you give

Posted: **Mon Dec 16, 2024 6:07 pm**

@newbee85
I suggest that you follow this guide to dual booting created by our own @FullScale4Me
https://fullscale4me.com/Dual-Boot-MX-L ... -Guide.pdf

Posted: **Mon Dec 16, 2024 6:33 pm**

newbee85 wrote: Mon Dec 16, 2024 1:39 pm
fehlix wrote: Mon Dec 16, 2024 11:03 am Also don't forget to verify the downloaded ISO, either with the sha512 checksum file or even better with the provided signature file.
how do you do you do that?

In case you don't have Linux already, you can verify the checksums provided this way on Windows:
Probably easiest with an example:
* Download both the ISO and the checksum file, for official snapshot iso's we use sha512 checksums:

Code: Select all

iso file :	MX-23.4_December_x64.iso
sha512sum:	MX-23.4_December_x64.iso.sha512

* Open within the download folder where both files have been saved a "Terminal"/"Commandline", suggest to open the PowerShell terminal:
On the PS-prompt:
First way, using build-in tool "certutil" with this command:

Code: Select all

certutil -hashfile .\MX-23.4_December_x64.iso SHA512

which should calculate and display a long checksum like this:

Code: Select all

SHA512-Hash of .\MX-23.4_December_x64.iso:
6e975cdde8bb4fbb96d6dab4050384617ddd9917ea754b6d47fc6d4caef5b2d46edef65d4f9ac6c13f93df3629b7a3a8cf506fd5b2ff7009a6e55e125e586709

alternatively use a powershell function to calculate the hash-sum this way:

Code: Select all

(Get-FileHash .\MX-23.4_December_x64.iso -Algorithm SHA512).hash
6E975CDDE8BB4FBB96D6DAB4050384617DDD9917EA754B6D47FC6D4CAEF5B2D46EDEF65D4F9AC6C13F93DF3629B7A3A8CF506FD5B2FF7009A6E55E125E586709

Now display the content of the downloaded .sha512 file with "type" command:

Code: Select all

type MX-23.4_December_x64.iso.sha512
6e975cdde8bb4fbb96d6dab4050384617ddd9917ea754b6d47fc6d4caef5b2d46edef65d4f9ac6c13f93df3629b7a3a8cf506fd5b2ff7009a6e55e125e586709  MX-23.4_December_x64.iso

You can now manually /visually compare this long string, which should be identical.

Alternatively instead of trying to compare those long checksum strings, let PowerShell do this with:

Code: Select all

(Get-FileHash .\MX-23.4_December_x64.iso -Algorithm SHA512).hash -eq "6e975cdde8bb4fbb96d6dab4050384617ddd9917ea754b6d47fc6d4caef5b2d46edef65d4f9ac6c13f93df3629b7a3a8cf506fd5b2ff7009a6e55e125e586709"
True

Both checksum - the calculated and the provided would match and you get "True".
You copy/paste from the output of the "type" command (Click the checksum to select, Enter to copy, and Right-click to paste.)

In addition to the checksum verification, there are also pgp/gpg/GnuPG-signature files provide to download.
To perform a gpg-sIgnature verification of the iso-file on WIndows some tools would need to be installed as Windows does not
provide a build-in tool do do this. E.g use Gpg4win https://www.gpg4win.org/

On Linux
To perform checksum verification run the tools sha512sum like this:

Code: Select all

sha512sum --check MX-23.4_December_x64.iso.sha512
MX-23.4_December_x64.iso: OK

A signature verification on MX Linux, where we have gpgv verifier tool installed looks like this:
using this way:
gpgv sig-file followed by iso-file

Code: Select all

gpgv  MX-23.4_December_x64.iso.sig  MX-23.4_December_x64.iso

and would display this

Code: Select all

gpgv: Signature made Sun Dec 15 17:38:41 2024 EST
gpgv:                using RSA key F27753A18E92E3937E6335E770938C780679EE98
gpgv: Good signature from "Adrian <adrian@mxlinux.org>"

but only if the file would match to the signature provided.
Also the above signature shows that the "signer" is really the one we know and who has generated the snapshot.
You would first get the signers public-signature key imported into the gpg keyring.
More about this gpg-signaure file verification for MX Linux and how to import the public signing key
here at the MX Linux Wiki https://mxlinux.org/wiki/system/signed-iso-files/
HTH

Posted: **Tue Dec 17, 2024 1:44 am**

fehlix wrote: Mon Dec 16, 2024 6:33 pm In case you don't have Linux already, you can verify the checksums provided this way on Windows:
Probably easiest with an example:
* Download both the ISO and the checksum file, for official snapshot iso's we use sha512 checksums:
Code: Select all
iso file :	MX-23.4_December_x64.iso
sha512sum:	MX-23.4_December_x64.iso.sha512

This is an excellent tutorial for verifying MX downloads. There's also checksums for the official ISOs on the website.

One of the things I noticed is that when running recent versions of Rufus (I tested this with v4.6-portable), you can have Rufus read and compute multiple checksums automatically. By clicking the small circle with a checkmark inside it that is to the left of the "SELECT" button, Rufus will compute the MD5, SHA-1, SHA-256, and SHA-512 checksums of the selected file.

Pick one of these, such as the SHA-256 alphanumeric string, and compare it to the SHA-256 of the ISO you've downloaded and ensure that they match. If they don't, your USB won't work as expected.

Posted: **Tue Dec 17, 2024 2:33 am**

It seems like these are different ways to go?
I started this one: https://fullscale4me.com/Dual-Boot-MX-L ... -Guide.pdf
And it says:
Consider implementing a data sharing area between Windows and MX Linux when you are
setting up Dual Boot. Use FAT32, ExFAT or NTFS format. Most USB drive come as FAT32

I have no idea what that is about?

Posted: **Tue Dec 17, 2024 3:03 am**

newbee85 wrote: Tue Dec 17, 2024 2:33 am I started this one: https://fullscale4me.com/Dual-Boot-MX-L ... -Guide.pdf
And it says:
Consider implementing a data sharing area between Windows and MX Linux when you are
setting up Dual Boot. Use FAT32, ExFAT or NTFS format. Most USB drive come as FAT32

I have no idea what that is about?

FullScale4Me's guide quite literally gives three explanations of what that's about. The section you cited, in full, reads:

Data Sharing area between Windows & Linux

Consider implementing a data sharing area between Windows and MX Linux when you are setting up Dual Boot. Use FAT32, ExFAT or NTFS format. Most USB drive come as FAT32.

Suggested name: MyData

• Create a 3rd partition that is visible to both after the Windows disk partition.
• Setup a Cloud Storage account: Google Drive, OneDrive, DropBox, Mega, etc.
• Purchase an external Thumb drive or SSD hard drive caddy to exchange files.

If you don't intend to transfer Windows files to the Linux partition or transfer Linux files to the Windows partition, then you can ignore this step. You can set up cloud storage later if you want.

EDIT: typo

Posted: **Tue Dec 17, 2024 3:56 am**

ok, I went to the next step, iff i type BitLocker or manage BitLocker in the search box it only find results on the web,so I guess I don't have it?
the other step is backup windows keys, : they mean the windows product keys? I make a backup of windows, so I guess it is not needed, next step is: Shrink Windows C drive partition, I have enough space, so I guess that is not needed?

Posted: **Tue Dec 17, 2024 4:48 am**

newbee85 wrote: Tue Dec 17, 2024 3:56 am iff i type BitLocker or manage BitLocker in the search box it only find results on the web,so I guess I don't have it?

Steps to disable BitLocker are in FullScale4Me's guide under section 3.4. You mentioned you're running Windows 10 Home, so this section is relevant to you:

Dual Boot: MX Linux & Windows – Installation Guide wrote: 3.4 Disable BitLocker
BitLocker must be Disabled before doing any Hard Drive reconfiguration tasks.

• Windows 11 Pro – BitLocker is enabled and should be disabled.
• Windows 11 Home – Microsoft has started force enabling BitLocker (as of 2Q 2024).
• Windows 10 – at the time of writing has BitLocker is not enabled.

If you want to know, precisely, the BitLocker status of your Windows volume, you can run "manage-bde -status" from an elevated command prompt and check the Protection Status. There is ample documentation online on other ways to verify this.

newbee85 wrote: Tue Dec 17, 2024 3:56 am next step is: Shrink Windows C drive partition, I have enough space, so I guess that is not needed?

Be specific here. What, precisely, does "enough space" mean? You know from section 3.71 of the guide what the steps are to add a new partition for installing MX Linux. FullScale4Me has even included screenshots so you can compare your disk layout against the example in the guide. You haven't given any information about your partitions, so I can't guess if you have enough unallocated space on the disk to add a new partition or not. FullScale[0] is clear on how much free space a hard disk needs to have:

Dual Boot: MX Linux & Windows – Installation Guide wrote: 3.7 Freeing space for Linux on the Windows Drive C
MX Linux needs a minimum of 8.5 Gb of free space and preferably 20 Gb is recommended.

I want to be very clear here. This does not mean you need 20 gigs of free space on your Windows C: drive. It means you need your Windows C: drive to be at least 20 gigs smaller than the total capacity of the hard disk.

In other words, if the total capacity of the hard disk is 465 GB, the C: drive can't be larger than about 440 GB. Dual-booting means installing a new OS alongside Windows, not inside Windows. You are going to create that space so that the MX Linux installer can find it.

[0] I've got to start abbreviating this. Apologies.

Posted: **Tue Dec 17, 2024 7:31 am**

@newbee85 wrote:

next step is: Shrink Windows C drive partition, I have enough space, so I guess that is not needed?

If your intention is to install MX on to your external Toshiba HDD, then you should rethink your plan. It can be done, but it's not something a newbie to Linux should attempt.
This leaves your Seagate internal drive as the target and it's absolutely essential that you use Win 10's disk management utility to shrink it's partition to create the space for MX. If you don't, Win 10 will still consider that space to be it's own and will overwrite it at the first opportunity.
Take this to heart.
Your biggest hurdle to learning Linux will be unlearning Windows, but it's well worth the effort.

Posted: **Tue Dec 17, 2024 6:30 pm**

My new quote about Dual Boot:

Dual Boot is easy to setup using the short/concise guides found on the Internet .....until it's not!
FullScale4Me, December 17, 2024

Two primary reasons for this are: 1) PC makers interpret the UEFI standard and implement their interpretation of what it says.
2) Windows 11 is a 'moving target' of sorts. Many of my edits to my guide were necessitated due to Microsoft's changes.

Early on I found the need for an outline to help the newbies and to ground others so minor sub-topics were not skipped to cause future discussions here. Thus

2.0 Summary of How-To Steps:

◦ Windows settings changes:

▪ Create a Windows 'Recovery Disk' - can be DVD or USB.
▪ Backup your BitLocker and Windows Keys.
▪ Disable BitLocker in Windows (if enabled).
▪ Disable Windows Fast Startup.
▪ Defragment Hard Drive.
▪ Shrink Windows C drive partition.
▪ Create the new partition for MX Linux.
• Create a (optional) data sharing (Windows ←--> Linux) partition.

◦ PC Firmware settings changes:

▪ Set a Supervisor/Admin password (if needed).
▪ Turn off CSM/Legacy/BIOS Boot. May exist in two (or more) places.
▪ Change SATA controller mode to 'AHCI' (from RAID/RST/Optane).
▪ Disable/Turn OFF Secure Boot.
▪ Change the Boot Order to USB drive first (Disks).
▪ Fast Boot - Turn off/set to ‘Thorough’ if present.
▪ Enable/turn on USB Boot ability (off by default on some PCs).

◦ Install MX Linux.

▪ Prepare MX boot USB – GPT preferred.
▪ Install MX Linux on the new partitions.
▪ Reboot.

A newbie-level user should print that page and use it as a check list; both for personal research and to ensure all steps were performed.

As it stands 'chapter' 2 (above) assumes a single disk is in use. Elsewhere 2 disks are recommended (both in my guide and a distro that sounds like something you would use for a bad breath issue). I'll leave the creation of 'chapter 2b' for my edits in or before January 2025.

edit: feedback

Posted: **Tue Dec 17, 2024 7:34 pm**

FullScale4Me wrote: Tue Dec 17, 2024 6:30 pm Early on I found the need for an outline to help the newbies and to ground others so minor sub-topics were not skipped to cause future discussions here.

Thanks for compiling and maintaining this guide. It's helped a bunch of people since you've published it and serves as a nice counterpoint to the official MX user manual.

I am wondering, however, if it wouldn't be useful to skip future discussions here by including shorter, simpler instructions for some of the minor subtopics. As in, "Run 'manage-bde -off C:' into an admin command prompt." This is an unambiguous statement and users don't necessarily even need to understand BitLocker syntax in order to copy and paste it.

In the end, disabling BitLocker and Fast Boot create discussions here that often skew towards the "how do I do that?" side rather than the more esoteric questions about startup sequences and bootloaders that you'd typically consider to be a discussion. A short and sweet "just run this" command in the guide may cut down on the confusion.

Posted: **Tue Dec 17, 2024 7:55 pm**

@DukeComposed
[0] I've got to start abbreviating this. Apologies.

I dont think you should be abbreviating those extra words they can make a world of difference between crystal clear and clear as mud. Personally I like a good read of info.

Posted: **Tue Dec 17, 2024 8:21 pm**

artytux wrote: Tue Dec 17, 2024 7:55 pm I dont think you should be abbreviating those extra words

You're really bothered by skipping "4Me" a few times?

Posted: **Tue Dec 17, 2024 8:24 pm**

DukeComposed wrote: Tue Dec 17, 2024 8:21 pm
artytux wrote: Tue Dec 17, 2024 7:55 pm I dont think you should be abbreviating those extra words
You're really bothered by skipping "4Me" a few times?

Must be an American saying - Dunno

Posted: **Tue Dec 17, 2024 9:05 pm**

FullScale4Me wrote: Tue Dec 17, 2024 6:30 pm ▪ Run MX Boot Repair from Live USB.
Run ‘Repair GRUB configuration file’ and close the program.
▪ Reset the ‘UEFI Boot Order’ with MX Boot Options. Reboot.

Not sure, about those two, at least some explanation, why a ‘Repair GRUB configuration file’
may be needed. It may be that it was needed in the past, but I think that WIndows entry in the grub menu should be displayed normally now.
Also Reset ‘UEFI Boot Order’ is probably in most cases not needed, b/c the installer will set MX UEFI entry onto the first position
within the UEFI boot order list. Exception may be mentioned and LiveUSB would be of help.

Posted: **Wed Dec 18, 2024 12:34 am**

fehlix wrote: Tue Dec 17, 2024 9:05 pm
FullScale4Me wrote: Tue Dec 17, 2024 6:30 pm ▪ Run MX Boot Repair from Live USB.
Run ‘Repair GRUB configuration file’ and close the program.
▪ Reset the ‘UEFI Boot Order’ with MX Boot Options. Reboot.
Not sure, about those two, at least some explanation, why a ‘Repair GRUB configuration file’
may be needed. It may have been in the past needed, but I think WIndows entry in Grub menu,
should now normaly show up.
Also Reset ‘UEFI Boot Order’ is probably in most cases not needed, b/c the installer will set MX UEFI entry onto the first position
within the UEFI boot order list. Exception may be mentioned and LiveUSB would be of help.

Thanks for catching that. I just removed it from my local copy. I have a few pending edits yet to add. I need good proofreaders! A change in 2023 removed the need to do at least one of those steps.

Some PC motherboards have an additional layer of security (Windows/Custom) that prevents adding new NVram entries and/or saving any non-Microsoft path. My how-to covers this, but no MX Tool is needed to perform the changes.

Posted: **Wed Dec 18, 2024 11:44 am**

Thanx for all the help, I just understood there is a possibility of experimenting with linux within windows, with virtualbox,https://www.virtualbox.org/wiki/Downloads I will try that first, when I succeed, I don't need dual boot, that would help,so maybe I will come back to this later

Posted: **Wed Dec 18, 2024 12:07 pm**

newbee85 wrote: Wed Dec 18, 2024 11:44 am Thanx for all the help, I just understood there is a possibility of experimenting with linux within windows, with virtualbox,https://www.virtualbox.org/wiki/Downloads I will try that first, when I succeed, I don't need dual boot, that would help,so maybe I will come back to this later

VirtualBox is certainly one way to try it out, but also to keep longer. Another way would be to generate a LiveUSB stick and with enabled persistence kind of a "MX Linux" on a stick. where data and any changes can be stored, no installation on hard-drive needed.

Posted: **Thu Dec 19, 2024 2:23 am**

DukeComposed wrote: Tue Dec 17, 2024 7:34 pm
FullScale4Me wrote: Tue Dec 17, 2024 6:30 pm Early on I found the need for an outline to help the newbies and to ground others so minor sub-topics were not skipped to cause future discussions here.
Thanks for compiling and maintaining this guide. It's helped a bunch of people since you've published it and serves as a nice counterpoint to the official MX user manual.

I am wondering, however, if it wouldn't be useful to skip future discussions here by including shorter, simpler instructions for some of the minor subtopics. As in, "Run 'manage-bde -off C:' into an admin command prompt." This is an unambiguous statement and users don't necessarily even need to understand BitLocker syntax in order to copy and paste it.

In the end, disabling BitLocker and Fast Boot create discussions here that often skew towards the "how do I do that?" side rather than the more esoteric questions about startup sequences and bootloaders that you'd typically consider to be a discussion. A short and sweet "just run this" command in the guide may cut down on the confusion.

Thank you very much for that sage advice! I did collapse the SATA controller issue (has to be in 'AHCI mode') a lot. It all boils down to what works/stops working in Windows 10 and 11. In the latter, MicroSoft's 'Control Panel reconstruction' has been an ongoing work that borks the where to go 'to get 'er done' continually in 2023-24.

I realize some newbies do get frazzled when they see 33 pages. I've added a bit in the beginning of it warning that the length is attributed to coverage of edge cases (>9 pages). Perhaps I need to also call out that it's (profusely at times) illustrated?

Dual Boot is easy to setup using the short/concise guides found on the Internet.....until it's not! FullScale4Me, December 17, 2024.

It’s likely 1/3 or more of this guide is not used by most people. A lot of time in editing it has been adding fine detail for edge cases for one lesser brand or possibly one difficult model.

The flip side is the security paranoid types never click the link - OMG a PDF file! They just balloon the Q&A here to 3 or more pages in their 'help me' threads.

I'll do more of the collapse (& cutting) when I add the second outline for dual disk drive dual boot. It needs some clarity as dual hard drive is the 'preferred' advice offered in the forums of Ubuntu based distros.

‘Dual Boot: MX Linux & Windows-Installation Guide‘ updated December 19, 2024

Posted: **Thu Dec 19, 2024 2:55 am**

@FullScale4Me

Posted: **Thu Dec 19, 2024 2:56 am**

FullScale4Me wrote: Thu Dec 19, 2024 2:23 am I did collapse the SATA controller issue (has to be in 'AHCI mode') a lot. It all boils down to what works/stops working in Windows 10 and 11. In the latter, MicroSoft's 'Control Panel reconstruction' has been an ongoing work that borks the where to go 'to get 'er done' continually in 2023-24.

Writing technical documentation is a double-edged sword and it always will be. For every user who complains "Gee, this guide looks nice, but it's just a bunch of commands... it doesn't explain what to do or whyyyyy" you'll have another user come along and complain "Welp,there's a lot of steps here explaining what to do... but nothing here tells me how to do it or what to type".

Both of these categories of users are obtuse and each will fail to gain enlightenment in his own unique way. You can't win 'em all.

In the case of this thread, OP seemed wildly unprepared for the responsibilities of resizing a Windows system partition and disabling BitLocker, two things that might not be difficult for an experienced Windows user, but which are downright incomprehensible when you are fundamentally unclear on some core computing concepts. The guide did not help him.

This is the burden of being an author. Writing something like "Just run manage-bde -off" may help more people, but there's a good chance a lot of readers won't understand what they're doing, or why. And you'll get complaints about it. Or, if you spend time explaining what BitLocker is, why it's used, and why it needs to be turned off in order to boot something else, there's a good chance a lot of readers won't pay attention to a word of it and feel like they've gotten lost. And you'll get complaints about it. You can't win 'em all.

When I am king, the dual-booting instructions will read: "How to dual-boot: Install Windows. Make enough unallocated space on your disk for a Linux install. Create a new partition from the unallocated space and install Linux into the new partition. Install a bootloader that can boot Windows and Linux. If any of these steps are unclear to you, you are not ready to dual-boot." I am a lenient but uncompromising king.

The trick to implementing a good set of instructions, which I will again say you've already done, is providing clarity without merely providing rote commands to run. It's a guide meant to be read and understood, not a dual-booting script. You really can't prevent people from trying to punch above their weight. You can only try to help them realize they're in the wrong fight before they get hurt.

Posted: **Thu Dec 19, 2024 3:03 am**

@DukeComposed

Just checked-out your tag-line:

http://www.catb.org/~esr/faqs/smart-questions.html

Awesome Stuff

Thanks for your tireless efforts

Posted: **Thu Dec 19, 2024 9:01 pm**

First off thank you to @fehlix @j2mcgreg @DukeComposed @operadude for the feedback given.

I just finished a long edit session on my Dual Boot: MX Linux & Windows-Installation Guide after last night's quick edit (fehlix's suggestions) was uploaded to my website.

I cut down on the depth of the whys when it felt like it was or was heading to being a techie history lesson. I thinned out greatly the Fast Startup (aka hibernation) and BitLocker sections per suggestion from DukeComposed ... The rest were lightened a bit. A few sections were moved to the end as they were supplemental sub-topics that were not prerequisite in nature. The page count dropped from 31 to 21 pages. My retesting of the sub-items showed once again Microsoft had made some changes. The good part of it was the how-to differences between Windows 10/11 had dissolved; more unneeded text zapped. operadude thanks for cheering me on over time, yes, I did notice.

‘Dual Boot: MX Linux & Windows-Installation Guide‘ PDF 1.00 Mb updated 8 PM EST (GMT -5) December 19, 2024

MX Linux Forum

dual boot installation

dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation

Re: dual boot installation