[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] ramdisk bug
On Thu, 12 Aug 2010 14:24:22 , Peter Slegg <p.slegg@scubadivers.co.uk> wrote:
>
> I tried the trunk build from yesterday and arcview misbehaves
> again.
>
Hello,
I wanted to have a look at this ramdisk issue, but unfortunately
I can't find ramfs.xfs on my system.
I can neither find it in the archives on my disc, nor on the recently
downloaded or available builds, nor even on Sapremint pages.
I found this : http://sparemint.atariforge.net/sparemint/mint/kernel/xfs/fnramfs/fnramfs-0.70.tar.gz
but the file is reported as corrupted.
Might someone point me to the right file ?
Edit : OK, I could find a not corrupted LZH file there :
http://sparemint.org/sparemint/mint/kernel/xfs/fnramfs/fnramfs-0.70.lzh
which I copied to my MiNT folder.
Then, after reboot, as it wasn't bound to r, unlike what the install file
states, I added the line alias r: U:\ram into the cnf file.
Rebooted, checked that double-clicking r opened the drive, then opened
the fnramfs lzh file and dragged/dropped it into r... which lead to nothing.
Or, rather, a message from ArcView complaining it couldn't find the file.
So, I tried with selecting a file into the archive and dropping it into
the drive. Then, it said that the file had been extracted but, when looking
at r content, nothing was there, with "no objects" being displayed.
I then dragged & dropped a single file from another drive, and this could
be copied to and was displayed into r.
I gave it another try with the archive, which this time ArcView said it had
been correctly extracted, but which still wasn't displayed into the drive.
As it's behaving the same way with two different ramdisk files, I think it's
rather an ArcView or system issue - unless both the ramdisks were built
using the same libs, compiler, source, ... ? -.
Regards,
J.-Luc