Conference hydra::amiga_v1

    I only use TurboBackup.  A GREAT Pd/Shareware type copy program. 
    
    I strongly suggest using that rather than diskcopy.
    
    Steve
    

Maybe a power problem? You could be right at the edge and spinning
both floppies at once pushes you over?

John

    Saw this on the UseNet a while ago. Not sure if it's the same as what
    your seeing.
    
            <<< FRSOLD::IS$NOTES:[NOTES$LIBRARY]AMIGA_SYS.NOTE;2 >>>
                         -< comp.sys.amiga - postings >-
================================================================================
Note 4695.3                A500 Floppy Drive Weirdness                    3 of 5
FRSOLD::ZIMMERMANN "uvicctr.UVic.CA!iwood"           42 lines  10-JAN-1990 07:12
--------------------------------------------------------------------------------
Path: shlump.nac.dec.com!decwrl!wuarchive!cs.utexas.edu!rice!uw-beaver!fluke!ssc-vax!uvicctr.UVic.CA!iwood
From: iwood@uvicctr.UVic.CA.UUCP (Ian Wood)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: A500 Floppy Drive Weirdness
Message-ID: <881@uvicctr.UVic.CA.UUCP>
Date: 9 Jan 90 02:46:01 GMT
References: <3512@cbnewsl.ATT.COM>
Reply-To: iwood@uvicctr.UVic.CA.UUCP (Ian Wood)
Distribution: usa
Organization: University of Victoria, Victoria B.C. Canada
Lines: 29
Xref: shlump.nac.dec.com comp.sys.amiga:46456 comp.sys.amiga.tech:9457
 
There is a problem with the DISKCOPY program on a whole whack of Workbench 1.3
disks that Commodore put out around Christmas.  As well as the write errors,
the bad diskcopy will sometimes guru.  Check the size of the DISKCOPY file.
If the file is 17380 bytes and the version is 1.3.1, it is the hooped version.
The guru problem only seems to come up from Workbench, not CLI.
 
A lot of the dealers around here didn't know about the problem.  The guys at
Moebius Computer Systems in Victoria found it and phoned Commodore, who didn't
know (I think).  But then Moebius is a real Amiga store, run by a bunch of
Amiga hackers who got into the retail business because they had a calling to
spread the word.....
 
Flame Retardent :  I don't work for Moebius or get consideration for my 
                   words here, etc, etc.
 
 
 
-- 
Ian Wood
Systems Operator                                UUCP   : iwood@uvicctr.uvic.ca
University of Victoria                          BITNET : CCIAN@UVVM
C eh N eh D eh                                           (It's a Sierra, Eric)
 
Disclaimer (noun) :
   An heinously vulgar concept perpetuated by bureaucrats and lawyers.
=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=
            "And what if I should refuse to get this Loc-Nar?"
                 "You die.  She dies.  EEEVERBODY dies."
=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-=+=-= 
    

    > The funny thing is that ALL other disk operations work perfectly
    
    When I bought my 2000, it would always hang during disk copies.
    The Memory Location gave me a new diskcopy and that solved the
    problem (i.e. it was a known problem). 
    
    The workbench 1.3.2 update (WJG::DUA1:[AMIGA]WB132.ZOO) has a 
    new version of diskcopy (which I am using and which has not given
    me any trouble).  You could try that and see if it helps.
    
    Yours
    Erg

 
    
>    The workbench 1.3.2 update (WJG::DUA1:[AMIGA]WB132.ZOO) has a 

This is not world readable until someone tells me it's OK to make it so.

Didn't I just read a message here somewhere that CBM said it is ok to 
distribute this?

John

    I have seen this when the disk has the BYTE BANDIT virus on it. If you
    do not have VIRUSX, you can try to format the disk via the CLI. If it
    only does the first couple of tracks and stops its most lickly
    infected. 
    
    					Peter
    
    

    I had a version of disk copy that had a neat bug in it - a bit
    different to this though.
    
    Doing a single disk-to-disk copy would get the read/verify mixed up and
    on the second lot of source disk reads would then try to verify the
    destination - and get a validation error.  replaced the executable and
    all ok.
     

    
    Well, taking the possibilities one by one,
    
    I don't think it's power related because I can have both disks
    spinning, reading and writing at the same time with no problem (just
    not from diskcopy.)
    
    It's not a virus (at least not one that VirusX knows about.) This
    was my first suspicion, as I've had Byte Bandit before and know
    that it affects disk operations.
    
    It could be a duff version of Diskcopy, but my 1.3 enhancer was
    bought over a year ago, and diskcopy doesn't work from the CLI or
    the workbench. When thinking about it, I don't know if diskcopy
    has ever worked, as I very rarely use it. I'll upgrade to 1.3.2
    (which was distributed here in the UK as a freebie on a magazine
    cover disk) and see if that's the problem.
    
    			Thanks,
    				Alan T.
    

    
    	Alan,
    
    		We (by that I mean "my son and I") had what sounds like
    the same thing and were told that it was a known problem. we were
    advised to delete dskcpy and copy over the version from 1.2 This
    we did and it now works fine.
    
    	Ref the version 1.3.2 - what magazine was this please?
    
    				Paul
    

    
    OK, I'll try that too, but I'm puzzled ! If it's a known problem,
    why doesn't anyone know about it ?
    
    WB 1.3.2 was distributed on the cover disk of Amiga Computing with
    the November/December issue. I'll look tonight and confirm which
    one tomorrow.
    
                                      Alan T.

    WB 1.3.2 was on the December issue coverdisk of Amiga Computing.
    
    Unfortunately I didn't get time to try the 1.2 diskcopy last night.
    
    					Alan T.
    

    Solved it! It was a virus called LAMER II. Apparently this little
    b*gg*r disables diskcopy, and randomly trashes blocks. This also
    explains some apparently random read/write errors which I was blaming
    on the (cheap) media I was using....
    
    VirusX 3.2 didn't pick it up, but V4.0 does. I found it on 78 disks,
    some of which weren't previously installed ! Luckily, no games or
    anything else which required a custom bootblock were infected.
    
              			Alan T.
    

I've also been infected with the LAMER II virus. I found it on 8 floppies and 
cleaned it up with VIRUSX4.0. I then recopied the c directory on DH0: (ofs) and 
FH0: (ffs) of the hard disk from the 1.3 distribution diskette.

What else I should do to make sure I'm clear of this social disease?

Don