Trick to validate a new Windows 10 DVD once K3b burned it on Linux

[ceg]

Is there a way to verify a Windows 10 DVD once it's burned from Linux?

1. I downloaded the Windows 64-bit & 32-bit ISO files.
https://www.microsoft.com/en-us/software-download/windows10
2. I ran a checksum (md5sum) on each so I have a checksum.
$ md5sum Win10_English_x32.iso
99feb0f9e7262b7eefa460840a31b59d Win10_English_x32.iso
$ ls -l Win10_English_x32.iso
-rw------- 1 x x 3052865536 Aug 21 04:58 Win10_English_x32.iso
$ md5sum Win10_English_x64.iso
23e397a21a9e01f141c64b7e1260314a Win10_English_x64.iso
$ ls -l Win10_English_x64.iso
-rw------- 1 x x 4083853312 Aug 20 23:58 Win10_English_x64.iso
3. I burned the 64-bit ISO to dvd after hitting the K3b "verify" button.
4. But, I forgot to hit the verify button when burning the 32-bit iso.

QUESTION:
Given I have the MD5 checksum for the 32-bit ISO file on Linux, is there
a way to verify the 32-bit Windows 10 dvd, after the fact?

NOTE: I'm traveling this weekend, to install it on my kid's computer
at school, and I don't have a Win7sp1 or Win8.1 at home to check
against.

[Mike Tomlinson]

En el artículo <mr8n35$t2r$1...@news.mixmin.net>, ceg
<curt.gul...@gmail.com> escribió:

>Given I have the MD5 checksum for the 32-bit ISO file on Linux, is there
>a way to verify the 32-bit Windows 10 dvd, after the fact?

Yes. On Linux:

md5sum /dev/dvd

(or whatever Linux calls your raw DVD device. If /dev/dvd doesn't work,
try /dev/cd, /dev/cdrom, /dev/cdrom0, /dev/scd, /dev/sr0 or /dev/scd0.)

This will read the entire disk, and the checksum should be the same as
that for the file.

If you wanted to do this on Windows, you'd need to find a command line
version of md5sum and point it at the raw Windows device, e.g.

md5sum.exe \\.\CdRom0

whether that works depends on whether the authors of md5sum.exe have
built in the ability to understand raw Windows devices - they may be
expecting to deal with standard filenames only. You'd have to try it or
ask them.

or, a much easier way if you have Cygwin installed, is:

md5sum /dev/sr0

--
(\_/)
(='.'=) Bunny says: Windows 10? Nein danke!
(")_(")

[ceg]

On Sat, 22 Aug 2015 04:17:53 +0100, Mike Tomlinson wrote:

> Yes. On Linux:
>
> md5sum /dev/dvd
>
> (or whatever Linux calls your raw DVD device. If /dev/dvd doesn't work,
> try /dev/cd, /dev/cdrom, /dev/cdrom0, /dev/scd, /dev/sr0 or /dev/scd0.)
>
> This will read the entire disk, and the checksum should be the same as
> that for the file.

$ md5sum /dev/dvd
md5sum: /dev/dvd: No such file or directory

$ md5sum /dev/cd
md5sum: /dev/cd: No such file or directory

$ md5sum /dev/cdrom
md5sum: /dev/cdrom: No medium found

$ md5sum /dev/cdrom0
md5sum: /dev/cdrom0: No such file or directory

$ md5sum /dev/scd
md5sum: /dev/scd: No such file or directory

$ md5sum /dev/scd0
md5sum: /dev/scd0: No such file or directory

$ md5sum /dev/sr0
md5sum: /dev/sr0: No medium found

$ md5sum /dev/sr1
This made the external USB-connected DVD burner whir away for
something like a few minutes (or thereabouts), but it finally
stopped whirring and reported the following:

$ md5sum /dev/sr1
99feb0f9e7262b7eefa460840a31b59d /dev/sr1

From that, I conclude three things:
1. The internal cd burner is /dev/sr0 (probably)
2. The external dvd burner is /dev/sr1 (almost certainly)
3. The 32-bit Win10 checksum matches that of the ISO on the HDD!

Thanks for explaining how to verify, after the fact, a Windows 10
ISO once burned to DVD disc on Linux.

[ceg]

On Sat, 22 Aug 2015 03:46:39 +0100, Good Guy wrote:

> If you didn't get any error messages then it should be ok and there no
> need for further verification.

Heh heh heh ... you clearly don't have the same laptop and DVD burner
that I have!

I get coasters all the time, without errors showing up in K3b on Linux.
ImgBurn, on Windows, is better at logging the errors.

The good news is that the following command validates the image on HDD:

$ md5sum Win10_English_x32.iso
99feb0f9e7262b7eefa460840a31b59d Win10_English_x32.iso
$ ls -l Win10_English_x32.iso
-rw------- 1 x x 3052865536 Aug 21 04:58 Win10_English_x32.iso

And the following validates that image burned to DVD optical media:

[Mike Tomlinson]

En el artículo <mr8tmr$a8t$1...@news.mixmin.net>, ceg
<curt.gul...@gmail.com> escribió:

>Thanks for explaining how to verify, after the fact, a Windows 10
>ISO once burned to DVD disc on Linux.

You're welcome.

You're wasting your time replying to "Good Guy", by the way. He's an
idiot and frequently gives out incorrect information, as he did in his
reply to you earlier. Best killfiled.

[Dave Cohen]

On Sat, 22 Aug 2015 06:14:30 +0100, Mike Tomlinson wrote:

> En el artículo <mr8tmr$a8t$1...@news.mixmin.net>, ceg
> <curt.gul...@gmail.com> escribió:
>
>
>>Thanks for explaining how to verify, after the fact, a Windows 10 ISO
>>once burned to DVD disc on Linux.
>
> You're welcome.
>
> You're wasting your time replying to "Good Guy", by the way. He's an
> idiot and frequently gives out incorrect information, as he did in his
> reply to you earlier. Best killfiled.

Apart from his being an idiot, something with which I concur, he insists
on including html code in his posts. I've asked him why this occurs, is
it a setting on his news reader? He seems to bear a grudge against Linux.

[Caver1]

Yes he hates Linux and has stated that he will post in HTML because he
thinks it's
better.


--
Caver1

Civilization degrades the many to exalt the few.
-- Amos Bronson Alcott

[Wildman]

I remember him saying that he posts in HTML because it
aggravates us.

--
<Wildman> GNU/Linux user #557453
The cow died so I don't need your bull!

[OldGuy]

If you ran ISOBUSTER (the free part) it would tell you if it had a
problem busting it.
You need disk space for the results but then you just erase that.

--- news://freenews.netfront.net/ - complaints: ne...@netfront.net ---

[Mike Tomlinson]

En el artículo <mra6lm$4nm$3...@dont-email.me>, Dave Cohen
<nob...@nowhere.com> escribió:

>Apart from his being an idiot, something with which I concur, he insists
>on including html code in his posts. I've asked him why this occurs, is
>it a setting on his news reader?

He does it deliberately to annoy people, which is an abuse of his
account. Usenet is a text medium and HTML postings are not text.

Complaints should be sent to his news provider, Albasani, at
ab...@albasani.net, quoting the following:

Injection-Info: news.albasani.net; logging-data="Ea7AZDsHNz0qFFJVATSwkT+
Uz4kK3nZzIaTH4AimvlTFoOqRH8JqOi98JTtRUPtOQ3Klyfy+5UR2LiQgXbeAJMmm3vYl57y
74+03ErGX7YmgsrauutUN8uAzJJfO35C0"; mail-complaints-
to="ab...@albasani.net"

> He seems to bear a grudge against Linux.

He's too much of a blinkered idiot to realise that it's a tool just like
any other. There are situations where Windows is the correct tool for
the job, and situations where Linux is the correct tool for the job.
But he's too narrow-minded to see that.

[Rene Lamontagne]

He also hates Older people and Canadians, A very distasteful person.

Regards, Rene

[ceg]

On Sat, 22 Aug 2015 06:14:30 +0100, Mike Tomlinson wrote:

> You're wasting your time replying to "Good Guy", by the way. He's an
> idiot and frequently gives out incorrect information, as he did in his
> reply to you earlier. Best killfiled.

Thanks for the advice.

I brought the 64-bit DVD that I burned on Linux to my kid today up at
college, and we installed Windows 10 without any hitches. It took about a
half hour on a low-end Dell Inspiron 15 which was originally Windows 8.1
from Dell.

http://i.imgur.com/N62Hgfp.jpg

It was pretty easy, I must say, so, I can verify that the Linux download
and burn of the Windows 10 ISO works just fine.

1. We popped the DVD into the optical drive
2. Windows 8.1 asked us to run the Microsoft setup.exe
3. That installed Windows 10 in about a half hour.

That was pretty much it.

I didn't play with Win10 for more than a couple of minutes, just to see
if Windows 10 was working, and it was. (My kid will surely complain if
there are issues.)

I noticed a "C:\Windows.old" which is probably the old Windows 8.1, but,
other than that, it didn't seem all that different upon initial inspection
other than the horrid tiles were gone (partly put in the Start Menu).

[ceg]

On Sat, 22 Aug 2015 09:57:43 -0700, OldGuy wrote:

> If you ran ISOBUSTER (the free part) it would tell you if it had a
> problem busting it.
> You need disk space for the results but then you just erase that.

Thanks for that advice.
I used the 64-bit ISO today, which was downloaded on Linux and burned on
Linux usin K3b, and it worked perfectly in a Windows 8.1 machine to
install Windows 10.

http://i.imgur.com/N62Hgfp.jpg

[Mike Tomlinson]

En el artículo <mrbnnn$gbt$1...@news.mixmin.net>, ceg
<curt.gul...@gmail.com> escribió:

>I didn't play with Win10 for more than a couple of minutes, just to see
>if Windows 10 was working, and it was. (My kid will surely complain if
>there are issues.)

If it doesn't work out, you have 30 days to revert to 8.1. That's what
the Windows.old folder is for.

Glad it went well.

[William Unruh]

On 2015-08-23, ceg <curt.gul...@gmail.com> wrote:
> On Sat, 22 Aug 2015 06:14:30 +0100, Mike Tomlinson wrote:
>
>> You're wasting your time replying to "Good Guy", by the way. He's an
>> idiot and frequently gives out incorrect information, as he did in his
>> reply to you earlier. Best killfiled.
>
> Thanks for the advice.
>
> I brought the 64-bit DVD that I burned on Linux to my kid today up at
> college, and we installed Windows 10 without any hitches. It took about a
> half hour on a low-end Dell Inspiron 15 which was originally Windows 8.1
> from Dell.

How much extra room does it take? And does it reformat anything on the
drive. I have a Dual Boot Win 8.1/Mageia5/Fedora machine, and Win 8 is
not on a large partition.

[ceg]

On Sun, 23 Aug 2015 08:38:21 +0100, Mike Tomlinson wrote:

> If it doesn't work out, you have 30 days to revert to 8.1. That's what
> the Windows.old folder is for.

I will tell the kid to move Windows.old to Windows.bck (or something)
before the 30 days run out.

[ceg]

On Sun, 23 Aug 2015 16:03:21 +0000, William Unruh wrote:

> How much extra room does it take? And does it reformat anything on the
> drive. I have a Dual Boot Win 8.1/Mageia5/Fedora machine, and Win 8 is
> not on a large partition.

I didn't look, and the machine is in the kid's room at school, so,
someone else will need to answer that one.