Currently I am working on signing a 64-bit driver for a USB tool which is used to scan areas of the skin.
My setup is like this:
DTM Controller and DTM Studio are
running on a Server machine (Windows
Server 2003 R2 SP2)
DTM Client running on a Client Machine (Windows 7 64-bit)
I have managed to run tests on the client, using DTM Studio, but I get a couple of errors and I´m not sure why but I have some ideas.
The failures I encounter are the following:
Run INFTest against a single INF
RunJob – Copy of CHKINF and INFTest Library Job
Could not find user specified INF files. Bailing out...
Could not expand user supplied list of infs into individual filenames.
Sleep Stress With IO
RunJob – Sleep_Stress_With_IO .
Device has issues and not ready for test. Device Problem Code is: 28
Disable Enable With IO
RunJob – Disable_Enable_With_IO
Device has issues and not ready for test. Device Problem Code is: 28
Common Scenario Stress With IO
Execute_Device_Status_Check_Script
Device has issues and not ready for test. Device Problem Code is: 28
When I located the INF file in DTM Studio and added the tests I received the error: „No devices using the specified driver“. This is off course correct as the machine running the DTM Client (Windows 7 64-bit) does not have the driver installed for the USB tool.
So my question is:
Do i need to install the driver for the USB tool on the client machine?
If that is needed then the client machine must run a different version of Windows which brings to me my next question:
Can I run Logo tests successfully for a Windows 7 64-bit OS when the Client (running DTM Client) is set up using a different OS?
I managed to answer my questions:
Do I need to i install the driver for the USB tool on the client machine?
Yes this is needed.
Can I run Logo tests successfully for a Windows 7 64-bit OS when the Client (running DTM Client) is set up using a different OS?
No. The client machine must be set up using the target OS.
Related
Doing windows driver development for first time, I want to deploy my first driver.
But I don't have a second computer.
Microsoft docs:
Typically when you test and debug a driver, the debugger and driver run on separate computers. The computer that runs the debugger is called the host computer, and the computer that runs the driver is called the target computer. The target computer is also called the test computer.
I am starting with vhidmini2 as my project base (the UMDF2 version).
I want to know if the Windows Sandbox feature can be used in place of test computer?
My driver will not be interacting with any hardware.
You can set up Windows Sandbox for kernel debugging with CmDiag (undocumented, but mentioned by Jonas L):
First you need to enable development mode (everything needs to be run from an Administrator command prompt):
CmDiag DevelopmentMode -On
Then enable network debugging (you can see additional options with CmDiag Debug):
CmDiag Debug -On -Net
This should give you the connection string:
Debugging successfully enabled.
Connection string: -k net:port=50100,key=cl.ea.rt.ext,target=<ContainerHostIp> -v
Now start WinDbg and connect to 127.0.0.1:
windbg.exe -k net:port=50100,key=cl.ea.rt.ext,target=127.0.0.1 -v
Then you start Windows Sandbox and it should connect:
Microsoft (R) Windows Debugger Version 10.0.22621.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Using NET for debugging
Opened WinSock 2.0
Using IPv4 only.
Waiting to reconnect...
Connected to target 127.0.0.1 on port 50100 on local IP <xxx.xxx.xxx.xxx>.
You can get the target MAC address by running .kdtargetmac command.
Connected to Windows 10 19041 x64 target at (Sun Aug 7 10:32:11.311 2022 (UTC + 2:00)), ptr64 TRUE
Kernel Debugger connection established.
(When I set this up initially I was getting some error when starting Windows Sandbox and I had to reboot, but this might not be necessary)
A few times I got error 0x80070020, this seems to be because the port isn't available (perhaps reserved by Hyper-V?). Switching to port 12345 fixed it for me.
The Windows Sandbox is basically a virtual machine, so you can load drivers into it as long as they do not need to interact with hardware.
But there is also one extra limitation: there does not seem to exist a way to disable the drivers signature check in the Windows Sandbox, as this requires a restart which is not possible for the sandbox. Thus, your driver has be signed to be loaded and tested.
EDIT: the Sandbox supports rebooting since Windows 11 Build 2250, so it should be possible to disable the drivers signature and install custom drivers now (cannot test though, still on W10).
I'm deploying windows 10 via SCCM on new computer it loads into PXE then reboot.. When I try ipconfig I'm not getting ip so I though it will be problem with NIC.. so I tried to load all available drivers for this desktop and still not working.. I'm out of ideas..
Thanks
"so I tried to load all available drivers for this desktop and still not working.. "
Did you mean that you add all drivers of this model into the boot image which associated with the OSD task sequence? If so, that is not recommended by MS. You should only import the actually required NIC drivers or storage drivers into the boot images(both x86 and x64).
Another important point here is you should add the NIC drivers match the boot image version instead of the OS version you are trying to deploy. For example, add NIC drivers for win10 to the boot image 10.x.xxxxx (which is from the ADK 10 RTM or later).
An application, consists basically on a communication between a microcontroller and a pc, is running perfectely on Windows 7 64 bits. Since i have windows 10 installed, the application doesn t work anymore. Even the serial communication isn t established. ( an error shown that the application can not establish the communication)
I have verified the microcontroller with other Terminal running on Windows and no Problem within. Also i think that the Problem could be on the Code, the application was created with visual Studio, well i don t have any experience with visual Studio,so that i would ask you if there is a way to check that this application for instance will not work on Windows 10!
Thank you in advance
You indicate that the application will run, therefore it is unlikely that the application is incompatible with Windows 10. You're getting an error saying that the application is unable to communicate with the serial port, so the application is opening. Most applications which flat out won't work with Win 10 use older, unsupported versions of .Net or expect a FAT filesystem and simply won't run.
This suggests that Windows 10 did not have a native driver for your serial port. This is not too shocking; the older pin serial ports currently see exclusive use and are replaced (for most users) by USB-connecting components. I would check the computer's Device Manager. If you don't see any serial ports there, or see them but with an error, Win 10 probably did not have the driver required. From there I would contact the motherboard or serial bus card manufacturer for updated drivers, if they exist.
I am working on this example on writing a simple Windows driver and debugging it from VS:
https://msdn.microsoft.com/en-us/library/windows/hardware/hh439665(v=vs.85).aspx
My Setup
Host: Windows 7 Physical system
Target: Windows 7 Physical system
Connection type: Serial cable (USB to serial in host, serial in
target)
Provisioning the target system is successful. Serial connection parameters are correct (tested the serial connection with different software). Driver is built and installed successfully in the target but "Break all" command does nothing. I am able to attach to a different process in the target.
I have seen similar questions and the usual response is to check for a mismatch between the connection parameters in the host and the target. I have checked this and the parameters are correct.
I would appreciate any advice.
Thanks!
I am working on a driver for a remote desktop server. Something like UltraVNC(in house protocol).
First of I see that mirror drivers are not supported on windows 8.
Only subset of DDI as a remote display driver.
1)
Does that mean I need to implement Remote Display Driver for windows 8?
2)Starting of with mirror driver and only adding the DDI specified here enough to have Remote Display Driver run on windows 8 (Will it install no windows 8)? It says that remote display driver is a subset of mirror driver.
http://msdn.microsoft.com/en-us/library/windows/hardware/hh974665(v=vs.85).aspx
3) Are there any any any examples? It looks like the mirror driver example is no where to be found ?
UPDATE : (on wdk 7.1) I found these examples.
4) I looked at Utlra VNC server source and It looks like they only have drivers up to Windows 7. However VNC SERVER still supports windows 8(for that it just does GDI stuff on user level to get the image update). So they have not implemented it.
There is a Remote Desktop Protocol Driver. Can that be used ?
5) what is the best place to start ?
Is this windows' way to limit remote desktop server implementation so that it is harder to compete with RDP.
6)
if implementing windows 8 implementing the DDIs necessary to have remote desktop driver is not enough to run it on windows.
Is the api below only way to do it on windows 8.
http://msdn.microsoft.com/en-us/library/windows/desktop/hh404487(v=vs.85).aspx
On Windows 8, there is a "Desktop Duplication API". With this API, it seems that you do not need to develop a driver anymore. Doc is here.
The "Remote Display Drivers" documented here is a bit mysterious...