utsushi/scanner install not going good at all

telorast everything went swimmingly. easy peazy. except
1) as you suggest I copied deb/usr/share stuff into lib64 utsushi---the two folders in there (utsushi and doc) had binaries and archive files. but i stuck them in there all the same.

2)FAIL at symlink command. Brother do you have a symlink command?
I have 63 FAILED entries of the ln -sv command, failed spectacularly in every way you can fail in every fail combination including the dreadful 'already a file' message.

I think this is entirely do-able. Did I need to copy the two deb/user/share folders in lib64/utushi?
Brother do you have a symlink command?
here's one of my 63 greatest fails attempts today: sudo ln -s /usr/lib64/utsushi/esci-interpreter /usr/lib64/utsushi/utsushi/esci-gt-s650

Good times. Almost there. Glass half full. Let's do it.
Axios Thank you, too. In Solus there's a few ways to accomplish everything. In DEB there's 89 ways and the sheer volume of built-in redundancies in Deb's flavors--plus no deb is as good looking as solus)--make me have to remember every convoluted and over-complicated tasks/steps, then there's the 4 repos submitted with no reason. I flirted for a while (MX) but me and Deb are polar opposites. Ixnay on the $50 but I'm glad to see an option exists.

Axios It was suggested I dump all this stuff in my lib64/utushi:
deb/usr/x86/utushi:

and my share/x86/doc:

I'm not sure they belonged where it was suggested---as I interpreted said suggestion---I put them. I got some wonderful advice on how to execute this so I know I didn't get it all. On me.

Now:

Axios If it was me from the directories i posted above copy them over to the same location otherwise i think the symb links wont work not sure about that tho copy all those i showed above you will have some .0,some docs,and a .bin you must have the .bin as its the scanner firmware. and as the other gentleman said might need be root i read that online to somewhere but try it first without

by same location as it pertains to solus I don't know what you mean. deb lib to solus lib? deb share to solus share? and which exactly since these names are plentiful?
by same bin as the scanner firmware, I don't either. I found it's bin on the top picture and maybe put where it doesn't belong. throw that bin i which solus bin folder?
I'm an idiot in many ways. I spent 90 minutes understanding symlinks and I never understood them. There are targets and target files and target directories and it's all jibberish because I can't find any webpage smart enough to teach me contextualization....at least for what's left of my brain and the 90 min I had...
(instead of tangibles all websites visited had ls -something /path/to/directory /path/to/file..........or some combination of vague terms that I couldn't conceptualize).

the (terminal) errors weren't about 32bit they were about all my symbolizing being redundant 'file already exists'--a common theme.
I just need to wrap my head around
1) where do the deb plugin files go exactly in solus?
1a) do I need to extract the archived stuff from deb/utsushi and deb/share? archive them where?
2) how do I symlink to fix the broken 650 link?

Axios telorast you both mention changing all my sudo cp copied files to root. But after I copied them to lib folder and right-clicked them they were already root and resembled telorast 's picture exactly so they fixed themselves without my intervention?

all in all I appreciate your patience with me.

Axios telorast

I have files in wrong places. CP and MV commands I used yesterday successfully (I cut and paste them!) are useless today of course. Simple plans to rip out the detritus and start fresh with telorast 's commands, and Axios 's insight are of course scuttled. I'm the same cretin sunup to sundown. Linux is different every hour which keeps it interesting I suppose.

Making Solus see this scanner is what I imagine planning a cremation would be like. Except making it see a scanner has a demoralizing aspect a cremation does not. So maybe it's worse...The fault is mine (crappy research and blind faith) but I stand my analogy. Maybe I should write code

Be in touch soon gents. I will succeed with your help.
Many distros recognize the 650 plugin and interpreter for this scanner--but I have no interest in using any distro but Solus. Stay tuned. And thanks for your support.

telorast the .deb files and directories from /usr/share/doc to /usr/share/doc
followed precisely as I see it:

where does the binary factor in? is that in the right place?
I also have to force a handful of files to execute as root, too I think.
Thanks for the input. Almost there.

scanimage -dList of available devices:
v4l:/dev/video0
utsushi:esci:gt-s650:usb:/sys/devices/pci0000:00/0000:00:16.2/usb3/3-2/3-2:1

except for the two broken files that need to talk.
will google later! it's been an adventure.
If this goes i the toilet there's some epson non-flatbeds (continuous feed?) that I wonder are solus compatible? Box Store will be down for a trade maybe.

fingers crossed

you notice @telorast was very precise with saying directory or file? I hope my pictures of his 3 directives (copies) were accurate.

I didn't copy anything -R to preserve attributes but I'm thinking I should have.
Root took possession of them and won't let me make some the files executable (grayed out) via properties tab.

Hope I'm close. Feel like Sisyphus...

Axios the .bin file is the file that translates because that scanner needs a translator thats how it talks to your scanner yup from what i saw its in the right place

so much debris in my head. i forgot I mentioned the bin was not marked executable. and can't be thru permissions.
this is probably relevant.
will look for a permission command that does not lay strife on the file...tomorrow, which it almost is