He/Him. Formerly sgibson5150@kbin.social.

  • 4 Posts
  • 69 Comments
Joined 10 months ago
cake
Cake day: March 7th, 2024

help-circle



  • sgibson5150@slrpnk.netOPtoLinux@lemmy.mlvirtio-win question
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    22 days ago

    Forgot to include the boot/system volume. It’s a lovely time waster when you’re dealing with disk images that are hundreds of gigabytes in size that have to be copied over the network. 😆

    I’ll add Disk2hvd screenshots when I get a sec.

    Situation gets slightly more complicated if you had multiple drives in your system when you installed Windows, of course. Installer might put system volume on a different drive, so you’d have to image more than one drive to get a working system. Might get a little confusing as to which volumes should go in which image. There’s a tool called GWMI that might help with that since afaik the volume guids don’t show up in the Windows Disk Management snap-in.

    Edit: The promised screenshot. In my case, I knew the volume labelled SYSTEM resided on the same disk as my C: drive. Probably don’t have to include the recovery partition, strictly speaking, but I did.










  • Worst example is friend who, after being hospitalized for accident while car surfing, died car surfing again. I wasn’t present for either event.

    Second worst is dude with head injury (unrelated) started talking about crystals and toxins and juice fasting. Called him out one day, and it was catastrophic. This one is still alive, at least AFAIK.

    Third, divorce. You will find out who your real friends are when you get divorced.