Path: utzoo!attcan!utgpu!watmath!isishq!f171.n221.z1.FIDONET.ORG!izot
From: izot@f171.n221.z1.FIDONET.ORG (Geoffrey Welsh)
Newsgroups: comp.sys.cbm
Subject: 1571 and Assembler-64 incompatibility
Message-ID: <2452.247F6F62@isishq.FIDONET.ORG>
Date: 25 May 89 12:30:27 GMT
Sender: ufgate@isishq.FIDONET.ORG (newsout1.25)
Organization: FidoNet node 1:221/171 - Izot's Swamp, Kitchener ON
Lines: 25


 > From: eravin@dasys1.UUCP (Ed Ravin)
 > Message-ID: <9771@dasys1.UUCP>
 
 > What's going on?  It seems to be the 1571 prematurely closing files.
 
   OK, here's my guess (could be way off base, but enough of these guesses 
might dig up the problem...):
 
   The 1571, when powerered up, is in 1541 mode. This is automatically changed 
to 1571 mode when it is accessed using a burst mode command (by a C128). 
However, it will stay in 1541 (single-sided) mode if used by a C64 or a C128 
in 64 mode.
 
   If for any reason your drive is being reset (either by a hardware or by a 
UJ command) by the C64, it will return to single-side mode and any attempts to 
access files which are on the top (second) side of the disk will cause errors 
(and, if your software is kinda smart, "premature closing" of the files.)
 


--  
 Geoffrey Welsh - via FidoNet node 1:221/162
     UUCP: ...!watmath!isishq!171!izot
 Internet: izot@f171.n221.z1.FIDONET.ORG