samba - Jun 2019 - error when trying to copy file from samba share to old Windows CE share

If I open the file with notepad++, make an edit and save it, then it
will copy successfully. If I open it with regular Notepad, and
edit/save the file, it still fails. Changing the filename/extension
did nothing. Is there a way on windows to view extra attributes or
something?

On Wed, Jun 19, 2019 at 3:13 PM Sonic <sonicsmith at gmail.com>
wrote:
>
> On Wed, Jun 19, 2019 at 10:41 AM Dan Arena <ddan39 at gmail.com>
wrote:
> > Yes, that is exactly the case. Just tested what you asked; copied a
> > file from PC desktop to samba share, then back to desktop, and now the
> > copy of the file will not copy from the PC desktop to the CE share,
> > but the original file still copies successfully. This is pretty odd...
>
> It appears it would be one of two things, either the file contents get
> changed/infected in a way that triggers some protection in the CE
> device, or the file name is converted/munged into a character
> set/encoding that doesn't work for the CE device. Try renaming that
> test file (including extension) that  wouldn't copy to the CE after
> the transfer to Samba and back and see if it will then copy. Also the
> contents can be verified by doing a "diff" (or whatever tool is
at
> your disposal) between the original and the one that made the round
> trip.
>
> Chris

Can't you compare the files (orig and round trip)? I think Windows has
"fc" - file compare (use "fc /b for binary files)" - can run
it from a
shell. This way you'll know if the content has changed.
You can examine the permissions/attributes of both files quite easily
- I doubt there's something hidden that wouldn't show up.

after opening with notepad++ and just adding/deleting a character so I
could click the Save button, `fc /b` still says "no differences
encountered"

On Wed, Jun 19, 2019 at 4:10 PM Sonic <sonicsmith at gmail.com>
wrote:
>
> Can't you compare the files (orig and round trip)? I think Windows has
> "fc" - file compare (use "fc /b for binary files)" -
can run it from a
> shell. This way you'll know if the content has changed.
> You can examine the permissions/attributes of both files quite easily
> - I doubt there's something hidden that wouldn't show up.