Re: New direction on the Kaypro 16

Slor wrote:
> Nope. Check out my previous thread for all the gory details. Bottom line
> it there is nothing in that segment that appears to be a formatting
> routine. Only strings in the whole thing are copyright, boot error, and
> disk failure messages.

Let's do some discovery: First of all, are you ABSOLUTELY SURE you
have a WD1002-HD0? Does it look like this:

http://www.mylinuxisp.com/~jdbaker/oldsite/images/WD1002HDO.jpg

The WD "HDO" (hard disk only) model 1002 is a version of their 1002-05
controller. (Here's WD1002-05 info:
http://www.xs4all.nl/~fjkraan/comp/wd1002/ )

It's important to identify the EXACT model of controller because it was
different for many of them:

WD1002-WAH, WD1003-WAH, and -WA2 versions, 16-bit, MFM, no
apparent onboard formatter
WD1002A-WX1, MFM, for the IBM XT (or AT with "superBIOS" ROMS), drive
number in AH, interleave in AL, g=C800:5
WD1002S-WX2A, MFM, for the IBM XT (or AT with "superBIOS" ROMS), drive
number in AH, interleave in AL, g=C800:5
WD1002-27X, RLL, 8-bit, but F000 feature has no ROM, others use
g-C800:5 to
format
WD1002A-27X, RLL, 8-bit, similar to above but with SuperBIOS (allows
dynamic entry for drive parms etc)
WD1002-FOX, Floppy/Floppytape controller, no ROM

no ROM = you're screwed without the proper magic port write info :-)

Also, let's take a look at the code block. First of all, are you sure
the copyright messages you're seeing at c800:0 are the controller?
Does it say Western Digital in it somewhere?

I want to see a disassembly of the block. Create a text file called
showme.scr:

--begin editing--
d c800:0
u c800:0
q
--end editing--

....and pass it to debug with this command-line:

debug < showme.scr > output.txt

....and it should create both a dump and a disassembly of the first 128
bytes of c800. Show us the output.txt file. What we're looking for is
a JMP at byte 5.

Did you try the alternate addresses of cc00:5 or c800:0800? Those were
usual WD alternates. If you have a Western digital controller that is
smart enough to coexist with another WD controller, it should install
its ROM at a secondary address; the formatter would then likely be at
CA00:5 Try _u_nassembling all of those in debug as well, looking for a
JMP.

Keep us posted...

.

Relevant Pages

  • Re: Northstar Horizon and Socor IQ130 HELP
    ... the NorthStar controller, with some limitations because the NS ... because it was a NS boot rom that expected a NS disk controller. ... Nominally North*Stars do not have 8" drives as the standard controller ...
    (comp.os.cpm)
  • Re: Laser printer booting problem
    ... everything behaves normally except the display doesn't work. ... The control panel has about 8 buttons, 3 LEDs and a VFD. ... There are two boards to the printer: the DC controller and the formatter. ...
    (sci.electronics.repair)
  • Laser printer booting problem
    ... everything behaves normally except the display doesn't work. ... The control panel has about 8 buttons, 3 LEDs and a VFD. ... There are two boards to the printer: the DC controller and the formatter. ...
    (sci.electronics.repair)
  • Re: Laser printer booting problem
    ... everything behaves normally except the display doesn't work. ... The control panel has about 8 buttons, 3 LEDs and a VFD. ... There are two boards to the printer: the DC controller and the formatter. ...
    (sci.electronics.repair)
  • Re: WinVice High Density 1.6MB support?
    ... ram, rom, CIA, and WD177x-compatible controller. ... 6502 CPU, CMOS variant ... that CMDs manual states that they worked around the ...
    (comp.emulators.cbm)