Re: Two 1541-II drives with problems

Hello.

I had a brief return to this project. I bought a working 1541-II board from eBay, just for a reference. I am still getting exactly the same symptoms (no stepper movement, drive halts), same thing with both drive mechanisms. 

As I have no reason to blame this board having the same fault, I am now almost positive that I must have two faulty drive mechanisms (and the boards that I have, could have been working all along). I am afraid that earlier while fiddling with these drives, I must have connected the drive cables wrong way around. As said on the Ray Carlson's site: "If accidently reversed, you can do serious damage to the drive board or mechanism".

I see at least two 1541-II mechanisms on eBay, although of different manufactorer. Are the drive mechs interchangable?

--
Ville


Gerrit Heitsch <gerrit@laosinh.s.bawue.de> kirjoitti 25.4.2014 kello 17.21:

> On 04/25/2014 07:16 AM, Marko Mäkelä wrote:
>> On Thu, Apr 24, 2014 at 11:16:29PM +0200, silverdr@wfmh.org.pl wrote:
>>>       diff - compare files line by line
>>> 
>>> But diff can be used as well.
>> 
>> To compare binary files that are of the same size, I often do something
>> like this:
>> 
>> od -Ax -t x1 file1.bin > file1.txt
>> od -Ax -t x1 file2.bin > file2.txt
>> 
>> diff -u file1.txt file2.txt
> 
> Looks a bit complicated. I usually do the following:
> 
> cmp file1 file2
> 
> If you don't get a complaint, they are the same. If you get a message aboug differing, you do it again with the '-l' option:
> 
> cmp -l file1 file2
> 
> This will list all the differences (octal) and where they are (decimal).
> 
> Then are times when I need to compare 2 whole directory trees (like verifying a backup done with 'rsync'). This is best done with
> 
> diff -r dir1 dir2
> 
> and will tell you if files differ or are missing from one tree. It works with any size (tested up to 2 TB per directory). Doesn't care about text or binary.
> 
> Should work on most UNIX variants.
> 
> Gerrit
> 
> 
> 
> 
> 
>      Message was sent through the cbm-hackers mailing list


       Message was sent through the cbm-hackers mailing list