Month: November 2017

New PHIL Family Group

Posted by

0

Well actually not very new……. I have been very slack on the One Name Study for the last few years when I have been busier on the Open Source Software stuff. Philip Gammon contacted me over five years ago apparently, but got back in touch recently. This prompted me, with information from his email, to find the tree I had started back then (but not finished) and continue linking his tree to the BMD and census data for Gammon people that I have collected in my indexes. This is a family that has been in the Maidstone (Kent, England) area for many years. I really need more copies of certificates to confirm relationships, and/or to dig a bit deeper into other datasets to go back further in time. The work so far can be found here:

PHIL Family Group

Phil has a lot more information about his family tree than I have in my database, and believes there is a connection with the STEP Family Group of Boxley, Kent.

We have a DNA result from the PHIL Family Group in the FamilyTreeDNA Gammon Project. The haplogroup in this result seems to be distinct from other DNA tests in the Gammon project. Results from someone connected to the STEP family would be very interesting. Do you know anyone called Gammon with connections in Kent?

Updates to HOWES Family Group

Posted by

0

It was a bit of a rainy day today, so I have done a bit of work on the HOWES family Group after feedback on the website from Stephen HOWES who is a descendant of that family.

With information from Steve, it looks like the family moved from Kings-Ripton from nearby Buckworth in the old county of Huntingdonshire (now Cambridgeshire).

I must put the effort in to index the church records for Huntingdonshire.

Link to the Family Group: HOWES Family Group

Photo of Buckworth All Saints Church by By Chris Stafford, CC BY-SA 2.0, https://commons.wikimedia.org/w/index.php?curid=7138320

Installing Ubuntu Studio alongside Windows 10

Posted by

1

I recently installed Ubuntu Studio 17.10 Artful Aardvark on a spare USB disk for my son. His computer had Windows 10, but there was no space inside the case for an extra internal disk. I selected the option during the install process to boot Ubuntu Studio with the Windows Boot Manager. But unfortunately, after the installation completed the computer would only ever boot into Windows – there was no Grub menu.

There was plenty of information online about this problem. As usual with these type of problems, some of the information seemed trust worthy, and some not! I thought I would record here what worked for me, in case I ever get stuck again.

It turned out that I had to go into Windows and use the command  line to point the Windows Boot Manager at the right EFI file.

As I didn’t trust the advice at first, I ran the command with the Windows “help” option (which I had forgotten after not using Windows for many years) to find out what the command did:

C:\Windows\system32>bcdedit /?

This showed me the command to investigate what the current setting was:

C:\Windows\system32>bcdedit /enum

Windows Boot Manager

——————–

identifier {bootmgr}

device partition=\Device\HarddiskVolume2

path \EFI\Microsoft\Boot\bootmgfw.efi

description Windows Boot Manager

locale da-DK

inherit {globalsettings}

default {current}

resumeobject {9c35ad51-1f6a-11e7-aeb5-f52aab87eca4}

displayorder {current}

toolsdisplayorder {memdiag}

timeout 30

Windows Boot Loader

——————-

identifier {current}

device partition=C:

path \Windows\system32\winload.efi

description Windows 10

locale da-DK

inherit {bootloadersettings}

recoverysequence {9c35ad53-1f6a-11e7-aeb5-f52aab87eca4}

recoveryenabled Yes

isolatedcontext Yes

allowedinmemorysettings 0x15000075

osdevice partition=C:

systemroot \Windows

resumeobject {9c35ad51-1f6a-11e7-aeb5-f52aab87eca4}

nx OptIn

bootmenupolicy Standard

I could then see that Windows Boot Manager was still loading the old EFI file (bootmgfw.efi). This gave me the confidence to run the magic command found on the internet to point Windows Boot Manager at the right EFI file:

C:\Windows\system32>bcdedit /set {bootmgr} path \EFI\ubuntu\shimx64.efi

After a brief panic that maybe that the installer had not installed the EFI file with that exact name, or that it had not installed Grub at all, and that I was about to brick my son’s computer (and never here the end of it), I rebooted.

Voila! Grub appeared, and I could boot into both Windows and Ubuntu Studio. Now all I have to do is buy a USB MIDI/Audio interface so we can hook up the computer to his electronic drum kit, and my old Roland keyboard.