Do you ever use the LInux box to remote into windows? I am having a heck of a time......

OK, so just for grins I checked this out.
At least on my 18.04, Remmina is part of the distributions and is ready to use. Near as I can tell, this has been around and included since Ubuntu 12 or so.
1) Open a terminal window.
2) Just invoke it: $ remmina
3) Pops up GUI window, offers choice of RDP, SSH and VNC connections. Select RDP. (Cute, I'll have to see how SSH does to another Linux box. Useful)
4) Enter Computer Name of remote Win box. ( You did enable remote access, right? Do select Network Level Authentication when enabling it in Windows Settings.)
5) Enter your username on that machine and, if needed, password.
6) You may need to adjust color settings if you'll get an error. The default H264 generated an error. I found 32 bit Truecolor to work.
7) Save this as default.
8) Connect.

If you're running BOINC on the Win box, you need to understand that GPU processing will stop during the RDP session. This is a Windows issue, in that the RDP handler has its own video driver, and shuts down the GPU driver while the RDP session is active. Always has, which is why when all my crunchers were still Win7/10 I never used RDP from the daily driver to do stuff on them.
There may be a way to save the connection info for the next session, but if so I didn't find it. Looks like the info can be found in remmina --help, though

Hope this is useful. Thanks for asking the question, glad I learned this for that one time I'll need it. :)
Later, Jim ...

---

Do you ever use the LInux box to remote into windows? I am having a heck of a time......

OK, so just for grins I checked this out.
At least on my 18.04, Remmina is part of the distributions and is ready to use. Near as I can tell, this has been around and included since Ubuntu 12 or so.
1) Open a terminal window.
2) Just invoke it: $ remmina
3) Pops up GUI window, offers choice of RDP, SSH and VNC connections. Select RDP. (Cute, I'll have to see how SSH does to another Linux box. Useful)
4) Enter Computer Name of remote Win box. ( You did enable remote access, right? Do select Network Level Authentication when enabling it in Windows Settings.)
5) Enter your username on that machine and, if needed, password.
6) You may need to adjust color settings if you'll get an error. The default H264 generated an error. I found 32 bit Truecolor to work.
7) Save this as default.
8) Connect.

If you're running BOINC on the Win box, you need to understand that GPU processing will stop during the RDP session. This is a Windows issue, in that the RDP handler has its own video driver, and shuts down the GPU driver while the RDP session is active. Always has, which is why when all my crunchers were still Win7/10 I never used RDP from the daily driver to do stuff on them.
There may be a way to save the connection info for the next session, but if so I didn't find it. Looks like the info can be found in remmina --help, though

Hope this is useful. Thanks for asking the question, glad I learned this for that one time I'll need it. :)
Later, Jim ...

HI Jim,

One thing to add: If running on a GUI (I use Cinnamon), the installation of Remmina will place an icon in the Internet section of the "start menu". That is how I start Remmina. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Tom,

I don't think anyone else has had as much problems getting the nvidia drivers to work on Ubuntu 18 as you.

True. And I have been disappointed about how "slow" the screen responds under Ubuntu compared to Lubuntu.

But since the Zorin was turnkey for the Nvidia drivers and seems to be running Boinc as well as Ubuntu did, while having a much more responsive screen like Lubuntu did, I think I will pretend it won't break or give me any "more" trouble and not touch it because it is not (currently) broken. ;)

Tom

---

A proud member of the OFA (Old Farts Association).

the ONLY problem I ever had was after running the coolbits command and writing an xorg.conf file, sometimes the bus ID gets changed of the GPU driving the monitor. ... just manually edit the xorg.conf file to return device/screen 0 to being the bus ID back to the GPU that shows the BIOS at boot.

sudo nano /etc/X11/xorg.conf
--make changes to file in nano--
[Ctrl]+X to save changes
reboot

That's been the issue that's plagued me on my HP boxes since day 1. Can't ever count on where the desktop is actually going to show up. The times I tried to change the xorg.conf file I ended up unbootable, and had to go back to the backup.
Must be about time for me to tackle that issue again, now that SETI is wound down and most crunchers are turned off, and figure out how I'm doing wrong something that should be so simple.

For anyone who is interested, I finally figured out my problem with trying to modify xorg.conf, and it was a strange one.
When trying to sort out which GPU was which, as it turns out nvidia writes PCI bus ID numbers in xorg.conf as decimal numbers, but it reports them via nvidia-smi in hexadecimal. On the HP boxes, the dec numbers of one GPU match the hex numbers of a different one, so each time I was editing ID 28h I was changing 40dec, as opposed to 28dec which was of course 1Ch. Wasn't immediately obvious, given that the first 4 GPUs were devs 04-05-06-07, which of course are the same either way.
Always the little things ...

---

. . I just thought I would keep this thread from oblivion ...

. . I miss the conversations that were so much a part of S@H, E@H is dead quiet by comparison. And it gets dead boring just humming along with my NVidia cards trundling along in OpenCL mode. Oh for the excitement of gurus making apps that lifted the productivity of those cards and the fun of tweaking them to get it right ...

Stephen

. . I just thought I would keep this thread from oblivion ...

. . I miss the conversations that were so much a part of S@H, E@H is dead quiet by comparison. And it gets dead boring just humming along with my NVidia cards trundling along in OpenCL mode. Oh for the excitement of gurus making apps that lifted the productivity of those cards and the fun of tweaking them to get it right ...

Stephen

+1

---

the ONLY problem I ever had was after running the coolbits command and writing an xorg.conf file, sometimes the bus ID gets changed of the GPU driving the monitor. ... just manually edit the xorg.conf file to return device/screen 0 to being the bus ID back to the GPU that shows the BIOS at boot.

sudo nano /etc/X11/xorg.conf
--make changes to file in nano--
[Ctrl]+X to save changes
reboot

That's been the issue that's plagued me on my HP boxes since day 1. Can't ever count on where the desktop is actually going to show up. The times I tried to change the xorg.conf file I ended up unbootable, and had to go back to the backup.
Must be about time for me to tackle that issue again, now that SETI is wound down and most crunchers are turned off, and figure out how I'm doing wrong something that should be so simple.

For anyone who is interested, I finally figured out my problem with trying to modify xorg.conf, and it was a strange one.
When trying to sort out which GPU was which, as it turns out nvidia writes PCI bus ID numbers in xorg.conf as decimal numbers, but it reports them via nvidia-smi in hexadecimal. On the HP boxes, the dec numbers of one GPU match the hex numbers of a different one, so each time I was editing ID 28h I was changing 40dec, as opposed to 28dec which was of course 1Ch. Wasn't immediately obvious, given that the first 4 GPUs were devs 04-05-06-07, which of course are the same either way.
Always the little things ...

I had known this for a long time. Guess, Nvidia decided to use "user-friendly" enumeration for the Nvidia X Server Settings and the xorg.conf file as they are user facing. But nvidia-smi sticks with the system device enumeration format which is hexadecimal.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

. . And petri remains in covert mode ...

. . Oh BTW ... Happy Bastille Day! :)

Stephen

? ?

. . Hi folks,

. . I thought I would point out an issue I have been experiencing. I was using Avast as my virus checker but since it's last update several days ago it has been attacking boinc.exe. I tried to make it an "exception" but no go there, Avast continued to cripple it, and also downed manager. So I have now had to remove Avast and rely on a different virus checker.

Stephen

:(

. . Hi folks,

. . I thought I would point out an issue I have been experiencing. I was using Avast as my virus checker but since it's last update several days ago it has been attacking boinc.exe. I tried to make it an "exception" but no go there, Avast continued to cripple it, and also downed manager. So I have now had to remove Avast and rely on a different virus checker.

Stephen

:(

Stephen go into your AV and just mark your BOINC folders exempt from being scanned. ;-)

Cheers.

Stephen go into your AV and just mark your BOINC folders exempt from being scanned. ;-)
Cheers.

. . When it came up I tried to set it as exempt but it still kept getting chucked out and flagged. :( It wasn't a file scan detected virus, it said it was a "behaviourally " detected virus :(

Stephen

:(

Wasnt seti no longer offering work?

---

Wasnt seti no longer offering work?

. . Yes SETI is in hibernation so far as volunteer processing of telescope data is concerned, but the backroom processing is in high gear even though it does not involve us plebs :)

. . However there are other programs still running on the BOINC network such as Einstein at home for which I am processing data. So when some random behaviour by M$ or a 3rd party antivirus utility screws up the BOINC folder and its operation it causes me grief. A few weeks ago M$ kicked off another unwanted 'fupdate' and since then Windows Defender is now very active on that machine when I am sure it was not before. I don't know if it is due to a bad interaction between Windows Defender and the other utes or just between WD and BOINC but since that update (and subsequent updates) the machine has been crashing boinc.exe and boinc.mgr sporadically and often. :(

Stephen

:(

Running Windows Defender here with no issues on 2 systems, although i've always had BOINC & it's data folders excluded, and while i've got all of my system updates delayed, Windows Defender still gets updated every few days.

---

Grant
Darwin NT

Running Windows Defender here with no issues on 2 systems, although i've always had BOINC & it's data folders excluded, and while i've got all of my system updates delayed, Windows Defender still gets updated every few days.

. . Yep, since WD has been active I get updates several times each week :(. But maybe it is something about the other antivirus utes that upsets things. If I could find the setting menu for WD I would try to stop it accessing the BOINC drive ...

Stephen

Running Windows Defender here with no issues on 2 systems, although i've always had BOINC & it's data folders excluded, and while i've got all of my system updates delayed, Windows Defender still gets updated every few days.

. . Yep, since WD has been active I get updates several times each week :(. But maybe it is something about the other antivirus utes that upsets things. If I could find the setting menu for WD I would try to stop it accessing the BOINC drive ...

Stephen

. . I have found the settings screen for the M$ WD, and I have set the BOINC folder as excluded. Now to see if the problems cease ? ? ?

Stephen

Running Windows Defender here with no issues on 2 systems, although i've always had BOINC & it's data folders excluded, and while i've got all of my system updates delayed, Windows Defender still gets updated every few days.

. . Yep, since WD has been active I get updates several times each week :(. But maybe it is something about the other antivirus utes that upsets things. If I could find the setting menu for WD I would try to stop it accessing the BOINC drive ...

Stephen

. . I have found the settings screen for the M$ WD, and I have set the BOINC folder as excluded. Now to see if the problems cease ? ? ?

Stephen

Unless you did a custom install you should have 2 BOINC folders and both need to be excluded Stephen, the data folder is normally hidden (and the most likely to trigger a false AV alert or problem) so you may need to unhide it to exclude it. ;-)

Cheers.

[Unless you did a custom install you should have 2 BOINC folders and both need to be excluded Stephen, the data folder is normally hidden (and the most likely to trigger a false AV alert or problem) so you may need to unhide it to exclude it. ;-)

Cheers.

. . Thanks, I will check on that ...

Stephen

Hey Wiggo,

. . How r things? Not much messaging happening these days. I noticed you have dropped one machine from E@H, not a technical problem I hope. I must admit I am taking advantage of an ongoing cold spell in Sydney to wind my boxes up. Sadly it won't last much longer and then I might pull the plug on the hot running units myself.

. . Keep well

Stephen

:)

PS howdy to Grant as well. And of course any of the usual suspects who are still reading the message boards.

Hey Wiggo,
. . How r things? Not much messaging happening these days. I noticed you have dropped one machine from E@H, not a technical problem I hope. I must admit I am taking advantage of an ongoing cold spell in Sydney to wind my boxes up. Sadly it won't last much longer and then I might pull the plug on the hot running units myself.
. . Keep well
Stephen
:)

G'day Stephen,
I've been keeping busy with a few other projects and trying to keep the yard under control while doing a bit of catch up brewing. As to my other rig, it needs cleaning out and I really don't need the heat that it throws out either so I just turned it off until the heat is required again. ;-)

As to staying well is up to me learning to slow down, but I'm getting reminded more often to do so. :-D

Have fun.