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 shenanigans, so this was refreshing.
Also, "Windows To Go" and "Windows To Stay" are really funny feature names.
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.
Not to get TOO far off topic, but you just reminded me of the 300+ line batch file I was using for my BBS back in the early 90s. Lots of errorlevel checks to handle door transitions, Fidonet, etc.
You could get some ridiculously complicated batch files if you really needed the added functionality.
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.
My process for this is usually:
- Poke at the EXE for a few hours to days. Sometimes it's just a self-extracting executable and you can just find the raw firmware binary. Sometimes you have to spend a few days relearning the basics of R2/Ghidra, and eventually can grab the firmware.
- Then, if you've found it, figure out how to load it. When you think you have an idea, make sure it's really late and you're deliriously tired, so you're SURE you can do it without bricking it. Plus, where's the fun in not bricking it? You can always take that random Pomona SOIC knockoff clip and start dumping random ROMs off whatever chips.
- Finally, if you were awake enough to not fall for the previous step - scrap all the work you've done, and commit to spending a while figuring out how to create a bootable windows USB. Or, if you can't get that to work for one of the many possible reasons, borrow a windows laptop. But you're probably too tired for that at this point anyway, so create a windows VM in QEMU, and repeatedly restart your machine as you mess with configs to get passthrough working for whatever you need to get the VM to connect to the device. Launch the utility, start the EXE - it starts working. Get so excited, you accidentally disconnect everything halfway through. Somehow the monitor seems to still work, but you swear there's just something not quite right about it. A few years later, take out the SOIC clip again.
(based on an agglomeration of my personal mishaps)
In all likelihood, yes - this project will likely allow you to do that perfectly fine! But I'd be prepared for the installer to be total bloatware that doesn't work or works for most of the process before something goes wrong.
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.
Is it really that unapproachable? I confess, I also prefer files that aren't 3k lines long, but when I have to deal with them, I basically deal with them as I deal with many files, one tab/split per "area" I want to work with. So if I'm working with three areas, I have three splits open that are focused on each area, and jump between the splits. Basically the same as if it was three files.
torphedo|1 year ago
Also, "Windows To Go" and "Windows To Stay" are really funny feature names.
Mogzol|1 year ago
[1] https://github.com/modmii/modmii.github.io/blob/master/Suppo...
Kwpolska|1 year ago
Writing a Batch script of any length, let alone 3085 lines, is completely insane with PowerShell being part of the default install.
Firehawke|1 year ago
You could get some ridiculously complicated batch files if you really needed the added functionality.
unknown|1 year ago
[deleted]
rosywoozlechan|1 year ago
theGeatZhopa|1 year ago
[deleted]
userbinator|1 year ago
_ol1s|1 year ago
holysheet|1 year ago
arthur2e5|1 year ago
https://www.hamilton.edu/academics/centers/writing/seven-sin...
firecall|1 year ago
Maybe situations where the standard recovery env is borked? Was that the case in the recent CrowdStrike debacle?
neRok|1 year ago
Nah, it still worked fine on my work laptop and allowed to boot in to safe mode, which also worked (didn't crash).
4jck|1 year ago
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
zxexz|1 year ago
In all likelihood, yes - this project will likely allow you to do that perfectly fine! But I'd be prepared for the installer to be total bloatware that doesn't work or works for most of the process before something goes wrong.
aspenmayer|1 year ago
windozedev|1 year ago
ChoGGi|1 year ago
https://www.hirensbootcd.org/
proneb1rd|1 year ago
diggan|1 year ago
letaem77|1 year ago
unknown|1 year ago
[deleted]
heraldgeezer|1 year ago
unknown|1 year ago
[deleted]
unknown|1 year ago
[deleted]
kosolam|1 year ago
windozedev|1 year ago
zx1000|1 year ago