home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!uwm.edu!ux1.cso.uiuc.edu!usenet.ucs.indiana.edu!stupid!francisr
- From: francisr@stupid.ucs.indiana.edu (Rob Francis)
- Newsgroups: comp.sys.next.sysadmin
- Subject: Re: System panic while reading CDROM
- Message-ID: <BxB10I.KFx@usenet.ucs.indiana.edu>
- Date: 6 Nov 92 17:09:53 GMT
- Article-I.D.: usenet.BxB10I.KFx
- References: <1dd5ajINNd7q@crcnis1.unl.edu>
- Sender: news@usenet.ucs.indiana.edu (USENET News System)
- Organization: Indiana University
- Lines: 27
- Nntp-Posting-Host: stupid.ucs.indiana.edu
-
- In article <1dd5ajINNd7q@crcnis1.unl.edu> hickman@cse.unl.edu (Hubert B. Hickman) writes:
- >Well I seem to have myself an interesting problem. Some time
- >back I received the NeXT 3rd party demo CDROM. I accessed some
- >of the demos shortly after I received it and everything seemed
- >pretty much OK. Note that at this time I was running 2.1 and
- >had to update the CDROM filesystem as per instructions included
- >in the CDROM.
- >
- >Since that time I have upgraded to 3.0. Since our local user
- >group is holding a meeting on Saturday, I thought it would be
- >a good idea to show this CDROM at the meeting. So, I take
- >it out, pop it in the drive and try to navigate around in it.
- >Well, at about the 4th or fifth directory - BLOOEY - system
- >panic. This happens consistently every time I try to read the
- >demo CD. I can read the 3.0 upgrade CD just fine, runs apps of
- >it, copy things from it, etc. No problems with it.
-
- I encountered this the day after I upgraded to 3.0. If you recall,
- there was a script that you had to run when you got the 3rd Party ROM
- --it altered /usr/filesystems/CDROM.fs and is bogus to 3.0 i.e., it
- makes 3.0 panic. Just copy /usr/lib/filesystems/CDROM.fs off of the
- 3.0 CD, and all will be well.
-
- -rob
- ----
- Rob Francis Unix Systems Specialist, Indiana University
- francisr@indiana.edu (812)855-0327
-