#I will be constantly adjusting this OP to fit the needs of the community for clarity#

This is not urgent, as a matter of fact I am excited to jump in as a new member of the Slackware community for my first true Linux journey! I aim to keep a journal (hopefully daily) on fixing what I can. I will document any findings and update accordingly, this may take some time. After getting some good feedback and security advice, I will log everything offline initially. Over time I will organize my journal for others who may want to see what I did, and learn on what not to do. If you're feeling generous, feel free to take a look (or a laugh!) of my updates and comment down below on suggestions or insults. Either way I clearly suck anyway, so nothing can bring me down! Thank you in advance!

Current Setup:

• Host Operating System: Windows 10 Professional
• Host Hypervisor: VMWare Workstation Pro-15.5.6
• Virtual Machine that is being tested: Slackware--current

Current Hardware (just in case):

• Here

Legend:

• VMWare Workstation Pro: WP
• VMWare Tools: VMT
• Slackware--current: SWc

Synopsis:

After a full installation of SWc on WP, I proceeded with the VMT installation. Since then, I have been having strange issues.

Issues listed (updated as needed):

• Keyboard/Mouse on login is disabled (GUI/startx)
• LZMA compression failure on boot
  
• pings fail (after reboot w/ VMT installed)
  

This section is just an update. Check here to see what has changed.


UPDATE 9/7/2020: After blacklisting kernel updates through slackpkg (as prescribed from AlienBob) I am able to run SWc so far! The only hiccup I have right now is having to run this command every time on boot-up to stretch my screen nicely:
Other than that, I installed VLC got it working and I'm loving the challenge! Thanks again, AlienBob for the wiki and words of wisdom. I know you do a lot for the community, and I truly appreciate the work you put in. I will more than likely read this wiki more than man pages right now to really get the OS down over time. It will still be a challenge no doubt, but I will stay the course. I wonder if I could get that command to auto-run on a login after putting in my UserName/Password? It's not a big deal, because I'm really happy to be making positive progress. I will log my steps and edit them, along with posting what I did in a few days. Thanks again!!

as i remember, you need to use --ignore-errors to run the VMWare installer

I typically have been using this line within the pwd to install VMWare Tools:
Do I add "--ignore-errors" to the end of the command above? So it would be:



I will try this, but I don't why that would fix my mouse and keyboard from being completely disabled. Thanks for the feedback.

did you get the .bundle file? or did you extract them?

I don't know what the .bundle is, sorry. I'm super new to Linux, so there's a lot of things I probably won't understand right away. VMWare works fine on 14.2. I'm just having problems with "--current". It should theoretically follow the exact same procedure with installing the Tools addon for the VM. So to answer your question this is what I do:

• After I install and update, I am at my desktop (in full-screen mode)
• I navigate my cursor to the top of VMWare and allow the hidden panel to reveal the menus.
• I click "VM," then navigate down to "Install VMWare Tools," which is (counting bottom as 1) 2nd from the bottom.
• After the add-on notifies it is ready I extract the vmware-tools directory to the /tmp destination
• Using the CLI, I navigate to the folder and enter the commands I posted earlier for installing.
• I answer the questions, and everything works. Except after reboot, nothing is saved and devices start to fail.

Hi ul7.
In order to help you in a better way.
Can you precise those elements:
- it seems (according to the links you've posted) that the host machine runs on Windows. True?
-for the VMware tools install on the guest, I have noticed the same thing. After an upgrade (on the guest).
I have the same thing when upgrading the kernel on slackware-stable. As I don't really need the VMware tools most of the time, I didn't dig more about the problem.(when I want to use VMware tools, I reinstall them. Yeah, I know I'm lazy;-)).


Other thing about another of your questions. The bundle is the script which install VMware workstation on your host OS. The --ignore-errors is relevant when you're installing VMware workstation on a Linux host OS.

OK I adjusted the OP. Let me know if this isn't good enough.

OK, I saw that. So I have not those issues (e.g. keyboard/mouse and lzma). The only thing is that after upgrading kernel, the VMware tools need to be reinstalled on guest.
As I run on slackware-based systems since 1998, I must admit i'm pretty ignorant about windows. I well know how to wipe it out of the HD and a few things but that's all.
FYI, when you share docs, publish them in an open format (not.docx) some people are windows-phobic in the linux world. Prefer txt files or pdf if you want.;-)(and also avoiding google drive). Simply including your txt file as citation or code in your post is sufficient.
For record, a document any Linux user should have read, very useful when you begin.
http://www.catb.org/~esr/faqs/smart-questions.html

OK thanks, I didn't want to flood the main thread. I'm pretty new to all of this, including forums. I will adjust it over time. Thanks again.

We all have began, don't be afraid to make errors, this is the best way to progress.

I will update in a few days on what I did. Short summary: slackpkg is not something to just type without thinking. I learned that the hard way. I probably need to host Slackware on my machine without a hypervisor to confirm some more tests. I'm glad I'm learning in a VM now, rather than on the host. This thread is marked solved for now.