WEBVTT

00:00:00.080 --> 00:00:06.400
now back in the days of serial ata gen 2. when we were booting dinosaur

00:00:04.240 --> 00:00:10.880
operating systems like Windows 7 a typical high performance SSD would be

00:00:09.280 --> 00:00:16.880
rated somewhere in the neighborhood of around 230 to 250 megabytes a second for

00:00:15.040 --> 00:00:25.160
reads and writes which got me thinking when sony released

00:00:20.960 --> 00:00:28.000
sd cards that are rated up to

00:00:25.160 --> 00:00:32.640
300 megabytes a second okay technically 299 on the rights could we boot Windows

00:00:31.039 --> 00:00:38.390
from these and what would the experience be like

00:00:43.200 --> 00:00:50.320
ifixit's protech toolkit gives you the tools you need to tackle any electronics

00:00:47.360 --> 00:00:55.120
repair challenge visit ifixit.com Linus at the link below and get yours today so

00:00:52.800 --> 00:01:01.280
these puppies have actually been out for quite a while but it took sony almost a

00:00:58.879 --> 00:01:05.600
year to send them to us because apparently

00:01:02.640 --> 00:01:11.040
uh they and along with anything else made of nand flash memory have been in

00:01:08.240 --> 00:01:15.840
very very short supply so what's special about them is not really the capacity i

00:01:13.760 --> 00:01:20.880
mean 128 gigs should be noted is

00:01:17.439 --> 00:01:22.400
pretty decent for an SSD from you know

00:01:20.880 --> 00:01:26.720
back when these kinds of speeds would have been reasonable

00:01:24.159 --> 00:01:33.119
but it's not that it's that because these are sdxc2 so these are uh s2 cards

00:01:31.200 --> 00:01:38.479
and high-end ones at that you've actually got additional contact pins on

00:01:35.680 --> 00:01:42.720
the back of them that enable these extra speeds now what that means is that while

00:01:40.079 --> 00:01:47.920
they are backwards compatible with devices and with card readers that are

00:01:45.840 --> 00:01:52.479
only sdxc capable to get the most out of it we are

00:01:50.479 --> 00:01:57.600
going to need a special reader so this is the uh the wow that's a terrible

00:01:56.479 --> 00:02:05.600
product name i mean i guess it's descriptive this is the sony uhs2 compatible high speed

00:02:03.280 --> 00:02:09.360
doesn't explicitly say it's an sd card reader but whatever minor details so

00:02:07.759 --> 00:02:14.319
it's usb 3 and it's got a compatible slot back

00:02:12.000 --> 00:02:17.599
there for all those extra pins now the reason we need this is that

00:02:16.640 --> 00:02:24.640
while sd to SATA adapters which you know would

00:02:20.879 --> 00:02:27.520
allow us to plug this into a SATA port

00:02:24.640 --> 00:02:31.599
do actually exist in fact we covered a particularly abominable one of them a

00:02:29.920 --> 00:02:35.200
little while ago on this channel takes 10 micro sds and then gives you one SATA

00:02:34.239 --> 00:02:39.519
interface these products because they're

00:02:37.360 --> 00:02:43.040
pretty stupid haven't been updated in a long time which means they're using very

00:02:41.280 --> 00:02:47.200
outdated controllers in fact this is only running SATA 1 speeds and that was

00:02:45.599 --> 00:02:52.560
the least of its problems in terms of performance so we actually need that

00:02:49.440 --> 00:02:53.680
reader in order to plug our card into

00:02:52.560 --> 00:02:57.200
the system at all oh we're also going to need this

00:02:55.680 --> 00:03:01.200
Windows installed usb

00:02:59.120 --> 00:03:03.000
all right so there's our install

00:03:02.319 --> 00:03:09.090
drive

00:03:17.040 --> 00:03:26.720
forgot about this so

00:03:21.680 --> 00:03:29.040
you can install Windows to a usb device

00:03:26.720 --> 00:03:32.879
um i was actually a little bit worried there that we just it wasn't going to

00:03:30.159 --> 00:03:38.159
show up at all but you need a special type of Windows installation you can't

00:03:35.440 --> 00:03:43.280
just do it by putting a usb install disk in the system and installing it to it it

00:03:40.480 --> 00:03:47.920
doesn't like that so what we have to do is we have to create what's called a

00:03:44.879 --> 00:03:49.760
Windows to go installation

00:03:47.920 --> 00:03:52.560
now i've never successfully gotten that to work before

00:03:53.040 --> 00:03:59.040
so yeah so we're going to use a utility called

00:03:56.080 --> 00:04:04.080
rufus we're going to grab a Windows 10 image that we downloaded from microsoft

00:04:01.760 --> 00:04:08.319
and then we just need to point it at

00:04:05.760 --> 00:04:10.640
our usb drive and

00:04:09.040 --> 00:04:15.840
create a bootable disk it's supposed to just be right here

00:04:16.479 --> 00:04:24.080
so microsoft uh in their infinite wisdom

00:04:20.799 --> 00:04:25.840
stopped allowing you to create a Windows

00:04:24.080 --> 00:04:32.560
to go installer using the not the iso but the like

00:04:29.040 --> 00:04:35.520
Windows media creation tool version

00:04:32.560 --> 00:04:39.040
so what you have to do is actually find

00:04:39.120 --> 00:04:44.320
a disk so fortunately i actually just i

00:04:42.160 --> 00:04:48.000
when i was doing an audit of our of our software around here

00:04:46.000 --> 00:04:52.400
um i just realized some of our Windows installs

00:04:50.240 --> 00:04:56.160
were not 100

00:04:53.600 --> 00:04:59.919
correctly legit uh so i just like ran out and bought a bunch of them so

00:04:57.280 --> 00:05:03.280
otherwise i wouldn't have a genuine Windows 10 disc because otherwise we've

00:05:01.600 --> 00:05:10.240
done everything digitally but what you need to have is an actual disk

00:05:06.240 --> 00:05:11.919
and you have to create an iso from that

00:05:10.240 --> 00:05:16.960
so that's what we're gonna have to do here we're gonna have to go back in time

00:05:15.039 --> 00:05:24.720
and rip this disk okay so we've got a Windows 10 image

00:05:20.000 --> 00:05:27.600
that theoretically should work now

00:05:24.720 --> 00:05:31.759
your target drive doesn't have the fixed oh what the hell are we doing

00:05:29.759 --> 00:05:34.000
no we don't want to use this shoot

00:05:34.639 --> 00:05:40.000
we need this okay

00:05:38.560 --> 00:05:42.320
hold on uh

00:05:42.639 --> 00:05:52.280
no there we go no label 128 gig okay

00:05:47.759 --> 00:05:52.280
hopefully this won't give us any errors

00:05:53.440 --> 00:05:58.240
that doesn't bode well i think we're gonna have to get some

00:05:56.639 --> 00:06:02.880
lunch or something i'm really hungry actually

00:06:00.639 --> 00:06:06.479
here we are so that did take a fair bit longer than usual

00:06:04.960 --> 00:06:11.840
but by all appearances this is like pretty

00:06:09.919 --> 00:06:17.120
normal window stuff c drive

00:06:13.199 --> 00:06:18.560
sony mrws1 usb device

00:06:17.120 --> 00:06:21.759
cool all right so let's do some stuff then

00:06:20.800 --> 00:06:28.880
oh okay i'm feeling a little bit of leg

00:06:25.039 --> 00:06:30.160
wow actually hold up a hold on a second

00:06:28.880 --> 00:06:36.479
like you see anything measured in milliseconds you go it's probably pretty small

00:06:32.800 --> 00:06:37.840
but nine thousand milliseconds is nine

00:06:36.479 --> 00:06:40.880
seconds of average response time

00:06:39.919 --> 00:06:46.319
the main reason that we use SSD controllers

00:06:43.520 --> 00:06:48.560
and not sd cards is not the read and write speeds because those are

00:06:47.280 --> 00:06:53.680
sequential i mean the usb interface is part of the

00:06:50.639 --> 00:06:55.919
problem because compared to SATA or

00:06:53.680 --> 00:07:00.720
pci express NVMe it's much less optimized for random performance but the

00:06:58.800 --> 00:07:04.720
other issue is that an sd card is a relatively simple device it's just a

00:07:02.960 --> 00:07:08.800
little bit of nand flash and there's not really to my knowledge

00:07:06.960 --> 00:07:13.440
really any logic on it um compared to an SSD which has like

00:07:11.280 --> 00:07:16.400
these this complex controller it'll in a lot of cases have like a dram cache and

00:07:15.520 --> 00:07:22.000
it has many nand flash dies on it and then it can

00:07:19.759 --> 00:07:27.759
read from and write to them sometimes all at once in a very strategic manner

00:07:24.960 --> 00:07:32.720
so that it can optimize performance and endurance

00:07:29.759 --> 00:07:35.919
but even if it's not that bad i actually wouldn't recommend this as a daily

00:07:34.240 --> 00:07:39.199
driver system because you would kill your sd card

00:07:37.280 --> 00:07:41.919
probably very quickly it's like even though this sd card can

00:07:41.199 --> 00:07:48.880
do you know 300 megabytes a second reads and writes you can see we're at 99 usage

00:07:47.680 --> 00:07:56.840
at like one mega second total

00:07:52.160 --> 00:07:56.840
and that's because it is not optimized

00:07:58.080 --> 00:08:01.440
come on

00:08:01.440 --> 00:08:07.919
bear in mind of course that this is all on an eight core extreme

00:08:05.919 --> 00:08:10.639
edition processor or 10 core 10 chords excuse me

00:08:09.280 --> 00:08:14.639
it's interesting that even when it's basically not doing anything zero to one

00:08:13.120 --> 00:08:18.240
megabyte a second it still registers as being a hundred

00:08:16.720 --> 00:08:22.639
percent active with average response times in the three

00:08:20.080 --> 00:08:26.680
to five seconds range so we should get some drivers

00:08:27.919 --> 00:08:35.519
so we need a goal for ourselves we've got Windows running off an sd card

00:08:32.640 --> 00:08:39.519
but how normal is this experience

00:08:37.360 --> 00:08:43.519
can we game off it we need to get a game going and steam is

00:08:41.519 --> 00:08:47.360
still updating though i think this might actually be worse

00:08:45.279 --> 00:08:51.839
than running a mechanical drive it's writing at a whopping 500 kilobytes

00:08:50.080 --> 00:08:56.560
per second so it's clearly not doing a whole heck of a lot

00:08:54.640 --> 00:09:01.519
no the graphics driver is not compatible

00:08:58.640 --> 00:09:06.080
with this version of Windows how does it even know the difference

00:09:04.240 --> 00:09:11.600
that's stupid like looking at this there's no

00:09:09.519 --> 00:09:18.080
no there's no discernible difference here it's just Windows

00:09:14.000 --> 00:09:18.080
so maybe it's just that we need

00:09:18.240 --> 00:09:23.920
a bazillion updates which might be part of what it's been

00:09:21.760 --> 00:09:27.760
doing in the background here it's got 79 of them downloaded it's making

00:09:25.440 --> 00:09:31.839
everything so slow i really need steam to finish though

00:09:32.080 --> 00:09:39.519
a full day a full day it took

00:09:36.880 --> 00:09:43.120
over a full day

00:09:40.640 --> 00:09:48.399
for all of those Windows updates to run utterly ridiculous

00:09:46.480 --> 00:09:53.120
what we're doing now is with everything updated

00:09:50.959 --> 00:09:55.600
the game installed but i haven't tried it yet

00:09:54.000 --> 00:09:59.839
we're gonna find out how bad or good

00:09:58.000 --> 00:10:03.760
is the experience this

00:10:01.519 --> 00:10:08.480
is it okay we're in

00:10:05.760 --> 00:10:12.959
so the first thing that's noticeable other than that razer's

00:10:10.320 --> 00:10:17.600
gaming software managed to prompt me to install it itself

00:10:14.959 --> 00:10:22.560
is that our display is scaling correctly this is great

00:10:20.000 --> 00:10:25.760
so as long as no NVIDIA control panel though that's

00:10:24.399 --> 00:10:29.640
weird but this is showing up

00:10:32.720 --> 00:10:38.640
okay i really thought this was going to be a

00:10:37.040 --> 00:10:42.240
lot better without stuff running in the background

00:10:40.800 --> 00:10:47.440
like it's measuring it in bytes per second

00:10:44.399 --> 00:10:49.120
half a megabyte a second

00:10:47.440 --> 00:10:52.240
as far as i can tell it looks like we are ready to go to run

00:10:51.279 --> 00:10:56.560
a game so i installed doom which means that my

00:10:55.360 --> 00:11:00.720
drive is actually almost totally full like

00:10:58.560 --> 00:11:04.800
isn't that trippy opening up this pc

00:11:03.200 --> 00:11:08.320
and there's there's no drive there's just

00:11:06.560 --> 00:11:11.620
usb i just don't know how long it's going to

00:11:09.680 --> 00:11:14.749
take to launch

00:11:16.079 --> 00:11:19.120
that's not bad

00:11:19.839 --> 00:11:26.079
okay i haven't played a ton of doom but like

00:11:23.839 --> 00:11:29.079
that seemed like a very serviceable load time

00:11:29.600 --> 00:11:33.600
what did i do with this oh uh

00:11:34.800 --> 00:11:37.920
oh we had a hitch there

00:11:38.000 --> 00:11:41.000
hitch

00:11:42.079 --> 00:11:46.079
those hitches might have actually been anomalies

00:11:46.959 --> 00:11:50.320
this is not bad

00:11:50.880 --> 00:11:54.240
i am impressed

00:11:55.360 --> 00:12:00.480
oh there you go where'd he go

00:11:59.440 --> 00:12:04.880
get over it oh

00:12:02.480 --> 00:12:04.880
okay

00:12:06.800 --> 00:12:14.399
leg leg honestly this experience is way better

00:12:12.480 --> 00:12:18.399
than i expected you know i think the issues before with

00:12:16.800 --> 00:12:23.800
a little bit of lag might have just been anomalies because this is really smooth

00:12:24.079 --> 00:12:27.040
not bad at all

00:12:27.200 --> 00:12:32.000
ah i mean the game is called doom so you

00:12:30.560 --> 00:12:40.000
know i think we have our answer so

00:12:36.000 --> 00:12:42.560
can you do it the answer is yes

00:12:40.000 --> 00:12:46.000
so yeah it's a pretty crap experience to boot off of all things considered but

00:12:44.320 --> 00:12:51.200
it's not designed for that kind of use and they're blazing fast for just

00:12:48.240 --> 00:12:54.959
straight reads and straight rights and i still think it's

00:12:52.959 --> 00:12:58.399
impressive that it works at all

00:12:56.160 --> 00:13:02.399
i mean the fact that you can run Windows off of something

00:13:00.399 --> 00:13:07.680
this big and it's usable not to mention that like

00:13:04.959 --> 00:13:11.440
okay compared to when i got into pcs the capacity

00:13:08.959 --> 00:13:16.320
is actually similar to what you might have gotten out of something like a mac

00:13:13.279 --> 00:13:18.480
store diamond max 9 like the hard drive

00:13:16.320 --> 00:13:23.920
i got for my first self-built computer was 120 gigs

00:13:22.480 --> 00:13:28.800
and that is freaking incredible because i like to

00:13:26.240 --> 00:13:32.160
tell myself that that wasn't that long ago

00:13:30.320 --> 00:13:36.240
private internet access supports a variety of vpn protocols and types of

00:13:34.560 --> 00:13:40.480
encryption and authentication allowing you to dial in exactly the level of

00:13:38.240 --> 00:13:45.440
privacy protection that you need they've got apps for Windows macOS Android iOS

00:13:43.120 --> 00:13:49.760
Linux and google chrome with support for others coming soon you can connect up to

00:13:47.440 --> 00:13:54.160
five devices at the same time like your phone your laptop your desktop and their

00:13:52.079 --> 00:13:58.720
apps include dns leak protection and ipv6 leak protection you can check it

00:13:57.120 --> 00:14:03.040
out today at the link in the video description and if you've already got it

00:14:00.560 --> 00:14:06.160
well you can give it as a gift as well so don't miss out

00:14:04.880 --> 00:14:11.360
so thanks for watching guys if you disliked this video you can hit that button but if you liked it hit like get

00:14:09.920 --> 00:14:15.040
subscribed maybe consider checking out where to buy the stuff we featured at

00:14:12.959 --> 00:14:19.199
the link in the video description though again not for booting Windows off of

00:14:17.279 --> 00:14:22.320
maybe just for like a very high speed camera for example uh while you're down

00:14:21.199 --> 00:14:28.000
there you can check out our merch tour which has cool shirts like the one i'm wearing as well as our community forum