I suspect that many of us who have built computers from scratch
first started like you.  We then progressed to replacing a motherboard
in an existing pc (also memory and cpu, of course).  Then we built
a computer from scratch.

Since you already have a computer, you have access to this list
for help if you run into trouble.

You will maybe get the best prices by mail order, but if you have
a local supplier for motherboards and cpus, then their help can
be invaluable if you have problems.  Once I installed a mb and
it would not work.  I took it to the local guy and he told me my
memory was not in correctly - a common beginner's mistake.
I was very embarrased because I had checked and rechecked
the memory seating, but did not see that it was not quite in.  So,
if you can, buy local where you can get help.

Don't forget to look at the pcbuild web site.  There is an excellent
explanation of how to put in a mb - the scariest part.

Go for it!

Dean Kukral

-----Original Message-----
From: Paul Roeth <[log in to unmask]>
Date: Thursday, January 20, 2000 12:45 AM
Subject: [PCBUILD] PCBUILD: My first computer from scratch


>Hello,
>
>This will be my first successful post to this list (don't ask).  I'm
>relatively new to computers and want to build my own.  I'll preface this
with
>some information of my knowledge so you will get an idea how to respond
>(should you decide to).
>
>I've used several MS software packages (not an expert in any).
>I've installed service releases, patches and updates to some software.
>I've never installed an OS.
>I know what a driver is but wouldn't be able to pick one out in a list.
>I've added a network card to a computer but the computer "found new
hardware"
>and prompted me through the software installation.
>I've upgraded/added RAM to a computer but never touched a CPU.

Most motherboards come with ZIF sockets which are a lot less scary to
put a cpu into.  Often the mb/cpu vendor will send the cpu already inserted.
Slot One motherboards are easy, provided everything fits.

>I've never touched a jumper but I know what they are and what they are for.
>I have a slight understanding of the Master/slave relationship.
>I know very little about CMOS and BIOS.
>I know there are SCSI, AGP, IDE slots and one or more FDC slots.
>Don't know what IRQ's do per se, but know they are important.

You **should** not have to worry about these unless you run into trouble.

>I know what partitioning is but not how to do it.
>Have little understanding of FAT16/32 but know this is important.

You will likely tell windows to use 32 when you install the os.

>I know the expandability is dependent on the motherboard.

Pretty much it is a matter of how many PCI slots vs AT slots.

>Finally, I know enough to be grounded when I'm tinkering inside a computer.

Good!

>
>My idea of building a computer is as follows (not having any experience);
>1. Purchase the necessary hardware (case, motherboard, monitor, mouse,
>keyboard, sound card, video card, CPU, RAM, HD, power supply, fans, CD
drive,
>Floppy drive and modem.  (Not sure if cables come with any of this stuff.
>Also, not sure if parallel or serial ports come with this stuff either).
I'm
>sure I've missed something here, so please let me know.  Also, there must
be
>compatibility issues to work out so I hope you don't mind follow up
questions.

Usually the mb comes with disk drive cables.  The cd drive comes with a
sound
cable.  Make sure you get drivers for the cd.  The ports are built into the
mb.  The
power supply and fans usually come with the case.

>2. Assemble the components.

Don't forget the grounding part.

>3. Turn on the computer. (Do I hear POST beep here?)

Have a fire extinguisher ready.  <g>

>4. Partition the HD. (Don't know how)

You use fdisk, which you cleverly added to a dos boot disk from your
other computer (along with and editor and mouse drivers, etc.).

>5. Install the OS. (Send the check to Bill)
>6. Install necessary drivers.

Sometimes windows will have these, but for the latest stuff it will not.

>7. Install my favorite software.
>8. Throw the whole thing at the wall because it doesn't work. (OK, I won't
do
>that)
>
>I'm sure that if I follow the above, the computer won't work.  Some of
those
>steps must be out of order and some steps are missing completely.  Since I
>believe in doing as much research as I can perhaps someone would suggest
good
>reading, websites, or knowledge base/archive sites and how to use them.
>
>My apologies for such an exhausting post but I assure you all future posts
>will be shorter.  Thanks for any input, ideas or suggestions.
>Paul Roeth
>[log in to unmask]
>

         The PCBUILD web site always needs good submissions.  If
          you would like to contribute to the website, send any
               hardware tech tips or hardware reviews to:
                           [log in to unmask]