Date: Wed, 26 Feb 1997 19:38:27 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: A Rosina Bignall <bignall@aros.net> Cc: freebsd-questions@freebsd.org Subject: Re: Installing FreeBSD Message-ID: <Pine.BSI.3.94.970226193621.8482R-100000@localhost> In-Reply-To: <199702260600.XAA09967@shell.aros.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 25 Feb 1997, A Rosina Bignall wrote: > > Hm. Try NOT doing ANY post-install, just exit. You can do any of the > > post-install activities afterwards. > > Okay, I'll try it. Should it boot from the hard disk then, or should > I need to use the floppy. It never has gone through any questions for > BootEasy (if I remember what it's called correctly), but I don't know > if this is normal or not, since I've always used LILO previously. Booteasy auto-configs, and if you still have linux around you can use lilo. > > 1. Delete the freebsd slice and start anew. > > 2. Keep an eye on the ALT-F2 console during install. It may be having > > trouble and you're not seeing it. > > Okay, I'll watch an install next time. Hopefully I'll have time to > observe one tomorrow evening. Is there any way to capture all of it > somewhere since it's a rather long process over a 14.4 modem? Do you have a DOS slice on this computer? You could do a DOS install, or buy the CDROM. > > What install method are you using, I forgot. > > 2.1.7 via FTP over a PPP link. And, I've tried both Novice and custom > installs. Ok. > > The RAM may be defective then. DOS and friends are pretty lenient towards > > bad memory, but FreeBSD gives it a real workout and will ferret out any > > faulty RAM. > > Actually, I never use DOS/Windoze, I just keep it there for the > occasional time that my brother comes to visit and wants to play games > on it ;). I've been using Linux and have had no problems with it so > far, although I have had a few more crashes than I used to have, I > figured that that was due to the fact that I changed to a slightly > less stable kernel about the same time that I upgraded the RAM. But, > just to be sure, do you know of anyway that I can run a good check on > the memory to see if there are any problems with it. The best way is to find someone with a SIMM checker, an actual hardware device :) If you can get the system up, try compiling something; if it dies with a sig11 from program cc1, your memory is probably at fault. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.94.970226193621.8482R-100000>