[jcifs] RE: That SMB_COM_CLOSE thing...

[Christopher R. Hertel]

On Tue, Aug 20, 2002 at 12:48:40AM -0400, Allen, Michael B (RSCH) wrote:
:
> Well, "fixed" in that it just reads from the source and writes to the
> destination but yes, it does not use SMB_COM_COPY.

Yep.
I meant "fixed" as in the way that a dog or cat is "fixed" at the vet's.  
;)

> I have however prepared a super SMB_COM_COPY experimenter's dream of a
> jar file:
> 
> http://users.erols.com/mballen/jcifs-0.7.0bCopy.jar
> 
> The copyTo() method in this jar *does* use SMB_COM_COPY. And
> successfully if you useUnicode = false and you do not write the 0x4 format
> codes before each string. Doesn't look like ethereal decodes much of it but
> Netmon sure does.

How do you mean successfully?  Does windows support SMB_COM_COPY in some
forms?  From the discussion I thought (but I haven't been paying as much
attention as I should) that SMB_COM_COPY was simply not implemented in
Windows.

> 	I've made it so you can change just about every SMB_COM_COPY parameter
> 	using jCIFS properties. Here's the list:

Kewl.  Thanks!

> 	Have fun and watch out for blue screens!

Yep!

Tomorrow...  Gotta get some sleep.

Chris -)-----

-- 
Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/     -)-----   crh at ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org