> > Guess what? It does resolve the problem. So, the answer is not in the > software reset... it's some odd behavior that is related to in#2 + pr#2 > > But at least we know what the problem is not. ;-) > Just wondering if any of the info in this tech note can help - http://apple2.boldt.ca/?page=til/tn.aiic.006 Glenn