A lighter version of screenconnect that uses mono version 3.4 works good on angstrom 6.20 and the latest image 9.4 but does not work with debian or ubuntu any version for bbb.
The newer version 4.0 stable did not work on anything at all until the beta 4.1 in which only worked mostly stable on the angstrom 6.20 image, but once flashing to 9.4 it installs fine but never lets you set it up via the webpage setup link. Ubuntu and Debian not working of course. So it seems that the screenconnect team worked with some hacks to get the more mono intensive version of 4.1 to work but nowhere near as stable as on a windows machine. After researching out the links to requesting a good pure version of mono for armhf, My findings are somewhat confusing to if it should work or not. I will just take my gut feeling that the armhf needs master repositories for mono that is hard-float and not just patched to work. Screenconnect seems to continue to develop more and more features and that means mono for armhf will be less and less reliable because its just patched to barely work. After posting my request on the screenconnect forum there was only 24 hits to my link to ask for community support. This means I am a very small minority to want to have someone for free, write over 500 lines of code and adjusting headers. I think unless the developer of screenconnect figures this out, I will have to either use windows laptop to host the server, or i can use my beaglebone black as a server but stuck on angstrom 9.4 image only able to have a great stable 3.4 version of screenconnect to do my job supporting customers remotely. I am a total newb about what it takes to write code and make things work in linux and am pretty sure it takes great efforts to make anything work on proprietary computers like the beaglebone. Time will tell...mono or not to mono. On Wednesday, January 8, 2014 9:50:01 AM UTC-6, Jacob Bell wrote: > > all this help is appreciated, but is over my head, even the reporting mono > to debian group and mono group I dont follow. I will try to get the > screenconnect people to help acomplish this. I am just a user that wants a > low powered cheap computer to run screenconnect and debian has other nice > packages I could use for other things so I can multi-purpose it for greater > value and usefulness. I at this time am forced to return to the stock > Angstrom 6.20 image and reinstall screenconnect there where it works > decent. It just isnt any fun to have to find how to tweak the image with > all that garbage (cloud9, Bonescript, etc) going and hogging resources in > one way or the other. Angstrom does not cut it when it comes to other > guides to install such and such to work because nobody uses angstrom, most > guides are in debian or mostly ubuntu. > > > > On Wednesday, January 8, 2014 9:31:24 AM UTC-6, David Goodenough wrote: >> >> On Wednesday 08 January 2014 09:26:53 Robert Nelson wrote: >> > On Wed, Jan 8, 2014 at 9:25 AM, David Goodenough >> > >> > <[email protected]> wrote: >> > > On Wednesday 08 January 2014 07:18:34 Jacob Bell wrote: >> > >> I take it Ubuntu is in the same boat? >> > >> >> > >> I really dislike angstrom. >> > >> >> > >> Is there any way to make mono available. What can I do to get this >> going >> > >> to work with Debian? >> > > >> > > According to the Debian package pages, mono is available for ARM, but >> only >> > > armel not armhf. It might be worth going to the mono list for debian >> at >> > > [email protected] and asking if it is simply that >> > > no one has gotten around to building it for armhf, or if there is >> some >> > > reason (like the JIT has some assembler code which is endian >> dependant and >> > > no-one has rewritten it for armhf). If there is a call for it they >> might >> > > try building it for you. >> > >> > See: https://lists.debian.org/debian-arm/2012/02/msg00000.html >> Yuk! It still might be worth a try as that was nearly two years ago. It >> might also be worth going back to the mono developers (non-debian) list >> and >> asking there. >> >> David >> > >> > Regards, >> >> >> -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
