Having problems with message search?
We have applied latest WLK filters and
Rerun device path exerciser test.
PNP test still fails but I read on
Microsoft Forum that PNP test results can be skipped for Software driver by
applying Erata ID 295 and sending the readme file with Winqual submission.
There were instances of one professional
who got this driver signed two times with this change.
Regards
Viraj Shirgaonkar
Software Engineer
Persistent Systems
Limited
Extn 640
From:
discussion-pcausa@yahoogroups.com [mailto:discussion-pcausa@yahoogroups.com] On Behalf Of Thomas F. Divine
Sent: Friday, February 08, 2008
7:52 PM
To:
discussion-pcausa@yahoogroups.com
Subject: RE: [discussion-pcausa]
request for help on driver signing
What was the root cause of your problem?
Thomas
From: discussion-pcausa@
Sent: Friday, February 08, 2008
5:56 AM
To: discussion-pcausa@
Cc: viraj_shirgaonkar@
Subject: RE: [discussion-
Hi Thomas,
I am successful in creating CPK file after DTM Test results.
Thank you for your kind help in my journey of driversigning.
I have two submissions One for Service and another for Miniport.
So I have 2 CPK files one for each submission.
When I upload on WinQual submission tool, which CPK should I upload?
Can you please give our thoughts on this?
Regards
Viraj Shirgaonkar
Software Engineer
Persistent Systems Limited
Extn 640
From: discussion-pcausa@
Sent: Tuesday, February 05, 2008
11:40 AM
To: discussion-pcausa@
Subject: RE: [discussion-
It sounds like you are doing all that you can. I don’t
have any good advice to help you go further. You may have to open an incident
with the DTM group to help you get through this. That is not an easy task.
Wild ideas that I have never had to try myself but I would try
in desperation myself. I suspect that you have already done these.
1.) Shutdown
client.
2.) Reboot DTM
server.
3.) Restart
client.
4.) Wait a while
5.) Reset client
6.) Try to make
submission again.
Make sure all paths in your DTM installation contain only ASCII
characters and no whitespace. (Nothing says this should matter…).
Do both INF files include a CatalogFile entry? Is the catalog
file built using the Inf2Cat tool? Is the .CAT file signed using the WDK
signtool utility?
Does the create dimension test that is performed after you Reset
the client run to completion?
I believe that the create dimension test makes a catalog of
installed drivers, etc. and I think you can review these to see if your driver
is there.
Testing really shouldn’t be this hard.
Thomas
From: discussion-pcausa@
Sent: Tuesday, February 05, 2008
12:58 AM
To: discussion-pcausa@
Subject: RE: [discussion-
I am doing Service(NETIM.
Regards
Viraj Shirgaonkar
From: discussion-pcausa@
Sent: Tuesday, February 05, 2008
10:43 AM
To: discussion-pcausa@
Subject: RE: [discussion-
Which submission do you try to make first? Miniport or Service?
In any event, try reversing the order that you attempt to create
submissions. (and hold mouth correctly…).
Thomas
From: discussion-pcausa@
Sent: Tuesday, February 05, 2008
12:07 AM
To: discussion-pcausa@
Subject: RE: [discussion-
Hi Thomas,
Yes we do use static IP addresses for everything and also delete
previous pools and create fresh pool every time we run the tests .
We also place machine from cancelled pool to default and then drag
the machine from default pool to newly created pool.
All steps that we follow seem to be correct but still not able to
rectify this only error in our DTM Tests.
Regards
Viraj Shirgaonkar
From: discussion-pcausa@
Sent: Tuesday, February 05, 2008
10:27 AM
To: discussion-pcausa@
Subject: RE: [discussion-
I think it is essential for the submission creation process to
find the driver at that step.
I encountered this condition when using a multi-boot machine and
never was fully sure what steps “fixed” the problem.
On multi-boot machine after running any test and switching to a
new client image I have to remove all traces of the previous test from the DTM.
That is:
1.) Delete the
old submissions on the Device Console.
2.) In Job
Monitor, move machine to Default pool.
3.) In JM,
delete the pool itself.
4.) In JM
delete all test results.
Then
1.) Add the
Unclassified machine pool back.
2.) Move
machine from default pool to the newly re-created Unclassified pool.
3.) Reset the
client.
4.) Go to
dinner while the initial dimension preparation test runs.
5.) After
dinner, create the submissions again.
Are you using static IP addresses for everything?
Thomas F. Divine
From: discussion-pcausa@
Sent: Monday, February 04, 2008
11:24 PM
To: discussion-pcausa@
Cc: Joviano Dias
Subject: RE: [discussion-
Hi Thomas,
When we are creating a new submission by loading INF files from
Client Machine we get an Error:
Device Not Found, Still Continue? Yes or No.
If we select No, submission process stops .
Till now we were selecting Yes and going ahead with the tests.
Could this error may be a problem for our Plug and Play test error?.
Regards
Viraj Shirgaonkar
From: discussion-pcausa@
Sent: Monday, February 04, 2008
7:55 PM
To: discussion-pcausa@
Subject: RE: [discussion-
I used a workgroup configuration here.
My network does have two separate intranets in my office. One is
for normal message traffic and the second is reserved for testing. Both
machines had one interface on each network.
I did bind the NDIS IM being tested to only the one adapter on
the test network.
Thomas F. Divine
From: discussion-pcausa@
Sent: Monday, February 04, 2008
7:06 AM
To: discussion-pcausa@
Cc: Joviano Dias;
viraj_shirgaonkar@
Subject: RE: [discussion-
Hi Thomas,
Could I request for just one more piece of information on Plug and
Play Driver Test error that we are facing?
Do we have to setup the network of the two machines (DTM Client and
DTM Controller) in a specific way like additional NIC/ any other network
configuration…..?
Currently we have setup both the machines in Workgroup mode with
each machine having only one NIC.
Regards
Viraj Shirgaonkar
From: discussion-pcausa@
Sent: Monday, February 04, 2008
10:10 AM
To: discussion-pcausa@
Subject: RE: [discussion-
Sorry. Sounds like this could be a DTM setup problem.
Are these the results that you see when you use the Device
Console, select the submission and then press the Status button?
I just finished testing a NDIS 5 IM driver using the
Unclassified test on Windows XP. Vista x86 and
All six passed successfully with the PnP test being one of the
shortest runs.
I’m sorry, but I can’t be of further help…
Good luck,
Thomas F. Divine
From: discussion-pcausa@
Sent: Sunday, February 03, 2008
11:00 PM
To: discussion-pcausa@
Cc: viraj_shirgaonkar@
Subject: RE: [discussion-
Hi Thomas,
We have applied the changes suggested by you and we were successful
in eliminating 2 errors out of three.
The only error remaining is Plug and Play Driver Test. Report for
Plug and Play Driver Test is as follows
|
Pass[0] Fail[3] -:|:- Plug
and Play Driver Test |
|
- Pass[0] Fail[1] -:|:- RunJob
- Plug and Play Driver Test - Library Job Log: NotRequired |
|
Pass[0] Fail[1] -:|:- Run
Remove PNPDTest
Log: Missing |
|
Pass[0] Fail[1] -:|:- Run
Surprise PNPD Test Log: Missing |
|
Pass[0] Fail[1] -:|:- Run
Rebalance PNPD Test Log: Missing |
Can you please give us some suggestions on these errors?
Regards
Viraj Shirgaonkar
From: discussion-pcausa@
Sent: Thursday, January 31, 2008
9:39 PM
To: discussion-pcausa@
Subject: RE: [discussion-
Some
additional thoughts...
If you are unfamiliar with WLK I would suggest that you attach WinDbg to the
test client at first. The debug message output during the test will give you
some feeling about what is going on.
In addition, if you have WinDbg attached and the driver crashes, then you
can investigate the cause of the crash on the spot.
You should also try to insure that your test client is reliable and do some
test runs with known good drivers. I invested many hours of "dry
runs" just
learning what it takes to be successful. In the early stages it is not
uncommon to have to make many attempts at a test before you actually get it
to pass.
Using the DTM is, unfortunately, extremely frustrating. Believe it or not,
DTM is much better now than it was a year ago.
Thomas F. Divine
> -----Original Message-----
> From: discussion-pcausa@
> pcausa@yahoogroups.
> Sent: Thursday, January 31, 2008 10:18 AM
> To: discussion-pcausa@
> Subject: RE: [discussion-
>
> It looks like you have a lot of problems.
>
> 1.) INF Test
> ============
> It is always frustrating the first time you try to make a solid set of
> INFs.
> My suggestion is to take the INF files from the Passthru sample from a
> recent DDK (Build 3790 or later) and systematically modify those files.
> The
> Passthru sample INF file from earlier DDKs and from some older PCAUSA
> samples have some problems.
>
> You still haven't provided any information about the error returned by
> the
> DTM when it runs the INFTest, This information:
>
> "> cmd /c set
> path=%path%;
> BDC8-48C
> 8EEFD9CA4 &&
> "C:\WTT\JobsWorkingD
> 48C8EEFD9CA4\
> 386\inftest.
> > C:\WTT\JobsWorkingD
> 48C8EEFD9CA4
> -f /LG -l %windir%\inf\
> > Failed with ExitCode 1
> > Resolution
> > No resolution provided."
>
> Is of no help to me and no help to you either. Use the DTM Device
> Console,
> select your submission, then press the Status button on the right. When
> the
> status page is displayed, press the Report button at the bottom right.
> It
> brings up a page where the INFTest should appear in RED. Drill through
> that
> until you find the inftest.xml file. Open that and you should find more
> information - although it is difficult to read XML...
>
> There may be problems in the way you may have created your submission
> for
> the NDIS IM driver. You must create two submissions" one for the IM
> service
> and one for the IM miniport. If you create one submission and select
> two INF
> files it will fail. Remember, the test is called "Run INFTest against
a
> single INF file". If you provide two INF files, it will fail.
>
> You must be using the mist recent WLK, of course.
>
> In addition, there are still problems with the WLK when testing IM
> filter
> drivers. As a matter of fact, my testing has shown that even with a
> good set
> of INFs and the most current WKL the INF test will still fail.
>
> Unless...
>
> You add the most recent filters to your DTM. See the URL:
>
> https://winqual.
>
> When I added the filter update, the INF file test passed.
>
> If the INFTest fails you may have problems with other tests.
>
>
> 2.) PnP Test
> ============
> I have never seen this fail with a NDIS IM driver. Perhaps the WLK
> filter
> update will fix this issue. If not, then the WDK includes pnp test
> tools
> that you can run outside of the DTM.
>
>
> 3.) Device Path Exerciser
> ============
> Here the problem is clear. Read the Device Path Exerciser and try to
> understand what it is doing. Basically, it is going to call your
> driver's
> IOCTL entry points with bogus data in an attempt to uncover places in
> your
> driver where you have not taken the time to validate input parameters.
> For
> example, an IOCTL may expect a DWORD input, and you assume that a DWORD
> is
> provided. The test may pass something shorter than a DWORD or no input
> buffer at all.
>
> The DDK provides a stand-alone version of the DevicePath exerciser I
> believe. If not, then DriverVerifier can be configured to do the same
> thing.
>
> Once you find a problem with the debugger fix it - but don't stop
> there.
> Understand that you should validate all inputs before using them and
> systematically fix similar problems in other IOCTLs where DV may not
> have
> (yet) found a problem.
>
> Good luck,
>
> Thomas F. Divine
>
>
>
> > -----Original Message-----
> > From: discussion-pcausa@
> > pcausa@yahoogroups.
> > Sent: Thursday, January 31, 2008 5:31 AM
> > To: discussion-pcausa@
> > Subject: [discussion-
> >
> >
> > Problems faced during driver signing process as discussed
> > during previous posts.
> > 1) We ran inf2cat tool to generate catalog files on passthru
> > filter driver's INF files and we found that catalog directive was
> > missing in those files.
> > 2) We added CatalogFile directive in Version Section in these
> > INF files and passed these files to inf2cat tool and Cat files were
> > successfully completed with our change.
> > 3) Then we ran chkinf utility .First we got some errors. So we
> > made following changes to INF files
> > a) we changed Msft macros value from Microsoft
> > to "test_Company" in both INF files
> > b) commented Copyfiles which was not assigned a value in
> > Passthrump.ndi Section
> > 4) After we made following changes Passthru's netsf.inf and
> > netsf_m.inf files gave us success in chkinf utility.
> > 5) With this we had some base INF files testing passing our
> > tests in inf2cat and chkinf utilities.
> > 6) Then we used the above understanding to resolve the errors
> > in NETIM.INF and NETIM_M.INF.
> > 7) In NETIM.INF in DestinationDirs section %windir%\inf
> > directory-id was given wrong value ( instead of giving value 20,
> > value 17 was given). We removed this error.
> > 8) Manufacturer PCAUSA section changed to normal case.
> > 9) Commented DelService directive in
> > PCASIMCL.Ndi.
> > service not defined.
> > 10) With these changes all errors that we were getting in
> > inf2cat and chkinf utilities were eliminated.
> > 11) After running DTM tests on the above INF files Results were
> > as follows:
> > a) Run INF test against single INF failed.
> > b) Device Path Exerciser test was continuously running because
> > client got crashed when test was running.
> > c) Plug and Play driver test was found to be failing.
> >
> > 12) We checked the details of above errors
> > PNPD Errors
> > 1. Remove PNPDTest
> >
> > Failed to Parse the RollupCounts XML
> > file "C:\WTT\JobsWorkingD
> > BC0685948898\
> > Remove PNPDTest".
> > Error Code 1025 (Unknown error (0x401))
> > Resolution
> > No resolution provided.
> >
> >
> >
> >
> > 2. Run Surprise PNPD Test
> > Failed to Parse the RollupCounts XML
> > file "C:\WTT\JobsWorkingD
> > BC0685948898\
> > Surprise PNPD Test".
> > Error Code 1025 (Unknown error (0x401))
> >
> > 3. Run Rebalance PNPD Test
> > Failed to Parse the RollupCounts XML
> > file "C:\WTT\JobsWorkingD
> > BC0685948898\
> > Rebalance PNPD Test".
> > Error Code 1025 (Unknown error (0x401))
> > Cannot Find Pattern "C:\WTT\JobsWorkingD
> > BA6E-4CD7-B814-
> > Error Code 2 (The system cannot find the file specified)
> >
> > Resolution
> > No resolution provided.
> >
> > CHKInf and INFTest Library Job
> >
> > 1. The Execute Task with Commandline
> >
> > cmd /c set path=%path%;
> > 6061-4E2B-BDC8-
> > && "C:\WTT\JobsWorkingD
> > 48C8EEFD9CA4\
> > C:\WTT\JobsWorkingD
> > 48C8EEFD9CA4 -f /LG -l %windir%\inf\
> > Failed with ExitCode 1
> > Resolution
> > No resolution provided.
> >
> > Device Path Exerciser
> >
> > 1. Client Machine Crashes.
> >
> > Could you please guide us in this area?
> >
>
>
>
>
> ------------
>
> Copyright (c) 1999-2008 Printing Communications Assoc., Inc. (PCAUSA)
>
> Yahoo! Groups Links
>
>
>
Offline 
Send Email
