I have no idea why it wouldn't work, are you using an display USB adapter?
Can you give me some details what your setup is. How many display adapters (what type) and what is attached to it?
Only thing I noticed is that there was USB mentioned in the XML, sadly there have been some problems with USB adapters before - but I was hoping that this was fixed now.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That is a very complex setup you have (from the point of the program). Unfortunately USB adapters have been always causing lots of trouble since those are apparently not that well supported by the windows API. I tried to come up with some windows API extensions for version 6 which made them work for simple setups, but apparently your setup is too much for the program to handle.
Especially since loading does not work at all (even before a reboot) I don't know if I can come up with a fix for your problem. 99% of all problems are related to rebooting the computer, if it doesn't work before a reboot then it's typically a windows API problem for which I can't do much about.
The only thing I can come up with right now is a very basic test version which disables the adapter ID matching completely, just to make sure that this isn't causing any trouble. You can get it here: https://drive.google.com/file/d/1d9c1M7t3sY8iH4ONrVMk_9Gl0B36GIe0
This is just the command line version with a new parameter called "-noIDMatch", this one will disable the ID matching completely. Be aware that it must be passed before the load parameter.
You can use it like this: MonitorSwitcher.exe -noidmatch -load:C:\Users\Martin\AppData\Roaming\MonitorSwitcher\Profiles\test.xml
If by using this version you are able to switch between profiles directly after saving them, i.e. without a reboot, then there might be hope. If not then there is unfortunately not much I can do since it then will be a windows API limitation with USB adapters.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the special verison - I will test it out when I am back in the office later this week.
I did do a bit of expermentation based on your guidance regarding the USB senario - I have a home setup where one display is DisplayPort driven natively off the laptop DisplayPort and another DisplayPort monitor off of a USB3 --> DisplayPort adapter.
In this configuration I was able to save and load a configuration file in v7 without problems.
I did a debug load just so you could see if interested.
Martin - good news the noidmatch option appears to work - I have done minimal testing.
primary4 setup is 4 monitors, 2 native displayport, 2 USB->DVI
tredmill setup is 2 monitors USB3-Displayport
I have captured the debug when loading each one for your review. I will do more testing but it appears basic switching back and forth works. I will check for the after reeboot / dock / undock scenarios
That is ineed good to know, so something is going wrong with the Adapter ID Matching. That means there is hope :-)
Unfortunately I do not have much time right now for working on the project, but please let me know how it behaves after a reboot (I would expect that it won't).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Windows 10 will not load profile. I have looked at the other posts regarding the issue and the Error 87 thread and not avail.
I am using the latest version posted ver 7.00, same error as previous verion 6 gave.
I have deleted the profiles, recreated and problem and errors do not change.
The debug log is attached
Let me know how I can help determine what the issue is, I have used the program for years using Windows 7 on the same machine without issues.
Kind Regards,
Bob Rion
Last edit: Bob Rion 2017-11-14
Very unfortunate that the alternative mode also fails for you :(
Can you also attach the xml file of the profile you were loading?
Does it only fail to work after a reboot or does it never work at all?
Martin - sorry for the delay
It fails on all launches, even after just creating a new profile and then trying to immediatley reload it.
Attached is the xml
I have no idea why it wouldn't work, are you using an display USB adapter?
Can you give me some details what your setup is. How many display adapters (what type) and what is attached to it?
Only thing I noticed is that there was USB mentioned in the XML, sadly there have been some problems with USB adapters before - but I was hoping that this was fixed now.
Martin
Yes I have 2 monitors attached to Native Display Port and 4 Monitors with USB Display Link adapters. This worked flawlesssly under Windows 7.
Anything I can do to help with a fix ?
Kind Regards,
BER
That is a very complex setup you have (from the point of the program). Unfortunately USB adapters have been always causing lots of trouble since those are apparently not that well supported by the windows API. I tried to come up with some windows API extensions for version 6 which made them work for simple setups, but apparently your setup is too much for the program to handle.
Especially since loading does not work at all (even before a reboot) I don't know if I can come up with a fix for your problem. 99% of all problems are related to rebooting the computer, if it doesn't work before a reboot then it's typically a windows API problem for which I can't do much about.
The only thing I can come up with right now is a very basic test version which disables the adapter ID matching completely, just to make sure that this isn't causing any trouble. You can get it here:
https://drive.google.com/file/d/1d9c1M7t3sY8iH4ONrVMk_9Gl0B36GIe0
This is just the command line version with a new parameter called "-noIDMatch", this one will disable the ID matching completely. Be aware that it must be passed before the load parameter.
You can use it like this:
MonitorSwitcher.exe -noidmatch -load:C:\Users\Martin\AppData\Roaming\MonitorSwitcher\Profiles\test.xml
If by using this version you are able to switch between profiles directly after saving them, i.e. without a reboot, then there might be hope. If not then there is unfortunately not much I can do since it then will be a windows API limitation with USB adapters.
Martin
Thanks for the special verison - I will test it out when I am back in the office later this week.
I did do a bit of expermentation based on your guidance regarding the USB senario - I have a home setup where one display is DisplayPort driven natively off the laptop DisplayPort and another DisplayPort monitor off of a USB3 --> DisplayPort adapter.
In this configuration I was able to save and load a configuration file in v7 without problems.
I did a debug load just so you could see if interested.
I will run further tests later this week.
Kind Regards,
Martin - good news the noidmatch option appears to work - I have done minimal testing.
primary4 setup is 4 monitors, 2 native displayport, 2 USB->DVI
tredmill setup is 2 monitors USB3-Displayport
I have captured the debug when loading each one for your review. I will do more testing but it appears basic switching back and forth works. I will check for the after reeboot / dock / undock scenarios
That is ineed good to know, so something is going wrong with the Adapter ID Matching. That means there is hope :-)
Unfortunately I do not have much time right now for working on the project, but please let me know how it behaves after a reboot (I would expect that it won't).
Martin
Yes as you suspected it fails after reboot with the -87 error - Any idean when you could take a look at required changes ?
Let me know if I can help in any way - your program is great for what I need and miss it daily.
Kind Regards,
Martin - Hope your Holidays were good. Any thoughts on when you could look at this again ?
Kind Regards,