A computer components & hardware forum. HardwareBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » HardwareBanter forum » General Hardware & Peripherals » Storage (alternative)
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Problem with phantom files on MemStickDuo



 
 
Thread Tools Display Modes
  #1  
Old March 19th 09, 06:15 PM posted to comp.sys.ibm.pc.hardware.storage
DManzaluni
external usenet poster
 
Posts: 45
Default Problem with phantom files on MemStickDuo

I have a 2 gig non-Sony Memstick ProDuo which seems only to be able to
hold 1 gig. After that it writes broken files. Full sized but
broken. So it can write a 50 gig video file but as soon as it starts
to read it, the read stops. No amount of self-formatting can help this
situation.

The situation seems to be caused in whole or in part by retaining some
files in a recycle folder called TRASHES which as far as I can see can
only be seen on a Mac. These mysterious files can be written over but
when one does so, the resulting files cannot be read. Is this an
inherent problem with the Sony format or is there something I can be
doing wrong? Once you have written about 100 files on a camera in
(for example) burst mode, it becomes a bit tedious deleting each one
individually: I wonder if deleting them collectively on the PC or the
Mac causes these phantom files to be created? Or if the stick still
wouldnt write them properly when writing gets to the second 'part' of
the stick?

Is there any way of checking these sticks for things aking to bad
clusters or sectors? Or indeed of marking them bad? Should I be able
to do this with some (new?) UBCD4WIN cd utility?
  #2  
Old March 20th 09, 02:34 AM posted to comp.sys.ibm.pc.hardware.storage
Arno[_3_]
external usenet poster
 
Posts: 1,425
Default Problem with phantom files on MemStickDuo

DManzaluni wrote:
r I have a 2 gig non-Sony Memstick ProDuo which seems only to be able to
hold 1 gig. After that it writes broken files. Full sized but
broken. So it can write a 50 gig video file but as soon as it starts
to read it, the read stops. No amount of self-formatting can help this
situation.


The situation seems to be caused in whole or in part by retaining some
files in a recycle folder called TRASHES which as far as I can see can
only be seen on a Mac. These mysterious files can be written over but
when one does so, the resulting files cannot be read. Is this an
inherent problem with the Sony format or is there something I can be
doing wrong? Once you have written about 100 files on a camera in
(for example) burst mode, it becomes a bit tedious deleting each one
individually: I wonder if deleting them collectively on the PC or the
Mac causes these phantom files to be created? Or if the stick still
wouldnt write them properly when writing gets to the second 'part' of
the stick?


Is there any way of checking these sticks for things aking to bad
clusters or sectors? Or indeed of marking them bad? Should I be able
to do this with some (new?) UBCD4WIN cd utility?


Maybe you got a faked drive, i.e. one with less flash than
claimed on the thing. These do report the wrong size to the
system. In your case it would need to report 50GB in
size. If this is the problem, you can only throw it away.

Arno
  #3  
Old March 20th 09, 08:14 PM posted to comp.sys.ibm.pc.hardware.storage
DManzaluni
external usenet poster
 
Posts: 45
Default Problem with phantom files on MemStickDuo

On Mar 19, 10:34*pm, Arno wrote:
DManzaluni wrote:

r I have a 2 gig non-Sony Memstick ProDuo which seems only to be able to





hold 1 gig. *After that it writes broken files. *Full sized but
broken. * So it can write a 50 gig video file but as soon as it starts
to read it, the read stops. No amount of self-formatting can help this
situation.
The situation seems to be caused in whole or in part by retaining some
files in a recycle folder called TRASHES which as far as I can see can
only be seen on a Mac. *These mysterious files can be written over but
when one does so, the resulting files cannot be read. *Is this an
inherent problem with the Sony format or is there something I can be
doing wrong? *Once you have written about 100 files on a camera in
(for example) burst mode, it becomes a bit tedious deleting each one
individually: I wonder if deleting them collectively on the PC or the
Mac causes these phantom files to be created? Or if the stick still
wouldnt write them properly when writing gets to the second 'part' of
the stick?
Is there any way of checking these sticks for things aking to bad
clusters or sectors? Or indeed of marking them bad? *Should I be able
to do this with some (new?) UBCD4WIN cd utility?


Maybe you got a faked drive, i.e. one with less flash than
claimed on the thing. These do report the wrong size to the
system. In your case it would need to report 50GB in
size. If this is the problem, you can only throw it away.

Arno- Hide quoted text -

- Show quoted text -


No, all the right sizes are being shown, - I can defragment this
drive when it starts not writing properly and it shows i gig used out
of 2 gig in the drive
  #4  
Old March 20th 09, 11:08 PM posted to comp.sys.ibm.pc.hardware.storage
Arno[_3_]
external usenet poster
 
Posts: 1,425
Default Problem with phantom files on MemStickDuo

DManzaluni wrote:
On Mar 19, 10:34?pm, Arno wrote:
DManzaluni wrote:

r I have a 2 gig non-Sony Memstick ProDuo which seems only to be able to





hold 1 gig. ?After that it writes broken files. ?Full sized but
broken. ? So it can write a 50 gig video file but as soon as it starts
to read it, the read stops. No amount of self-formatting can help this
situation.
The situation seems to be caused in whole or in part by retaining some
files in a recycle folder called TRASHES which as far as I can see can
only be seen on a Mac. ?These mysterious files can be written over but
when one does so, the resulting files cannot be read. ?Is this an
inherent problem with the Sony format or is there something I can be
doing wrong? ?Once you have written about 100 files on a camera in
(for example) burst mode, it becomes a bit tedious deleting each one
individually: I wonder if deleting them collectively on the PC or the
Mac causes these phantom files to be created? Or if the stick still
wouldnt write them properly when writing gets to the second 'part' of
the stick?
Is there any way of checking these sticks for things aking to bad
clusters or sectors? Or indeed of marking them bad? ?Should I be able
to do this with some (new?) UBCD4WIN cd utility?


Maybe you got a faked drive, i.e. one with less flash than
claimed on the thing. These do report the wrong size to the
system. In your case it would need to report 50GB in
size. If this is the problem, you can only throw it away.

Arno- Hide quoted text -

- Show quoted text -


No, all the right sizes are being shown, - I can defragment this
drive when it starts not writing properly and it shows i gig used out
of 2 gig in the drive


Hmm. So how can you write a 50G file to a 2G filesystem? That is
not possible....

Arno

  #5  
Old March 23rd 09, 02:35 AM posted to comp.sys.ibm.pc.hardware.storage
DManzaluni
external usenet poster
 
Posts: 45
Default Problem with phantom files on MemStickDuo

On Mar 20, 7:08*pm, Arno wrote:
DManzaluni wrote:
On Mar 19, 10:34?pm, Arno wrote:
DManzaluni wrote:


r I have a 2 gig non-Sony Memstick ProDuo which seems only to be able to


hold 1 gig. ?After that it writes broken files. ?Full sized but
broken. ? So it can write a 50 gig video file but as soon as it starts
to read it, the read stops. No amount of self-formatting can help this
situation.
The situation seems to be caused in whole or in part by retaining some
files in a recycle folder called TRASHES which as far as I can see can
only be seen on a Mac. ?These mysterious files can be written over but
when one does so, the resulting files cannot be read. ?Is this an
inherent problem with the Sony format or is there something I can be
doing wrong? ?Once you have written about 100 files on a camera in
(for example) burst mode, it becomes a bit tedious deleting each one
individually: I wonder if deleting them collectively on the PC or the
Mac causes these phantom files to be created? Or if the stick still
wouldnt write them properly when writing gets to the second 'part' of
the stick?
Is there any way of checking these sticks for things aking to bad
clusters or sectors? Or indeed of marking them bad? ?Should I be able
to do this with some (new?) UBCD4WIN cd utility?


Maybe you got a faked drive, i.e. one with less flash than
claimed on the thing. These do report the wrong size to the
system. In your case it would need to report 50GB in
size. If this is the problem, you can only throw it away.


Arno- Hide quoted text -


- Show quoted text -

No, all the right sizes are being shown, - *I can defragment this
drive when it starts not writing properly and it shows i gig used out
of 2 gig in the drive


Hmm. So how can you write a 50G file to a 2G filesystem? That is
not possible....

Arno- Hide quoted text -

- Show quoted text -


sorry for the mispring: Obviously i meant 50 mb, not gig
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Phantom Drive on My PC whitesmith Storage (alternative) 1 July 22nd 08 02:09 PM
phantom disk - longish Rod Speed Storage (alternative) 3 April 24th 05 04:00 AM
P5AD2 Premium phantom restart problem Dave Horoschak Asus Motherboards 7 November 18th 04 02:18 AM
Aerocool Phantom Mark Overclocking AMD Processors 0 August 17th 04 09:33 PM
Phantom Ryan Nvidia Videocards 0 May 11th 04 11:28 AM


All times are GMT +1. The time now is 09:07 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 HardwareBanter.
The comments are property of their posters.