I’m using ‘DPInst’ to install my virtual com driver,
But the driver wasn’t installed correctly.The flag was set to ‘/f /lm’.
The content of log file is as follow:
INFO: ****************************************
INFO: 10/23/2006 14:04:40
INFO: Product Version 2.0.1.0.
INFO: Version: 5.1.2600 Service Pack 2
INFO: Platform ID: 2 (NT)
INFO: Service Pack: 2.0
INFO: Suite: 0x0100, Product Type: 1
INFO: Architecture: X86.
INFO: Interactive Windows Station
INFO: Command Line: ‘DPInst.exe /f /lm’
INFO: ****************************************
INFO: Current working directory: ‘C:\WINDDK\WDF\KMDF10\VCom\bin’
INFO: Running on path ‘C:\WINDDK\WDF\KMDF10\VCom\bin’
INFO: No valid ‘dpinst.xml’ file provided.
INFO: Install option set: legacy mode on.
INFO: Install option set: Force install if driver is not better.
INFO: Found driver package: ‘C:\WINDDK\WDF\KMDF10\VCom\bin\statbus.inf’.
INFO: Found driver package: ‘C:\WINDDK\WDF\KMDF10\VCom\bin\VCom.inf’.
INFO: Preinstalling ‘c:\winddk\wdf\kmdf10\vcom\bin\statbus.inf’ …
INFO: ENTER: DriverPackagePreinstallW
SUCCESS:c:\winddk\wdf\kmdf10\vcom\bin\statbus.inf is preinstalled.
INFO: RETURN: DriverPackagePreinstallW (0xB7)
INFO: ENTER: DriverPackageGetPathW
SUCCESS:Found driver store entry.
INFO: RETURN: DriverPackageGetPathW (0x0)
INFO: Preinstalling ‘c:\winddk\wdf\kmdf10\vcom\bin\vcom.inf’ …
INFO: ENTER: DriverPackagePreinstallW
SUCCESS:c:\winddk\wdf\kmdf10\vcom\bin\vcom.inf is preinstalled.
INFO: RETURN: DriverPackagePreinstallW (0xB7)
INFO: ENTER: DriverPackageGetPathW
SUCCESS:Found driver store entry.
INFO: RETURN: DriverPackageGetPathW (0x0)
INFO: ENTER: DriverPackageInstallW
INFO: Installing INF file “C:\WINDOWS\system32\DRVSTORE\statbus_03A410A2A11BE1575BF2E33B7A13BA91A51D4AD2\statbus.inf” of Type 6.
INFO: Looking for Model Section [Standard.NTx86]…
INFO: No matching devices found in INF “C:\WINDOWS\system32\DRVSTORE\statbus_03A410A2A11BE1575BF2E33B7A13BA91A51D4AD2\statbus.inf” on the Machine.
INFO: No drivers installed. No devices found that match driver(s) contained in ‘C:\WINDOWS\system32\DRVSTORE\statbus_03A410A2A11BE1575BF2E33B7A13BA91A51D4AD2\statbus.inf’.
SUCCESS:Installation completed with code 0xE000020B.
INFO: RETURN: DriverPackageInstallW (0xE000020B)
INFO: No matching device was found for ‘c:\winddk\wdf\kmdf10\vcom\bin\statbus.inf’. Driver will be installed when plugged in.
INFO: ENTER: DriverPackageInstallW
INFO: Installing INF file “C:\WINDOWS\system32\DRVSTORE\vcom_0D735A8AB9D403DA3B9367B174A84B7A53FF4A35\vcom.inf” of Type 6.
INFO: Looking for Model Section [MSFT.NTx86]…
INFO: No matching devices found in INF “C:\WINDOWS\system32\DRVSTORE\vcom_0D735A8AB9D403DA3B9367B174A84B7A53FF4A35\vcom.inf” on the Machine.
INFO: No drivers installed. No devices found that match driver(s) contained in ‘C:\WINDOWS\system32\DRVSTORE\vcom_0D735A8AB9D403DA3B9367B174A84B7A53FF4A35\vcom.inf’.
SUCCESS:Installation completed with code 0xE000020B.
INFO: RETURN: DriverPackageInstallW (0xE000020B)
INFO: No matching device was found for ‘c:\winddk\wdf\kmdf10\vcom\bin\vcom.inf’. Driver will be installed when plugged in.
INFO: Returning with code 0x200
INFO: 10/23/2006 14:04:43
Hi,
If you look at the com_vdd.htm that is vdd subdir in the DDK for Windows
2003 for example, you will set how to install Virtual Device Drivers that
utilizes the Virtualization hardware for x86 programs to run in v86, Virutal
8086 mode. Note you need only to copy your dll and to modify a registry
entry. I would guess that indeed DPinst will allow this. I do not know
DPinst but you could do this an inf file. You only need to copy you dll and
modify the Registry.
Anyway it is nice to see someone else looking at the way Microsoft
virtualizes DOS programs. I think it is real cool the way it is done with a
application by trapping on resources and then virtualizing the hardware.
Not the hardware state is not shared though.
By the way someone has been working with VISTA in this area because my
Virtual DOS Com driver that supports an old multiserialport vxd for Windows
95 were you can virtualize multiport COM ports by setting up just 2 things:
(1) What irq to use for the UART port and (2) what is the base io for the
port. This applications could be developed for more than just 4 Com ports
for Windows 95/98/Me. Cool this is done I think for Virtualization. Anyway
VISTA runs these Virtual COM ports much better. For example Procom would be
jerky when type between two Virtual COM ports in 2000, XP, 2003. But with
VISTA this is gone. ---- Smooth------
William Michael Jones
wrote in message news:xxxxx@ntdev…
> I’m using ‘DPInst’ to install my virtual com driver,
> But the driver wasn’t installed correctly.The flag was set to ‘/f /lm’.
>
> The content of log file is as follow:
>
> INFO:
> INFO: 10/23/2006 14:04:40
> INFO: Product Version 2.0.1.0.
> INFO: Version: 5.1.2600 Service Pack 2
> INFO: Platform ID: 2 (NT)
> INFO: Service Pack: 2.0
> INFO: Suite: 0x0100, Product Type: 1
> INFO: Architecture: X86.
> INFO: Interactive Windows Station
> INFO: Command Line: ‘DPInst.exe /f /lm’
> INFO:
> INFO: Current working directory: ‘C:\WINDDK\WDF\KMDF10\VCom\bin’
> INFO: Running on path ‘C:\WINDDK\WDF\KMDF10\VCom\bin’
> INFO: No valid ‘dpinst.xml’ file provided.
> INFO: Install option set: legacy mode on.
> INFO: Install option set: Force install if driver is not better.
> INFO: Found driver package: ‘C:\WINDDK\WDF\KMDF10\VCom\bin\statbus.inf’.
> INFO: Found driver package: ‘C:\WINDDK\WDF\KMDF10\VCom\bin\VCom.inf’.
> INFO: Preinstalling ‘c:\winddk\wdf\kmdf10\vcom\bin\statbus.inf’ …
> INFO: ENTER: DriverPackagePreinstallW
> SUCCESS:c:\winddk\wdf\kmdf10\vcom\bin\statbus.inf is preinstalled.
> INFO: RETURN: DriverPackagePreinstallW (0xB7)
> INFO: ENTER: DriverPackageGetPathW
> SUCCESS:Found driver store entry.
> INFO: RETURN: DriverPackageGetPathW (0x0)
> INFO: Preinstalling ‘c:\winddk\wdf\kmdf10\vcom\bin\vcom.inf’ …
> INFO: ENTER: DriverPackagePreinstallW
> SUCCESS:c:\winddk\wdf\kmdf10\vcom\bin\vcom.inf is preinstalled.
> INFO: RETURN: DriverPackagePreinstallW (0xB7)
> INFO: ENTER: DriverPackageGetPathW
> SUCCESS:Found driver store entry.
> INFO: RETURN: DriverPackageGetPathW (0x0)
> INFO: ENTER: DriverPackageInstallW
> INFO: Installing INF file
> “C:\WINDOWS\system32\DRVSTORE\statbus_03A410A2A11BE1575BF2E33B7A13BA91A51D4AD2\statbus.inf”
> of Type 6.
> INFO: Looking for Model Section [Standard.NTx86]…
> INFO: No matching devices found in INF
> “C:\WINDOWS\system32\DRVSTORE\statbus_03A410A2A11BE1575BF2E33B7A13BA91A51D4AD2\statbus.inf”
> on the Machine.
> INFO: No drivers installed. No devices found that match driver(s)
> contained in
> ‘C:\WINDOWS\system32\DRVSTORE\statbus_03A410A2A11BE1575BF2E33B7A13BA91A51D4AD2\statbus.inf’.
> SUCCESS:Installation completed with code 0xE000020B.
> INFO: RETURN: DriverPackageInstallW (0xE000020B)
> INFO: No matching device was found for
> ‘c:\winddk\wdf\kmdf10\vcom\bin\statbus.inf’. Driver will be installed when
> plugged in.
> INFO: ENTER: DriverPackageInstallW
> INFO: Installing INF file
> “C:\WINDOWS\system32\DRVSTORE\vcom_0D735A8AB9D403DA3B9367B174A84B7A53FF4A35\vcom.inf”
> of Type 6.
> INFO: Looking for Model Section [MSFT.NTx86]…
> INFO: No matching devices found in INF
> “C:\WINDOWS\system32\DRVSTORE\vcom_0D735A8AB9D403DA3B9367B174A84B7A53FF4A35\vcom.inf”
> on the Machine.
> INFO: No drivers installed. No devices found that match driver(s)
> contained in
> ‘C:\WINDOWS\system32\DRVSTORE\vcom_0D735A8AB9D403DA3B9367B174A84B7A53FF4A35\vcom.inf’.
> SUCCESS:Installation completed with code 0xE000020B.
> INFO: RETURN: DriverPackageInstallW (0xE000020B)
> INFO: No matching device was found for
> ‘c:\winddk\wdf\kmdf10\vcom\bin\vcom.inf’. Driver will be installed when
> plugged in.
> INFO: Returning with code 0x200
> INFO: 10/23/2006 14:04:43
>
>
William Michael Jones wrote:
If you look at the com_vdd.htm that is vdd subdir in the DDK for Windows
2003 for example, you will set how to install Virtual Device Drivers that
utilizes the Virtualization hardware for x86 programs to run in v86, Virutal
8086 mode…
Anyway it is nice to see someone else looking at the way Microsoft
virtualizes DOS programs. I think it is real cool the way it is done with a
application by trapping on resources and then virtualizing the hardware.
Not the hardware state is not shared though.
I hate to burst your bubble, but the original poster did not really mean
“virtual device driver” in the sense that you mean. He is referring to
a driver that offers a virtual COM port to 32-bit applications. A VDD
in the traditional NT sense is a 32-bit user-mode DLL; he is trying to
install a kernel driver written with KMDF.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Thanks Tim.
Sorry about the post. I thought Virtual for here meant VDD which is wrong.
You are talking about a kernel mode COM port redirector. The reply about
VISTA being much smoother is correct for the VDD though.
-cheers.
William Michael Jones
wrote in message news:xxxxx@ntdev…
> I’m using ‘DPInst’ to install my virtual com driver,
> But the driver wasn’t installed correctly.The flag was set to ‘/f /lm’.
>
> The content of log file is as follow:
>
> INFO:
> INFO: 10/23/2006 14:04:40
> INFO: Product Version 2.0.1.0.
> INFO: Version: 5.1.2600 Service Pack 2
> INFO: Platform ID: 2 (NT)
> INFO: Service Pack: 2.0
> INFO: Suite: 0x0100, Product Type: 1
> INFO: Architecture: X86.
> INFO: Interactive Windows Station
> INFO: Command Line: ‘DPInst.exe /f /lm’
> INFO:
> INFO: Current working directory: ‘C:\WINDDK\WDF\KMDF10\VCom\bin’
> INFO: Running on path ‘C:\WINDDK\WDF\KMDF10\VCom\bin’
> INFO: No valid ‘dpinst.xml’ file provided.
> INFO: Install option set: legacy mode on.
> INFO: Install option set: Force install if driver is not better.
> INFO: Found driver package: ‘C:\WINDDK\WDF\KMDF10\VCom\bin\statbus.inf’.
> INFO: Found driver package: ‘C:\WINDDK\WDF\KMDF10\VCom\bin\VCom.inf’.
> INFO: Preinstalling ‘c:\winddk\wdf\kmdf10\vcom\bin\statbus.inf’ …
> INFO: ENTER: DriverPackagePreinstallW
> SUCCESS:c:\winddk\wdf\kmdf10\vcom\bin\statbus.inf is preinstalled.
> INFO: RETURN: DriverPackagePreinstallW (0xB7)
> INFO: ENTER: DriverPackageGetPathW
> SUCCESS:Found driver store entry.
> INFO: RETURN: DriverPackageGetPathW (0x0)
> INFO: Preinstalling ‘c:\winddk\wdf\kmdf10\vcom\bin\vcom.inf’ …
> INFO: ENTER: DriverPackagePreinstallW
> SUCCESS:c:\winddk\wdf\kmdf10\vcom\bin\vcom.inf is preinstalled.
> INFO: RETURN: DriverPackagePreinstallW (0xB7)
> INFO: ENTER: DriverPackageGetPathW
> SUCCESS:Found driver store entry.
> INFO: RETURN: DriverPackageGetPathW (0x0)
> INFO: ENTER: DriverPackageInstallW
> INFO: Installing INF file
> “C:\WINDOWS\system32\DRVSTORE\statbus_03A410A2A11BE1575BF2E33B7A13BA91A51D4AD2\statbus.inf”
> of Type 6.
> INFO: Looking for Model Section [Standard.NTx86]…
> INFO: No matching devices found in INF
> “C:\WINDOWS\system32\DRVSTORE\statbus_03A410A2A11BE1575BF2E33B7A13BA91A51D4AD2\statbus.inf”
> on the Machine.
> INFO: No drivers installed. No devices found that match driver(s)
> contained in
> ‘C:\WINDOWS\system32\DRVSTORE\statbus_03A410A2A11BE1575BF2E33B7A13BA91A51D4AD2\statbus.inf’.
> SUCCESS:Installation completed with code 0xE000020B.
> INFO: RETURN: DriverPackageInstallW (0xE000020B)
> INFO: No matching device was found for
> ‘c:\winddk\wdf\kmdf10\vcom\bin\statbus.inf’. Driver will be installed when
> plugged in.
> INFO: ENTER: DriverPackageInstallW
> INFO: Installing INF file
> “C:\WINDOWS\system32\DRVSTORE\vcom_0D735A8AB9D403DA3B9367B174A84B7A53FF4A35\vcom.inf”
> of Type 6.
> INFO: Looking for Model Section [MSFT.NTx86]…
> INFO: No matching devices found in INF
> “C:\WINDOWS\system32\DRVSTORE\vcom_0D735A8AB9D403DA3B9367B174A84B7A53FF4A35\vcom.inf”
> on the Machine.
> INFO: No drivers installed. No devices found that match driver(s)
> contained in
> ‘C:\WINDOWS\system32\DRVSTORE\vcom_0D735A8AB9D403DA3B9367B174A84B7A53FF4A35\vcom.inf’.
> SUCCESS:Installation completed with code 0xE000020B.
> INFO: RETURN: DriverPackageInstallW (0xE000020B)
> INFO: No matching device was found for
> ‘c:\winddk\wdf\kmdf10\vcom\bin\vcom.inf’. Driver will be installed when
> plugged in.
> INFO: Returning with code 0x200
> INFO: 10/23/2006 14:04:43
>
>