2 May
2006
2 May
'06
11:20 p.m.
Hi Again
This is true that the disk change could be an issue but it won't
be an issue for me. I don't use it for DOS disk and use my own
software to talk directly to the controller and DMA. Like I said,
I use it to transfer images of disk for my M20 ( uses PCOS ).
I've seen mention of using control-c or control-break to get
DOS to reread the directories rather than use the image it
read in memory.
I did some more searching today and found a good source of
various bits and pieces about drives but I left the piece of paper
with the page at work. I'll post it tomorrow.
It talked about the disk change line but it didn't connect in my
head until I read the other mail that it might be this line that
conflicts with the 1.44M drive.
Thanks
Dwight
From: Fred Cisin <cisin at xenosoft.com>
On Tue, 2 May 2006, dwight elvey wrote:
Hi Fred and all
Yes, I meant 34. I've been fiddling with a laptop drive
and it has the 26 pin z connector and that number stuck
out in my head.
Also, 34 was the answer. I put a piece of tape on pin
34 of the 360K drive and all seems well now. It seems
like the 1.44M use that line for detecting the 720k
disk while the 360K used it for disk change. I just
couldn't recall what line was involved.
You MIGHT now have a 360K that does not notice when you change diskettes!
Be careful
IF you get a situation where that drive shows you the previous DIR,
instead of the current one after changing diskettes, don't write
until the OS knows it.
^C (Ctrl +C) will tell DOS that the disk has been changed.
It's documented in CP/M, and undocumented in MS-DOS.