www.virtualacorn.co.uk/forum

Just trying to transfer a bunch of directories and files across to the WinXp side using a removeable disc, when the filer on XP stopped when it got to a file (created withing RO) that ended in / as in filename/ (filename.) whereas filename/txt (filename.txt) would be fine, ending in / (.) was 'unreadable'.

I created the files when it was a sprite image and I was almost ready to make it a /jpg (.jpg)

And XP quit the copy action!
Did not offer to 'skip'.
Is this for real?

They also don't say which directory the file is in so I could rename it. Just file <name/> cannot be read, stopping the copy action. Or some such. If I happen to know such a file, XP won't let me rename it either.

Is this a toy OS or what.

Brian
(first time XP-user)

All operating systems have restrictions on the character set that can be used in a filename, this includes RISC OS (for example &, $ etc)

But a period is allowable in Windows, isn't it? Perhaps only with a 2 character minimum file extension following it.
I assumed RISC OS turned the / char into . as usual when we write /txt at the end of a text file, so that Winxp will see it as that.
Annoying the way it doesnt 'skip' problem files.

If you try and rename a file under Windows so that it ends in a full stop/period you will find that the renamed file does not have the full stop at the end. If you have files with (effectively) broken extensions I am not sure what else you could reasonably expect to happen.