2008-08-04

25 new messages in 15 topics - digest

microsoft.public.development.device.drivers
http://groups.google.com/group/microsoft.public.development.device.drivers?hl=en

microsoft.public.development.device.drivers@googlegroups.com

Today's topics:

* Is my idea can be implement? - 2 messages, 2 authors
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/2f949c9bf2e925c0?hl=en
* X64 driver signing - 3 messages, 3 authors
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/4610e90a692e6edb?hl=en
* regarding upgrade window server 2003 sp2 - 3 messages, 3 authors
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/ee07b3492e452d46?hl=en
* storport.sys bug - 1 messages, 1 author
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/b5de7db2feec1021?hl=en
* Handle power Irp when 2 devices supported - 4 messages, 2 authors
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/f670e535c8b707fb?hl=en
* How to use IoConnectInterrupt to register IRQ 14 or 15? - 1 messages, 1
author
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/118773a4b0470033?hl=en
* Releasing a COM Port from an Active Application - 1 messages, 1 author
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/32010f335fbe5e48?hl=en
* break point in mux.sys - 1 messages, 1 author
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/c6b7b4c6288df3a2?hl=en
* swatch schweiz armbanduhren swatch irony aluminium swatch sfk billige - 1
messages, 1 author
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/854170d531047e3a?hl=en
* How to get EMF bits from a print processor? - 1 messages, 1 author
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/f8112001c928c914?hl=en
* what happened in sdbus.sys? - 3 messages, 2 authors
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/903fd3535d1478aa?hl=en
* Get Device information according to GUID - 1 messages, 1 author
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/4a971243d2ac50fa?hl=en
* Programatically display Device Driver Update Dialog,... - 1 messages, 1
author
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/4e507786e869f405?hl=en
* Winusb vendor supplied control command transfer to the device - 1 messages,
1 author
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/5f79b2e4c4b9a7ac?hl=en
* AVStream driver: audio rendering problem - 1 messages, 1 author
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/96e2a0c0027beaf7?hl=en

==============================================================================
TOPIC: Is my idea can be implement?
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/2f949c9bf2e925c0?hl=en
==============================================================================

== 1 of 2 ==
Date: Sun, Aug 3 2008 11:36 pm
From: "Robin"


Hi David,

Thanks for your response.

First of all I'll make clear of my idea:
(1) Not every sectors on the disk will be encrypted with my "WDE", such as the first cylinder of the disk which contain the MBR;
(2) The boot code of MBR will replaced by my code, and the other sectors of the first cylinder will contain my code which is PCI BIOS functions and INT13 filter and system lodaer, It's can be called "my boot loader";
(3) Before load system code, such as ntldr, the "encryption enviroment" will be ready. From then on all of the disk reading and writting options are filtered by my code(my int13 filter, they do the encrytion and decryption and 'raw' disk read and write);

Seagate's FDE is a good idea to implement whole disk encryption, as you said, they should be supported by special BIOS, but I don't want do that.

OK, come back to my idea:
(1) Pre-OS: The INT13 filter is implement reading and writting sectors in secure mode, and PCI's functions is to implement the driving of PCI card to do the encrypt and decrypt operations, these function will be called by my INT13 filter.

(2) After OS start up: The PCI driver will drive my PCI crypto card, and disk filter driver do the reading and writting disk sectors in a secure mode, they will "use" PCI device to do the encrypt and decrypt operations through PCI driver.

But, here is the focus of my problem, when the system starting, assume that the PCI driver is loaded first, my INT13 filter is still working in the origial mode, which will access PCI crypto card in the pre-os manner, is there have any conflict? Such and i386 protection mode problem, or the address of the PCI configuration space, status and otherwise.


Thanks Devid


Robin 04/08


"David Craig" <drivers@nowhere.us> wrote in message news:%23e2tSFe9IHA.3612@TK2MSFTNGP04.phx.gbl...
There are several phases in booting from a hard drive:

1. First the BIOS will use INT 13h, usually the 0x4n variants with current BIOS to load the MBR into 0000:7C00h. It is then executed.
2. The MBR code will load the partition boot record (PBR) from the active partition and it will be executed at the same address.
3. The PBR code will load the initial OS code and what this is named varies depending upon the OS being loaded.
4. Windows will load all boot start drivers into memory. Hint: this is IMPORTANT!!!
5. Each boot start driver will have its DriverEntry() invoked. Maybe the add device routine will be invoked followed by a start IRP.
6. After all those boot start drivers are up and running the OS will stop using the INT 13h BIOS software interrupts.

In step 5 you need to query the BIOS code (your extension if you have one or code loaded by the MBR if you use that method). The information passed into your boot start driver will be needed to do the encryption from then on. You might consider looking at Seagate's FDE drives that have encryption in the drive's firmware. That does require the BIOS be written to support those drives since no hard drive is accessable until password credentials, used to obtain access to the encryption key, are provided, validated, and presented to the drive.

When doing this type of code regardless of whether it is on-drive, or a PCI device you will find VMWare useful. Also an ICE will be needed or a lot of patience and knowledge about how storage is used in PCs.

"Robin" <digitalhuman@hotmail.com> wrote in message news:O$n2Nid9IHA.5668@TK2MSFTNGP04.phx.gbl...
Hi all,

I want encrypt whole disk by PCI crypto-card, it's not a partition encryption but WHOLE DISK, so the system partition of OS will be encrypted.
To implement this idea, I will:
(1)Drive my PCI crypto-card before the system booting(so called pre-os driver);
(2)Hook my int13 filter to BIOS, which will do the decryption use my PCI crytpo-card;
(3)Implement a PCI driver for NT, which will drive my PCI crypto-card after the system starting up;
(4)Implement a disk filter driver for NT, whill will implement the read and write of disk sectors in secure mode(encryption and decryption);


My problem is: When the system starting up, the driver of disk and PCI crypto-card will be loaded,
(1) If the PCI crypto-card driver will be loaded first, can INT13 filter call the PCI pre-os 'driver' after it is loaded? If not, the gaps is system can't read encrypted sectors any more!
(2) If the disk filter driver will be loaded first, the INT13 filter will be pasted, any read and write of the disk sectors will be processed by the driver, but at this time, the PCI driver not loaded, can I call the "pre-os driver funtion" to do crypto?


Is there any suggestion ?


Thanks and best regards

Robin 04/08

== 2 of 2 ==
Date: Mon, Aug 4 2008 10:50 am
From: "Maxim S. Shatskih"


>(2)Hook my int13 filter to BIOS, which will do the decryption use my PCI
crytpo-
>card;

Since you have a crypto card, the proper place for this hook will be the card's
EEPROM chip which will be presented as extension BIOS to the rest of the
machine.

>(1) If the PCI crypto-card driver will be loaded first, can INT13 filter call
the PCI
>pre-os 'driver' after it is loaded? If not, the gaps is system can't read
encrypted
>sectors any more!

If the crypto card's driver will be boot-start - then the problem is solvable
by waiting for PCI card's device interface arrival notification in the disk
filter.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com


==============================================================================
TOPIC: X64 driver signing
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/4610e90a692e6edb?hl=en
==============================================================================

== 1 of 3 ==
Date: Mon, Aug 4 2008 2:30 am
From: Vikram


Hi,

I have an application which accesses the PCI bus temperature sensors through
Kernel Mode Driver.

I recently ported this application and driver to x64 platform.
I was able to test sign the Driver and now want to run the application on
the target machine; I have some queries regarding the same,Can you please
answer them?

1.Can only checked built drivers be test signed? Can we test sign free built
drivers as well?
2.To run the test signed driver on target testing machine, is WDK
compulsorily required on the testing machine?
3.If WDK is not present on the testing machine and I want to run my
application on it, is there some way other then "Disable Driver Signature
Enforcement" and "Attach a kernel debugger" method?
4.If I embed the signature in the driver, is there some standard Windows API
which takes care of adding the signature file to the certificate manager of
testing machine?

Regards,
Vikram

== 2 of 3 ==
Date: Mon, Aug 4 2008 9:02 am
From: "Gianluca Varenni"

"Vikram" <Vikram@discussions.microsoft.com> wrote in message
news:2206AA1F-2ABC-44D5-A432-A6C6E4B6B231@microsoft.com...
> Hi,
>
> I have an application which accesses the PCI bus temperature sensors
> through
> Kernel Mode Driver.
>
> I recently ported this application and driver to x64 platform.
> I was able to test sign the Driver and now want to run the application on

I suppose the target machine is running Vista/Srv08, right?

> the target machine; I have some queries regarding the same,Can you please
> answer them?
>
> 1.Can only checked built drivers be test signed? Can we test sign free
> built
> drivers as well?

Yes.

> 2.To run the test signed driver on target testing machine, is WDK
> compulsorily required on the testing machine?

No. You need to have the machine booted in test signing mode and have the
test certificate installed on your machine among the trusted root
certification authorities of the machine.

> 3.If WDK is not present on the testing machine and I want to run my
> application on it, is there some way other then "Disable Driver Signature
> Enforcement" and "Attach a kernel debugger" method?

Set the machine to boot in test signing mode, test sign the driver, install
the test certificate.

> 4.If I embed the signature in the driver, is there some standard Windows
> API
> which takes care of adding the signature file to the certificate manager
> of
> testing machine?

You need to use certmgr.exe to do that.

In practice, follow the instructions in the white paper Kernel Mode Code
Signing Walkthrough available here

http://www.microsoft.com/whdc/winlogo/drvsign/kmcs_walkthrough.mspx

Have a nice day
GV


--
Gianluca Varenni, Windows DDK MVP

CACE Technologies
http://www.cacetech.com


>
> Regards,
> Vikram


== 3 of 3 ==
Date: Mon, Aug 4 2008 11:21 am
From: "Maxim S. Shatskih"


> 1.Can only checked built drivers be test signed? Can we test sign free built
> drivers as well?

Yes.

> 2.To run the test signed driver on target testing machine, is WDK
> compulsorily required on the testing machine?

No, you only need to install the test certificate to the store.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com


==============================================================================
TOPIC: regarding upgrade window server 2003 sp2
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/ee07b3492e452d46?hl=en
==============================================================================

== 1 of 3 ==
Date: Mon, Aug 4 2008 4:59 am
From: qwert


I have a question regarding windows server 2003 sp2.
Normally service packs are released as SP1 and sp2,if I am not wrong.
what does windows server 2003 r2 mean????

IS it a service pack of windows server 2003????????

== 2 of 3 ==
Date: Mon, Aug 4 2008 5:19 am
From: "Pavel A."


qwert wrote:
> I have a question regarding windows server 2003 sp2.
> Normally service packs are released as SP1 and sp2,if I am not wrong.
> what does windows server 2003 r2 mean????
>
> IS it a service pack of windows server 2003????????

R2 is not a service pack. Read this:
http://technet.microsoft.com/en-us/windowsserver/bb428898.aspx

Regards,
--PA

== 3 of 3 ==
Date: Mon, Aug 4 2008 11:22 am
From: "Maxim S. Shatskih"


> Normally service packs are released as SP1 and sp2,if I am not wrong.
> what does windows server 2003 r2 mean????

Some pre-SP2 functionality (not bugfixing) update.

> IS it a service pack of windows server 2003????????

No, but the timeline was:
- SP1
- R2
- R2 SP2

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com


==============================================================================
TOPIC: storport.sys bug
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/b5de7db2feec1021?hl=en
==============================================================================

== 1 of 1 ==
Date: Mon, Aug 4 2008 6:22 am
From: bkroeter@gmail.com


Yes, I can confirm that is a problem. But it is not a show stopper.
Have a look at this Vminiport sample: http://www.perisoft.net/miniport/index.htm


==============================================================================
TOPIC: Handle power Irp when 2 devices supported
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/f670e535c8b707fb?hl=en
==============================================================================

== 1 of 4 ==
Date: Mon, Aug 4 2008 8:07 am
From: John


On Fri, 1 Aug 2008 11:44:21 -0700, "Doron Holan [MSFT]"
<doronh@online.microsoft.com> wrote:

>what is the relations type that you being queried for in the QDR? it is
>normal to be repeatedly requeried for busrelations. you just return the PDO
>each time in the relations list
>
>d

It is busrelations.

It's been a while since I visited this code and I had to sit down and
take a good look as to what was happening.
During the AddDevice phase, the driver created the FDO for its device.
Then the IRP_MN_START_DEVICE occurred. Here is where the driver
created the PDO for the secondary device (This is where I got
confused, "I'm much better now".

When the QDR was processed. the driver notified the system about the
busrelations of the secondary device.

The AddDevice phase started for the secondary device and the driver
created the FDO for that device. Initialization of the secondary
channel occurred when the IRP_MN_START_DEVICE was received for the
secondary channel. Everybody was happy.

I used the sample code from Walter Oney book, "Programming the
Microsoft Windows Driver Model".

If you're familiar with this book, it talked about wearing the PDO hat
or FDO hat while processing PNP IRPs. All this worked just fine. But I
failed to implement the PDO/FDO hats scheme for the Power IRPs. All
processing occured for the FDO. If the PDO was received the driver
should just complete the IRP. I didn't do that and I think this is
where my problem lies.

I'm going to add the PDO hat for the secondary device and see what
happens.

== 2 of 4 ==
Date: Mon, Aug 4 2008 11:22 am
From: "Doron Holan [MSFT]"


i suggest that you look at porting to KMDF, all of this crud is taken care
of for you w/out you writing a single line of code.

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.


"John" <jvasquez@cox.net> wrote in message
news:oq5e949b717a5eu8bhukeghot2qf5kilcc@4ax.com...
> On Fri, 1 Aug 2008 11:44:21 -0700, "Doron Holan [MSFT]"
> <doronh@online.microsoft.com> wrote:
>
>>what is the relations type that you being queried for in the QDR? it is
>>normal to be repeatedly requeried for busrelations. you just return the
>>PDO
>>each time in the relations list
>>
>>d
>
> It is busrelations.
>
> It's been a while since I visited this code and I had to sit down and
> take a good look as to what was happening.
> During the AddDevice phase, the driver created the FDO for its device.
> Then the IRP_MN_START_DEVICE occurred. Here is where the driver
> created the PDO for the secondary device (This is where I got
> confused, "I'm much better now".
>
> When the QDR was processed. the driver notified the system about the
> busrelations of the secondary device.
>
> The AddDevice phase started for the secondary device and the driver
> created the FDO for that device. Initialization of the secondary
> channel occurred when the IRP_MN_START_DEVICE was received for the
> secondary channel. Everybody was happy.
>
> I used the sample code from Walter Oney book, "Programming the
> Microsoft Windows Driver Model".
>
> If you're familiar with this book, it talked about wearing the PDO hat
> or FDO hat while processing PNP IRPs. All this worked just fine. But I
> failed to implement the PDO/FDO hats scheme for the Power IRPs. All
> processing occured for the FDO. If the PDO was received the driver
> should just complete the IRP. I didn't do that and I think this is
> where my problem lies.
>
> I'm going to add the PDO hat for the secondary device and see what
> happens.
>

== 3 of 4 ==
Date: Mon, Aug 4 2008 1:35 pm
From: John


On Mon, 4 Aug 2008 11:22:52 -0700, "Doron Holan [MSFT]"
<doronh@online.microsoft.com> wrote:

>i suggest that you look at porting to KMDF, all of this crud is taken care
>of for you w/out you writing a single line of code.
>
>d

That would be great. However, I just don't have the time. The driver
overall works; just a few bugs pop-up once in a while. Plus upper
management won't allow me to change it because it (the driver) works.
I even tested the driver in Vista and no problems encountered, so this
driver will probably never get changed to KMDF.

I did fix my problem though. I just didn't handle the power management
correctly for the multifunction adapter.

Thanks for your suggestions.


== 4 of 4 ==
Date: Mon, Aug 4 2008 2:44 pm
From: "Doron Holan [MSFT]"


if it is based on oney's book (not to say that it is completely buggy,
overall it is good), you will have lots of latent bugs taht will creep up on
you over time.

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.


"John" <jvasquez@cox.net> wrote in message
news:anpe945tcr8fm56ocrvrd7t9u06hjunssj@4ax.com...
> On Mon, 4 Aug 2008 11:22:52 -0700, "Doron Holan [MSFT]"
> <doronh@online.microsoft.com> wrote:
>
>>i suggest that you look at porting to KMDF, all of this crud is taken care
>>of for you w/out you writing a single line of code.
>>
>>d
>
> That would be great. However, I just don't have the time. The driver
> overall works; just a few bugs pop-up once in a while. Plus upper
> management won't allow me to change it because it (the driver) works.
> I even tested the driver in Vista and no problems encountered, so this
> driver will probably never get changed to KMDF.
>
> I did fix my problem though. I just didn't handle the power management
> correctly for the multifunction adapter.
>
> Thanks for your suggestions.
>
>


==============================================================================
TOPIC: How to use IoConnectInterrupt to register IRQ 14 or 15?
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/118773a4b0470033?hl=en
==============================================================================

== 1 of 1 ==
Date: Mon, Aug 4 2008 10:38 am
From: "Maxim S. Shatskih"


> For example: Intel IDE or SATA Control
>
> They can set their PCI Device to use IRQ 14/15 or INTA, when booting.

They set this in BIOS, and then Windows borrows these BIOS settings by
IRP_MN_QUERY_RESOURCES.

> so, i dont know how to handle a hard code IRQ.

I cannot understand why you ever need a hardcoded IRQ. Just use the IRQ which
PnP gives you, this is simple.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com


==============================================================================
TOPIC: Releasing a COM Port from an Active Application
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/32010f335fbe5e48?hl=en
==============================================================================

== 1 of 1 ==
Date: Mon, Aug 4 2008 11:23 am
From: "Doron Holan [MSFT]"


i have my doubts it will even work then...the only way he would know that
this scheme would work is if he had src for both apps...and if he did, he
should just fix the first app to release the com port

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.


"Ray Trent" <rat@nospam.nospam> wrote in message
news:ehI9bAD9IHA.356@TK2MSFTNGP02.phx.gbl...
> Obviously this isn't something that's going to work in the general case,
> but to be fair to the OP (who didn't really word their question very well,
> however), I can certainly see creating a mechanism that would work for one
> specific set of known applications.
>
> Doron Holan [MSFT] wrote:
>> you can do that, but what will it mean? what if both apps want different
>> baud rates? how will you know which app to report data to?
>>
>
>
> --
> Ray


==============================================================================
TOPIC: break point in mux.sys
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/c6b7b4c6288df3a2?hl=en
==============================================================================

== 1 of 1 ==
Date: Mon, Aug 4 2008 12:18 pm
From: ttan


Hi all,

I set target machine registry as DEFAULT DWORD 0xFFFFFFFF.
When I bring up the winDbg, there are so many messages print out. I tried
to set a break point in Mux driver such file protocol.c but the break point
never get set in there, it just break and hold the target machine but it
never actually set a break point in the code. How to I do a single step mux
driver I used F10,F11 but it doesn't work.
I also need help on how to set the debuger to print out only mux driver
messages?

Thanks in advance,


==============================================================================
TOPIC: swatch schweiz armbanduhren swatch irony aluminium swatch sfk billige
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/854170d531047e3a?hl=en
==============================================================================

== 1 of 1 ==
Date: Mon, Aug 4 2008 12:22 pm
From: sdgvfwe@yahoo.is.com


swatch schweiz armbanduhren swatch irony aluminium swatch sfk billige


+
+
+
BILLIGE SWATCH UHREN KAUFEN
http://jhku.net/SWATCH-UHREN/
http://jhku.net/SWATCH-UHREN/
http://jhku.net/SWATCH-UHREN/
+
+
+
BILLIGE ROLEX UHREN KAUFEN
http://jhku.net/rolexuhren/
http://jhku.net/rolexuhren/
http://jhku.net/rolexuhren/
+
+
+
BILLIGE BREITLING UHREN KAUFEN
http://jhku.net/breitlinguhren/
http://jhku.net/breitlinguhren/
http://jhku.net/breitlinguhren/
+
+
+


http://spielzeug-figuren.mirror-server.net - Spielzeug Figuren
http://groups.google.de/group/supply-kind-of-hdmi-cable/web/hdmi-kabel-10-meter
http://www.gamesforum.ca/showthread.php?t=311744

swatch fivb
swatch irony
flik flak
swatch beat
swatch moonscape
swatch cordless ii isdn
swatch stores
swatch group
swatch sweet
swatch blue
swatch ring
swatch berlin
swatch shop
swatch scuba
swatch group deutschland
swatch bijoux
swatch group deutschland
swatch the beep
swatch phone
swatch.de
swatch service
swatch sweet sarong
swatch irony aluminium
swatch automatic
swatch sweet sarong
swatch telecom ag
swatch chrono
swatch irony lady
kaufen
swatch watches
swatch armband
swatch twinphone bedienungsanleitung
swatch irony
swatch simplissima
uhren
swatch cordless 2


==============================================================================
TOPIC: How to get EMF bits from a print processor?
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/f8112001c928c914?hl=en
==============================================================================

== 1 of 1 ==
Date: Mon, Aug 4 2008 2:03 pm
From: Yannick Fortin


So there is no other way to get the EMF than parsing the spool file?
That's what I was trying to avoid... In that case, why is everyone
saying that it's better to have a print processor than to capture the
spool file directly from the file system?

Oh well. Thanks for the info.


Yannick


> http://www.undocprint.org/winspool/spool_files#reading_job_data
> http://www.undocprint.org/formats/winspool/spl
>
>> Hi all.
>>
>> I have read all the DDK documentation and the archives here talking about
>> print processors, EMF vs RAW spooling, etc. Ashwin's posts have been quite
>> informative on this subject.
>>
>> One thing eludes me, though. Like many others, I am trying to get access
>> to the EMF (more precisely, the EMF in the spool file, I am aware of the
>> file formats, etc.) to extract the text from it. Some of the previous
>> threads on the subject said that the print processor would be the place to
>> do that.
>>
>> Problem is: how do I get access to the EMF from the print processor? From
>> my understanding, the print processor requests and receives EMF *handles*
>> before giving them back to GDI with GdiPlayPageEMF.
>>
>> Can you call GetEnhMetaFileBits with this handle? This seems unlikely
>> since that function expects an HEMHMETAFILE, not a HANDLE -- unless the
>> HANDLE is really an HENHMETAFILE? Or maybe treat the handle as a pointer
>> to the EMF bits?
>>
>> Thanks for any information you may share on this subject.


==============================================================================
TOPIC: what happened in sdbus.sys?
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/903fd3535d1478aa?hl=en
==============================================================================

== 1 of 3 ==
Date: Mon, Aug 4 2008 7:39 pm
From: kunikiyou


I see a endless loop in following code of sdbus.sys with 16-bit PCMCIA card.
Does any one know what it is waiting for? and why it failed? Thanks.

push 32h
push ebx
call sdbus!SdbusReadRegisterUshort (aecda542)
mov esi,eax
test si,100h
movzx edi,si
mov dword ptr [ebp+8],edi
je sdbus!SdhcGetErrorStatus+0x3b (aecd85eb)

sdbus!SdhcGetErrorStatus+0x27:
push 3Ch
push ebx
call sdbus!SdbusReadRegisterUshort (aecda542)
mov dword ptr [ebp-4],eax

== 2 of 3 ==
Date: Mon, Aug 4 2008 8:57 pm
From: "Alexander Grigoriev"


Your card was unplugged or reset. All registers are read as FFFF. This is a
common mistake to fail to check for the device unplug.

"kunikiyou" <kunikiyou@discussions.microsoft.com> wrote in message
news:D6CF02B0-E08F-43C4-9BCA-27950C5A9F6C@microsoft.com...
>I see a endless loop in following code of sdbus.sys with 16-bit PCMCIA
>card.
> Does any one know what it is waiting for? and why it failed? Thanks.
>
> push 32h
> push ebx
> call sdbus!SdbusReadRegisterUshort (aecda542)
> mov esi,eax
> test si,100h
> movzx edi,si
> mov dword ptr [ebp+8],edi
> je sdbus!SdhcGetErrorStatus+0x3b (aecd85eb)
>
> sdbus!SdhcGetErrorStatus+0x27:
> push 3Ch
> push ebx
> call sdbus!SdbusReadRegisterUshort (aecda542)
> mov dword ptr [ebp-4],eax
>


== 3 of 3 ==
Date: Mon, Aug 4 2008 9:54 pm
From: kunikiyou


Thank you very much, Alexander.

This happens when resuming from S4, that means the card has not been powered
on? Thanks.

"Alexander Grigoriev" wrote:

> Your card was unplugged or reset. All registers are read as FFFF. This is a
> common mistake to fail to check for the device unplug.
>
> "kunikiyou" <kunikiyou@discussions.microsoft.com> wrote in message
> news:D6CF02B0-E08F-43C4-9BCA-27950C5A9F6C@microsoft.com...
> >I see a endless loop in following code of sdbus.sys with 16-bit PCMCIA
> >card.
> > Does any one know what it is waiting for? and why it failed? Thanks.
> >
> > push 32h
> > push ebx
> > call sdbus!SdbusReadRegisterUshort (aecda542)
> > mov esi,eax
> > test si,100h
> > movzx edi,si
> > mov dword ptr [ebp+8],edi
> > je sdbus!SdhcGetErrorStatus+0x3b (aecd85eb)
> >
> > sdbus!SdhcGetErrorStatus+0x27:
> > push 3Ch
> > push ebx
> > call sdbus!SdbusReadRegisterUshort (aecda542)
> > mov dword ptr [ebp-4],eax
> >
>
>
>


==============================================================================
TOPIC: Get Device information according to GUID
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/4a971243d2ac50fa?hl=en
==============================================================================

== 1 of 1 ==
Date: Mon, Aug 4 2008 7:51 pm
From: Tim Roberts


Shiri Schneider <ShiriSchneider@discussions.microsoft.com> wrote:
>
>Thanks for your response.
>I tried using SetupDi functions in my code and i couldn't get the friendly
>name of the device properly.
>That's why i was intersted in getting the friendly name in other way without
>using SetupDi.

SetupDi is the right way. There are a lot of parameters, and a lot of ways
to get them wrong.

>Do you know if there us an API in the WMI that expose this options? - if not
>do you have an example of using SetupDi in c# to get the friendly name
>according to GUID.

I believe it is exposed through WMI, but I'm not enough of a WMI guy to
know it.
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.


==============================================================================
TOPIC: Programatically display Device Driver Update Dialog,...
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/4e507786e869f405?hl=en
==============================================================================

== 1 of 1 ==
Date: Mon, Aug 4 2008 7:54 pm
From: Tim Roberts


Kerem Gümrükcü <kareem114@hotmail.com> wrote:
>
>thanks for the kind answer! I am talking about
>these dialogs:
>
>http://www.pro-it-education.de/staff/keremg/misc/1.JPG
>http://www.pro-it-education.de/staff/keremg/misc/2.JPG
>
>How do i invoke them on a selected Device,...can you tell
>me how to do this,...?

Like I said, UpdateDriverForPlugAndPlayDevice. That is, assuming you
really want to update the driver, and not just invoke the dialogs.
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.


==============================================================================
TOPIC: Winusb vendor supplied control command transfer to the device
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/5f79b2e4c4b9a7ac?hl=en
==============================================================================

== 1 of 1 ==
Date: Mon, Aug 4 2008 9:43 pm
From: rb


Hi all

I wanna use control pipe of usb to send the vendor supplied commands to the
device (i.e usb printer)
I am using winusb to do so, but I am not getting the way through which I
could send custom commands to the device.
Could any one pls provide me with the details needed to do so.

thanxs


==============================================================================
TOPIC: AVStream driver: audio rendering problem
http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/96e2a0c0027beaf7?hl=en
==============================================================================

== 1 of 1 ==
Date: Mon, Aug 4 2008 10:24 pm
From: ShivaP


Hi,

I have a AVStream driver for a USB based A/V capture device. Issue is with
the audio decoding and rendering. video decoding and rendering is fine. The
Capture driver source filter audio output pin when connected to a audio
decoder supporting
MEDIASUBTYPE_AAC one type of decoding filter, its perfect.

But with another vendor decoding filter of the same media subtype_aac
format, audio decoding and rendering is not happening.

Pin connection is fine.
KSDATARANGE_AUDIO,

I have given MEDIATYPE as AUDIO
media subtype as MEDIASUBTYPE_AAC
specifier as WAVEFORMATEX
channel -2 (stereo), min&max bits/sample 16, min&max frequency -48000

I checked in GraphEdt application, both the decoder's one working & another
not working both have under Pin-->type the guid for the MEDIAsubtype_AAC. Pin
connection is fine with both the decoders to the capture filter audio output
pin.

Only in one decoder, audio rendering is not happening. I had put a dump
filter at the ouptut of the decoder, but no data isdumped in the o/p of
decoder.

If I put the dump at the o/p of audio o/p pin, data is dumped in the file
and I am able to play them.

When pin negotiation is successful, what else can stop a decoder from
decoding the audio frames.??

Can anybody give me some clue on this issue..

Thanks,..

==============================================================================

You received this message because you are subscribed to the Google Groups "microsoft.public.development.device.drivers"
group.

To post to this group, visit http://groups.google.com/group/microsoft.public.development.device.drivers?hl=en

To unsubscribe from this group, send email to microsoft.public.development.device.drivers+unsubscribe@googlegroups.com

To change the way you get mail from this group, visit:
http://groups.google.com/group/microsoft.public.development.device.drivers/subscribe?hl=en

To report abuse, send email explaining the problem to abuse@googlegroups.com

==============================================================================
Google Groups: http://groups.google.com?hl=en

No comments: