Hello,

I've problems with my driver(w2k, wxp)

1) formating virtual drive with fat32, i get error: system could not
finish operation, but drive was successfully formated. NTFS works fine.

2) sometimes system sends strange ioctl 0x0066001b, what is this?
Device type 66, command 06 ??

3) my major trouble, i cannot share my virtual drive,
When someone trying access to my shared virtual drive, gets error
"Not enough server storage is available to process this command".
Not all my machines show this error, sometimes works fine :(

Does someone have solution for mounting readonly ntfs drives on w2k?
Maybe exist a patch for that.

--
Marcin Gabryszewski

Re: virtual drive driver and few problems by Z

Z
Thu Mar 09 18:57:32 CST 2006

A write-protection should be added to your driver.

If your driver is a miniport one, some mode sense data is necessary.

"Marcin Gabryszewski" <look_at_footer@invalid.addres.com> wrote in message
news:duovh1$sl4$1@nemesis.news.tpi.pl...
> Hello,
>
> I've problems with my driver(w2k, wxp)
>
> 1) formating virtual drive with fat32, i get error: system could not
> finish operation, but drive was successfully formated. NTFS works fine.
>
> 2) sometimes system sends strange ioctl 0x0066001b, what is this?
> Device type 66, command 06 ??
>
> 3) my major trouble, i cannot share my virtual drive,
> When someone trying access to my shared virtual drive, gets error
> "Not enough server storage is available to process this command".
> Not all my machines show this error, sometimes works fine :(
>
> Does someone have solution for mounting readonly ntfs drives on w2k?
> Maybe exist a patch for that.
>
> --
> Marcin Gabryszewski



Re: virtual drive driver and few problems by heinz

heinz
Fri Mar 10 00:07:23 CST 2006

> ioctl 0x0066001b, what is this?

That would be FT_BALANCED_READ_MODE

As far as your other issues, you can base line your responses to
commands versus say a flash card reader. It could be you are not
handling something you need or reporting an improper response but I
suspect there is actually a data corruption issue here and so look
closely at your reads and writes. It might be helpful to run a util to
watch the I/O activity in this case to see what is going on:
http://www.perisoft.net/bushound