Hi
You have been of much help for me. Thanks for all the information.
Because I thought "apt" was a typo on your part, I installed via apt-get!
Honestly, I have been gathering heaps of information so far here and there
online, and that's why I don't have apparently a clear understanding of
what I'm doing with all the software and gadgetry around me. Are you saying
apt installs different things than what apt-get would?

On Sat, Mar 16, 2019 at 1:17 AM Mala Dies <[email protected]> wrote:

> Hello,
>
> I think any vnc viewer should work. I use realvnc b/c of its simplicity
> plus their updates are nice. They have made it a long way from scrap to
> market place in time.
>
> Seth
>
> P.S. Did you ever get your updates to work? If so and if you are updating,
> did you ever install the xfce4 via apt or apt-get? I installed it and on my
> BBB, I still needed a tightvncserver install to make the desktop work.
>
> On Friday, March 15, 2019 at 10:46:52 AM UTC-5, Sardar Vayghannezgad wrote:
>>
>> Thanks a million for your support. Like I just posted, I'm connected now.
>>
>>
>>>  you already have the realvnc viewer on your Desktop client
>>>
>> Actually, I have tightvnc viewer. Isn't this different than "realvnc
>> viewer", which you mentioned? Was that a typo, or should I install realvnc
>> on my desktop too?!
>>
>> On Thursday, March 14, 2019 at 11:59:37 PM UTC+3, Mala Dies wrote:
>>>
>>> Hello Again Sir,
>>>
>>> Yes Sir, I know this is getting repetitious.
>>>
>>> ...
>>>
>>> After you find a way to get online, this is the set of commands to get
>>> your system up and running w/ a Desktop Env. on the BBB.
>>>
>>> sudo apt install xfce4 tightvncserver
>>>
>>> I am sure you already have the realvnc viewer on your Desktop client.
>>>
>>> Seth
>>>
>>> P.S. If this is getting boring, I am looking into more options but try
>>> the SD Card w/ MachineKit and a Ethernet cable.
>>>
>>> On Thursday, March 14, 2019 at 1:49:16 PM UTC-5, Sardar Vayghannezgad
>>> wrote:
>>>>
>>>> Thanks a lot for your reply. What I end up seeing on puTTY after typing
>>>> sudo apt-get install [no matter what!]" is the following:
>>>> Reading package lists... Done
>>>> Building dependency tree
>>>> Reading state information... Done
>>>> E: Unable to locate package xfce4
>>>>  the last line, actually. And like I said in the original post, this
>>>> happens still when I can ping to google. To the best of my knowledge if you
>>>> can ping to google, you are connected, right?! And thus you must be able to
>>>> download, but I am not. I'm coming to the conclusion that this primarily
>>>> has something to do with BBB driver not appearing on my device manager,
>>>> despite thatI have installed the drivers from BeagleBoard/getting-started.
>>>>
>>>> On Thursday, March 14, 2019 at 7:19:27 PM UTC+3, Mala Dies wrote:
>>>>>
>>>>> Oh and Sir,
>>>>>
>>>>> You might want to try, b/c the typing on the X client is showing
>>>>> incorrect values, XFCE for your desktop client. I found that this works at
>>>>> times, too. Here: https://www.xfce.org/. If I am not mistaken, you
>>>>> can just use "sudo apt install xfce4."
>>>>>
>>>>> Seth
>>>>>
>>>>> P.S. I need to double check the apt install xfce4 cmd but I think that
>>>>> is it. I will keep looking around for other info. I have been waiting to
>>>>> get into this idea, the Machine Kit stuff, but I have been unable to find
>>>>> time. I will reply soon.
>>>>>
>>>>> On Thursday, March 14, 2019 at 1:16:50 AM UTC-5, Sardar Vayghannezgad
>>>>> wrote:
>>>>>>
>>>>>> Hi all,
>>>>>> I have been struggling for the past ten days, as a brand new user, to
>>>>>> get my Beaglebone Black rec C (element 14) to run Machinekit on my Win 
>>>>>> 8.1
>>>>>> PC. To save you the long story, I am totally lost. What I've been able to
>>>>>> learn during my time playing with all the software and hardware
>>>>>> around me from forums, blogs, sites, personal intuition, etc comes
>>>>>> down to:
>>>>>>
>>>>>>    - successfully flashing an image on a microSD card and then
>>>>>>    transfer them on to the BB-Black, so that it can run without the 
>>>>>> flash card
>>>>>>    inside,
>>>>>>    - connecting BBB to my PC via puTTY and to the internet (albeit,
>>>>>>    apparently Google only, as I cannot have puTTy download any packages)
>>>>>>
>>>>>> Since I am desperately looking for some dummies pointers on the
>>>>>> issues I have, I'm giving all the software/hardware coordinates I
>>>>>> think are important:
>>>>>>
>>>>>> The image I'm using is from here
>>>>>> <https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit>
>>>>>>
>>>>>> My Questions are:
>>>>>>
>>>>>>    1. BBB does show up on my PC with the default image
>>>>>>    <https://beagleboard.org/latest-images> it comes out with, and I
>>>>>>    can go through the instructions available on Beagleboard/getting
>>>>>>    started webpage <https://beagleboard.org/getting-started#step2>,
>>>>>>    but once I replace it with another Image
>>>>>>    
>>>>>> <https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit>,
>>>>>>    it doesn't seem to appear as a drive on my PC nor anywhere on the 
>>>>>> Device
>>>>>>    Manager. However, I can putty it to my PC, and share my PC WiFi with 
>>>>>> it.
>>>>>>    Given that I have installed the required drivers from BBoard
>>>>>>    Getting Started <https://beagleboard.org/getting-started#step2>,
>>>>>>    Is this normal?!! If not, What is it that causes this? (I have 
>>>>>> searched
>>>>>>    high and low online, but haven't come up with a concrete conclusion)
>>>>>>    2. I can use my PC WiFi to connect BBB to the Google per online
>>>>>>    instructions, yet any attempt, via puTTY, to download Machinekit
>>>>>>    Packages
>>>>>>    
>>>>>> <http://www.machinekit.io/docs/getting-started/install-runtime-packages/>
>>>>>>  (Just
>>>>>>    in case, is the link right for my case?!!) from the related website 
>>>>>> leads
>>>>>>    in the error:
>>>>>>
>>>>>> machinekit@beaglebone:~$ sudo apt-get install machinekit-xenomai
>>>>>> Reading package lists... Done
>>>>>> Building dependency tree
>>>>>> Reading state information... Done
>>>>>> E: Unable to locate package machinekit-xenomai
>>>>>>
>>>>>>
>>>>>> or
>>>>>> machinekit@beaglebone:~$ sudo apt-get install machinekit-posix
>>>>>> Reading package lists... Done
>>>>>> Building dependency tree
>>>>>> Reading state information... Done
>>>>>> E: Unable to locate package machinekit-posix
>>>>>>
>>>>>>               3. I have downloaded the Machinekit Client on my PC.
>>>>>> What else do I need? I can see online that I need download tightVNC 
>>>>>> viewer
>>>>>> both on my PC and on the BBB via puTTY. right? Provided that I can do so,
>>>>>> do I need to download a VCP (Visual Control Panel) like QtQuickVcp to use
>>>>>> in conjunction with Machinekit? Should I install this on my PC or BBB or
>>>>>> both?!!!
>>>>>>
>>>>>>             4. My keyboard is misspelling on ThightVNC window. How
>>>>>> can I fix this?
>>>>>>
>>>>>> Any help, however small, would be appreciated.
>>>>>>
>>>>> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/fa18a288-3cd2-4bee-a4f9-c5a5155d7caf%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/fa18a288-3cd2-4bee-a4f9-c5a5155d7caf%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAP_f9LQT4KZ_pYTFwq%3D8SBXyFBhUTsxyAJN%3DfT3ZvB44wppUyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to