Live data from Hacker News

Windows recovery environment and bootable USB creator in 200kb

github.com

41–50 of 50 posts

Re: Windows recovery environment and bootable USB creator in 200kb

#41
post #7

AFAIK the "Windows Recovery Environment" is actually a stripped-down minimal version of Windows missing most of the normal userland and parts of the kernel, which people have extended and customised in various ways.

The overall design was inspired by the simple text based ui of clockworkmod recovery for android. There are zero dependencies as well.

>clockworkmod recovery

Now there's something I haven't heard of in a while. I remember using it on the original Droid phone when messing with roms

Re: Windows recovery environment and bootable USB creator in 200kb

#42

Earlier quoted context omitted.

That still has the same issue. Powershell will refuse to run scripts that are not signed by default.

Sign the powershell script. It’s not that large of a hurdle to get a code signing cert, though it certainly isn’t trivial.

Code signing certs must have the key HSM’d these days. It’s a big hurdle.

Re: Windows recovery environment and bootable USB creator in 200kb

#43
post #33

Earlier quoted context omitted.

If you are writing a bat wrapper, you might as well write the wrapper in c# at that point (which I do for anything that requires a condition or a loop)

The threshold you’ve chosen is crazy low, for me. A condition or a loop? You’re writing everything in C# then. Everything worth writing, anyway.

Pretty much, yep. The batch file is just for pre providing arguments and checking awkward error codes from robocopy

Re: Windows recovery environment and bootable USB creator in 200kb

#44
post #19
post #8

Wow, this is the largest batchfile I've ever seen! And I thought my 200-ish line one from high school was pushing it. Honestly huge respect for having the dedication to go this far with batch. I knew about the pseudo-function-calling features and a little bit of the weird syntax, but just skimming there's a lot of stuff in here I haven't seen before. Usually people saying "X in Y KiB" are doing some crazy linker shen…

Speaking of large batch files, if anyone has ever softmodded a Wii, there is a good chance you used ModMii, which is by far the largest batch program I've seen. The main script [1] is a batch file that clocks in at over a megabyte. I used to be pretty into the Wii modding scene and remember talking with the author of that script about random batch things a few times. I can't imagine maintaining a file that big. [1] h…

21k loc, one file... dear god. that trumps it all, for sure. and wow, the repo is still getting active commits.

Re: Windows recovery environment and bootable USB creator in 200kb

#45
post #11

can I use this to install monitor drivers? make a bootable usb, add the installer onto the bootable usb and install the firmware? https://www.lg.com/au/support/product-support/cs-32GS95UE-B.... I thought about doing it through WINE, but that kinda scares me. unfortunately my monitor received new firmware only installable through an exe, I only have my linux desktop

Sometimes simple utilities like this are runnable under FreeDOS/MS-DOS booted from a USB flash drive and/or CD. Other times, you need Win32, and would use something like modern Hiren’s Boot CD, which is Windows 10 based iirc, unlike the original releases which were XP based iirc.

Re: Windows recovery environment and bootable USB creator in 200kb

#47

Earlier quoted context omitted.

That still has the same issue. Powershell will refuse to run scripts that are not signed by default.

Sign the powershell script. It’s not that large of a hurdle to get a code signing cert, though it certainly isn’t trivial.

You have to go through a humilating process to get it as well as pay few hundred $$$ to one of MS street vendors.

Re: Windows recovery environment and bootable USB creator in 200kb

#48
post #47

Earlier quoted context omitted.

Sign the powershell script. It’s not that large of a hurdle to get a code signing cert, though it certainly isn’t trivial.

You have to go through a humilating process to get it as well as pay few hundred $$$ to one of MS street vendors.

you have to prove who you are, yes. I don't know what you mean in the 2nd half of the sentence.

Re: Windows recovery environment and bootable USB creator in 200kb

#49
post #47

Earlier quoted context omitted.

You have to go through a humilating process to get it as well as pay few hundred $$$ to one of MS street vendors.

you have to prove who you are, yes. I don't know what you mean in the 2nd half of the sentence.

lemme explain quickly: you have to prove a lot of different things on paper, not just who you are; in reality this is just a money-milking side-hustle business for Microsoft. The process I had to go through had many different steps but in the end it all just relied on a blind trust between me and vetting team from the first step.

Re: Windows recovery environment and bootable USB creator in 200kb

#50
post #49

Earlier quoted context omitted.

you have to prove who you are, yes. I don't know what you mean in the 2nd half of the sentence.

lemme explain quickly: you have to prove a lot of different things on paper, not just who you are; in reality this is just a money-milking side-hustle business for Microsoft. The process I had to go through had many different steps but in the end it all just relied on a blind trust between me and vetting team from the first step.

lemme respond quickly: code signing certs are in use by many more than just microsoft. if i want a code signing cert from digicert, microsoft doesn't get any money, digicert does. i can use it for more than just powershell scripts, of course, i can sign anything. they are useful things to have. getting them is a pain in the ass, yes, but it's supposed to be. they want to filter out identity impersonators and do everything they can to issue a cert to a person that is who they say they are. that's the whole point of the cert, so that's why you must show all of that proof.
Post reply on HN