3B2 Device table wierdness

[Bill Kennedy]

In article <1284 at ssbn.WLK.COM> I wrote:
[ stuff about showing hard disk 0 as HD10, drive 1 as NULL ]

>Please email (since this is so odd) and if others want to know
>too, I'll post the answer.  Thanks!

Brian Kantor (brian at ucsd.EDU) got me started, and I got several replies,
so I figured I'd summarize and maybe keep some others out of a dead end
street that has my footprints in it.  Thanks to all!

:Date: Mon, 5 Feb 90 09:20:56 EST
:From: Mike Pearce <casux4!@casux4.UUCP:map>
:Subject: 3B2/310 devices showing up as NULL
:
:I assume that you have 2 72MB drives and not a 10MB within you 3B2.
:If this is true, then I know what you have done, I think :-),
:Firstly, You have used drives that were NOT used previously in a 3B2.
:Secondly, you have formated these drives with the Idtools package.
:If this is what you did, then you didn't enter the correct drive type
:when you entered all of the data to format the drive.
:I think you must of entered '0 or 1' instead of '8'.
:If you don't know what I am talking about please talk to the person who
:formated your 72MB drives. Otherwise If you need a walk-though then I will
:give you the steps you need to go though to correct the problem.
:
:I had the same problem when I added a second 72MB drive to my 310. It
:came out as NULL and then as a Floppy device until I fixed the drive type.
:The information about drive types, I found out, is within the 3B2
:maintainance manual that comes with the Idtools.
:
:Hope this helps.
:
:	Mike Pearce	att!attdso!tws4!map

Mike Pearce had a perfect bulls eye, what he describes is *exactly* what
I had done.  Brian got me prowling around, and Mike confirms what I thought
I figured out.

:From: ram%attcan at gpu.utcs.toronto.edu
:Subject: Re: 3B2 Device table wierdness
:Date: 	Mon, 5 Feb 90 12:11:49 EST
:
:Try shutting down the system to firmware mode (either use shutdown -i5 -g0 -y)
:or do a normal shutdown and hit the reset button as soon as the system passes
:diagnostics.
:
:You will be asked for a name of a program to edit, at which point type
:"filledt".  This will re-write the equipped devices table for the appropriate
:devices.
:
:Regards
:
:------------------------------------------------------------------------------
:     Richard A Meesters                |
:     Technical Support Specialist      |     Insert std.logo here
:     AT&T Canada                       |
:                                       |     "Waste is a terrible thing
:     ATTMAIL: ....attmail!rmeesters    |      to mind...clean up your act"
:     UUCP:  ...att!attcan!ram          |
:------------------------------------------------------------------------------

What Richard describes, and then Mark (below) brings up an interesting
"feature".  I found a command, edittbl that will take some text and make
it into a file suitable for filledt and even put it in /dgn for you.  I
will ASSume that this means that you could invent some names for subdevices
and build your own table to describe a Frammis IV disk drive, Fortesite IX
tape drive, etc.  Then you could filledt with that and have something other
than those devices named for you.

:Date: 5 Feb 90 09:24:41 EST (Mon)
:From: fenicks!mjm at uunet.UU.NET (Mark J. Muthig)
:
:The command you need to run. I believe, is 'filledt(8)'.  It usually runs
:automatically at power-up, but I do remember some problems in the past.
:
:Hope this helps,
:
: Mark J. Muthig
: Phoenix Telecom, Inc., 500 Helendale Road, Rochester, NY  14609
: UUCP: uunet!fenicks!mjm
:      {allegra,cornell,kodak,rutgers,seismo}!rochester!ritcv!phoenix!mjm
: ATTMAIL: attmail!phxmail!mjm   VOICE: 716/654-7030   FAX: 716/654-7653

Again, many thanks to all and particularly for the prompt responses!
-- 
Bill Kennedy    {texbell,att,cs.utexas.edu,sun!daver}!ssbn!bill
                bill at ssbn.WLK.COM  or attmail!ssbn!bill