using fast mem to display directory contents

trixster · 16 April 2016, 13:16

Hi all,

I'm using both Fblit and Ftext in my startup-sequence and the latest version of PeterK's icon.library. All 'seem' to work fine and Ftext certainly seems to improve text rendering speed and is verifiable using the tests in sysspeed. Icon.library does its thing and icons reside nicely in fast memory, not chip memory.

However.... I've noticed that opening a Workbench directory with a very large number of files and selecting View By -> Name starts to eat up Chip Memory by the bucket load. View By -> Icon does not as Fast Memory is used, as expected.

Is this normal? Is there a way to get directories to use fast memory when viewing them by Names rather than Icon?

Cylon · 16 April 2016, 22:52

You are probably using Workbench 3.1 or lower. This (stupid) ChipRAM eating for text display is gone with Workbench 3.5 and above iirc.
So, yes, this is (was) normal. Blame those silly developers.

trixster · 17 April 2016, 00:06

And there's no patch to fix Names view?

daxb · 17 April 2016, 16:27

Maybe you go for a file mananger instead? Is there a reason for using workbench windows with text view?

trixster · 17 April 2016, 17:30

My NAS has an unsorted folder with over 4000 album-less random mp3s in it. I'd like to be able to drag and drop them straight into AmigaAmp rather than have to move the ones I want to play into another directory first in order to avoid the Name view chip mem faff. I can get around it by using playlists but it'd be good if there were a way to fix this annoying issue.

16 April 2016, 13:16	#1
trixster Guru Meditating Join Date: Jun 2014 Location: England Posts: 2,346	using fast mem to display directory contents Hi all, I'm using both Fblit and Ftext in my startup-sequence and the latest version of PeterK's icon.library. All 'seem' to work fine and Ftext certainly seems to improve text rendering speed and is verifiable using the tests in sysspeed. Icon.library does its thing and icons reside nicely in fast memory, not chip memory. However.... I've noticed that opening a Workbench directory with a very large number of files and selecting View By -> Name starts to eat up Chip Memory by the bucket load. View By -> Icon does not as Fast Memory is used, as expected. Is this normal? Is there a way to get directories to use fast memory when viewing them by Names rather than Icon?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
No fast mem when booting	AndersHP	support.Hardware	17	02 April 2014 15:20
Use of 4MB PCMCIA Fast Flash Memory as Fast RAM in A1200	nkarytia	support.Hardware	10	16 September 2011 13:37
CD32/SX1 Fast mem not showing up in CWBv26	Claw22000	project.ClassicWB	3	25 March 2011 03:44
Writing the contents of a directory to a text file	Shoonay	support.Other	8	02 July 2007 17:55

16 April 2016, 22:52	#2
Cylon Registered User Join Date: Oct 2014 Location: Europe Posts: 472	You are probably using Workbench 3.1 or lower. This (stupid) ChipRAM eating for text display is gone with Workbench 3.5 and above iirc. So, yes, this is (was) normal. Blame those silly developers.

17 April 2016, 00:06	#3
trixster Guru Meditating Join Date: Jun 2014 Location: England Posts: 2,346	And there's no patch to fix Names view?

17 April 2016, 16:27	#4
daxb Registered User Join Date: Oct 2009 Location: Germany Posts: 3,305	Maybe you go for a file mananger instead? Is there a reason for using workbench windows with text view?

17 April 2016, 17:30	#5
trixster Guru Meditating Join Date: Jun 2014 Location: England Posts: 2,346	My NAS has an unsorted folder with over 4000 album-less random mp3s in it. I'd like to be able to drag and drop them straight into AmigaAmp rather than have to move the ones I want to play into another directory first in order to avoid the Name view chip mem faff. I can get around it by using playlists but it'd be good if there were a way to fix this annoying issue.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)