installing Tiny Core Linux 7.2 on Vmware ESXi virtual machine

[nmm4829]

It looks like the command should be:

Code: [Select]

$ xrandr --output Virtual1 --mode 800x600

shows this message: cannot find mode 800*600

[Juanito]

did you enter 800x600 or 800*600?

[nmm4829]

did you enter 800x600 or 800*600?

i had used * instead of x.
thanks, now it works as expected, but tools in the bottom of the screen are not shown anymore in 800x600 resolution
( Exist, Editor, control panel,Apps,runprogram...)

[Juanito]

If they are not off the bottom of the screen, right-clicking on the middle of the bottom of the screen might bring them back.

If you click on the desktop background you will get a menu allowing you to start various applications.

[nitram]

If you meant wbar, quick and dirty, open a terminal:

Code: [Select]

tc@box:~$ killall wbar
tc@box:~$ wbar &


[nmm4829]

If you meant wbar, quick and dirty, open a terminal:

Code: [Select]

tc@box:~$ killall wbar
tc@box:~$ wbar &


Excellent !!! thank you very very very much dear Juanito and dear nitram
i achieved exactly what i needed in TCL
yes i meant the bottom toolbar which you called wbar
this command exectly did what i needed:
tc@box:~$ killall wbar
tc@box:~$ wbar &

now my final step here is to try adding these 2 lines of code in a startup file which i guess is the same onboot.lst to check whether my desirable setting will apply automatically every time my TCL virtual machine starts.
i that works, i will close this threat

[nmm4829]

i checked out onnbot.lst but seems false place to pase these 3 lines of codes:

xrandr --output Virtual1 --mode 800x600
tc@box:~$ killall wbar
tc@box:~$ wbar &

so what file in i can add above lines of commands so that everytime i power on my TCL virtuam machine, they be executed automatically ?
 i swear this would be my final question 

[Juanito]

You might want to read the tinycore book:

http://tinycorelinux.net/book.html

..onboot.lst is for loading extensions on boot.

/opt/bootlocal.sh is the place for commands to run on startup and /home/tc/.X.d is the place for commands to run when the gui starts.

[Juanito]

If you create a file such that:

Code: [Select]

$ cat /home/tc/.X.d/xrandr
xrandr --output Virtual1 --mode 800x600
..you won't need to restart wbar.

You can test by exiting to the prompt and then "startx"

You will need a backup for the xrandr file to persist across reboots

[nmm4829]

i am really sorry for my poor knowledge here. i am a Microsoft specialist and i have spent lots of years on Microsoft advanced networking services and i am an expert in my filed.
i can provide great help if someone needs on advanced windows server services.
but i am not familiar with Linux base and it is not reasonable to expect i be familiar with Linux base
because of that i need the exact procedure instead of getting a general help statement.
so if possible please provide me a precise step-by-step procedure in order to being able to do that.

for example i need someone tell me such guide:
open a terminal
type this command "...something...." to create a new script file here :  /home/tc/.X.d
inside that script file, type in these 3 lines of commands:
xrandr --output Virtual1 --mode 800x600
tc@box:~$ killall wbar
tc@box:~$ wbar &

[andyj]

If you read the instructions in the comments of the app you will see that there are client programs that need to be started when you log in. One goes in your .profile the other in .xsession. After this you can change the resolution by resizing the window. Host folders will work too if you have them enabled.

[Juanito]

You can create the file like this:

Code: [Select]

$ echo "xrandr --output Virtual1 --mode 800x600" > /home/tc/.X.d/xrandr

As already said, you will not need the wbar commands if the above command executes when the gui starts.

[nmm4829]

You can create the file like this:

Code: [Select]

$ echo "xrandr --output Virtual1 --mode 800x600" > /home/tc/.X.d/xrandr

As already said, you will not need the wbar commands if the above command executes when the gui starts.

Oh my God. eventually i achieved what i needed.
Juanito, you saved my life at last.
it is about 5 days i am struggling to achieve  this step.
now my TCL VM is started in 800x600 and wbar is shown.

thanks you very very much for all Guys helped me here.
really without knowing Linux basics, one can't do simple tasks.
thanks again.
if someone here needed any help on microsoft services, feel free to ask me.
i will be glad to help in order to thanks to your guides
sorry for poor English   
best regards for all guys here 

[andyj]

From the open-vm-tools app comments in open-vm-tools.tcz.info:

Comments:       Download and install in console before reboot; do not install while in X.
                Add to ~/.profile before startx to enable shared folders:
                        [ $(which vmware-checkvm) ] && [ vmware-checkvm ] && [ -d /mnt/hgfs ] && vmhgfs-fuse /mnt/hgfs
                Add to ~/.xsession after mouse-config to enable copy/paste, mouse grab/ungrab, and desktop resizing:
                        [ $(which vmware-checkvm) ] && [ vmware-checkvm ] && vmware-user &
                Move wbar to upper left vertical because wbar doesn't know when the desktop is resized.
                Aterm text does not render correctly, use lxterminal instead.
                Kernel modules removed, now all tools are userspace.
                Verify permissions for /dev/fuse are 1666.
                Loading the extension should create /mnt/hgfs. Verify that it happened and the permissions are 777.
                Files in shared folders will not be visible to anyone other than the user that
                        mounts them, including root. This is why if the shared folders are mounted
                        in a directory that is in a tree in /opt/.filetool.lst, backups will fail.
                Xorg and its dependencies are not needed for text only VM's.

Based on your posts, reading the instructions first might have saved a lot of pain. Also, I suspect that most of us are proficient at MS Windows too. I personally have been using MS OS's since 1986 (on a 4.77 MHz 8088 maxed out to 640 kB of RAM), so I'm familiar with their software. That's why we're using Linux 

[nmm4829]

From the open-vm-tools app comments in open-vm-tools.tcz.info:

Comments:       Download and install in console before reboot; do not install while in X.
                Add to ~/.profile before startx to enable shared folders:
                        [ $(which vmware-checkvm) ] && [ vmware-checkvm ] && [ -d /mnt/hgfs ] && vmhgfs-fuse /mnt/hgfs
                Add to ~/.xsession after mouse-config to enable copy/paste, mouse grab/ungrab, and desktop resizing:
                        [ $(which vmware-checkvm) ] && [ vmware-checkvm ] && vmware-user &
                Move wbar to upper left vertical because wbar doesn't know when the desktop is resized.
                Aterm text does not render correctly, use lxterminal instead.
                Kernel modules removed, now all tools are userspace.
                Verify permissions for /dev/fuse are 1666.
                Loading the extension should create /mnt/hgfs. Verify that it happened and the permissions are 777.
                Files in shared folders will not be visible to anyone other than the user that
                        mounts them, including root. This is why if the shared folders are mounted
                        in a directory that is in a tree in /opt/.filetool.lst, backups will fail.
                Xorg and its dependencies are not needed for text only VM's.

Based on your posts, reading the instructions first might have saved a lot of pain. Also, I suspect that most of us are proficient at MS Windows too. I personally have been using MS OS's since 1986 (on a 4.77 MHz 8088 maxed out to 640 kB of RAM), so I'm familiar with their software. That's why we're using Linux 

Thanks that was helpful but i still tell that without knowing some basics about Linux, we can't do simple stuff in this OS (but in windows we can).
if because of some bugs which exists in all operating systems, we give up an operating system completely, i think we are making big mistake.