Skip to main content

Posts

Showing posts with the label Windows

Roadmap until 2027 and beyond - Docklight / Docklight Scripting / VBScript / Windows 11

UPDATE 2025/09 - It seems that contrary to Microsoft's roadmap announcement some Windows 11 24H2 new installations come with the VBSCRIPT Windows Feature disabled by default. Please see our related Windows 11 24H2 troubleshooting info for more details and instructions to fix this.  Original news item from 2025/01, with updated release plan for Docklight V2.5:  As we have stepped into 2025, it's a good time to discuss our ideas for the future of Docklight and Docklight Scripting.  Docklight and Docklight Scripting have always been developed and maintained with an "it just runs" focus, carefully maintaining full compatibility and avoiding any breakage with any new release. At the same time, the software world continues to evolve or is even revolutionized by AI tools, and a newly designed Docklight today would certainly look different from our existing Windows offerings.  So let's provide some answers to some obvious questions. (And, no, I didn't ask ChatGPT to ...

Debugging USB HID applications

UPDATED 2016-06: See our latest extensions and USB HID related fixes for Windows 10 . Did you design a custom USB HID device and wonder why you cannot test its application protocol with the same ease as serial COM (RS232, ..) or network TCP connections?  Well we did, too, along with quite a few of our users. So it was high time to get this feature off the wishlist and into the software. See the Docklight FAQ - USB HID , or download the new software directly from here:  https://docklight.de/download/Docklight_Scripting.zip While we are still on our way to a concise and fully documented implementation, we found the current V2.0.200 version already very useful for our own projects with fullmo.de - a Microchip PIC based communication gateway running a custom ASCII protocol via USB HID. How to use Docklight Scripting V2.0.200 can connect to your custom HID device via the VID (vendor ID) and PID (product ID) code, if you use the following commun...