Always fun building a PC. Most of the times things will work, but sometimes there's a dodgy connector or a driver issue. I've not built one in a while, but then the old one does okay. I do need to trace a fault on an old one that has no video output.
You are viewing a single comment's thread from:
If you put a computer in a milk crate, might that expose the motherboard a bit more to the risk of excessive amounts of electric shock? I'm hoping that enough fan action would blow away the dust. I probably should buy a computer vacuum or something.
It could get dusty. My PC case has filters on the fans and other vents, but I do not clean it out very often anyway.
The biggest risk may be the possibility of frying the motherboard via electric shock, secondly might be messing it up with liquids. In third place, I'm thinking dust. I've never cleaned my 5 year old laptop here. But in the future, I'm thinking of being more cautious. I did use a regular vacuum on a desktop.
Yeah being an open case it's something I need to be more careful around. Though by using old parts I dont really care if it fries or gets dusty. If it was not for this project I would have scrapped them.
I agree.
Hah yeah used parts is always a hit or miss thing. And sometimes these machines are so old trying to find drivers is almost impossible.
Luckily ubuntu has them in their repos. With Windows you gotta goto the manufactures site and hope they still have the files.
I find most things 'just work' on Ubuntu. Linux can be easier to set up than Windows despite what many people think.
I use Ubuntu Mate 16.04. Yeah, Linux tends to have a repository of older drivers of all sorts of things. The one tricky thing that I recently figured out was how to unblacklist my ethernet driver on my laptop. I don't even know how my Ethernet port stopped working for like the past year or longer. But I got it working again finally some hours ago. It turned out that the Ethernet driver was on a blacklist file. So, I went into the file and removed it and then added the driver name to another file to make sure the driver would load during startup. I don't know how many hours it took me to solve that problem. But am glad I solved the puzzle.
Hah yeah I've gone through some strange troubleshooting as well on Linux. Can take hours to figure out what's wrong.. glad you got your issue resolved. Never heard of that problem.
I generally Google my problems and find forums where people discuss having similar issues if not the same exact problems.