Sign in to follow this  
Followers 0
kjpolker

writing a kvm switch program

6 posts in this topic

I have 2 computers hooked up to 1 monitor, instead of going into monitor settings I was wondering if I could throw together a program that is always running and starts on boot up (that's easy) where I can set a hot key such as scroll lock+1(main comp) scroll lock+2(alt comp) and it does the work for me. This would be very very similar to a KVM switch that you can buy only through a program rather than a physical device. Any help or thoughts on this? I would write an example script but I don't know where to begin. Thanks for any help =)

Share this post


Link to post
Share on other sites



That would depend entirely on the driver for that monitor having a scriptable interface or a DLL you could call to programatically switch inputs.

So, what makes you think it has one?

:)


Valuater's AutoIt 1-2-3, Class... Is now in Session!For those who want somebody to write the script for them: RentACoder"Any technology distinguishable from magic is insufficiently advanced." -- Geek's corollary to Clarke's law

Share this post


Link to post
Share on other sites

#3 ·  Posted (edited)

Well if it's a driver it has to have ioctl commands. That's how drivers communicate with applications.

Edited by Richard Robertson

Share this post


Link to post
Share on other sites

Well if it's a driver it has to have ioctl commands. That's how drivers communicate with applications.

Yes, and since controlling the monitor's input selection is not going to be a native Win32 kernel built-in call, you would have to find applicable documentation of the monitor driver's available interfaces to know what call to make. At least, that was my interpretation...

:)


Valuater's AutoIt 1-2-3, Class... Is now in Session!For those who want somebody to write the script for them: RentACoder"Any technology distinguishable from magic is insufficiently advanced." -- Geek's corollary to Clarke's law

Share this post


Link to post
Share on other sites

Yes, and since controlling the monitor's input selection is not going to be a native Win32 kernel built-in call, you would have to find applicable documentation of the monitor driver's available interfaces to know what call to make. At least, that was my interpretation...

:)

And that, my friend, is why drivers are confusing. :)

Share this post


Link to post
Share on other sites

Okay well it sounds like I am leaving this program alone for a couple of years since I am not sure about half the stuff I heard =P Thanks for replies though.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0