[comp.sys.next] Missing 75 megs?!?

kheit@remus.rutgers.edu (KHEIT) (05/22/91)

Hey, does anyone out there know how to get the full size of a 660
drive into a usable form???  I mean the drive starts out as 760 megs
unformatted I think (the standard maxtor that comes with the cubes),
and next promises 660 megs...Under the workspace it says I have 619
megs and finally when I see the I use the inspector It turns out I'm
only seeing 545 megs!!!
	What gives?  Heck at this point I wouldn't mind even having
just the 619 megs the workspace promises me (although 660 would  be
better).  I used the single partition option when I did the build
disk, but thought that maybe it still makes a secret little partition,
but I couldn't find any extra partitions as root.
	Does anyone know where 1) the missing megabytes are and more
importantly 2) how can I get them back.
	Thank you, John.

mycroft@kropotki.gnu.ai.mit.edu (Charles Hannum) (05/24/91)

In article <May.21.15.07.46.1991.22834@remus.rutgers.edu> kheit@remus.rutgers.edu (KHEIT) writes:

   Hey, does anyone out there know how to get the full size of a 660
   drive into a usable form???  I mean the drive starts out as 760 megs
   unformatted I think (the standard maxtor that comes with the cubes),
   and next promises 660 megs...Under the workspace it says I have 619
   megs and finally when I see the I use the inspector It turns out I'm
   only seeing 545 megs!!!


I can only say two things about this:

  1) You get a *lot* of software with the NeXT.  B-)

  2) Check the size of your swapfile.