Re: 3B2 Disks



On 2009-01-11, Bill Gunshannon <billg999@xxxxxxxxxxx> wrote:
In article <slrngmirtg.e2f.dnichols@xxxxxxxxxxxxxxxxxx>,
"DoN. Nichols" <dnichols@xxxxxxxxxxx> writes:
On 2009-01-11, awesie@xxxxxxxxx <awesie@xxxxxxxxx> wrote:
[Originally posted in comp.sys.att. Forwarded here on recommendation.]

I have a 3b2 that works but whose password has been lost to the ages.
I have a copy of the disk images for the 3b2 including the "System
Essentials" disk, but I need to find a way to get these onto a floppy.

O.K. I've never worked with a 3B2 -- just the 3B1 -- but what
is the floppy size -- 5.25" or 3.5"


The 3B1 and the 3B2 have nothing in common with each other.

The vendor. And the fact that they both are computers.

And the fact that they both ran SysVr? OS versions (with various
add-ons. :-)

And -- I've got a 3B2 external drive housing attached to one of
my 3B1s, to hold both the boot drive (no longer internal) and the second
drive, plus a "floppy tape" drive. Granted, it took a bit of creative
wiring to do that all.

But since they both were SysV unix, there may well be enough
similarity in disk formats to allow one to look at a disk belonging to
the other.

And *any* SCSI disk (if his system uses SCSI, either a direct
SCSI disk, or a MFM or such adapted to SCSI by an external card) should
be readable on a sector-by-sector basis to allow some of my suggestions
to work. After all -- the two systems which I described gaining access
to were not even AT&T products -- one was Tektronix with the NS 32016
CPU, and the other was Intergraph with a Fairchild "clipper" CPU. The
first ran a BSD flavor of OS, and the second a SysV flavor. The first I
broke the password on using a 3B1 as the password cracking engine, and
the second I accessed the raw sectors on using a Sun 2/140 (BSD to
access a drive from a SysV based system.

The 3B1 was
a Convergent Technologies box sold by AT&T and the 3B2 was an AT&T designed
and manufactured box using the WE32000 CPU.

Both with the AT&T "Death Star" logo, and similar color schemes,
FWIMBW.

I will look later today, but,
sadly, I believe I threw all my 3B2 software away years ago when my last
3B2 died. If I still have any of them, they yours for the postage.

And -- if you *don't* have them, it is still possible that he
may be able to use some of the ideas which I covered.

Enjoy,
DoN.

--
Email: <dnichols@xxxxxxxxxxx> | Voice (all times): (703) 938-4564
(too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
--- Black Holes are where God is dividing by zero ---
.



Relevant Pages

  • file systems disappearing
    ... The config is two SCSI disks and one IDE disk. ... Recently one of the large partitions on the second SCSI ... The IDE disk is used for data that is static, ... "images" is a mount point for one of the 2nd scsi disk file systems. ...
    (comp.unix.solaris)
  • Re: How to make disk device "Available"?
    ... >> PROM Revision ... > I cannot tell from that output if that is the LUN you are ... Description: 1.0 GB SCSI Disk ...
    (comp.unix.aix)
  • Re: what to do about "cannot dump to dumpdev hd(1/41): space for
    ... The brand new SCSI disk does the exact same thing the old one did. ... Divvy looks the same, the same 3 bad blocks were complained about when I added the disk with mkdev hd the first time, when I do fsck -ofull on /dev/part4 and /dev/part5 they both have the same warning about the filesystem being larger than the filesystem it is currently in etc. so at this point it looks like a good copy of the original disk. ... Then investigate the remaining tapes. ...
    (comp.unix.sco.misc)
  • Re: what to do about "cannot dump to dumpdev hd(1/41): space for
    ... hard disk showing 255 hds, ... If a panic reports 0 blocks of dump space, ... Changing the starting block of a valid file system ... If you feel you must restore from tape, get a new SCSI disk, ...
    (comp.unix.sco.misc)
  • Re: [ANNOUNCE] sdparm 0.92
    ... Just got it and tried on an external usb disk. ... Could you add the ability to spin down/up a scsi disk? ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)