KDMF Driver Deployment to Windows 7 Virtual Machine - c

I get the following error when I try to deploy the KDMF Driver template to a provisioned Windows 7 host:
error: Network debugging is not available for Windows versions 6.1 or earlier.
I've tried updating the host by installing the latest WDK and the Windows SDK. I'm at a loss for what to do.

For a Windows 7 VM, you will need to do kernel debugging through serial. If you are using HyperV, you can simply configure a virtual COM port that goes through a named pipe.
In Visual Studio, you can then configure your kernel debugger settings for serial debugging over a named pipe. Even outside of Visual Studio, that's the most reliable way I know to kernel debug a Win7 VM.

The target computer must be windows 8 or later for kernel mode debugging over a network.

Related

MsSQL driver which could not establish a secure connection by using Secure Sockets Layer (SSL)?

I use standard driver com.microsoft.sqlserver.jdbc.SQLServerDriver to connect to a MSSQL server. I run my program in Eclipse and encounter error:
Failed to obtain JDBC Connection; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException:
The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption.
Error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]"
My environment is openjdk version "11.0.11" 2021-04-20 LTS and the project use same JRE system library in Eclipse. The weird thing is, I package my project to JAR and it runs well in another machine, which is openjdk version "11.0.9.1" 2020-11-04 LTS.
A few months ago, I was able to run my program in the development environment, but now I fail. I may have made some changes to the development environment during this period, so I don't know if it has anything to do with the JDK version.
Any hint is welcome and thank you in advance.
Thanks for SchmitzIT! The thread is actually guide me to a workable solution which I would like to re-post here for a record!
https://aws.amazon.com/blogs/opensource/tls-1-0-1-1-changes-in-openjdk-and-amazon-corretto/
Above article have some valuable information which works for me:
JDK8 8u292 and newer, JDK11 11.0.11 and newer, JDK16 is disabling TLS 1.0 and 1.1
Modify (remove TLSv1 and/or TLSv1.1) jdk.tls.disabledAlgorithms in java.security configuration file located in the jre/lib/security folder for OpenJDK 8 or conf/security for OpenJDK 11 and higher will enable legacy TLS!
PS. But add a file enableLegacyTLS.security to override setting in java.security doesn't work for me (OpenJDK 11). Don't know why.

Can driver for Windows 10 Desktop be used for Windows 10 IoT directly?

On a Windows 10 Desktop, I can install Samsung's USB Driver for Mobile Phone, downloadable from Samsung's Developer portal, so that their mobile phone is recognisable in Windows 10 desktop when connected over USB port.
Since I don't have access to the driver source code, rebuilding the driver to be a Universal Driver is not an option. I'm also not sure whether this is already a universal driver or not.
So, the question is whether it is possible to directly use the driver binaries, such as .sys, .inf file extracted from the desktop driver on the Minnowboard Max running Windows 10 IoT? Would it be compatible? I noticed that in the GPIO sample driver project, in addition to the .sys and .inf file, a ACPI table dat file generated from ASL file is required for deploying the driver, is it possible to get around it if the desktop USB driver can be reusable directly?

Cannot debug over VPN - Visual Studio 2010

I have no trouble debugging from Visual Studio 2010 when I go to work and wire into the LAN.
However, when I telecommute over the corporate VPN, I cannot debug, because when I try to debug, the monitor correctly shows a status of <datetime> CONNECTED, but Visual Studio 2010 comes back with the "Unable to connect ...The remote computer cannot connect back to this computer" message.
There is no change in procedure between debugging from home or debugging from work; it simply won't work over the VPN...
The remote machine is my VM running on corporate servers someplace. I can ping my developer machine from the remote virtual machine, and I'm using Windows authentication mode. Both machines are Windows 7 64-bit.
The application I wrote is deployed using the full-trust mode of ClickOnce.
Why?
Here's what was wrong:
Our corporate firewall allows remote clients to come in via SSLVPN and see everything at the corporation. What our firewall does not have is the reverse rule which allows computers already within the firewall to see remote clients as soon as they log in.
Therefore, the machine being debugged, which was running MSVSMON.EXE, could not see the machine running the Visual Studio 2010 debugger.

Remote usb connection C

I'm trying to connect to an USB device that's on a remote PC (because there is no 64-bit driver for it, remote PC is 32-bit).
I know the commands that I need to send to make settings on the device but I don't know how I can get connected to it. Is there a C++ or C# library that makes it possible to connect to this device on a remote PC?
You might be able to build something using Microsoft's RemoteFX technology, assuming Windows is your target platform.

VNC or NX from Mac client to Linux server

I run an NX server and tightvncserver on my linux box (Ubuntu 10.04), with default settings.
I have NX client and Chicken of VNC on my Mac (Snow Leopard).
I'd like to share desktop of the linux server with my Mac client, i.e., control the existing Linux user session from Mac.
But it seems that on my Mac both NX and VNC connections start a new session on the server.
I'd love to know how to do a "desktop sharing" instead of standalone remote session.
Try winswitch - it will give you a GUI where you can start/stop sessions, the X11 display of your Linux machine will be shown as an existing session which you can "shadow"/"copy" via NX or VNC. (there are installers for macs and windows too)
If you want to do this by hand you can use x0vncserver for VNC and nxagent -S for NX, but then you will also have to deal with port configuration and IP/hostname addressing.. (as well as configuring nx DISPLAY environment variable which is totally non trivial)

Resources