On 01/14/2016 11:45 PM, Tod Merley wrote:
potential issues: mbr uefi - many ways to solve none easy.

On Thu, Jan 14, 2016 at 7:44 PM, Kevin Cummings <cummi...@kjchome.homeip.net <mailto:cummi...@kjchome.homeip.net>> wrote:

    On 01/14/16 22:19, Michael D. Setzer II wrote:
    > My Classroom Lab at the College has Lenovo I7 computers that
    came with
    > Windows 7 about 2 years ago. I changed them to dual boot with
    Fedora, and
    > just recently upgraded them to Fedora 23. Never had any issues
    with the
    > installation of the Fedora or doing updates. I wanted to check
    out the
    > Windows 10 upgrade process on one machine, but have run into all
    kinds of
    > issues.
    >
    > 1. Booting the Windows 7, the Windows 10 upgrade would just keep
    showing
    > the option to request the upgrade and I would be notified. Never
    got any
    > notification??

    I upgraded both my wife's and my mother's computers to W10 for them
    (both were windows only machines).  As I recall, at the time,
    Microsoft
    would "log" the update request, and feed the update to the computers
    while they were running over a period of time (kings a long and slow
    download to help spread the load on the Microsoft servers). So,
    essentially, you'd have to boot W7, and leave it running until
    Microsoft
    gets around to downloading the update to the machine.  After that,
    you'll get both an email and a notification that the upgrade is
    ready to
    be run.  You can then spend 1-2 hours waiting for the installation to
    complete.  Along the way, it will reboot 3-4 times, and it expects
    that
    the reboot process will directly reboot windows to continue the
    upgrade.

    Based on that, you might want to disable the dual boot, upgrade
    windows,
    then re-enable the dual boot.  (At a bare minimum, you might be
    able to
    change the Grub loader to default to Windows until the upgrade is
    finished.)  This assumes that Windows updates work in your dual boot
    scenario without any problems, so the Windows upgrade should as well.

    > 2. When thru some web pages, and found a link that was upgrade
    now, and
    > it seemed to down and go thru the process of getting the Windows
    10 files.
    > Said it was going to reboot, and install. It rebooted, and still
    had the grub
    > menu, so selected the windows option, and it seemed to be doing
    something,
    > but then came up with an error message and said it could
    complete. Took me
    > to a web page, but of couse the error number wasn't anywhere to
    be found
    > there or on a search. Just restored the W7 image, so dual boot
    process is
    > fine.

    Sorry, I run any Winows images in VMs on my Linux machines.  I
    don't do
    dual boot anymore.  And Microsoft won't upgrade my XP images to
    W10.  B^)

    > Are there any tricks to getting the upgrade to work with a dual
    boot setup.
    > Don't know if the Windows 10 upgrade can not handle a grub boot
    loader
    > setup?
    >
    > Thanks.
    >
    > Use Linux for all my courses, but other teachers sometimes need
    to do
    > things on the windows, and wanted to at least take a look at it.
    >
    > +----------------------------------------------------------+
    >   Michael D. Setzer II -  Computer Science Instructor
    >   Guam Community College  Computer Center

You will have to make the dual-boot default to starting Windows or the upgrade will hang when it tries to reboot itself. If you restore the Windows boot loader altogether you will be safer.

I had Windows 8.1 and PCLOS on one drive, Windows on sda1 and PCLOS on sda6 (/) and sda7 (/home). I think sda5 was swap, I don't remember. sda5, sda6 and sda7 were on the extended partition. When Windows got done, the Linux partitions were gone, and there was just one big unallocated partition where they were. If your Windows 7 was installed on two partitions (a tiny boot partition sda1 and a big partition for the main system, sda2, then you may be better off, I don't know. Mine was not. (It is now.) I had copied the /home partition to another drive before starting this mess, and I wound up making new partitions where the unallocated space was, copying /home back, and reinstalling /. The Linux system is still a little flaky, and I can't get the scanner to work, but it's almost OK. (I haven't really put in the time to make the scanner work again--hopefully it will.)

--doug
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Reply via email to