titterton.barry at gmail.com
Wed Apr 27 10:36:34 UTC 2016
On 26/04/16 17:11, A Pearson wrote:
> Mint Cinnamon 17.3 64 bit from LXF 207 Feb 16
> Its been a long time since I came to the group as most of the talk was
> way above my head and I use desktops not laptops as they are easier to
> modify so that was another reason.
> I hope I have got the posting right as its many years since last time.
> Installed Mint OK but it will not recognise password or username which I
> had installed a few minutes earlier.
> Typing them in correctly with correct case several times just gave the
> message that either wrong names had been entered or the case was wrong.
> I have re installed four times now booting on to a clean HDD and no
> mistake has been made. During install I went through the process of
> getting Mint to identify the keyboard which is a Microsoft business
> model of British format.
> It is on its own drive dual booted from the BIOS for either the Linux or
> Win 7 drives. I do not use the Grub bootloaders etc as experience shows
> that if you remove Linux you lose access to Windows and have to start
> all over again.
> I am quite proficient with windows PC's but relatively new with Linux
> having tried a couple of distros in the last ten years but now wish to
> make a determined effort with Mint.
> Hope you can advise so I can move on. Found nothing definite on Google
> which was mainly people losing their passwords which is not this case.
> Thanks in anticipation that you may be able to help me with something
> not too complicated.
> Durham mailing list - Durham at mailman.lug.org.uk
Is this problem with a desktop machine?
This can also be a problem with Lubuntu as well, so Mint may have
accidentally picked up the same bug.
With Lubuntu's bug you can select any language at installation but on
first boot the newly installed system always reverts to a US keyboard
layout. Therefore if you used any of the special characters when setting
your password during installation, you may find that you are
accidentally typing different characters during your first log-in attempt.
Jonathan's suggestion is a good one as it will get around this potential
bug. When you manage to log-in you can then check what the keyboard is
actually doing by trying each special character key in a Writer document.
Also using GRUB for dual booting shouldn't cause that big a problem. I'm
sure that I have seen articles where users have rejected a dual boot
installation, removed the Linux partition, and got the Windows boot
loader working again without having to completely re-install the Windows
OS. I think that the Windows install disc has a repair facility which
will do this. I don't use Windows myself but I will try and find an
article for you if you want?
More information about the Durham