infrared landscapeacabI was on Cohost! by mykocalico

objectively too many tv/anime/manga screencaps


photography, especially infrared



new music listening notes


  • no nazis, no terfs, no yimbies

last.fm recently played


Alt: The Cohost Daily Tag
cohost.org/TagOfTheDay
Landing Page
kukkurovaca.com/
Obsidian Vault / Psuedoblog
plaintextadventure.com/
Combined RSS Feed
kukkurovaca.com/rss.xml

cathoderaydude
@cathoderaydude

trying to back up the hdd on this ancient little UMPC. working on these things feels like trying to cajole a small, injured animal into eating

"honey. hey darling. come on, eat the usb drive. i know you know this is Software. you like Software. come on. please christ you dumbass eat the Software i am trying to save your life you are The Last Of Your Kind please act in self preservation"


cathoderaydude
@cathoderaydude

the device, by the way. little bastard computer

htc shift x9500. hugely popular in eastern europe for some reason; tons of people over there made custom roms for it and shit.

roms, because: yes, it came with window vist, but it also has a button that makes it switch to a horrifically limited copy of windows mobile that really, really does not want to be displayed on an 8" screen. what kind of monster would do this? answer: HTC

so anyway, the primary chip is an intel mobile processor based on the pentium-m that's so decrepit that it just identifies itself as "genuine intel processor 800mhz". like, that's literally the CPU identifier string. the winmo env runs on a second computer inside with an ARM11 SoC, and the button just KVMs between the two, so theoretically (unlike winmo-on-x86, which is a real thing that CAN hurt you, but has almost no viable software available) it can run arbitrary apps.

thus, there's a bunch of aftermarket shit to jailbreak the winmo env and do just that. people report... varied success. it's not a good idea anyway but i still absolutely had to have the Object, and i was lucky enough to find one in ukraine in perfect condition for a cold hundo. bad battery (owo inflates your cells big and round) but wcyd

i did not realize until after i received it that you can flip the screen up into Posting Angle and the first time i did it, i thought i was breaking the mechanism


cathoderaydude
@cathoderaydude

oh my god

i opened it up (a waste of time it turned out; the HDD is ZIF) and my first reaction was Wow What a Compact Unit, and my second was Wait Holy Shit THAT'S THE HARD DRIVE CABLE

IT HAS A HOLE IN IT FOR THE FAN


You must log in to comment.

in reply to @cathoderaydude's post:

in reply to @cathoderaydude's post:

checked in on this because the timeline seemed suspiciously familiar and yeah, the processor in the Shift was the first revision of what would become Intel Atom, before it officially had a name

wild

in reply to @cathoderaydude's post:

my procedure for taking a backup, was:

  • put clonezilla on a USB drive with enough free space to write the image to
  • (or) put clonezilla on any usb drive, use the "to ram" option, and have a USB drive big enough. I think this worked with the 1GB of RAM in my Shift.
  • boot clonezilla, and try to get to a root shell
  • run hdparm -N to check for the sector LBA sizes for the HPA (the hidden partition for Vista recovery)
  • you'll hopefully see /dev/sda: max sectors = some number/some larger number, HPA is enabled - if you do not, the HPA has been wiped or the HDD has been replaced without a clean image
  • keep both of those numbers safe somewhere, and set it to the larger of the two with hdparm -N the larger number

now the HPA is visible; now you can back it up with ddrescue and clonezilla.

  • mount the destination drive and cd to it
  • sudo ddrescue -d -f -r3 -P32 -S /dev/[device] ./[name]-image.ddrescue.img ./[name]-mapfile.ddrescue.map

Replace [device] with the device you want to back up. The entire device, so sda not sda1.

Replace [name] with the name you want to give the image.

Finally, before you return to the OS, after the imaging is all done, reset the HPA to its original size.

(oh, cohost ate the HTML in the comment. uh, that kinda sucks)

That's... huh. Maybe they put out a BIOS change or there was a revision they weren't doing HPA with. My CLIO110 had an HPA, and was dumped with that method.

Once dumped, I also tried to hijack the fn+f3 restore, but the BIOS/EC disabled the keyboard while recovery was in progress, after the "WARNING DATA GO BYE PRESS F10 TO CONTINUE OR POWER OFF" alert.

"wait, what do you mean, I don't even see the hard drive cable. i see the port on the side of the hard drive, though, so I'll start from there and follow it to see where it goes...oh noooooooooo"