I took the original SD card out of my inkpad and did most of the manipulations on the new card using my linux desktop. 840-c39e5f65-fw5.15.dd is the image of my new card extracted using dd. I am saving it in case I have to go through the process again with another new card. After rebooting with the new card, I went to the system menu and reformatted the new larger partition. This erased all of the old contents, so I had to copy over ebooks and applications again. I did that almost five years ago, so the details are hazy in my memory. It is possible that I tried to fix the original filesystem to save the contents and then expand it, but I vaguely recall not trusting the results and reformatting to start fresh.
My Inkpad is a bit of a pain to open, so I don't really want to take the card out and test it elsewhere. I still have another SD card with a previous attempt on it, so I tried that instead on my eeepc with Windows 7. It detected the card within a few seconds and asked me if I wanted to repair some problems it found. I said no, dismissed the popup for dealing with the contents, and was able to browse the contents of the VFAT filesystem using file explorer. I did not notice any unusually long pauses during any of that (although, to be fair, the eeepc is a painfully slow computer, so I'm used to waiting around for it to do stuff).
You can get a terminal on the device if you install pbterm on it (search this forum for that). Personally, I prefer using utelnetd instead to get a terminal session over telnet. I can use my desktop keyboard instead of the software keyboard in pbterm, and I can run vi in the telnet session.
|