Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!UNCAEDU.BITNET!svermeulen%Ins.MRC.AdhocNet.CA From: svermeulen%Ins.MRC.AdhocNet.CA@UNCAEDU.BITNET (Steve Vermeulen) Newsgroups: comp.sys.amiga Subject: Arp Copy vs. AmigaDOS Copy Message-ID: <880610121707.02j@Ins.MRC.AdhocNet.CA> Date: 10 Jun 88 18:17:07 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 39 I am posting this question from a fellow AMUCker that was asked on our Club BBS. The question is why would this happen, does the AmigaDOS Copy command do some special magic that ARP's Copy does not do? The message follows: ----------------*********--------------*********----------------- Msg: #10844 Sec: D - Developer SIG 25-May-88 06:20 AM Subj: ARP Copy Command (R) From: Al Kaufmann To: Stephen Vermeulen (X) I know you have access to USEnet so maybe if you consider the following important you will forward the message to the producers of ARP - C. Heath? Every so often I copy over my most important system disks to newly formatted disks using the command "copy df0: to df2: all" to improve the performance of the disks. (Us peons without FFS still have to do things like that. Actually this time my disk had a read error, thank God of disksalv but that is besides the point.) Imagine my surprise that system performance actually deteriorated. After the files were copied the command "dir opt a" took 44.5 seconds, much longer than it normally takes. After scratching my head for a while I realized the only thing changed was that I was using the ARP copy command instead of the AmigaDOS copy. After repeating the procedure this time using the AmigaDOS copy command the same directory command only took 21.1 seconds. This may not be a bug perse but certainly the ARP copy command needs some more work. I do have the ARP Copyflags set to NC but this shouldn't really make a difference. AK ----------------*********--------------*********----------------- Has anyone else experienced this? Stephen Vermeulen.