Serious bug in new ASyncWB

[xenic]

Today I tried to copy a project icon (with no associated file) to another partition and it failed with a requester stating: "Error while copying "FileX1", object not found". I have a lot of project icons that I use to start programs with different Tooltypes. They need no associated file since their purpose is simply to start programs with specified Tooltypes. The original Workbench builtin copy and previous versions of ASyncWB had no problem copying those project icons.

To reproduce: Drag SYS:System/Shell to another partition (like ram:).
Broken ASyncWB version is 53.14 (03/02/2013).

[Phantom]

I reproduced it as you suggested with exactly the same result and using the same version of ASyncWB.

[nbache]

This problem is already logged in Bugzilla. Now a reference to this thread has also been added there (not by me).

Still, thanks for reporting.

Best regards,

Niels

[xenic]

@nbache
Thanks for letting me know it's in the Bugzilla.

[Amigo1]

This problem is already logged in Bugzilla. Now a reference to this thread has also been added there (not by me).

Still, thanks for reporting.

Best regards,

Niels

Also I noticed ASYNCWB does not appear in "Exchange" anymore. Well, I'm not sure it ever did, but AFAIK it is a commodity.

[lazi]

One year passed since the first post and I am just now witnessed the problem.
No need to report it, so I report that I am experienced the same as you

[xenic]

One year passed since the first post and I am just now witnessed the problem.

I reported the ASyncWB bug as soon as the new version was released and assumed that it would be quick and easy to fix it and release the fixed version. All that's required is to undo whatever was changed to cause the problem.

So many of the problems I've reported or confirmed for other people have not been fixed that I usually don't bother reporting bugs anymore. Here are some of the topics where I've reported problems or bugs that remain unfixed:

• TOPIC - Missing Multiview icon in Update + bugs?
  Still waiting for fixed text.datatype.
  
  TOPIC - Calculator Problem (bug?)
  Tape still opens on WorkBench if you open Calculator on another screen and select the "Show Tape" menu item.
  
  TOPIC - X1000 Radeon graphics problem
  Still have some graphics corruption on my X1000. Hans fixed the drivers but explained that the remaining problems need to be fixed in OS4.
  
  TOPIC - X1000 - Debug output bug
  Still unresolved.
  
  TOPIC - USBCtrl restart freezes X1000 input.
  Still unresolved.
  
  TOPIC - AmigaGuide library bug and inconsistancy.
  Still unresolved.
  
  TOPIC - usbprinter.device problem if printer not turned on.
  There were 5 pages of discussion and several methods of reproducing the problem were presented.
  
  TOPIC - Request: Add usbprinter.device includes to SDK
  Not yet.

There are other topics that I've forgotten and lots of other bugs that I've confirmed for people in other topics.

[chris]

There are other topics that I've forgotten and lots of other bugs that I've confirmed for people in other topics.

There are others that have been fixed but haven't filtered down to us mere mortals yet (some chooser.gadget, Intuition bugs).
Things do tend to get fixed eventually but can take an exceptionally long time (and often a lot of effort to get them acknowledged as bugs). I trust the devs are focussed on more important things.

[nbache]

The following is a general observation about IT projects but is likely to fit also for AmigaOS.

Some fixes are distributed (in our case via the AmiUpdate system) more or less as soon as they are fixed, but others may still be fixed, but have to wait until some dependent component can also be released, or for other reasons.

You can't conclude that something has not been fixed just because you haven't received the fix yet.

But of course the fix is not useful for the end user until it has been distributed.

Best regards,

Niels

[xenic]

You can't conclude that something has not been fixed just because you haven't received the fix yet.
Niels

There must be some limit how long one should wait before concluding that a bug report has been ignored. For example, I reported the "usbprinter.device" problem in early 2010 with mesages in the OS4 Yahoo mailing list and in Amiga forums. In 2011 I reported the problem here in the Hyperion message board. It's hard to believe that the fix has been in beta testing for almost 5 years.