On Wed, 2005-09-21 at 00:57, Uwe Bonnes wrote:
> Our IOCTL handling is a mess.
Seems like it has only been needed and implemented for CDs, so far.
> I had a patch that splitted out IOCTL code handling to separate, loadable
> dlls, but the patch went by unnoticed. Look for Mail from around July 10
> "Michael" == Michael Ost <[EMAIL PROTECTED]> writes:
Michael> On Tue, 2005-09-20 at 18:22, Vitaliy Margolen wrote:
>> Tuesday, September 20, 2005, 6:11:49 PM, Michael Ost wrote: > Should
>> I put my code in CDROM_DeviceIoControl? Or handle it in >
>> NtDeviceIoControlFile? Sh
> From: Vitaliy Margolen
>
> So all you need to do
> is to find where this information is stored on windows (it
> has to be somewhere in registry
It's an IOCTL, so it is passed to the disk driver on Windows. Although it is
possible that the driver caches the info in the registry, I don't think
On Tue, 2005-09-20 at 18:22, Vitaliy Margolen wrote:
> Tuesday, September 20, 2005, 6:11:49 PM, Michael Ost wrote:
> > Should I put my code in CDROM_DeviceIoControl? Or handle it in
> > NtDeviceIoControlFile? Should I pass all other IoControlCodes except
> > IOCTL_DISK_DRIVE_GET_GEOMETRY for a veri
Tuesday, September 20, 2005, 6:11:49 PM, Michael Ost wrote:
> Any suggestions for a good "wineish" way to implement an IOCTL_ call for
> an IDE disk?
Use SCSI ioctls I think they should work on IDE drives as well.
> I have some code that reads geometry information out of
> /proc/ide/hd?/geometry t
