New Office Build

[mvbighead]

If the motherboard of your custom-built PC fails three years after the PC was built, your odds of finding the same model motherboard for a replacement are low. Sure, you could get another model, but that could potentially have a different chipset, different storage controller, a different network controller, different quantity and layout of expansion slots, different audio controller, etc.

The GX620 mobo might cost a bit more, but at least I know it's the same motherboard, meaning I won't have to reconfigure the OS to work with the new hardware. If you were to replace a whitebox motherboard with a diffferent model, you could be screwing with the OS for hours trying to get everything working again.

Hours? Hardly. Pop into device manager and install the drivers for devices that are missing them. Done.

I think you are missing the point. A custom built machine will have several options because you can fit any standard MB into the case. Dells, not so much. Further, should that person want to upgrade, they could do so at the cost of a MB, CPU, and memory most likely. The Dell, you either buy a new one or see what the best processor is that you can drop in it, and add more memory if possible.

The biggest thing is flexibility. If you want it, you build your own. If you don't care... you buy a Dell. There is no point bickering about this, as it is always a matter of personal preference. For me, I will likely never buy a Dell for myself. It seems the OP is in the same boat.

And to different this/that/theother with the new MB, it is quite possible that, at that time, the system either gets an overhaul or gets handed down to a kid. A complete OS reload wouldn't be out of the question at that time, so it doesn't matter much if the board has to be replaced. It's still better than not being able to find the exact motherboard he needs... not to mention the 90 plus bucks spent to buy a refurbished board that is no better than a brand new $40-50 board from newegg.

 

[Davidh373]

^ Agree :thumbsup:

 

[mfenn]

This costs money though, and usually a fair amount.

Mvbighead, you are usually pretty good in most threads, but you're having a tough time reading my posts in this one today! I specifically mentioned that ProSupport is standard in the cost of most business-class machines. Sure you can take it off, but it's still built in to the base price.

http://www.newegg.com/Product/Produc...82E16813138302

Not to pick nits, but I asked for a socket 423. 😉

EDIT: I should mention that I fundamentally agree that it is a personal preference whether to build or buy for basic home office machines. It's pretty clear cut that you build gaming rigs and buy business machines, but home office is kind of murky.

 

[theevilsharpie]

Hours? Hardly. Pop into device manager and install the drivers for devices that are missing them. Done.

I recently went through this myself when I set up my new PC. Here's how the process really goes:

1. Turn on computer, and wait 10-15 minutes for it to scan for and install the drivers for all of the new hardware. Wait for the computer to reboot.
2. Log into computer, and check device manager for missing devices
3. Open a web browser to get the new drivers, and curse when you realize that Windows doesn't recognize your new network adapter
4. Jump on another PC and download the appropriate drivers to a USB flash drive (Don't have another PC handy? Lulz)
5. Install drivers and reboot PC. Wait for PC to detect new hardware. You'll probably need to reboot again.
6. Remove drivers for old hardware from Add/Remove programs. Reboot (...again).
7. Configure the device manager to display unplugged hardware, and remove the drivers from there.
8. Install any other software needed by your new mobo
9. Reconfigure power settings to match new mobos capabilities

Total time: About 2 hours

Oh, and I didn't have to deal with any storage-related issues because I moved my storage controller with me. Were you using your old mobo's onboard storage controller? Good luck :awe:

 

[mvbighead]

I recently went through this myself when I set up my new PC. Here's how the process really goes:

1. Turn on computer, and wait 10-15 minutes for it to scan for and install the drivers for all of the new hardware. Wait for the computer to reboot.
2. Log into computer, and check device manager for missing devices
3. Open a web browser to get the new drivers, and curse when you realize that Windows doesn't recognize your new network adapter
4. Jump on another PC and download the appropriate drivers to a USB flash drive (Don't have another PC handy? Lulz)
5. Install drivers and reboot PC. Wait for PC to detect new hardware. You'll probably need to reboot again.
6. Remove drivers for old hardware from Add/Remove programs. Reboot (...again).
7. Configure the device manager to display unplugged hardware, and remove the drivers from there.
8. Install any other software needed by your new mobo
9. Reconfigure power settings to match new mobos capabilities

Total time: About 2 hours

Oh, and I didn't have to deal with any storage-related issues because I moved my storage controller with me. Were you using your old mobo's onboard storage controller? Good luck :awe:

You and I have totally different experiences then. Hell, even with XP it's never been that bad.

As for a flash drive and alternate computer with which to use to download NIC drivers. Your motherboard typically comes with something called a driver CD. I am the type of person that always wants to go with new drivers, but for the practice of getting started, you can always install the driver from the driver CD to get you connected to the Internet so that you can start downloading. It's not a tough experience.

Issues with disk controllers can sure happen from time to time, but if you wind up replacing your system with an altogether different chipset, you're probably best off reloading your OS. However, most cases even when replacing a board with a totally different chipset, I never have an issue booting. The only time you can certainly expect an issue is if you are using RAID.

About the only thing I can figure is that, for your example, you are replacing a board on a PIII 450 with 64mb of RAM running Windows 95. About the longest part in any rebuild is waiting for the OS to detect hardware, and from the 50+ times I had done this for customers 7-8 years ago, this took about 5 minutes tops. Then install chipset drivers, video drivers, sound drivers, NIC drivers, then reboot. Examine remaining missing drivers in DM, and add as needed. Total time, 30 minutes tops.

Other software needed by your motherboard? Boy are you reaching here! The only thing a motherboard NEEDS is drivers. Sure, you can install tweaking utilities and such that come with the board, but they are by no means necessary or required.

I can't seem to figure out what you are getting at, other than how bad you are working on a simple board replacement. Seriously, any time I do this for myself, I typically look at reloading my OS. Not a big deal for me, and I like a fresh build from time to time... makes the system feel new. As for a board replacement for someone else who doesn't want to have to reload, you look to find as similar a replacement board as you can. Perhaps going from an Intel 845 chipset to an 865. In some cases, you'll find the exact same board. Some cases, a board with the same chipset. Some cases, you have to go to a totally different chipset. In any case, there is work to be done on a board replacement... both physically and in the OS.


Oh, and mfenn... here's your socket 423 motherboard:
http://www.esaitech.com/commerce/catalog/product.jsp?product_id=50988

http://micropartsusa.com/d850gb-inte...urbished-.html

http://www.serversupply.com/products/part_search/pid_lookup.asp?pid=104022

http://www.google.com/products/cata...a=X&ei=nsANTs2ACvC00AGH17XGDg&ved=0CEwQ8wIwAA

And while the above links aren't the greatest, lets keep in mind that this socket lived in 2000 through 2001, 10 years ago. If someone is still hanging onto one of these puppies, it might be time to let it go.

 

[Davidh373]

You and I have totally different experiences then. Hell, even with XP it's never been that bad.

XP was that bad lol! At the same time, I've installed windows 7 on 6 different computers. Not once have I had it not automatically install a network driver that's functional.