Programming would be much more convenient if I could get a linux distribution to work. Unfortunately, what I managed to do instead was render my system unbootable, possibly even without it being my fault. This is my story.
Once upon a time, a young Zaka installed Ubuntu on his old laptop using wubi, an installer that actually runs under Windows! It worked without any major hitches and the Zaka was pleased.
Fast forward six or so years to the ugly future that is 2017, and things were very different. Wubi didn’t even work since he was using UEFI, and the unofficial fork that did work looked sketchy, so he tried to install it using a USB stick (okay, an SD card with an adapter to USB. It should work right, they’re both flash memory man… dad has a zillion sd cards and like zero pen drives).
The process was vaguely annoying but not too bad; download ISO, format the drive with rufus, try to install, get mysterious freezing crash! Okay, fuck that let’s try the acpi=off option for grub. Wew, setup actually starts. It’s sort of a pity how I couldn’t see any partitions and clicking any of the options on that screen caused a crash! Whew.
Okay fuck that, time to try this unofficial Wubi fork that supports UEFI and has unclear instructions clearly written by a very enthusiastic ESL. It seems to work, but I don’t use the MOK Manager the first time the option is given and then I never can for the rest of the time and eventually the boot seems to just skip over the grub thing and honestly fuck this shit.
Never say never! I download a Debian net install iso and do the now familiar bootable usb steps using rufus. It’s too bad my wireless firmware isn’t supported, because debian meow meow open source woof woof. Okay, I download the “with non-free firmware” iso instead, try again… it still doesn’t have the firmware I need, but I can do a minimal install at least. Wow. Ok so I actually have a working grub -> windows bootloader flow dual boot now, lemme try to manually install the firmware… oh yeah and I have to set it to not boot silently for some reason in grub to even get it to start, because for some reason not showing acpi errors (here we cum again!) makes the thing not boot. Wew. I put the firmware in /lib/firmware, it’s still not found during boot, the boot hangs later on, I wait, sigh, and hold the power button for 5 seconds to force shutdown for the umpteenth time that day, start it all up again, and…
I am currently using my bad old year 2010 faptop, getting a win10 install media thingy onto my totally-a-usb memory which is by now a micro sd in an sd card adapter in a usb adapter setup. It’s taking beyond forever. It may or may not let me reinstate the boot record. In either case, I should be able to preserve all important data SOMEHOW, though using a live usb for linux for recovery which would be my usual plan is kind of dicey when linux hates you.
All in all… this may or may not be entirely my fault, but my current message to whatever dev caused this is quite simply:
It is now the Future, and I am slighly less peeved. The Windows Media Creation tool is a piece of shit-stained vomit; it downloads a ~3gb iso in like four hours where I could get it in one through http or bittorrent. It also crashed with an unhelpful error after working for like five hours when I tried to use it directly with a USB stick, so I instead made it download the ISO (again, rip the hours of progress lost), formatted the usb stick with rufus, and used that instead.
I tried to recover the bootloader in some way using the windows installation media, failed, used the command prompt to backup some files, and reinstalled windows. I suppose if nothing else, I don’t have any hp bloatware on this thing any more! …and it’s working fine so far, with no data loss. Now if you’ll excuse me, I have some studying to do to catch up for the time I lost… that I totally wouldn’t have used chatting instead. Adios!