|
jsc42 wrote: Does anyone know what the commands they used were If you didn't make a point of asking the engineer, when he was standing in your living room, what the password he was using to log into the control panel of the modem was, then it's too late now. That said, you could wait for the service to go south again (which from the tone of this post seems to be one of those pending inevitabilities which one savors like they savor a Korean stir-fry made of inshore hagfish) so be sure to ask then.
It's hit or miss these days. There was a time when the password was common knowledge and everybody could use it to actually set the appropriate up/down speeds. And being in contact with tech support you could brag in realtime how the modem was this or the modem was that. But lately, the password is more proprietary. If you ask for it from the guy in your living room he'll hem and haw and say something like "well, I shouldn't do this" then give it to you. Or, as was the case once back at the turn of the century, "where can I leave my laptop open to the multitab control panel app where the password is in the clear while I use your lavatory?". And you could ... well ... "see" it and write it down.
Good luck with all that. I'd say just go with an internationally renowned broadband service provider and ditch that small start-up "their copper" cable straddler. It's ultimately cheaper by the way AND more reliable.
modified 8-Apr-21 12:22pm.
|
|
|
|
|
RedDk wrote: But lately, the password is more proprietary. If you ask for it from the guy in your living room he'll hem and haw and say something like "well, I shouldn't do this" then give it to you
I understand that the current method to get such things is to use hidden cameras to covertly watch all angles of the room and ensure that one is able to track everything entered into their device. Allegedly.
Security, innit.
|
|
|
|
|
So, I have treated myself with a 5120 x 1440 ultrawide monitor, which for coding purposes works perfect. Loads of pixels available for VS2019 to use; toolboxes and 3 concurrent code files open next to each other. Life is great.
However... when screen sharing with a client during a Teams meeting, I can share either my "desktop" or a specific application. None of these works very well. Oftentimes, I need to swap between different windows during the meeting, and as such, I cannot use the "share an app" approach. Sharing the desktop is even worse, as my clients usually have standard 1920x1200 or that kind of aspect ratio, and would be presented with a very wide and very low image of my entire desktop.
So, I've reverted to quickly switching my windows resolution to 2560x1440 before starting screen share, and then back again after the meeting. It works, but is annoying.
A lot of people are requesting the "share a custom screen area" feature in Teams: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/38834104-share-custom-area-of-screen
Have any of you come accross something that can mitigate this until MS decides to implement this feature?
I once found a winforms application that allegedly should be only the "frame" or "windows" around an application, hence allowing the meeting audience to see through that frame. that way, one could share that particular application and effectively obtain a custom area of screen sharing. However, I cannot find that again (my google-foo must be low currently) and I cannot remember if it was possible to click on the applications "behind" the one acting as presentation area.
Other alternatives include
- use two inputs on the monitor simultaneously, hence having two 2560x1440 monitors in the windows display options, and you can share only one of them. Not suitable for me, due to "gaming requirements" on the same setup.
- use screen splitting like PowerToys FanzyZones or DisplayFusion, but those virtual "splits" are not recognized by Teams as indivisual desktops. So, no-go as well.
Any ideas? Or maybe someone knows the application or one like it?
/Jan
Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
|
|
|
|
|
Would getting a second monitor be an option?
You could also use that monitor as a test monitor to see what the UI looks like on a typical screen.
|
|
|
|
|
Fueled By Decaff wrote: Would getting a second monitor be an option?
it's his only option with Teams, I think. Great suggestion.
OP, get a second monitor that you use with screen shares. Or, get rid of the obnoxious monitor size.
|
|
|
|
|
Hacksaw? I dont have room for another monitor next to this monstrous thing...
Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
|
|
|
|
|
I had the same issue with my UHD 3840 x 2160 monitor that I run at native scale. No one could see anything clearly.
So, I bought a 1920 x 1080 monitor and mounted it to the wall (making sure I hit a wall stud) with a VESA articulating arm so I can move it in or out of the way as needed.
The great thing is that most phones and even people with older equipment can handle that res.
|
|
|
|
|
what about above it? I have seen monitor arrays 3 wide and 3 high that worked ok. Although that was in the days of smaller displays.
|
|
|
|
|
He can just send hhis obnoxious sized monitor to me!
CQ de W5ALT
Walt Fair, Jr.PhD P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
I would try using a virtual machine for the sessions. You can "clone" your physical system into a virtual machine. Set the resolution to something friendly for Team or Zoom meetings. Connect to your projects via shared folders.
Lou
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
That's what I was going to suggest.
Window mode for the VM and within the VM the standard resolution that the other people have.
Only difference... I would not clone the system, if only used for the meetings a trimmed down version would be better. No need to have the whole drivers and so on in the VM.
I usually use one with standard drivers, 1 CPU kern, 10% of my drive size and 50% of my RAM as max.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Thanks for the suggestion! As I understand it; I would need to have my dev environment running inside a VM, and work through an RDP connection, only to gain the ability to have everything running inside an app that would be shareable from the physical machines OS, right?
To me, thats more troublesome than executing my "switch to 2560x1440.bat" before the teams meeting and then the "switch to 5120x1440.bat" after the meeting.
Why, oh why, can't we just have an option in Teams to share a part of the screen...
Or have NVidia register the physical monitor as a number of physical monitors. That way, Windows wouldn't know the difference, and everything would work.
Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
|
|
|
|
|
Jan R Hansen wrote: Thanks for the suggestion! As I understand it; I would need to have my dev environment running inside a VM, and work through an RDP connection, only to gain the ability to have everything running inside an app that would be shareable from the physical machines OS, right? If need the whole set of tools of your main OS... then yeah it is more a PITA than a help.
Jan R Hansen wrote: To me, thats more troublesome than executing my "switch to 2560x1440.bat" before the teams meeting and then the "switch to 5120x1440.bat" after the meeting. I have bookmarked your message... I am waiting the delivery of one 34 Inches monitor... but for private, my old monitor will be the second unit for the work lappie.
Jan R Hansen wrote: Why, oh why, can't we just have an option in Teams to share a part of the screen...
We are speaking about Microsoft... aren't we?
Jan R Hansen wrote: Or have NVidia register the physical monitor as a number of physical monitors. That way, Windows wouldn't know the difference, and everything would work. That's actually a good idea, give them the suggestion, they are some better than others getting feedback from users.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
|
Let's hope they implement it... but just in case, don't hold your breath
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Anything past 640x480 VGA is always a risk.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Jan R Hansen wrote: 3 concurrent code files open next to each other
I have always wondered how you manage this. While I am now used to mouse drag or to winkey move the files from one screen to the other, how do you manage setting up windows on the same screen ? Is there any native support using keyboard shortcuts to place 3 files across the screen ?
|
|
|
|
|
not three windows, just visual studio with three documents inside.Just right-click any document header-tab and select "New vertical document group"
Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
|
|
|
|
|
After researching a bit, I found out that widescreens come with application that can split your screen in virtual screens, hence acting as if you would have several monitors, which also mean you can use the usual dual-or-more monitor features and key shortcuts of windows. This sounds really cool !
|
|
|
|
|
Yes - it "sounds" really cool. The problem is, that it doesn't hold water. You cannot divide my Samsung CRG9 49" 5120x1440 monitor (or similar monitors, from other manufacturers) into anything that *windows* recognizes as multiple monitors.
There are a number of software solutions, like (previously mentioned)
- GitHub - microsoft/PowerToys: Windows system utilities to maximize productivity[^]
- DisplayFusion: Multiple Monitors Made Easy by Binary Fortress Software[^]
Easy Setting Box | Monitor Solution | Samsung Display Solutions[^]
but all of these are software tools that adds a way of organizing windows into sections of the monitor in a more convenient way. Microsoft Teams allows you to share applications or "desktops". The latter being actual displays that windows recognizes as physical displays.
So unless your graphics driver is able to map the actual monitor as separate physical devices, you're out of luck with Teams. For all other purposes, the tools mentioned above work just fine. PowerToys and the samsung tool are even free, and DisplayFlusion comes in a free (feature-restricted) edition as well.
Being able to split the physical monitor to allow shortcuts like WIN-ARROWLEFT etc work for window snapping would be great, but not available as of now.
Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
|
|
|
|
|
I thought that you could use several windows virtual desktops with different resolutions, bit this does not work.
What you could do is install an app that allows you to switch the resolution quickly - Still a hassle, but at least you do not need to navigate-click in these user-unfriendly monitor setup menus from windows.
What *could* help is checking in the video card app (catalyst or whatever you have) if they have a feature that may come handy.
|
|
|
|
|
Thanks. I already have a .bat-file which executes a powershell-script, that switches to a given resolution. Very fast and efficient. but still less elegant than getting away with sharing a custom part of your screen.
this
Import-Module $PSScriptRoot\setScreenResolution\setScreenResolution -Verbose
Set-ScreenResolution -Width 2560 -Height 1440
executes this (which I copied from a MS resource somewhere)
Function Set-ScreenResolution {
<#
.Synopsis
Sets the Screen Resolution of the primary monitor
.Description
Uses Pinvoke and ChangeDisplaySettings Win32API to make the change
.Example
Set-ScreenResolution -Width 1024 -Height 768
#>
param (
[Parameter(Mandatory=$true,
Position = 0)]
[int]
$Width,
[Parameter(Mandatory=$true,
Position = 1)]
[int]
$Height
)
$pinvokeCode = @"
using System;
using System.Runtime.InteropServices;
namespace Resolution
{
[StructLayout(LayoutKind.Sequential)]
public struct DEVMODE1
{
[MarshalAs(UnmanagedType.ByValTStr, SizeConst = 32)]
public string dmDeviceName;
public short dmSpecVersion;
public short dmDriverVersion;
public short dmSize;
public short dmDriverExtra;
public int dmFields;
public short dmOrientation;
public short dmPaperSize;
public short dmPaperLength;
public short dmPaperWidth;
public short dmScale;
public short dmCopies;
public short dmDefaultSource;
public short dmPrintQuality;
public short dmColor;
public short dmDuplex;
public short dmYResolution;
public short dmTTOption;
public short dmCollate;
[MarshalAs(UnmanagedType.ByValTStr, SizeConst = 32)]
public string dmFormName;
public short dmLogPixels;
public short dmBitsPerPel;
public int dmPelsWidth;
public int dmPelsHeight;
public int dmDisplayFlags;
public int dmDisplayFrequency;
public int dmICMMethod;
public int dmICMIntent;
public int dmMediaType;
public int dmDitherType;
public int dmReserved1;
public int dmReserved2;
public int dmPanningWidth;
public int dmPanningHeight;
};
class User_32
{
[DllImport("user32.dll")]
public static extern int EnumDisplaySettings(string deviceName, int modeNum, ref DEVMODE1 devMode);
[DllImport("user32.dll")]
public static extern int ChangeDisplaySettings(ref DEVMODE1 devMode, int flags);
public const int ENUM_CURRENT_SETTINGS = -1;
public const int CDS_UPDATEREGISTRY = 0x01;
public const int CDS_TEST = 0x02;
public const int DISP_CHANGE_SUCCESSFUL = 0;
public const int DISP_CHANGE_RESTART = 1;
public const int DISP_CHANGE_FAILED = -1;
}
public class PrmaryScreenResolution
{
static public string ChangeResolution(int width, int height)
{
DEVMODE1 dm = GetDevMode1();
if (0 != User_32.EnumDisplaySettings(null, User_32.ENUM_CURRENT_SETTINGS, ref dm))
{
dm.dmPelsWidth = width;
dm.dmPelsHeight = height;
int iRet = User_32.ChangeDisplaySettings(ref dm, User_32.CDS_TEST);
if (iRet == User_32.DISP_CHANGE_FAILED)
{
return "Unable To Process Your Request. Sorry For This Inconvenience.";
}
else
{
iRet = User_32.ChangeDisplaySettings(ref dm, User_32.CDS_UPDATEREGISTRY);
switch (iRet)
{
case User_32.DISP_CHANGE_SUCCESSFUL:
{
return "Success";
}
case User_32.DISP_CHANGE_RESTART:
{
return "You Need To Reboot For The Change To Happen.\n If You Feel Any Problem After Rebooting Your Machine\nThen Try To Change Resolution In Safe Mode.";
}
default:
{
return "Failed To Change The Resolution";
}
}
}
}
else
{
return "Failed To Change The Resolution.";
}
}
private static DEVMODE1 GetDevMode1()
{
DEVMODE1 dm = new DEVMODE1();
dm.dmDeviceName = new String(new char[32]);
dm.dmFormName = new String(new char[32]);
dm.dmSize = (short)Marshal.SizeOf(dm);
return dm;
}
}
}
"@
Add-Type $pinvokeCode -ErrorAction SilentlyContinue
[Resolution.PrmaryScreenResolution]::ChangeResolution($width,$height)
}
Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
|
|
|
|
|
Or this[^], which is quite clever.
|
|
|
|
|
Nice find! That was the exact app I mentioned in my original post. The problem seem to be that it doesn't work as desired in teams anyway, however - here is the link for future reference
GitHub - john--/FauxDesktop[^]
Do you know why it's important to make fast decisions? Because you give yourself more time to correct your mistakes, when you find out that you made the wrong one. Chris Meech on deciding whether to go to his daughters graduation or a Neil Young concert
|
|
|
|
|
having read thru the responses. They have been quite good. I especially like the virtual machines thing. That might work. Then you just share the RDP window into the virtual machine.
I have alittle bit of this problem. Not a huge monitor like yours but fairly large and larger than my customers on my desktop. I just use my little old laptop and RDP to my main butt kicker and do my teams meetings from there. It work for me. and my laptop has a better camera and sound card.
To err is human to really elephant it up you need a computer
|
|
|
|
|