Dear All,

Is it possilbe to set "MaximumTransferSize" more than 4096 Byte in WinXP.
I want to set it as 4608 Byte.
But if I do that in DDK, it show blue screen (-.-) and show following error
message
---- on blue screen ---=
IRQL_NOT_LESS_OR_EQUAL
STOP 0x0000000A
( 0x00000166,
0x00000002,
0x00000000,
0x804FC726)
---- Monitoring Driver ---
irp 0xC000000D
urp 0x80000300

Along to the document http://www.it-faq.pl/mskb/832/430.HTM, and
http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;832430, it looks
no problem in iso. mode.


DDK version 2600.1106
OS version winXP with SP2

Question 1) Along to my testing, when I use isorwr_mode(isorwr.c), I can
read over than 4608 byte by setting MaximumTransferSize as 4608 byte.
But if I use isostrm_mode(isostrm.c), can't set MaximumTransferSize as 4608
byte. Why I can not use 4608 MaximumTransferSize?
Is there any reference or document ??

Question 2) Sample inf file in the web, I find there is a definition for
MaximumTransferSize, what's the meaning of right two hex and decimal value?
.............
[RioDrv.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,RioDrv.sys
HKLM,"System\Currentcontrolset\Services\RioDrv\Parameters","MaximumTransferSize",0x10001,65536
............

Thanks~~
And Happy new year~~

Re: MaximumTransferSize in usb2.0, isochronous mode by Doron

Doron
Wed Jan 04 02:09:06 CST 2006

what is the callback when the bluescreen occurs? the output of !analyze -v?

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.


"noyman" <noyman@discussions.microsoft.com> wrote in message
news:1771C687-B056-432E-A22F-BE4156740332@microsoft.com...
> Dear All,
>
> Is it possilbe to set "MaximumTransferSize" more than 4096 Byte in WinXP.
> I want to set it as 4608 Byte.
> But if I do that in DDK, it show blue screen (-.-) and show following
> error
> message
> ---- on blue screen ---=
> IRQL_NOT_LESS_OR_EQUAL
> STOP 0x0000000A
> ( 0x00000166,
> 0x00000002,
> 0x00000000,
> 0x804FC726)
> ---- Monitoring Driver ---
> irp 0xC000000D
> urp 0x80000300
>
> Along to the document http://www.it-faq.pl/mskb/832/430.HTM, and
> http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;832430, it
> looks
> no problem in iso. mode.
>
>
> DDK version 2600.1106
> OS version winXP with SP2
>
> Question 1) Along to my testing, when I use isorwr_mode(isorwr.c), I can
> read over than 4608 byte by setting MaximumTransferSize as 4608 byte.
> But if I use isostrm_mode(isostrm.c), can't set MaximumTransferSize as
> 4608
> byte. Why I can not use 4608 MaximumTransferSize?
> Is there any reference or document ??
>
> Question 2) Sample inf file in the web, I find there is a definition for
> MaximumTransferSize, what's the meaning of right two hex and decimal
> value?
> .............
> [RioDrv.AddReg]
> HKR,,DevLoader,,*ntkern
> HKR,,NTMPDriver,,RioDrv.sys
> HKLM,"System\Currentcontrolset\Services\RioDrv\Parameters","MaximumTransferSize",0x10001,65536
> ............
>
> Thanks~~
> And Happy new year~~



Re: MaximumTransferSize in usb2.0, isochronous mode by noyman

noyman
Wed Jan 04 02:35:03 CST 2006

in Usostrm.c file..
IsoUsb_IsoIrp_Complete()
{
//to check if occupied . dwDataSize is 4608..
ProbeForWrite(pOutBuffer, dwDataSize, 1);
}

Thanks..



"Doron Holan [MS]" wrote:

> what is the callback when the bluescreen occurs? the output of !analyze -v?
>
> 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.
>
>
> "noyman" <noyman@discussions.microsoft.com> wrote in message
> news:1771C687-B056-432E-A22F-BE4156740332@microsoft.com...
> > Dear All,
> >
> > Is it possilbe to set "MaximumTransferSize" more than 4096 Byte in WinXP.
> > I want to set it as 4608 Byte.
> > But if I do that in DDK, it show blue screen (-.-) and show following
> > error
> > message
> > ---- on blue screen ---=
> > IRQL_NOT_LESS_OR_EQUAL
> > STOP 0x0000000A
> > ( 0x00000166,
> > 0x00000002,
> > 0x00000000,
> > 0x804FC726)
> > ---- Monitoring Driver ---
> > irp 0xC000000D
> > urp 0x80000300
> >
> > Along to the document http://www.it-faq.pl/mskb/832/430.HTM, and
> > http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;832430, it
> > looks
> > no problem in iso. mode.
> >
> >
> > DDK version 2600.1106
> > OS version winXP with SP2
> >
> > Question 1) Along to my testing, when I use isorwr_mode(isorwr.c), I can
> > read over than 4608 byte by setting MaximumTransferSize as 4608 byte.
> > But if I use isostrm_mode(isostrm.c), can't set MaximumTransferSize as
> > 4608
> > byte. Why I can not use 4608 MaximumTransferSize?
> > Is there any reference or document ??
> >
> > Question 2) Sample inf file in the web, I find there is a definition for
> > MaximumTransferSize, what's the meaning of right two hex and decimal
> > value?
> > .............
> > [RioDrv.AddReg]
> > HKR,,DevLoader,,*ntkern
> > HKR,,NTMPDriver,,RioDrv.sys
> > HKLM,"System\Currentcontrolset\Services\RioDrv\Parameters","MaximumTransferSize",0x10001,65536
> > ............
> >
> > Thanks~~
> > And Happy new year~~
>
>
>

Re: MaximumTransferSize in usb2.0, isochronous mode by Doron

Doron
Wed Jan 04 10:08:39 CST 2006

1) you can only call ProbeForWrite at passive level, this looks like a
completion routine which will probably run at dispatch level
2) you must use SEH (try/catch) around a call to ProbeForWrite
3) you must not pass NULL

why are you even probing the buffer in your completion routine? you should
probe the buffer when you receive it, lock it down and then you are done...

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.


"noyman" <noyman@discussions.microsoft.com> wrote in message
news:7A207BA6-E415-4DA5-B6DF-FDC8BAF48B4D@microsoft.com...
> in Usostrm.c file..
> IsoUsb_IsoIrp_Complete()
> {
> //to check if occupied . dwDataSize is 4608..
> ProbeForWrite(pOutBuffer, dwDataSize, 1);
> }
>
> Thanks..
>
>
>
> "Doron Holan [MS]" wrote:
>
>> what is the callback when the bluescreen occurs? the output of
>> !analyze -v?
>>
>> 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.
>>
>>
>> "noyman" <noyman@discussions.microsoft.com> wrote in message
>> news:1771C687-B056-432E-A22F-BE4156740332@microsoft.com...
>> > Dear All,
>> >
>> > Is it possilbe to set "MaximumTransferSize" more than 4096 Byte in
>> > WinXP.
>> > I want to set it as 4608 Byte.
>> > But if I do that in DDK, it show blue screen (-.-) and show following
>> > error
>> > message
>> > ---- on blue screen ---=
>> > IRQL_NOT_LESS_OR_EQUAL
>> > STOP 0x0000000A
>> > ( 0x00000166,
>> > 0x00000002,
>> > 0x00000000,
>> > 0x804FC726)
>> > ---- Monitoring Driver ---
>> > irp 0xC000000D
>> > urp 0x80000300
>> >
>> > Along to the document http://www.it-faq.pl/mskb/832/430.HTM, and
>> > http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;832430, it
>> > looks
>> > no problem in iso. mode.
>> >
>> >
>> > DDK version 2600.1106
>> > OS version winXP with SP2
>> >
>> > Question 1) Along to my testing, when I use isorwr_mode(isorwr.c), I
>> > can
>> > read over than 4608 byte by setting MaximumTransferSize as 4608 byte.
>> > But if I use isostrm_mode(isostrm.c), can't set MaximumTransferSize as
>> > 4608
>> > byte. Why I can not use 4608 MaximumTransferSize?
>> > Is there any reference or document ??
>> >
>> > Question 2) Sample inf file in the web, I find there is a definition
>> > for
>> > MaximumTransferSize, what's the meaning of right two hex and decimal
>> > value?
>> > .............
>> > [RioDrv.AddReg]
>> > HKR,,DevLoader,,*ntkern
>> > HKR,,NTMPDriver,,RioDrv.sys
>> > HKLM,"System\Currentcontrolset\Services\RioDrv\Parameters","MaximumTransferSize",0x10001,65536
>> > ............
>> >
>> > Thanks~~
>> > And Happy new year~~
>>
>>
>>



Re: MaximumTransferSize in usb2.0, isochronous mode by Alexander

Alexander
Wed Jan 04 10:09:57 CST 2006

If it's a user mode request, the buffer cannot be touched, unless you remap
it to kernel mode address.
Note that ProbeForWrite can throw an exception which you're supposed to
catch.

"noyman" <noyman@discussions.microsoft.com> wrote in message
news:7A207BA6-E415-4DA5-B6DF-FDC8BAF48B4D@microsoft.com...
> in Usostrm.c file..
> IsoUsb_IsoIrp_Complete()
> {
> //to check if occupied . dwDataSize is 4608..
> ProbeForWrite(pOutBuffer, dwDataSize, 1);
> }
>
> Thanks..
>
>
>
> "Doron Holan [MS]" wrote:
>
>> what is the callback when the bluescreen occurs? the output of
>> !analyze -v?
>>
>> 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.
>>
>>
>> "noyman" <noyman@discussions.microsoft.com> wrote in message
>> news:1771C687-B056-432E-A22F-BE4156740332@microsoft.com...
>> > Dear All,
>> >
>> > Is it possilbe to set "MaximumTransferSize" more than 4096 Byte in
>> > WinXP.
>> > I want to set it as 4608 Byte.
>> > But if I do that in DDK, it show blue screen (-.-) and show following
>> > error
>> > message
>> > ---- on blue screen ---=
>> > IRQL_NOT_LESS_OR_EQUAL
>> > STOP 0x0000000A
>> > ( 0x00000166,
>> > 0x00000002,
>> > 0x00000000,
>> > 0x804FC726)
>> > ---- Monitoring Driver ---
>> > irp 0xC000000D
>> > urp 0x80000300
>> >
>> > Along to the document http://www.it-faq.pl/mskb/832/430.HTM, and
>> > http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;832430, it
>> > looks
>> > no problem in iso. mode.
>> >
>> >
>> > DDK version 2600.1106
>> > OS version winXP with SP2
>> >
>> > Question 1) Along to my testing, when I use isorwr_mode(isorwr.c), I
>> > can
>> > read over than 4608 byte by setting MaximumTransferSize as 4608 byte.
>> > But if I use isostrm_mode(isostrm.c), can't set MaximumTransferSize as
>> > 4608
>> > byte. Why I can not use 4608 MaximumTransferSize?
>> > Is there any reference or document ??
>> >
>> > Question 2) Sample inf file in the web, I find there is a definition
>> > for
>> > MaximumTransferSize, what's the meaning of right two hex and decimal
>> > value?
>> > .............
>> > [RioDrv.AddReg]
>> > HKR,,DevLoader,,*ntkern
>> > HKR,,NTMPDriver,,RioDrv.sys
>> > HKLM,"System\Currentcontrolset\Services\RioDrv\Parameters","MaximumTransferSize",0x10001,65536
>> > ............
>> >
>> > Thanks~~
>> > And Happy new year~~
>>
>>
>>