Project

General

Profile

Bug #10649

Have a video to explain how to start Tails (and use the boot menu key)

Added by sajolida over 3 years ago. Updated 4 days ago.

Status:
Needs Validation
Priority:
Normal
Assignee:
Category:
Installation
Target version:
Start date:
11/24/2015
Due date:
% Done:

0%

Feature Branch:
doc/10649-boot-menu-animation
Type of work:
Graphics
Blueprint:
Starter:
Affected tool:
Installation Assistant

Description

It is a very common and blocking issue to know how to use the boot menu key on startup. Maybe having a small video or animation would do the trick. The proposed synopsis is:

  • Shut down
  • Identify the key
  • Power on
  • Repeatedly press the key until either Windows, Linux, or Tails starts

We should write François Prosper about that as he might be intersted in working on this.

1.png View (82.6 KB) Fransouwap, 11/30/2015 01:03 AM

2.png View (154 KB) Fransouwap, 11/30/2015 01:03 AM

3.png View (36.3 KB) Fransouwap, 11/30/2015 01:03 AM

Tails - Install from Windows.zip (487 KB) sajolida, 06/13/2019 06:11 PM

Tails - Install from Windows.zip (487 KB) sajolida, 06/13/2019 07:27 PM


Related issues

Related to Tails - Bug #10632: Improve troubleshooting section for restart Resolved 11/24/2015
Related to Tails - Feature #11111: Be more careful when documenting the BIOS Confirmed 02/12/2016
Related to Tails - Feature #7492: Explain graphically different steps of a typical use of Tails through photos or screencast Rejected 07/06/2014
Related to Tails - Bug #14835: Make the subtitle on our canonical logo optional Resolved 10/12/2017
Related to Tails - Bug #14788: Add anchors to the troubleshooting parts of the installation doc Needs Validation 10/04/2017
Blocks Tails - Feature #16080: Core work 2018Q4 → 2019Q2: User experience Confirmed 10/29/2018

History

#1 Updated by sajolida over 3 years ago

  • Target version changed from 246 to Tails_2.0

#2 Updated by Fransouwap over 3 years ago

Hello
Here's the steps I worked on, and the comment that goes with them :
1. While leaving the USB stick plugged in, shut down the computer
2. Switch on the computer, pressing and holding the key(s) corresponding to the PC constructor. Hold it until start is complete.
3. the computer should be now boot on Tails

As you see, it's a brief story, and it's just roughs so far. Some steps need to be improved I think, especially when you need to see what's on the screen. And the text is more your part so it's purely suggestions.

#3 Updated by sajolida over 3 years ago

  • Related to Bug #10632: Improve troubleshooting section for restart added

#4 Updated by sajolida over 3 years ago

  • QA Check set to Info Needed

Nice to see you on Redmine Fransouwap! As you might know already we're still having a discussion with tchou on the proper method to document. I'll summarize here my vision of it, I hope he'll complete it. I prefer doing it on this ticket so that other people from the project can take part in this decision, as it's not a pure UX question but has technical implications (what's working and what's not working). And I'm sorry to bring in more debates after you started working on this, but I think that this is a serious issue.

So, until now and as I personally always have been doing we're documenting the "press repeatedly" method, which is:

  • Shut down
  • Identify the key
  • Power on
  • Repeatedly press the key until either Windows, Linux, or Tails starts

After the UX testing, tchou proposed another method, the "press-and-hold" method, which is the one you started working on:

  • Shut down
  • Press-and-hold the key
  • Power on

Since then, I've discussing the "press-and-hold" with other developers and testing it. This lead me to identify two possible issues that I consider as blockers. I started documenting these on #10632 but I'll summarize my findings here:

1. Some BIOS models go into error mode when a key is pressed before powering on. It's called the "key stuck" error, like discussed here for example: https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T/When-booting-I-get-an-Error-0210-Stuck-Key-01-Lenovo-Thinkpad/td-p/1404855

2. Some computers don't boot using "press-and-hold" and seem to completely ignore the pressed key. That's the case of a Dell Inspiron I have access to.

In both of these cases the "press repeatedly" method would work.

I personally have no example of computers for which the "press repeatedly" method would not work or give blocking errors. But I admit that the complicated part is to press the key at the right time (that's why we explain to press it repeatedly). The benefit of the "press-and-hold" method is to be easier to execute but it can lead to blocking issues on some machines.

I think that tchou is right now in favor of documenting both (I don't know which one would come first).

I'm personally in favor of documenting only the "press repeatedly" method, which doesn't lead to lead to BIOS errors though is harder to execute. But hey, that's why we're proposing to do a screencast in the first place, no? I'm not really convinced by documenting both as we're trying to simplify things here and not introduce more "if ... else ..." clauses for the user to experiment with and debug mentally.

#5 Updated by sajolida over 3 years ago

I tested this on a Dell Inspiron 3330 today and the boot menu key, if pressed before powering on is ignored as well. Only the press repeatedly version works.

#6 Updated by tchou over 3 years ago

  • Assignee changed from tchou to sajolida

Hey,

I'm in favor of documenting the both methods, but before going deeper, I need a clarification: you are talking about "blocking issues". I'm not shure to understand. In the forum link I think that the difficult situation comes from the fact that the key is blocked (not just hold). If the user just reboot (without holding), it boot as normal no ? Do you have experienced tricky stuff to do to escape from a "press-and-hold method" ?

#7 Updated by sajolida over 3 years ago

Regarding the "key stuck" BIOS error, I think that from a hardware point of view it makes no difference whether the key is stuck (blocked in its pressed position by some glue, some sticky liquid, or a cat) or whether it's pressed and hold by the user on purpose (as you are proposing in your technique). In other words, I don't understand the difference that you seem to make between "blocked" and "hold" in your comment and I think that the BIOS seems both as the same. Otherwise, please elaborate.

Regarding having experienced myself tricky stuff with your technique, I didn't get the "key stuck" error but I found two laptops models (our of the three I tested) which completely ignore the key if it is pressed and hold before powering on the computer. So nothing tricky to escape, but just something that doesn't work.

#8 Updated by tchou over 3 years ago

  • QA Check deleted (Info Needed)

As always it's a cost and benefit question, with some error anticipating UX issues.

For me the benefit on the "press-and-hold" method is obvious : otherwhise the user would have stop. And the cost is that maybe it will fail. But we can anticipate it and explain it: maybe it won't work and boot windows, maybe there will be BIOS error message, but in any cases, he would just have to start again and try the "press repeatedly" method (or try first with other keys).

#9 Updated by tchou over 3 years ago

Note that I don't have know if we must propose to the the "press-and-hold" method after or before the "press repeatedly" one.

#10 Updated by sajolida over 3 years ago

During the January meeting, intrigeri proposed:

1. document "press repeatedly" with a screencast, and hope it works for the vast majority or (people, hardware) combinations;
2. as a fallback, "if it does not work, try that" style, quickly and cheaply document the "press and hold" method.  I believe this takes into account the experience that was shared here, the apparent unreliability of press-and-hold, and *also* the fact that many people may fail with "press repeatedly", even with a good screencast, because that's how it is.

#11 Updated by sajolida over 3 years ago

  • Target version deleted (Tails_2.0)

Let's say this is a bonus and not a blocker for the first release.

#12 Updated by sajolida over 3 years ago

  • Related to Feature #11111: Be more careful when documenting the BIOS added

#13 Updated by sajolida about 3 years ago

  • Assignee deleted (sajolida)

#14 Updated by u almost 2 years ago

  • Related to Feature #7492: Explain graphically different steps of a typical use of Tails through photos or screencast added

#15 Updated by u over 1 year ago

  • Assignee set to sajolida
  • QA Check set to Info Needed

I think it would still be useful to just have an animated gif in the "Tails does not start at all" section of https://tails.boum.org/install/win/usb/index.en.html. What do you think?

Assigning to sajolida for comment. Otherwise I'd say let's reject this ticket. Nothing happened since two years here.

#16 Updated by sajolida over 1 year ago

  • Description updated (diff)

Yeap. That's what I intented to write in the description of this ticket. Whether it's an animated GIF or an inlined video is an implementation detail, right? But won't fundamentally change the amount of work or the skills needed.

Animated GIT don't have sound, but that might be good as it will avoid having to translate it. Maybe we should go for a video without voice anyway.

#17 Updated by sajolida about 1 year ago

  • Target version set to Tails_3.8
  • QA Check deleted (Info Needed)

I'll contact some people I know who do animations and ask them for a quote.

#18 Updated by sajolida 12 months ago

  • Target version changed from Tails_3.8 to Tails_3.9

#19 Updated by sajolida 12 months ago

  • Blocks Feature #15392: Core work 2018Q2 → 2018Q3: User experience added

#20 Updated by sajolida 10 months ago

  • Target version changed from Tails_3.9 to Tails_3.10.1

I contacted them but nothing will happen before September → 3.10.

#21 Updated by sajolida 9 months ago

  • Subject changed from Have a screencast to explain how to use the boot menu key to Have a video to explain how to use the boot menu key

My next step is to write to of a friendly web studio doing graphical design (and even Bootstrap stuff!).

#22 Updated by sajolida 8 months ago

  • Target version changed from Tails_3.10.1 to Tails_3.11

#23 Updated by sajolida 8 months ago

  • Blocks deleted (Feature #15392: Core work 2018Q2 → 2018Q3: User experience)

#24 Updated by sajolida 8 months ago

  • Blocks Feature #16080: Core work 2018Q4 → 2019Q2: User experience added

#25 Updated by sajolida 6 months ago

  • Target version changed from Tails_3.11 to Tails_3.12

#26 Updated by sajolida 5 months ago

  • Target version changed from Tails_3.12 to Tails_3.13

#27 Updated by sajolida 4 months ago

  • Subject changed from Have a video to explain how to use the boot menu key to Have a video to explain how to start Tails (and use the boot menu key)

#28 Updated by sajolida 4 months ago

We now have a reasonable quote and an awesome team of graphic designer and animator. I'll get started with them ASAP.

#29 Updated by sajolida 3 months ago

  • Related to Bug #14835: Make the subtitle on our canonical logo optional added

#30 Updated by sajolida 3 months ago

  • Target version changed from Tails_3.13 to Tails_3.14

#31 Updated by CyrilBrulebois 25 days ago

  • Target version changed from Tails_3.14 to Tails_3.15

#32 Updated by sajolida 5 days ago

  • Related to Bug #14788: Add anchors to the troubleshooting parts of the installation doc added

#33 Updated by sajolida 5 days ago

  • Status changed from Confirmed to In Progress

Here is the final video!

https://git.tails.boum.org/ux/plain/boot%20menu%20key/boot-menu-key.webm

Now I'll integrate it in our installation instructions.

#34 Updated by sajolida 4 days ago

  • Related to deleted (Bug #14788: Add anchors to the troubleshooting parts of the installation doc)

#35 Updated by sajolida 4 days ago

Here is a branch! At the same time I'm tackling part of #14788.

@cbrownstein: Please have a look!

Notes:

  • I had to rewrite a bunch of Markdown into HTML so all translations were going to break anyway. It means that, for once, we can do all kind of smaller changes in the English text if we want :)
  • Not improving the content much (eg. Secure Boot) on purpose. We can do that later and now it's going to be better displayed to users. Yay!

@emmapeel + @goupille: This branch brings a big change in how people are referred to the troubleshooting sections and to your help desk. So please have a close look and tell me how you think all this will impact your work. It's on purpose that I'm not changing the content much for now (eg. Secure Boot). But tell me if you see other small fixes that could fit here. I'm attaching a ZIP version of the compiled page if that's easier for you to review.

@intrigeri: While working on this I think I found a bug in po4a. It was returning HTML errors when parsing the <video> tag. See 484c430d81. I'm fine with reporting it upstream with a bit of guidance from you if you think that it's worth it.

Ah, something else I would like your opinion on: I added a note for people to report about the boot menu key that worked for them to . Our list of possible boot menu keys hasn't been improved since we wrote it in 2015 (by lack of data). The note I added on /doc/anonymous_internet/networkmanager/no-wifi.inline brought some useful information already. So I thought about trying out something similar to improve the list of boot menu keys. I was tempted to point to collective addresses but I'm anyway going to be the one processing them so I thought that my personal address was the most efficient point of contact. We can always change it later on in case I'm fired :)

#36 Updated by sajolida 4 days ago

  • Feature Branch set to doc/10649-boot-menu-animation

#37 Updated by sajolida 4 days ago

@cbrownstein: Technical point, I put the video in the promotion-material repo (https://git-tails.immerda.ch/promotion-material) to avoid having this big binary in tails.git (and the USB image). To have it on your local build of the page you can either:

#38 Updated by sajolida 3 days ago

  • Related to Bug #14788: Add anchors to the troubleshooting parts of the installation doc added

Also available in: Atom PDF