Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: mingle on December 23, 2008, 10:39:23 AM
-
Hi,
This is a fairly fundamental question, I guess...
When I'm copying a large number of files from one HD partition to another, or from my external CF card adapter, I can't do anything else - apart from resize windows or drag the Workbench screen down.
I've never really noticed it before - admittedly I've never really copied many files around previously.
I have a Blizzard 030 accelerator, 32MB of fast RAM and I'm running KS/WB3.1 with the Executive task scheduler running as well...
Does this sound right, or is something amiss with my config?
Cheers,
Mike.
-
This is normal. OS3.9 allows Workbench to multitask while doing file operations. 3.5 might too, but I have never used it.
--
moto
-
I believe palin OS3.9 does not allow it either. Pretty sure it was BB1 that brought this in
-
You must have asyncwb running in your startup. Can't recall if it was 3.5BB2 or 3.9BB1 that introduced it, but - in any case - you should have 3.9BB2 installed for optimum experience so asyncwb would definitely be in there. I'm also not quite sure it is copied during installation, so you should check your installation disks/BB archives and find it and copy it yourself.
-
Lack of async operations in Workbench aside, using the internal IDE interface requires use of the CPU, and the filesystem process runs at priority 10.
If you really must be able to use some application or shell comfortably while such large copy is in progress, you can do it by raising the priority of the processes in question. Running them at priority 11 should help. Obviously this only works for the interactive processes, anything consuming tons of CPU time should not be adjusted.
BTW. Is 3.9 AsyncWB really stable? I remember talk of some nasty bugs in it.
-
Works fine in Os3.9 for me.. Never experienced any crash when running copies..
-
As has already been said it's totally normal. File operations are blocking in AmigaOS.
I remember first seeing non blocking file I/O (on the Amiga) for WB alternative "Scalos" and thinking, way cool!
If you do not have a DMA capable SCSI card then it probably isn't worth looking into as the CPU will be performing the File I/O?
-
There was Jazzbench many years ago - that was supposed to be fully multitasking. Or you could try "Run Copy ..." which should do the trick too (that might have been what Jazzbench did).
-
Wow, Jazzbench! That brought back memories! At the time I couldn't really work out what it was supposed to be other than a Workbench disk with some tools included. Did it have some more fundamental changes than that?
Also, was it Jazzbench that had a sample from 2001 of Hal saying "I'm sorry Dave, I'm afraid I can't let you do that" as the error sound?
--
moto
-
I have no idea, I never got it to work... when I came across it I was using an A500+ and I think Jazzbench was for earlier systems and just didn't like Kick2/ECS.
-
didn't jazzbench also allow/promise an 8 colour workbench in 1.3?
blimey, blast from the past...! :-D
-
@mingle
Perhaps you could simply use DirectoryOpus4 or some other filemanager like FileMaster (this one allows multitasking, unlike DOpus4) http://aminet.net/package/util/dir/NewFilemaster
-
Crumb wrote:
@mingle
Perhaps you could simply use DirectoryOpus4 or some other filemanager like FileMaster (this one allows multitasking, unlike DOpus4) http://aminet.net/package/util/dir/NewFilemaster
Bingo! Give the man a cigar. :-D
Don't use WB for things like copying files. Use a real file manager... which means DOpus or the like. You'll be much happier.
-
Piru wrote:
BTW. Is 3.9 AsyncWB really stable? I remember talk of some nasty bugs in it.
Yes, I remember having problems with it, but I can't remember the details. One quirky bug that I made a note of at the time was that if you tried to copy a hard link to another volume, it attempted to create a hard link spanning the volumes. But I think there might have been worse bugs too.
-
From memory you are using a compact flash card on the A1200 internal IDE bus? Reading data from the compact flash card is VERY fast. Writing to compact flash on your set up is VERY slow. I think this is just the way compact flash works and also due to the IDE bus on the A1200 that locks up the CPU when writing. I found that my original 40 meg hard drive writes faster than my compact flash!!!
-
alexh wrote:
As has already been said it's totally normal. File operations are blocking in AmigaOS.
That's slightly inaccurate, they are not blocking in AmigaOS, only in (old) Workbench.
I remember first seeing non blocking file I/O (on the Amiga) for WB alternative "Scalos" and thinking, way cool!
And in DirectoryOpus5 you can even copy from multiple sources to multiple destinations simultaniously.
If you do not have a DMA capable SCSI card then it probably isn't worth looking into as the CPU will be performing the File I/O?
Ofcourse it's still worth it, you can set the CPU priority used for the copy operation and do other operations in Workbench as normal.
-
ncafferkey wrote:
Piru wrote:
BTW. Is 3.9 AsyncWB really stable? I remember talk of some nasty bugs in it.
Yes, I remember having problems with it, but I can't remember the details. One quirky bug that I made a note of at the time was that if you tried to copy a hard link to another volume, it attempted to create a hard link spanning the volumes. But I think there might have been worse bugs too.
Speaking of hard links - how do I know that a file is a hard link in the first place? Neither workbench nor c:List is able to tell them apart. Not softlinks either for that matter.
-
@kolla
how do I know that a file is a hard link in the first place?
AmigaOS API is a bit screwed here.
The only dos.library level solution is to ExNext/ExAll the parent directory.
For softlinks you can also ACTION_LOCATE_OBJECT the specific name. If you get an error and Result2 is ERROR_IS_SOFT_LINK then it is a softlink. If the packet succeeds you must free the lock with ACTION_FREE_LOCK.
As for the dir and list commands, they just don't support links.
-
Piru wrote:
@kolla
how do I know that a file is a hard link in the first place?
AmigaOS API is a bit screwed here.
The only dos.library level solution is to ExNext/ExAll the parent directory.
For softlinks you can also ACTION_LOCATE_OBJECT the specific name. If you get an error and Result2 is ERROR_IS_SOFT_LINK then it is a softlink. If the packet succeeds you must free the lock with ACTION_FREE_LOCK.
As for the dir and list commands, they just don't support links.
Exactly, it seems very "half done".
The only thing I ever use linking for is a "makelink ram:Disk.info envarc:ram_disk.info soft" in s:user-startup, so that I can snapshot icon etc. as normal :-)
-
kolla wrote:
The only thing I ever use linking for is a "makelink ram:Disk.info envarc:ram_disk.info soft" in s:user-startup, so that I can snapshot icon etc. as normal :-)
I sometimes use hard links for saving disk space, e.g. for Poseidon installer disks (either in flashrom or on DD-disk) if there's the same icon multiple times (drawer or installer icons), I would hardlink the .info files to one "template". This would save me a few kilobytes of diskspace :-)
Other than that, hardlinks should probably be avoided at all costs, the chances that the filesystem supports them correctly is slim and they cause all kinds of troubles for most file managers.