Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!eru!hagbard!sunic!nuug!sigyn.idt.unit.no!solan4.solan.unit.no!gimme From: gimme@solan4.solan.unit.no (Olav Gimmestad) Newsgroups: comp.sys.amiga Subject: Re: How did I break Duplicate? Keywords: help duplicate Message-ID: <1990Sep20.081753.16706@idt.unit.no> Date: 20 Sep 90 08:17:53 GMT References: <10515@hubcap.clemson.edu> Sender: news@idt.unit.no (Usenet news admin) Reply-To: gimme@solan4.solan.unit.no (Olav Gimmestad) Organization: Norwegian Institue of Technology Lines: 25 In article <10515@hubcap.clemson.edu>, robert@hubcap.clemson.edu (Robert Reynolds) writes: |> All of a sudden, the Workbench menu command `Duplicate' has stopped |> working for me. This is WB1.3 on a hard disk. The behavior is as |> follows: the new `copy of blah.info' file gets created for the icon but |> then, immediately as far as I can tell, the machine gurus. This happens |> independent of the kind of file I'm trying to duplicate (directory or |> data file). If I do the (more or less) equivalent of `Duplicate' by |> hand it works fine, so it's not like my file system is so screwed up |> that no new files can be created or anything like that. |> |> Anybody have any ideas what might be wrong? How, exactly, does |> Duplicate work? If I wanted to assume that I somehow have a bad copy of |> Duplicate itself, what do I restore from originals to get back to a good |> one? LoadWB? |> |> Thanks for any help!! |> |> -- |> Robert Reynolds inet: robert@hubcap.clemson.edu |> CS Dept, Clemson Univ. uucp: ... !gatech!hubcap!robert |> phone: (803) 656-6783 I do not know what's wrong in your case, but I think I have found another bug in duplicate or copy. When I click on a disk I want to copy, then select duplicate from the WB menu, then I click on the disk I wanted to duplicate so it not is higliighted anymore, then I select CANCEL on the requester an the Amiga GURU. I use Kickstart 34.5 and wb 34.4. Is this an old bug? Is it ixed in V2.0? Olav Gimmestad