datahoarder

10,710 readers

7 active

0 users here now

Who are we?

We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.

We are one. We are legion. And we're trying really hard not to forget.

-- 5-4-3-2-1-bang from this thread

founded 6 years ago

moderation log

moderators

archivist@lemmy.ml

“No device found” on FlashGBX: remember to install the CH340 driver! (thebrainbin.org)

submitted 1 month ago by Auster@thebrainbin.org to c/datahoarder@lemmy.ml

9 comments fedilink hide all child comments

"No device found" on FlashGBX: remember to install the CH340 driver!

#GameBoy #GBC #GBA #FlashGBX #datahoarder

Just spent 3 hours trying to figure why it wouldn't be recognized by either my main computer, a VM with USB passthrough, or an old laptop I did a fresh install of an older Win10 build just for testing the dumper.

Turns out I was missing the driver for it. =.=

With that in mind, besides warning of that, I'd also add that if you got ~~a throwaway computer you can stick Windows on~~ a computer with Windows on, that may be the best option, as the setup version of FlashGBX for Windows comes with the needed driver.

Also rambling a bit, but Windows' device manager makes more sense than Linux Mint's, or at least it shows when an "unknown device" is connected or unplugged. That helped quite a lot.

you are viewing a single comment's thread
view the rest of the comments

[–] Auster@thebrainbin.org [S] 1 point 1 month ago* (1 child)

@pastermil@sh.itjust.works I did try the day I made the post. Windows' device manager was more helpful because it updated as soon as I plugged or unplugged a device, even confirming something was indeed happening because the list blinked every time it was updated. Thus that allowed me to do it multiple times in a row while watching which entry appeared or disappeared from the list without the need to keep inputting the commands manually.

permalink

fedilink

source

parent

hideshow 1 child comment

[–] pastermil@sh.itjust.works 1 point 1 month ago

Well, what was the output like?

permalink

fedilink

source

parent