|
I use RDC on a dual-monitor Windows 10 system (left monitor) to connect to a single-monitor Windows 7 system (right monitor). I can copy & paste between the two. Your experience is different, though, correct?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
I'm taking about copy & paste INSIDE RDC. Not from Host to Remote
In theory, theory and practice are the same. But in practice, they never are.”
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
|
|
|
|
|
I just now tried that, too, and it works as expected. I was using a couple of Notepad windows.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
I use plain old mstsc.exe (the standard RDP client), and it does work with multiple monitors, as long as they're adjacent. The trick is to make sure your .rdp file contains the correct monitor IDs - and they're NOT necessarily the same as those reported by the Display Settings utility. To get the correct monitor IDs mstsc.exe recognizes, run:
mstsc /l
...which will enumerate your monitors (the ID you need) and the resolution and coordinates they're running (that should be your indicator as to which monitor that line represents). In my case, as I'm writing this, it shows monitors 1, 3 and 5 (even though I only have 3 physical monitors hooked up) and based on the resolution shown, I know the correct IDs are 1 and 5.
Therefore, my .rdp file contains the line:
selectedmonitors:s:1,5
You CANNOT set this purely by using mstsc.exe's UI - this has to be done by manually editing the .rdp file with some text editor.
There's other settings that can be written to the .rdp file through the UI (telling it to use multiple monitors, etc). I'm not certain which of the following are necessary, but along with the line above, I also have these, which are probably related:
screen mode id:i:2
span monitors:i:1
use multimon:i:1
Bottom line is, I suggest you enable multiple desktops using the mstsc.exe UI, save the .rdp file, close mstsc.exe, and then manually tweak the content to ensure (a) the 3 lines above are there and (b) adjust the selectedmonitors line based on the IDs you're getting back.
Note that those IDs can change just by rebooting your system. It's annoying, but I don't know of any solution for that. Sometimes "#5" will become "#4", so I have to change that one line. If it goes back to #5, I change it back.
I also use mRemoteNG, but I never tried to get it to use more than one monitor at a time.
A co-worker of mine uses RDCMan from SysInternals, but I don't think it supports multiple monitors (or if it does, it's all-or-nothing).
|
|
|
|
|
While I appreciate you taking the time to reply, I'm not sure it answered my post.
When I'm in RDS, Copy & Paste doesn't work (Inside RDC, not Host to Remote. Copy text, past, nothing!), and the whole experience is reallllly slow. I've tried multiple 'fixes' over & over, with no luck. so I'm looking for an alternative.
In theory, theory and practice are the same. But in practice, they never are.”
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
|
|
|
|
|
Sorry, I thought you were focusing on multi-monitor support.
But, I do tend to stick with mstsc.exe, and generally, copy and paste does work.
|
|
|
|
|
I use Royal Terminal Services and have for years. The guy who created this is a CodeProject member and an excellent guy (naturally) to boot.
cheers
Chris Maunder
|
|
|
|
|
Thanks!
In theory, theory and practice are the same. But in practice, they never are.”
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
|
|
|
|
|
I see your copy+paste not working and rise it to copy+paste working across users.
I copy something in my session and you can paste it in your session.
That was RDC to a Windows Server 2012... really funny 
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.
|
|
|
|
|
Not talking about Users or Sessions.
Copy & Paste text INSIDE RDC not working
In theory, theory and practice are the same. But in practice, they never are.”
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
|
|
|
|
|
My guess is that there are several IT departments where I work scrambling to find a replacement.
I can already hear a director asking, "Is there any way we can get a copy of the codebase to maintain our own internal version of ICQ?"
|
|
|
|
|
By the way, the phrase "can we get a copy of the codebase to maintain our own version" should be heard as "now is a good time to update your resume"
|
|
|
|
|
Last time someone tried this, it was for MS Money. With no luck, unfortunately -> How to bin dump an excellent piece of software ... 
|
|
|
|
|
At least MS Money still works. Well, I've never used any of its online features, that is, so all offline functionality is still there and runs fine.
|
|
|
|
|
Sure. But I miss some modern features - like the filtersearch in comboboxes - and a few things I would have loved to implement. I actually see no point in keeping a source code sealed when it is not maintained anymore. I once started to reverse engineer, but that would be soooooo time consuming !
|
|
|
|
|
Rage wrote: I actually see no point in keeping a source code sealed when it is not maintained anymore.
Sometimes there are components that have been licensed that, themselves, are owned by third parties that are still very much under active development, and the licensing terms are such that it's an all-or-nothing type of deal.
Then there may by IP that they feel should be kept private.
Or there's a shared component that's re-used somewhere in another product that's still under support, and releasing the source would make it trivial to expose common vulnerabilities to anyone looking. Obviously security through obscurity should not be a thing, but the reality is, making the source public just lowers the bar.
I'm with you, there's plenty of abandoned closed source software I'd like to revive, even if only for my own use...but I just don't see that happening.
MS-DOS 4.x only got its source published a few weeks ago, and that was done, so they claim, "primarily for its historical importance". Don't get your hopes up for MS Money...
I've never used it myself, but HomeBank is free and has its source code available (I don't know however if it's open source according to the common terms), and claims to be able to open MS Money files. Depending on your goals, maybe you could take inspiration from that, even if only for the data import part...
|
|
|
|
|
MS Money still installs and works, even on Windows 11 v23H2.
|
|
|
|
|
Yes...I jumped into this thread to point that out.
|
|
|
|
|
Just as an aside. If you are still using MS Money there is a replacement Free Personal Finance Manager. | KMyMoney[^] . I think the two products are nearly identical.
I used to use it some time back and it looks like it is still supported. There used to be a conversion utility with it to import your MS Money database.
// TODO: Insert something here Top ten reasons why I'm lazy
1.
|
|
|
|
|
At least with MS Money, Microsoft made a free non-connected version available. The only problem is there is one version of Windows 10 where it didn't work, but someone with really good binary debugging skills figured out the issue and published the solution - on a Microsoft support site.
|
|
|
|
|
Another small rant, two-for-one.
1) Debugging console applications with parameters is painful.
I need to test against all the possible combinations of arguments, can't do it properly though, need to pass through the debug options... which are persistent.
And the console does not stay open (yes the checkbox is unchecked, also ignored by VS).
And the breakpoint after the parsing moves the focus to the VS window hiding the Command prompt.
Every test is a clickity-clickity-typety-clickity-clickity-clickity-clickity-clak.
![Elephant | [mastadon]](https://www.codeproject.com/script/Forums/Images/elephant.gif) you Microsoft.
2) Structures in watch window do not stay expanded.
Add other clickity-clickity-claks to a simple test.
Basically the best way to test this behavior is inserting test code and debug prints, as we used to do when we had to chisel bits one by one onto EEPROMS with tiny hammers and a lot of patience.
Told you it was a rant.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
The shortest horror story: On Error Resume Next
|
|
|
|
|
Sounds like a situation where unit tests would work well.
|
|
|
|
|
I like your thread subject  
|
|
|
|
|
Rename Main(...) to Main2(...)
Insert a Main() routine and make it call Main2 with your test cases.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
