The topic under discussion all follows from an original question "
Is it possible to rename HardDisc4?"
.... and what a user would need to do to achieve that.
The discussion has made it clear that you do not recommend that - and nobody has disputed that point with you.
However, a second person stated that he had made it all work with one exception
Quote:
Sorry to drag up this old thread but I've just been moving my VRPC installation and setting things up again, which included renaming the harddisc. I did get a single "disc not found" error, which I tracked down to the file boot.tasks.AccessSet. This references HostFS, so I suspect it's a VA-created file. Perhaps it could be re-jigged to have a relative file reference?
I simply answered his final question, giving a method by which he could eliminate his single remaining error.
I stick to my assertion that relative paths will work. The following just in the AccessSet file (on either VRPC or a Real RiscPC) will share multiple folders and the root of the hard disc.
Share Public
Share Apps -readonly
Share $
However, I remind you that I did say:
Quote:
I agree - it is far better to quote absolute paths.
Of course, I should also have commented on his "suspicion" that
boot.tasks.AccessSet file was a VA-created file. It is not. It is created by the !ShareFS application whether on a Real RiscPC or on VRPC.