Cannot run shell script command to install pen tablet

[TheMuffinMan]

I am trying to install the Star03 Linux Driver for the xp pen drawing tablet on my CentOS KDE Plasma desktop. However, the shell script file cannot execute and is not even recognized as being present. I have tried everything that I can think of such as writing an environment variable path to the /usr/lib/x86_64-redhat-linux6E/lib64, I have made it executable. I have checked the shell scripting to see if maybe there was a space in the first line of the script where the bin folder is referenced, I have tried executing it from both out of the folder and in the folder which results differently but both do not work. From out of the folder execution, by just dragging and dropping the file inside a terminal that is not opened in that folder I get this result out of the bash command:



[root@localhost]# '/home/justin/Documents/Linux Beta Driver(20190820)/Linux Beta Driver(20190820)/Linux_Pentablet_V1.3.0.0/Pentablet_Driver.sh'

basename: extra operand ‘Driver(20190820)/Linux’

Try 'basename --help' for more information.

/home/justin/Documents/Linux Beta Driver(20190820)/Linux Beta Driver(20190820)/Linux_Pentablet_V1.3.0.0/Pentablet_Driver.sh: line 10: /home/justin/Documents: Is a directory

[root@localhost Linux_Pentablet_V1.3.0.0]# sudo Pentablet_Driver.sh

sudo: Pentablet_Driver.sh: command not found



Otherwise by opening the folder up in the terminal and executing it as root, I just receive this response:



[root@localhost Linux_Pentablet_V1.3.0.0]# ./Pentablet_Driver.sh

./Pentablet_Driver.sh: line 1: Pentablet_Driver.sh: command not found



Does anyone have any idea how I can install the XP-Pen tablet on my CentOS desktop and why it is currently not working for me?

[northpoint]

Get rid of the "(" " )" in the paths and it will probably work fine.

[TheMuffinMan]

No, that will give the error:

bash: syntax error near unexpected token `('

[TheMuffinMan]

I was able to get a driver on however it was not the driver that I was expecting it to be. But, it worked just as it should have.

[lightman47]

For future reference, try using bash (or sh) to run scripts and see if that works. For example to run 'scriptname.sh': bash scriptname.sh