Xref: utzoo comp.sys.att:8128 comp.unix.questions:17981 comp.unix.i386:1420
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!dynasys!jessea
From: jessea@dynasys.UUCP ( Sysadmin.)
Newsgroups: comp.sys.att,comp.unix.questions,comp.unix.i386
Subject: Trouble with AT+T Unix fdisk on non AT+T Machine.
Message-ID: <4@dynasys.UUCP>
Date: 27 Nov 89 16:49:58 GMT
Reply-To: jessea@dynasys.UUCP (Jesse W. Asher - Sysadmin.)
Organization: Dynasys:  Consulting for the Future.
Lines: 21

I recently got a job as an instructor at a technical school teaching basic  
unix.  I'm familiar with other forms of unix (and xenix), but the school runs
AT+T 6386s with AT+T Unix V/386.  I'm not familiar with the details of AT+T
Unix (such as FACE, etc.) so I was given the complete set, manuals and all,
to install on my own system at home (Everex 386/16 w/4MB memory).  The problem
is that I can't get it to install.  What happens is that I boot from the 
3.5" floppy and it goes to fdisk.  I tell fdisk what partition(s) I want and
then hit "4", which is exit and update.  The system then hangs.  All it does
is the drive light comes on and stays on.  It will not go off until I reboot
the system.  Why does this happen?  Why will it not update the tables?  When
I reboot the system after it hangs, everything was like it was before I tried
to change it.  Do you think there could be compatibility problems?  I am
running a Seagate 4096 with an OMTI MFM controller (which has done just fine
under SCO Xenix).  Unfortunately, AT+T will not support me because I'm 
putting their unix at a non AT+T system!  Anybody have any ideas?  Thanx for
the help.


-- 
Jesse W. Asher - Dynasys - (901)382-1705       Internet: jessea@dynasys.UU.NET 
6196-1 Macon Rd., Suite 200, Memphis, TN 38134     UUCP: uunet!dynasys!jessea