Re: KMDF Fakemodem not working
- From: Tim <Tim@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 2 Oct 2007 04:09:05 -0700
Hi Doran and others,
This doesn't work for me.
I'm using the `Windows Vista and Windows Server Longhorn x86 Checked Build
Environment' on Vista 32bit. And I'm getting this error when trying to
install the fakemodem with devcon:
C:\WinDDK\6000\srcTry\kmdf\fakemodem\objchk_wlh_x86\i386>devcon.exe -r
install m
dmfake.inf {b85b7c50-6a01-11d2-b841-00c04fad5171}\fakemodem
Device node created. Install is complete when drivers are installed...
Updating drivers for {b85b7c50-6a01-11d2-b841-00c04fad5171}\fakemodem from
C:\Wi
nDDK\6000\srcTry\kmdf\fakemodem\objchk_wlh_x86\i386\mdmfake.inf.
devcon.exe failed.
I have no idea what is causing it to fail, since I haven't altered the
example in any way.. Does anyone have a fix?
Greetings,
Tim
"Doron Holan [MSFT]" wrote:
yes, try to use devcon to install the KMDF fakemodem sample. the readme and.
INf in the sample should tell you how to use devcon to install the driver.
You don't need to create a separate fake COM port, fakemodem will expose its
own.
d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Beat Nideröst" <BeatNiderst@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9CC6256B-0C0E-48CA-8CDF-9368A4EADAB8@xxxxxxxxxxxxxxxx
I'm trying to develop my first device driver but have some problems
getting
started. I downloaded the Vista WinDDK from MSDN and have built all the
sources using both the Vista x86 Free and Windows 2000 x86 Free build
environment.
It took a while to understand the differences, but I understand now that
there are two FakeModem samples in the DDK: the WDM version and the KMDF
version.
I successfully compiled both versions without changing any source code:
* I built the WDM version with the Windows 2000 x86 Free build environment
* I built the KMDF version with the Vista x86 Free build environment
I succeeded to install the WDM version on a Win 2003 Server x86 using the
Add New Hardware wizard. I had to disable a real modem driver, put the
device
id in the INF file and was able to install the fakemodem driver. After
that,
the device answered to my HyperTerminal queries and was also found OK
using
the modem diagnostics from the control panel.
I also tried to install the KMDF version on a Windows Vista computer Add
New
Hardware wizard. The PC doesn't have any physical com ports, but I
expected
that this would not be a problem, since the KMDF version of fakemodem is
"controllerless". This is different from the WDM version, which requires
real
hardware to run on. However, I never got past the last screen from the
setup:
"Choose COM ports...". Since I don't have any, I can't choose one, and the
installer fails.
Here my first questions:
* Why do I need to choose a COM port? The driver is supposed to be
"controllerless", isn't it?
* Should I be using a different tool than the Add New Hardware wizard to
install the driver? I have seen the command line tool devcon.exe, and have
read something about installing a driver at the root of the driver tree
instead of on a bus (or a com port maybe? I have no clue)... should I be
using this tool? Which command should I use? I never found the correct
command line options for it to work.
* Is there a way to install a fake COM port that the fake modem can
connect
to? Maybe a derivative from the serial driver? Has anybody tried that? Or
maybe a derivative from the echo sample?
* Would the toaster sample be of any help here? For example, should I try
to
install the toaster sample and add a virtual COM port? Or have it
enumerate a
matching device so that my modem would get installed? How should I do that
exactly?
Also, I have tried to install the fake modem driver on a virtual PC image
running Windows Vista x86. Advantage: the virtual PC adds two virtual COM
ports that I can use. And indeed, I can install the fake modem and choose
the
two COM ports. I have two modems listed then, the install runs correctly,
but
none of them are working:
* The modem diagnostics from the control panel show:
09-22-2007 18:25:56.366 - File: C:\Windows\system32\tapisrv.dll, Version
6.0.6000
09-22-2007 18:25:56.366 - File: C:\Windows\system32\unimdm.tsp, Version
6.0.6000
09-22-2007 18:25:56.366 - File: C:\Windows\system32\unimdmat.dll, Version
6.0.6000
09-22-2007 18:25:56.366 - File: C:\Windows\system32\uniplat.dll, Version
6.0.6000
09-22-2007 18:25:56.366 - File: C:\Windows\system32\drivers\modem.sys,
Version 6.0.6000
09-22-2007 18:25:56.366 - File: C:\Windows\system32\modemui.dll, Version
6.0.6000
09-22-2007 18:25:56.366 - File: C:\Windows\system32\mdminst.dll, Version
6.0.6000
09-22-2007 18:25:56.366 - Modem type: FakeModem DDK Sample controllerless
driver
09-22-2007 18:25:56.366 - Modem inf path: mdmfake.inf
09-22-2007 18:25:56.366 - Modem inf section: ModemX
09-22-2007 18:25:56.366 - Matching hardware ID:
{b85b7c50-6a01-11d2-b841-00c04fad5171}\fakemodem
09-22-2007 18:25:56.366 - Opening the modem device failed with error
00000001
* Also, when I use Hyperterminal to open the com port, hyperterm works
fine,
but I don't get any responses on ATA etc., whereas I did when I installed
the
WDM variant on Windows 2003.
I have tried several Virtual PC options:
* COM port not connected - nothing happens, as described above
* COM port connected to phyical port - I get an error because the physical
machine doesn't have any physical com ports
* COM port connected to a file on the host OS - this works fine, and I see
the commands I send to the COM port using Hyperterm or the modem
diagnostics.
I would have expected the fakemodem driver to pick up these commands and
react on them (instead of passing them through to the physical COM port),
however it didn't.
* Can anyone explain this behaviour? How can I get the KMDF fakemodem to
work on the Virtual PC or the PC without any COM ports?
Regards, Beat
- Follow-Ups:
- Re: KMDF Fakemodem not working
- From: Tim Roberts
- Re: KMDF Fakemodem not working
- Prev by Date: Re: Supporting discrete frame rate in AVstream driver
- Next by Date: Re: Mutex
- Previous by thread: Re: Mutex
- Next by thread: Re: KMDF Fakemodem not working
- Index(es):
Relevant Pages
|
