Help with Unisys 6065

Help with Unisys 6065

Post by Jeff Lenartowic » Sat, 11 Jan 1997 04:00:00



I came across a Unisys 6065 dual 486 processor with a passive backplane.
It 4 SCSI hard drives, a tape drive, and a 1.2 meg 5 1/4" floppy drive.
The I/O board has connections for everything but a monitor so I put a
monochrome graphics card in it to see what happens when I boot up.  The
screen doesnt show all of whats going on.  It cuts out words here and
there.  

I can see that it scans the scsi drives and Unix starts to load.   After a
couple of minutes the drive activity stops and the screen goes blank.  I
put in a floppy MS-DOS 6.2 disk and bootup up to an a:\ prompt but the
machine locks up as soon as the boot up stops.  I would like to get it
working and put Win NT on it.  I know there must be some way of changing
the system confiuration so I can put a 3 1/2" floppy drive in and to see
how much memery is on the memory board.  I just need some manuals for the
machine and I should be fine.  

Help!  Do you know where I can get manuals or help.

Jeff Lenartowicz

 
 
 

Help with Unisys 6065

Post by J.H. Park (korn » Sun, 12 Jan 1997 04:00:00


: I came across a Unisys 6065 dual 486 processor with a passive backplane.
: It 4 SCSI hard drives, a tape drive, and a 1.2 meg 5 1/4" floppy drive.
: The I/O board has connections for everything but a monitor so I put a
: monochrome graphics card in it to see what happens when I boot up.  The
: screen doesnt show all of whats going on.  It cuts out words here and
: there.  

Unisys U6000/65 Model has not graphics cards originally. So if you want
to see any messages of Unix on the VGA Mornitor, you should put VGA
color graphic cards in U6000/65, and then run SCU(System Configuration
Utility) Diskette. In the SCU, there is a option to change graphic cards
or dummy console using serial cable.

: I can see that it scans the scsi drives and Unix starts to load.   After a
: couple of minutes the drive activity stops and the screen goes blank.  I
: put in a floppy MS-DOS 6.2 disk and bootup up to an a:\ prompt but the
: machine locks up as soon as the boot up stops.  I would like to get it
: working and put Win NT on it.  I know there must be some way of changing
: the system confiuration so I can put a 3 1/2" floppy drive in and to see
: how much memery is on the memory board.  I just need some manuals for the
: machine and I should be fine.  

Well, I think you can contact local Unisys, and get some helps.
That machine is so old machine, so I don't have any manuals. :-(

: Help!  Do you know where I can get manuals or help.

: Jeff Lenartowicz

Good Luck,
--
           \__    __    __    __                __    __    __
          _/  \__/  \__/  \__/  \__/   __    __/  \__/  \__/  \__/
   Jae-Hwa Park  \__/  \__/  \__/  \__/  \__/ Unisys Korea Ltd.  \__


        \__/  \__/  \__/  \__/  \__/  \__/  \__/  \__/  \__/  \__
           \__/  \__/        \__/  \__/  \__/ AlzzaWare Linux !
                                            \__/        \__/  \__/

 
 
 

Help with Unisys 6065

Post by Michael Johansso » Sun, 19 Jan 1997 04:00:00


I'am not sure but I don't think NT can use the second CPU, this machine
is old
and I can't imagine it's compatible with Intel SMP standard. The
SCSI-controller
might also be a problem.

You can try to connect a dumb terminal to the serial port, the baudrate
normally is 9600. The lastest, and last I think, OS release for the
U6000/65
is SVR4 1.4.

Perhaps you should also send a note to comp.sys.unisys.

Michael Johansson

 
 
 

1. In article 26782@ecdcsvr.tredydev.unisys.com, gdk@tredysvr.tredydev.unisys.com () writes:

I have seen similar problems with SVR4 sockets (Solaris 2.2) - the process writing
to the socket *should* receive an EPIPE signal when the process reading from the
socket gives up and dies.  This happens 100% of the time on SunOS 4.1.x, but on
Solaris 2.2, about 1 in 10 times the EPIPE never arrives, and the writing process
'hangs' forever, even though its parent process is long gone.  I have truss output
from two IDENTICAL program runs, showing everything truss is capable of showing.
One of these processes exited as designed, and the other 'hung' on the write() to
the socket.  The truss outputs (about 2.5 reams (!!) of paper) have been gone over
in detail, both manually and by diff scripts, and they are almost identical - the
only differences are things like child PID's and tm and time_t structs containing
system times.  I would REALLY like to know why!  Anyone out there have a clue?

2. SCSI hassel: can't fdisk HP 1GB disk (no disk geometery)

3. Anyone help ID my unisys monitor?

4. More on Brian K. West...

5. Help: Remote printing from HP to UNISYS

6. Looking for some challanges?? Answer this .....

7. Help with screen 3.1, unisys 6000/30, psuedoterminals

8. Multilink PPP connection

9. UNISYS U6000/65 HELP

10. help wanted on unisys 5000/90 system

11. Unisys 6055's, SCSI, and Linux . . . HELP!

12. help scsi - unisys

13. DYNIX Unisys UNIX Printing Help - CR/LF and HP LaserJets