-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Lyris ListManager
Sent: Thursday, November 18, 2004 10:30 AM
To: ntdev index recipients
Subject: ntdev index: November 17, 2004
ntdev index for Wednesday, November 17, 2004.
Subject: RE: how to deal with the usb modem io control code for wi ndows
98
From: Dsingh@in.safenet-inc.com
Summary: This message is in MIME format. Since your mail reader
ID: 68013
Subject: RE: On Memory Allocation routines
From: “anees mannessery”
Summary: Thanks a lot Mats. That was indeed a detailed answer. I
ID: 68015
Subject: RE: On Memory Allocation routines
From: Mats PETERSSON
Summary: Yes, if you do lots of allocations and de-allocations,
ID: 68016
Subject: RE: Bluetooth driver stack implementations
From: “Shahar Talmi”
Summary: I am probably going to filter above the host controller
ID: 68018
Subject: Re: Getting ip address of the host from kernel mode
From: “Seshagiri Babu K.V.”
Summary: --0-2017134285-1100698092=:36406|Content-Type: text/pla
ID: 68019
Subject: Re: Getting ip address of the host from kernel mode
From: “Maxim S. Shatskih”
Summary: This is a multi-part message in MIME format.|------=_Ne
ID: 68021
Subject: IP Address Setting for Ethernet Interface
From: “Sagayac”
Summary: This is a multi-part message in MIME format.|------=_Ne
ID: 68025
Subject: RE: Bluetooth driver stack implementations
From: “Doron Holan”
Summary: WIDCOMM uses disjoint stacks, they don’t use a bus driv
ID: 68027
Subject: Re: IP Address Setting for Ethernet Interface
From: “Maxim S. Shatskih”
Summary: This is a multi-part message in MIME format.|------=Ne
ID: 68028
Subject: RE: Bluetooth driver stack implementations
From: “Shahar Talmi”
Summary: Yes, I’m aware of the WIDCOMM design. I already did a l
ID: 68029
Subject: Re: Bluetooth driver stack implementations
From: “Gary G. Little”
Summary: An obscure search on google will prove that. :)|–|The
ID: 68031
Subject: RE: Mounting network drive as a fixed drive
From: =?utf-8?Q?Jo=C5=BEe_Mlakar?=
Summary: U28gdGhlcmUgaXMgbm9vbmUgaGVyZSB0aGF0IGNhbiBwcm9wb3NlIGE
ID: 68034
Subject: RE: Bluetooth driver stack implementations
From: “Doron Holan”
Summary: You have not been 100% clear what your purposes are (wh
ID: 68035
Subject: Bug in OSR DeviceTree?
From: “Shahar Talmi”
Summary: While looking at the Device Tree of the MS Bluetooth dr
ID: 68036
Subject: SIMBAD
From: “Jamey Kirby”
Summary: OK, I have searched and searched and I can not find SIM
ID: 68038
Subject: RE: Is this Multithread safe, or does it require Interlocked
access?
From: “George Reilly (Volt)”
Summary: This is a multi-part message in MIME format.|------=_N
ID: 68041
Subject: RE: Bluetooth driver stack implementations
From: Calvin Guan
Summary: This message is in MIME format. Since your mail reader
ID: 68042
Subject: Re: Spammers are minning these OSR lists
From: PeterGV
Summary: Michal Vodicka wrote:|> Great. Fake sender address and
ID: 68043
Subject: Re: znuwwj
From: PeterGV
Summary: wangweijuan wrote:|> |I couldn’t have said it better my
ID: 68044
Subject: Re: Bug in OSR DeviceTree?
From: PeterGV
Summary: Shahar Talmi wrote:|> While looking at the Device Tree
ID: 68045
Subject: ATA commands
From: “Greg Jacklin”
Summary: Is there an example in the DDK that shows how to send A
ID: 68046
Subject: RE: ATA commands
From: “Mark Overby”
Summary: Not in current DDK’s. I think you would have to look at
ID: 68047
Subject: controlling device power states
From: “Kutty Banerjee”
Summary: Hi,| Is there a technique to control (by control panel,
ID: 68048
Subject: RE: Bluetooth driver stack implementations
From: “Doron Holan”
Summary: As said many times, if someone is an admin on the box (
ID: 68049
Subject: RE: controlling device power states
From: “Doron Holan”
Summary: There is no API to control devices themselves. The CPU
ID: 68050
Subject: Re: controlling device power states
From: “Kutty Banerjee”
Summary: May I reframe my question as follows. I figure that I/O
ID: 68051
Subject: Re: ATA commands
From: “Greg Jacklin”
Summary: I looked under the DDK and there appears to be an IOCTL
ID: 68052
Subject: RE: controlling device power states
From: “Doron Holan”
Summary: Only the power policy owner for the device is allowed t
ID: 68053
Subject: RE: ATA commands
From: “Mark Overby”
Summary: What layer are you looking to do this at, and more spec
ID: 68054
Subject: RE: Bluetooth driver stack implementations
From: Calvin Guan
Summary: This message is in MIME format. Since your mail reader
ID: 68055
Subject: Re: controlling device power states
From: “Kutty Banerjee”
Summary: Hi,|>"If you need the device in full power, do somethin
ID: 68056
Subject: RE: Bluetooth driver stack implementations
From: “Doron Holan”
Summary: If they are not an admin, they cannot touch the filters
ID: 68057
Subject: RE: controlling device power states
From: “Doron Holan”
Summary: Let’s see, these are pure guesses:|HD: cause disk traff
ID: 68058
Subject: Re: ATA commands
From: “Greg Jacklin”
Summary: I will be talking to a sata hdd and will be at usermode
ID: 68059
Subject: RE: ATA commands
From: “Mark Overby”
Summary: There is a seperate IOCTL set for SMART.|IOCTL_SCSI_MIN
ID: 68061
Subject: RE: Bluetooth driver stack implementations
From: “Prokash Sinha”
Summary: Yes indeed :)|-pro|-----Original Message-----|From: bou
ID: 68065
Subject: RE: controlling device power states
From: Dsingh@in.safenet-inc.com
Summary: This message is in MIME format. Since your mail reader
ID: 68066
---------------------------------------------------------------------
To receive the full text of these messages, send the following command
to xxxxx@lists.osr.com
get ntdev 20041117
Or, you can retrieve specific messages with a command such as:
get ntdev 68013 68015
---------------------------------------------------------------------
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@wipro.com To
unsubscribe send a blank email to xxxxx@lists.osr.com