Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(GUI): explain why some drives are not bootable out of the box #783

Merged
merged 1 commit into from
Oct 31, 2016

Conversation

jviotti
Copy link
Contributor

@jviotti jviotti commented Oct 28, 2016

The usual case is images requiring special treatment. We recommend the
users to use specialised tooling for those cases.

Signed-off-by: Juan Cruz Viotti jviotti@openmailbox.org

Etcher copies images to drives byte by byte, without doing any transformation
to the final device, which means images that require special treatment to be
made bootable, like Windows images, will not work out of the box. In these
cases, the general advice is to use tooling specific to those kind of images,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps "software" would be better here than "tooling" ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed!

@lurch
Copy link
Contributor

lurch commented Oct 28, 2016

Is it worth also explaining that Etcher doesn't set up "persistent" partitions like Unetbootin can do? (or should that come under a separate PR?)

@jviotti jviotti force-pushed the docs-not-bootable-images branch from bf7de52 to ea7cbf0 Compare October 29, 2016 04:02
@alexandrosm
Copy link
Contributor

you may want to include specific problematic cases, as well as the specific
tools? if we start listing them here, we will have them ready when we want
a list of what to include in our warnings feature.

Alexandros Marinos

Founder & CEO, Resin.io

+1 206-637-5498

@alexandrosm

On Fri, Oct 28, 2016 at 9:02 PM, Juan Cruz Viotti notifications@github.com
wrote:

@jviotti commented on this pull request.

In docs/USER-DOCUMENTATION.md
#783:

@@ -3,6 +3,15 @@ Etcher User Documentation

This document contains how-tos and FAQs oriented to Etcher users.

+Why is my drive not bootable?
+-----------------------------
+
+Etcher copies images to drives byte by byte, without doing any transformation
+to the final device, which means images that require special treatment to be
+made bootable, like Windows images, will not work out of the box. In these
+cases, the general advice is to use tooling specific to those kind of images,

Fixed!


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#783, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCHlfgzYvBlXzgDG8SWRyuoOGhPqIks5q4sVJgaJpZM4KjktU
.

The usual case is images requiring special treatment. We recommend the
users to use specialised tooling for those cases.

Signed-off-by: Juan Cruz Viotti <jviotti@openmailbox.org>
@jviotti jviotti force-pushed the docs-not-bootable-images branch from ea7cbf0 to 1853670 Compare October 31, 2016 05:25
@jviotti
Copy link
Contributor Author

jviotti commented Oct 31, 2016

@alexandrosm Done!

@lurch Good idea! I'll do it in a separate PR.

@jviotti jviotti merged commit f8349d4 into master Oct 31, 2016
@jviotti jviotti deleted the docs-not-bootable-images branch October 31, 2016 05:49
@lurch
Copy link
Contributor

lurch commented Oct 31, 2016

It also looks like "Windows 10 IoT Core Dashboard" is needed for writing Windows 10 IoT to a SD card
https://developer.microsoft.com/en-us/windows/iot/Docs/GetStarted/rpi3/sdcard/stable/GetStartedStep1.htm

jviotti pushed a commit that referenced this pull request Oct 31, 2016
Such image seems to require the "Windows 10 IoT Core Dashboard" tools.

See: #783 (comment)
Signed-off-by: Juan Cruz Viotti <jviotti@openmailbox.org>
jviotti pushed a commit that referenced this pull request Oct 31, 2016
See: #413
See: #783 (comment)
Signed-off-by: Juan Cruz Viotti <jviotti@openmailbox.org>
jviotti pushed a commit that referenced this pull request Oct 31, 2016
Such image seems to require the "Windows 10 IoT Core Dashboard" tools.

See: #783 (comment)
Signed-off-by: Juan Cruz Viotti <jviotti@openmailbox.org>
jviotti pushed a commit that referenced this pull request Oct 31, 2016
…#805)

See: #413
See: #783 (comment)
Signed-off-by: Juan Cruz Viotti <jviotti@openmailbox.org>
jviotti pushed a commit that referenced this pull request Oct 31, 2016
Such image seems to require the "Windows 10 IoT Core Dashboard" tools.

See: #783 (comment)
Signed-off-by: Juan Cruz Viotti <jviotti@openmailbox.org>
jviotti pushed a commit that referenced this pull request Oct 31, 2016
Such image seems to require the "Windows 10 IoT Core Dashboard" tools.

See: #783 (comment)
Signed-off-by: Juan Cruz Viotti <jviotti@openmailbox.org>
jviotti pushed a commit that referenced this pull request Nov 1, 2016
#804)

Such image seems to require the "Windows 10 IoT Core Dashboard" tools.

See: #783 (comment)
Signed-off-by: Juan Cruz Viotti <jviotti@openmailbox.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants