Why does copying a video file to flash drive save only as audio?

[L'Ecrevisse]

Using Windows XP, I have been trying to save a video saved to my HDD to a
flash drive.

The problem is, when I r/click and select the 'copy' option, it saves it to
the flash drive as an audio file.

When I r/click and select 'move' it saves it to the flash drive and then
plays correctly as a video.

Could someone please explain to me what has happened and what I need to do
to change whatever has happened to the 'copy' function?

 

[smlunatick]

Using Windows XP, I have been trying to save a video saved to my HDD to a
flash drive.

The problem is, when I r/click and select the 'copy' option, it saves it to
the flash drive as an audio file.

When I r/click and select 'move' it saves it to the flash drive and then
plays correctly as a video.

Could someone please explain to me what has happened and what I need to do
to change whatever has happened to the 'copy' function?

What is the complete size of the video file? Most "flash" drives are
usually formatted in FAT32 mode. Microsoft has placed a limit on th e
file size stored on FAT32 as 4GB.

 

[L''Ecrevisse]

What is the complete size of the video file? Most "flash" drives are
usually formatted in FAT32 mode. Microsoft has placed a limit on th e
file size stored on FAT32 as 4GB.

The original video file was about 5 minutes long, or less than 100MB.

It did save as a complete file, so that is not the problem.

 

[Frank Saunders MS-MVP IE,OE/WM]

The original video file was about 5 minutes long, or less than 100MB.

It did save as a complete file, so that is not the problem.

If you copy it back to your hard drive does it have the video?

 

[Mick Murphy]

Instead of right-click Copy or Move, I always use right-click>Send To>Send it
to your Flash Drive.


-
Mick Murphy - Qld - Australia

 

[Elmo]

Using Windows XP, I have been trying to save a video saved to my HDD to a
flash drive.

The problem is, when I r/click and select the 'copy' option, it saves it to
the flash drive as an audio file.

When I r/click and select 'move' it saves it to the flash drive and then
plays correctly as a video.

Could someone please explain to me what has happened and what I need to do
to change whatever has happened to the 'copy' function?

This might help: Open "My Computer", right-click the device, click
Properties, click the AutoPlay tab, and change the way the device is
handled.

 

[M.I.5¾]

Using Windows XP, I have been trying to save a video saved to my HDD to a
flash drive.

The problem is, when I r/click and select the 'copy' option, it saves it
to
the flash drive as an audio file.

When I r/click and select 'move' it saves it to the flash drive and then
plays correctly as a video.

Could someone please explain to me what has happened and what I need to do
to change whatever has happened to the 'copy' function?

What is the complete size of the video file? Most "flash" drives are
usually formatted in FAT32 mode. Microsoft has placed a limit on th e
file size stored on FAT32 as 4GB.

 

[smlunatick]

What is the complete size of the video file?  Most "flash" drives are
usually formatted in FAT32 mode.  Microsoft has placed a limit on th e
file size stored on FAT32 as 4GB.

-----------

The limit is nothing to do with microsoft.  It is a physical limitationof
the FAT32 filing system.  Microsoft couldn't have made it larger if they
wanted to (except by using a different filing system).

If this is a limit of the FAT32 system, then why can you have large
file in excess of 4GB under the older Windows 98.

 

[Bill in Co.]

If this is a limit of the FAT32 system, then why can you have large
file in excess of 4GB under the older Windows 98.

BS. Give *one* example of that (with FAT32)

 

[M.I.5¾]

What is the complete size of the video file? Most "flash" drives are
usually formatted in FAT32 mode. Microsoft has placed a limit on th e
file size stored on FAT32 as 4GB.

-----------

The limit is nothing to do with microsoft. It is a physical limitation of
the FAT32 filing system. Microsoft couldn't have made it larger if they
wanted to (except by using a different filing system).

If this is a limit of the FAT32 system, then why can you have large
file in excess of 4GB under the older Windows 98.

---------------

You couldn't. Windows 98 did not support files larger than 4GB. In fact
Windows 98 (and indeed the whole Win 9x line) had a serious bug that limited
files to 2GB for most applications under FAT32. The Win9x products
incorrectly handled the file size a signed number. This was eroneous as a
negative file size is an obviously absurd concept. But nevertheless, when
the file exceded 2GB in size, windows reported its size as negative and most
applications couln't cope. A few applications were aware of the problem
and internally conveted the file size to a unsigned number and then
correctly handled files of between 2 and 4GB.

 

[Bill in Co.]

If this is a limit of the FAT32 system, then why can you have large
file in excess of 4GB under the older Windows 98.

---------------

You couldn't. Windows 98 did not support files larger than 4GB. In fact
Windows 98 (and indeed the whole Win 9x line) had a serious bug that
limited
files to 2GB for most applications under FAT32. The Win9x products
incorrectly handled the file size a signed number. This was eroneous as a
negative file size is an obviously absurd concept. But nevertheless, when
the file exceded 2GB in size, windows reported its size as negative and
most
applications couln't cope. A few applications were aware of the problem
and internally conveted the file size to a unsigned number and then
correctly handled files of between 2 and 4GB.

That's because one of the bits (the MSB) in the word storing the filesize
was reserved for the sign bit (using signed integers), cutting the effective
range in half. I sure remember that problem popping up in Win98 - files
were limited to only 2 GB max, not 4 GB, with some apps.

And I think that bug was corrected in Win ME, with the newer version of the
shell32.dll file (that came with Win ME), if memory serves me correct. But
of course you were still limited to 4 GB for any single file, no matter
what, as long as you were using FAT 32.
And there never was a patch released that updated shell32.dll to fix that
for Win98/SE.

 

[M.I.5¾]

That's because one of the bits (the MSB) in the word storing the filesize
was reserved for the sign bit (using signed integers), cutting the
effective range in half. I sure remember that problem popping up in
Win98 - files were limited to only 2 GB max, not 4 GB, with some apps.

And I think that bug was corrected in Win ME, with the newer version of
the shell32.dll file (that came with Win ME), if memory serves me correct.
But of course you were still limited to 4 GB for any single file, no
matter what, as long as you were using FAT 32.
And there never was a patch released that updated shell32.dll to fix that
for Win98/SE.

No it wasn't fixed in WinME much like a whole raft of other stupid bugs. It
was fixed in the NT product line.