Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!news.dfncis.de!not-for-mail From: oberhage@uni-duisburg-essen.de Newsgroups: comp.sys.next.sysadmin Subject: Re: NeXT won't boot to GUI anymore... Date: 22 May 2013 15:12:49 GMT Lines: 33 Sender: Ruediger Oberhage Message-ID: References: <210b79a1-8a34-4b1f-b5b2-8bfa2c9a18ad@googlegroups.com> X-Trace: news.dfncis.de uc3hvQD5QJ4bBYSUEM15tQl0cz2kWUB/SA+jEJYO4avoW+ X-Orig-Path: not-for-mail User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (Linux/2.6.18-308.el5 (x86_64)) Xref: csiph.com comp.sys.next.sysadmin:7 Hello, are you sure that there didn't happen anything worse than deleten files from 'me'? This ... Sohrab Salehi wrote: : Hello, : I have a NextStation N1100 running a Next Mach OS 3.0. It was working fine until I accidentally removed some files (including ncb) from the me directory. It was really stupid... : [...] : -:tset: not found ... means, e.g., that the command tset isn't found. Either because /usr/ucb is not in your path, or because it doesn't exist any longer as /usr/ucb/tset. This could be due to a disk error, which would also explain, why the boot isn't going along; something is missing. And most probably n o t only in the 'me'-home-directory. : [...] : I was wondering if anyone knows why it isn't showing the GUI and how may I fix that? Any help is greatly appreciated. Have a look into the file /usr/adm/messages - if you can - and see if something is logged there about a problem and try to verify that you harddisk is physically intact and that no essential files are missing or unreachable (as said, you may forget the files from the 'me'-home-directory for now). Best of luck, Ruediger Oberhage