It is actually easier than you think. With the help of the devs, you could easily solve your problem, plus make them aware of the bug and fix it in upcoming releases. It might take a few days of messages on git back and forth with them, but in the end, yes, you will most probably solve your problem.
No, you Google the shit out of that particular problem, visiting reddit, forums, blogs and god knows what else, find a few bunch of registry files or reg snippets, copy/paste that, do a sanity check on each and every one of them, backup the registry (or a part of it at least), import them one by one in the hope that one of them fixes the problem… and then you discover that these were meant for Windows 7 and not 10 and that 10/11 had that shit removed or doesn’t actually obey that registry entry (a bug, they will fix it… some day…) and then just give up and learn to live with the problem.
They were transitioning to the new Metro look, that’s why the 10 different places for the same setting.
And seeing how slowly Control Panel is being transitioned to the new Metro Settings app, I’d have to guess that that thing is so deeply intertwined in the OS and so many things rely on it, that moving to something new is painfully slow.
My guess is, they had to run it in parallel. So many things relied on the old UI, not to mention run/cmd commands (printui, netplwiz to name a few), that simply just putting modern replacements for those things would have broken every single printer share, user credentials manager, etc., there is out there. So, they decided to run them in parallel. Smart choice if you ask me, since they own most of the desktop market share, if they decided to make a 180 turn on this, that would have cut a significant portion of their user market share… not to mention companies that heavily rely on MS products being pissed AF.
Never ever buy combo shit. Remember the DVD reader/CD burner combo crap back in the day? They were good at neither reading or burning anything. Thank god the fully featured DVD burners went down in price and these things died.
Read on the Mint forums a thread a while back, like from 2012 I think… someone had the same scanner as me and wrote to Hamrick about it, see if it’s supported. Unfortunatelly, no, it’s not… though this was a while back and maybe it’s supported now, who knows, will have to try I guess to know for sure.
In any case, VueScan has some generic drivers in it, but it’s far from that it supports every device out there. In general, it needs drivers for it to work, no different than any other scanning application.
Not everyone has top notch tech, or the money to afford it. 128GB for a phone is more than enough storage space, so if the price of the 256GB model is 30 or $40 plus, I’d opt for the 128GB model as well.
That's LTT in the bottom (lemmy.dbzer0.com)
Yeah yeah, we know you're special (lemmy.dbzer0.com)
Scanner: Microtek ScanMaker 3880, Chipset SQ113
Any progress on this, or is the 14 year old github repo I’ve been seeing the best thing?
Home Stalone (lemmy.dbzer0.com)
Flatpak be like... (lemmy.dbzer0.com)