Ontopic Random Computer-Electronics Thread

OMG what an embarrassing waste of time. Cloning the drive with Clonezilla resolved the issue.

:waw:
thats what the useless post i linked you to said :D

and that means you didnt fuckin wipe the eMMC completlely, because sector accurate cloning picked up a header that was on it and moved it to the new drive :D
 
thats what the useless post i linked you to said :D

and that means you didnt fuckin wipe the eMMC completlely, because sector accurate cloning picked up a header that was on it and moved it to the new drive :D
I'm sorry, but you're wrong there. It was totally empty. As confirmed by Windows Install, gparted, and the BIOS (which would fail to show it as a boot option when wiped).

I think the real fix was having an EFI partition on the new drive (as well as the eMMC). That really shouldn't matter, as BCD doesn't really care where you point it to load an OS, but here we are.
 
@fly i would look at running a Heroku or Foreman instance locally and deploying this to that local instance


this works for procfile based apps, which that one appears to be
ELI5 plz. None of that explains how to actually run github code locally.