lphillips@lpami.wimsey.bc.ca (Larry Phillips) (08/06/90)
In <8129@fy.sei.cmu.edu>, jol@sei.cmu.edu (Jun Lee) writes: >Hi. > >I too have been having some trouble connecting 2 Quantum Hard disks on my >Ami2000HD using 2091A controller. I have a Pro 40s and 80s drives. >I wanted to copy the 40meg drive onto the 80 using > copy dh0: dh1: CLONE. > >But it doesn't work. It copies for awhile then gets "stuck". >I called CBM and they told me that I should make sure the reselection >option in define drive part of HDtoolbox should be turned off for both >drives. This should fix the problem. >I would like to know if this is a correct solution or just another >bunch of crap that they gave me to get me off the phone. Define 'correct solution'. It works. You tell me if it's correct or not. It is definitely not a 'bunch of crap to get you off the phone'. >I would like to try it but it's going to take alot of work and time since >I have to back up the drives since this will wipe out all the data. It will not 'wipe out all your data'. Sure, HDToolBox will wipe the data if you tell it to, via low level format, or if you change the sizes or starting positions of your partitions, but changing the reselection option on a drive will not wipe any data. Try it on your new disk before you commit a lot of irreplacable data to it. -larry -- Sex is better than logic, but I can't prove it. +-----------------------------------------------------------------------+ | // Larry Phillips | | \X/ lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 -or- 76703.4322@compuserve.com | +-----------------------------------------------------------------------+
jol@sei.cmu.edu (Jun Lee) (08/07/90)
Hi.
I too have been having some trouble connecting 2 Quantum Hard disks on my
Ami2000HD using 2091A controller. I have a Pro 40s and 80s drives.
I wanted to copy the 40meg drive onto the 80 using
copy dh0: dh1: CLONE.
But it doesn't work. It copies for awhile then gets "stuck".
I called CBM and they told me that I should make sure the reselection
option in define drive part of HDtoolbox should be turned off for both
drives. This should fix the problem.
I would like to know if this is a correct solution or just another
bunch of crap that they gave me to get me off the phone.
I would like to try it but it's going to take alot of work and time since
I have to back up the drives since this will wipe out all the data.
Any info will be very much helpful.
ThanX
================================================================================
JUN LEE //
\/\/\_/\_8> \\ //
jol@sei.cmu.edu \X/
(412) 268-7602
================================================================================stan@phx.mcd.mot.com (Stan Fisher) (08/07/90)
> >I too have been having some trouble connecting 2 Quantum Hard disks on my >Ami2000HD using 2091A controller. I have a Pro 40s and 80s drives. >I wanted to copy the 40meg drive onto the 80 using > copy dh0: dh1: CLONE. > >But it doesn't work. It copies for awhile then gets "stuck". >I called CBM and they told me that I should make sure the reselection >option in define drive part of HDtoolbox should be turned off for both >drives. This should fix the problem. >I would like to know if this is a correct solution or just another >bunch of crap that they gave me to get me off the phone. >I would like to try it but it's going to take alot of work and time since >I have to back up the drives since this will wipe out all the data. >Any info will be very much helpful. I was told (first) that the new ROMs for the 2091 would fix this problem.. I bought the new ROMs and tried two drives (doing a copy clone too) and a ways into the copy it hung (same symptom you have and same one I'd had before the ROMs). Then I heard about the reselection problem and I tried that, tuning off reselection for both drives and saving that to each drive. This doesn't wipe out the drive contents, the information is stored (apparently) in the rigid disk block (cyl 0,1) and doesn't effect the current partition contents. So far the drives havn't hung since I did that.. though I haven't done a full "copy all clone" yet. (mine used to hang during other activity too besides the copy all clone.) My question is what the hell did I buy the Firmware update for? That was $32 I could have used elsewhere! Stan Fisher - stan@teroach.phx.mcd.mot.com - asuvax!mcdphx!teroach!stan Motorola Microcomputer Group, Tempe, Arizona - Voice (602) 438-3228 Call our User Group BBS "M.E.C.C.A." running SkyLine 1.31 @ (602) 893-0804
xrtnt@bethe.gsfc.nasa.gov (Nigel Tzeng) (08/07/90)
In article <13359@mcdphx.phx.mcd.mot.com>, teroach!stan@phx.mcd.mot.com (Stan Fisher) writes... ^> ^ ^I was told (first) that the new ROMs for the 2091 would fix this problem.. ^I bought the new ROMs and tried two drives (doing a copy clone too) and ^a ways into the copy it hung (same symptom you have and same one I'd had ^before the ROMs). Then I heard about the reselection problem and I tried ^that, tuning off reselection for both drives and saving that to each drive. ^This doesn't wipe out the drive contents, the information is stored ^(apparently) in the rigid disk block (cyl 0,1) and doesn't effect the ^current partition contents. So far the drives havn't hung since I did ^that.. though I haven't done a full "copy all clone" yet. (mine used to hang ^during other activity too besides the copy all clone.) ^ ^My question is what the hell did I buy the Firmware update for? That was ^$32 I could have used elsewhere! ^ ^ ^ Stan Fisher - stan@teroach.phx.mcd.mot.com - asuvax!mcdphx!teroach!stan ^ Motorola Microcomputer Group, Tempe, Arizona - Voice (602) 438-3228 ^ Call our User Group BBS "M.E.C.C.A." running SkyLine 1.31 @ (602) 893-0804 Could you post the chip numbers for the updated ROMs? I have a 2091A that says that it is a Rev 4.0 Modified (or Corrected I can't recall) and I'd like to check to see if I have the new roms. For those of you that may be wondering: No I didn't fry the 2091A or the Quantum with my idiocy last week. I'd still like to know what the probable failure paths may be since just because it works now doesn't mean I didn't screw something up. Thanks for any info, NT -------------------------------------------------------------------------------- // | Nigel Tzeng - STX Inc - NASA/GSFC COBE Project \X/ | xrtnt@amarna.gsfc.nasa.gov | Amiga | Standard Disclaimer Applies: The opinions expressed are my own.
plav@cup.portal.com (Rick M Plavnicky) (08/09/90)
On 8/7/90 06:47 40/1899 xrtnt@bethe.gsfc.nasa.gov (Nigel Tzeng) wrote: In article <13359@mcdphx.phx.mcd.mot.com>, teroach!stan@phx.mcd.mot.com (Stan F >^ >^I was told (first) that the new ROMs for the 2091 would fix this problem.. >[some chopped] >^My question is what the hell did I buy the Firmware update for? That was >^$32 I could have used elsewhere! >^ >^ >^ Stan Fisher - stan@teroach.phx.mcd.mot.com - asuvax!mcdphx!teroach!stan >^ Motorola Microcomputer Group, Tempe, Arizona - Voice (602) 438-3228 >^ Call our User Group BBS "M.E.C.C.A." running SkyLine 1.31 @ (602) 893-0804 >Could you post the chip numbers for the updated ROMs? I have a 2091A that say that it is a Rev 4.0 Modified (or Corrected I can't recall) and I'd like to >check to see if I have the new roms. My EPROMS were recently upgraded when my machine was in for other service. The part numbers and versions follow: 2091 ROMs --------- old, version 5.92: 390508-02 (even - U13) 390509-02 (odd - U12) new, version 6.1: 390721-01 (even) 390722-01 (odd) Hope this helps! > // | Nigel Tzeng - STX Inc - NASA/GSFC COBE Project > \X/ | xrtnt@amarna.gsfc.nasa.gov /* Rick Plavnicky ...!sun!cup.portal.com!plav -or- plav@cup.portal.com */