Hyperion Entertainment Message Boards

Hi,

as discussed on italian amiga forum (http://amiga.ikirsector.it/forum/viewto ... 37&t=17366) there's a bug in create/copy a directory inside itself, to explain it better try:

- create a new directory example in ram:
- copy it with the right mouse button choosing the item "copy"
- open the directory and paste

it'll start a process of directories recoursive creating, one inside the other

What version of ram-handler are you using?
I seem to recall that the old ram-handler had this feature, but it was fixed long ago.

tonyw wrote:What version of ram-handler are you using?
I seem to recall that the old ram-handler had this feature, but it was fixed long ago.

4.System:> version ram-handler full
ram-handler 53.3 (22.01.2011)

Just tried on X1000 AmigaOS4.1 upd6 and it unfortunately does what OP said.

One can Cancel the copy operations though

EDIT: The same happens on jxfs and sfs2 partitions, so it's not a problem in ram-handler

@SOFISTISOFTWARE
I do a such test on latest beta:
- by context menu create "aaaa" directory in the ram:
- copy it with the right mouse button choosing the item "copy"
- open the directory and paste

it'll start to do something heavy (process of directories recoursive creating, one inside the other i assume), and then after all crashes with 80000003 in AsyncWB - copy process.

So cleary a problem, and BZ are must , but dunno if it file system handlers, async wb, context menu, copy or what ? I already start to discuss it on os4beta list, and once roots will find out, i will make a proper BZ.

kas1e wrote:@SOFISTISOFTWARE
I do a such test on latest beta:
- by context menu create "aaaa" directory in the ram:
- copy it with the right mouse button choosing the item "copy"
- open the directory and paste

it'll start to do something heavy (process of directories recoursive creating, one inside the other i assume), and then after all crashes with 80000003 in AsyncWB - copy process.

So cleary a problem, and BZ are must , but dunno if it file system handlers, async wb, context menu, copy or what ? I already start to discuss it on os4beta list, and once roots will find out, i will make a proper BZ.

Thanks Kas1e, but don't loose your time in that problem because you have to keep up new OWB ... and new mplayer.... and new pdf reader... and...

Naa kas1e is also a betatester so reporting bugs is also his area

Thanks kas1e

When you try to create a directory loop, the illegal attempt has to get through several steps:
1. ASyncWB (if from WB)
2. C:Makedir (or C:Rename)
3. DOS
4. The filesystem (in this case, ram-handler).

If you type "move" or "rename" in a Shell, then the "C:Rename" command should stop it and give an error ("Infinite loop").
The ram-handler is the last place where it can be stopped. If you are dealing with a disk-based filesystem, then the filesystem for that partition is the last step.

I thought that ram-handler and env-handler were changed some time ago to prevent this occurring, which is why I asked what version of ram-handler you have there. I couldn't get it to happen on an up-to-date beta system, but I might be using the wrong method.

At the AmigaDOS level, copying is just creating distination directories that have the same name as the source directory and creating files (and copying the contents) with the same name as the source files. I don't think a handler or filesystem has any knowledge of where the dirs and files are being copied from; they just respond to the program creating files and dirs. The problem must be with ASyncWB. I recently fixed the same kind of "infinite recursion" problem in the latest release of Dopus4. Has anyone tried disabling ASyncWB to see if the default WorkBench copy has the same problem?

@xenic

I just tried with ASyncWB off.
The system does not let me paste the copied drawer in itself.

DOS doesn't even present me with a paste command (Icon pull down greyed out)
ContextMenu lets me copy and paste but paste does nothing

@TonyW

I thought that ram-handler and env-handler were changed some time ago to prevent this occurring, which is why I asked what version of ram-handler you have there.

Problem happens on any FS, not only on ram.

I couldn't get it to happen on an up-to-date beta system, but I might be using the wrong method.

I am also have all latest beta components and can reproduce problem very easy. Just do the same as sofisoftware do and what all the others do to reproduce it:

- by context menu create "aaaa" directory in the ram:
- select it , and by right mouse button spawn a menu in which choice "copy"
- then open that "aaaa" directory, press RMB again, and in menu choice "paste" => you will see a problem + crash.