From owner-freebsd-questions@FreeBSD.ORG Wed Aug 25 22:58:23 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC06B16A4E5 for ; Wed, 25 Aug 2004 22:58:23 +0000 (GMT) Received: from sccimhc92.asp.att.net (sccimhc92.asp.att.net [63.240.76.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5E1243D1F for ; Wed, 25 Aug 2004 22:58:23 +0000 (GMT) (envelope-from FreeBSD@insightbb.com) Received: from [192.168.1.239] (12-202-28-183.client.insightbb.com[12.202.28.183]) by sccimhc92.asp.att.net (sccimhc92) with ESMTP id <20040825225823i9200920p1e>; Wed, 25 Aug 2004 22:58:23 +0000 From: Steven Friedrich To: freebsd-questions@freebsd.org Date: Wed, 25 Aug 2004 18:58:22 -0400 User-Agent: KMail/1.6.2 References: <412D0FB3.4080608@daleco.biz> In-Reply-To: <412D0FB3.4080608@daleco.biz> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408251858.22625.FreeBSD@InsightBB.com> Subject: Re: FreeBSD architecture X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Aug 2004 22:58:24 -0000 On Wednesday 25 August 2004 06:16 pm, Kevin D. Kinsey, DaleCo, S.P. wrote: > Riki wrote: > >Hi, > > > >I would like to know if FreeBSD could work on my PC. I noticed a lot of > >stuff about supported architectures, but that isn't my language yet and I > >can't tell if my computer fits into one of them or not. I would really > >appreciate your assistance. > > > >I have a pentium 4, intell processor. I have windows xp on one hard drive > >and I would like to put your software on the other. > > > >Thanks, > > > >Erika > > The Intel Pentiums, AMD Durons & Athlons, Via C3s ... and so > many more, are all (x86) architecture. Your Pentium IV is likely > a "686" class CPU [unless they've upped the ante again ;-) ] > > As someone else said, more likely to be at issue are your > hardware peripherals, particularly modems and propietary > USB devices. USB devices that adhere to standards [like > umass for storage] are fine. Some people have to jump through > a few hoops for USB scanners and some cameras though; it seems > to depend on what kind they are. If you have some expensive peripherals, > (maybe if you're a photographer, for example), you might Google for > "FreeBSD <> Problems" ... if you find that some > device causes some issues, you might not be ready to run FreeBSD. > Of course, your next statement may mitigate some of that danger. > > You said, "windows xp on one hard drive" and FreeBSD "on the other"; > you'll be doing what's called "dual booting". You'll want to research > the "how to" of doing that somewhat carefully. Although FreeBSD's > "boot manager" can handle this situation if Windows doesn't interfere > with it, the possibility exists that it might. There are a number of other > "boot manger" programs (GRUB, LILO, GAG are three) that might help > with this issue as well. > > Welcome to FreeBSD! > > Kevin Kinsey > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" I've mentioned it in replies to other users, but it bears repeating. I recommend mobile racks instead of dual-booting. I stopped dual-booting in 1994 after MicroShit blew away one too many partitions. I now use mobile racks and I remove the MicroShit disk, which is in a front panel removable tray, and I slid in FreeBSD, or Linux, or anything else on a different tray. And I have two hardware identical boxes, so if one takes a dive, I can move the drives to the other box and whammo, I'm back in business. Mobile racks I use are only $35/US. Money well spent. And as I've pointed out in other mails, one box can then be used with a drive that you can experiment on, risking nothing more than having to rebuild that drive, and your production drive can be safely on the shelf while you learn new things.