Re: [MiNT] ramdisk bug

[Alan Hourihane <alanh@fairlite.co.uk>]

On Wed, 2010-08-11 at 10:14 +0000, Helmut Karlowski wrote:
> Alan Hourihane wrote:
> 
> > On Wed, 2010-08-11 at 09:38 +0000, Helmut Karlowski wrote:
> > > Alan Hourihane wrote:
> > >
> > > > On Wed, 2010-08-11 at 00:26 +0200, Jo Even Skarstein wrote:
> > > > > When trying to reproduce Peter's problem with the ramdisk, I came across
> > > > > a problem that might be related: The fileselector doesn't list any files
> > > > > in u:\ram. Have tried opening files on u:\ram using the fileselector in
> > > > > various programs, the problem is always the same.
> > > > >
> > > > > However, if I type the name of the file I wish to load, the program
> > > > > loads it without problems. So the file is definitely there.
> > > > >
> > > > > The problem doesn't occur on other filesystems. See case #176 in the
> > > > > bugtracker. I'm using the trunk build from today.
> > > >
> > > > I suspect this is a UI problem. Commandline tools show no problems.
> > >
> > > 10 (XaSYS): Dpathconf(u:\ram\): bad path
> >
> > And that's meant to show what ?
> 
> What's bad with 'u:\ram\'?

It seems there's just a small name matching problem on lookup.
Completely unrelated to the reported problem.

> > Test app please.
> 
> XaAES.

Jeesh. A small test app that isolates and demonstrates, is what
I meant.

> > Try removing the trailing slash too.
> 
> This seems to work on all other FS - why not on ramfs?
> 
> So better remove it in the ramfs.

Sure. I can take a look at it but it doesn't fix the reported problem.

Alan.