[Virtualacorn-list] File present in VA but absent in Windows

[Brian Jordan]

On 28 Dec, M J D Brown <mjdb at dorevale.demon.co.uk> wrote:

On 28 Dec, Brian Jordan <brian.jordan9 at btinternet.com> wrote:

[Snip]

> >> When I clamber up the directory tree under Windows and open the
> >> relevant directory the file is not there and cannot be persuaded to
> >> appear when the option to show hidden files is invoked. Is this an
> >> indication of a hard drive problem, a subtlety in Windows or me
> >> being particularly thick? If any or none of the above would some
> >> kind soul help me to fix this?

> This is very odd, as I was under the distinct impression that Virtual
> RISC OS hard drives were actually single files so far as the Windows
> filing system are concerned.  Thus I am surprised that the deletion of
> a single RISCOS file should make any use of the Windows Recycle Bin.
> What seems to be happening is that the  RISC OS deletion action is
> being thwarted by Windows deciding that the file is presently in use by
> a running program ie by Virt...SA as reported by Brian Jordan below.

To clarify, I am using HostFS with my VA. A directory, called HardDISC4
in this case, is present under Windows and within it is the full
directory tree as seen by RISC OS behind the drive icon on the VA icon
bar. Individual files can be moved, edited renamed etc. from both sides.
My problem was that the recycle bin ($.!Boot.Resources.!RecycBin.Bin)[1]
had within it a file which could be seen but not written to under RISC OS
and which could not be seen at all in a Windows directory viewer. Until,
that is, I set a Windows option to view hidden files. The missing file
then became visible under Windows, which claimed it was a system file,
[2] and it was finally deleted.

[Snip]

[1] The RISC OS bin under Select works well, deleting a file sends it to
the bin which can be viewed from the icon bar and which appends "-1",
"-2" etc to identically named files. A configurable expiry time controls
when the files are finally deleted.

[2] It was originally a .jpg file retyped to .txt which I had been
experimenting with the better to understand EXIF tags. Maybe I somehow
scrambled a byte sequence in there which meant something to Windows
causing it
to be classified as a system file?

As I posted, all is now working as I expect and I no longer get the
message that a file cannot be removed from the bin every time I start the
VA.

-- 
______________________________________________________________________

Brian Jordan
>From somewhere in North Hampshire. England. UK.
______________________________________________________________________