For your first question, the answer is actually very simple. It's because of the difficulty of finding service material. If I have my camera handy I may make a guide but at the same time, it has to make sense. I have a policy of 2007 and up being considered for guides only, since I consider this reasonable. I don't think it's really worth making a guide for a 2002 Dell, for example. It's going to get little to no use because after 10+ years that thing is going to be treated as eWaste.
Could I do it? Absolutely, and I have before in the past but these days I stick to 2007+ for guides, since these are almost always at least a C2D, which are far more useful today then any Pentium 4.
Back when I wrote this, I was really only taking in small jobs on occasion, and this didn't happen a lot. These days, I can get them with little trouble and if I want an old system because it's going to be eWasted, it's almost always mine even without asking. This is because of my data destruction policies. My policies are HIPAA/privacy law cases get the drive back(this is a liability protection for both parties, and to help them stay in compliance. As soon as the drive leaves the door, it's a breach.), business cases are in multiple classes(they can ask for the drive at any level, too.) and home users have the choice entirely. These policies played a major role in making it easy to get good jobs.
-
While I am all about keeping old machines out of the landfill, I only really do that with C2D machines these days. I don't think it really makes sense to fix Pentium 4 machines when I can get C2D equipment. I'll fix it if I have a use case that needs it or it's more ideal(i.e. XP machines) but for the most part I will only fix C2D and up, and I will still use a 1st gen Core i series machines. They're definitely showing their age, but I can fix that with Linux if it comes to it. I have just had too many problems with the older Dell machines to justify continuing to repair them. I have used CRT's with these, too but once again I don't keep any CRT. I stick to Trinitron rebadges and good ones like the Compaq Business ones if it's not based on a Sony CRT.
+
While I am all about keeping old machines out of the landfill, I only really do that with C2D machines these days. I don't think it really makes sense to fix Pentium 4 machines when I can get C2D equipment. I'll fix it if I have a use case that needs it or it's more ideal(i.e. XP machines) but for the most part I will only fix C2D and up, and I will still use 1st gen Core i series machines. They're definitely showing their age, but I can fix that with Linux if it comes to it. I have just had too many problems with the older Dell machines to justify continuing to repair them. I have used CRT's with these, too but once again I don't keep any CRT. I stick to Trinitron rebadges and good ones like the Compaq Business ones if it's not based on a Sony CRT.
This all more or less happened, because of all the problems I had with a Dimension XPS 5150 with Win98 FE back in the day, since Win 9x was known to be very, very unstable because of 16/32-bit code. If the 16-bit code or underlying DOS code crashed, you got a BSOD since 16-bit is considered "real mode" and a real mode crash is fatal where a 32-bit crash isn't as bad. You lose the application that crashed, but not the system. Since this happened on a regular basis, so I also had to fix this on a regular basis. I also took it apart years back too. This all happened 16 years as of the initial wring, and now at least 20. Once it gets that far, it's no longer a hobby. It's a career.
For your first question, the answer is actually very simple. It's because of the difficulty of finding service material. If I have my camera handy I may make a guide but at the same time, it has to make sense. I have a policy of 2007 and up being considered for guides only, since I consider this reasonable. I don't think it's really worth making a guide for a 2002 Dell, for example. It's going to get little to no use because after 10+ years that thing is going to be treated as eWaste.
Could I do it? Absolutely, and I have before in the past but these days I stick to 2007+ for guides, since these are almost always at least a C2D, which are far more useful today then any Pentium 4.
Back when I wrote this, I was really only taking in small jobs on occasion, and this didn't happen a lot. These days, I can get them with little trouble and if I want an old system because it's going to be eWasted, it's almost always mine even without asking. This is because of my data destruction policies. My policies are HIPAA/privacy law cases get the drive back(this is a liability protection for both parties, and to help them stay in compliance. As soon as the drive leaves the door, it's a breach.), business cases are in multiple classes(they can ask for the drive at any level, too.) and home users have the choice entirely. These policies played a major role in making it easy to get good jobs.
While I am all about keeping old machines out of the landfill, I only really do that with C2D machines these days. I don't think it really makes sense to fix Pentium 4 machines when I can get C2D equipment. I'll fix it if I have a use case that needs it or it's more ideal(i.e. XP machines) but for the most part I will only fix C2D and up, and I will still use a 1st gen Core i series machines. They're definitely showing their age, but I can fix that with Linux if it comes to it. I have just had too many problems with the older Dell machines to justify continuing to repair them. I have used CRT's with these, too but once again I don't keep any CRT. I stick to Trinitron rebadges and good ones like the Compaq Business ones if it's not based on a Sony CRT.
-
This all more or less happened, because of all the problems I had with a Dimension XPS 5150 with Win98 FE back in the day, since Win 9x was known to be very, very unstable because of 16/32-bit code. If the 16-bit code or underlying DOS code crashed, you got a BSOD. This happened on a regular basis, so I had to fix this crap on a regular basis. I also took it apart years back too. This all happened 16 years as of the initial wring, and now at least 20. Once it gets that far, it's no longer a hobby. It's a career.
+
This all more or less happened, because of all the problems I had with a Dimension XPS 5150 with Win98 FE back in the day, since Win 9x was known to be very, very unstable because of 16/32-bit code. If the 16-bit code or underlying DOS code crashed, you got a BSOD since 16-bit is considered "real mode" and a real mode crash is fatal where a 32-bit crash isn't as bad. You lose the application that crashed, but not the system. Since this happened on a regular basis, so I also had to fix this on a regular basis. I also took it apart years back too. This all happened 16 years as of the initial wring, and now at least 20. Once it gets that far, it's no longer a hobby. It's a career.
For your first question, the answer is actually very simple. It's because of the difficulty of finding service material. If I have my camera handy I may make a guide but at the same time, it has to make sense. I have a policy of 2007 and up being considered for guides only, since I consider this reasonable. I don't think it's really worth making a guide for a 2002 Dell, for example. It's going to get little to no use because after 10+ years that thing is going to be treated as eWaste.
-
Could I do it? Absolutely, and I have before in the past but these days I stick to 2007+ for guides, since these are almost always at least a C2D, which are far more useful today then any Pentium 4.
-
Back when I wrote this,I was really only taking in small jobs on occasion, and this didn't happen a lot.These days, I can get them with little trouble and if I want an old system because it's going to be eWasted, it's almost always mine even without asking.This is because of my data destruction policies. My policies are HIPAA/privacy law cases get the drive back(this is a liability protection for both parties, and to help them stay in compliance. As soon as the drive leaves the door, it's a breach.), business cases are in multiple classes(they can ask for the drive at any level, too.) and home users have the choice entirely. These policies played a major role in making it easy to get good jobs.
+
Could I do it? Absolutely, and I have before in the past but these days I stick to 2007+ for guides, since these are almost always at least a C2D, which are far more useful today then any Pentium 4.
-
While I am all about keeping old machines out of the landfill, I only really do that with C2D machines these days. I don't think it really makes sense to fix Pentium 4 machines when I can get C2D equipment. I'll fix it if I have a use case that needs it or it's more ideal(i.e. XP machines) but for the most part I will only fix C2D and up, and I will still use a 1st gen Core i series machine. I have just had too many problems with the older Dell machines to justify continuing to repair them. I have used CRT's with these, too but once again I don't keep any CRT. I stick to Trinitron rebadges and good ones like the Compaq Business ones if it's not based on a Sony CRT.
+
Back when I wrote this, I was really only taking in small jobs on occasion, and this didn't happen a lot. These days, I can get them with little trouble and if I want an old system because it's going to be eWasted, it's almost always mine even without asking. This is because of my data destruction policies. My policies are HIPAA/privacy law cases get the drive back(this is a liability protection for both parties, and to help them stay in compliance. As soon as the drive leaves the door, it's a breach.), business cases are in multiple classes(they can ask for the drive at any level, too.) and home users have the choice entirely. These policies played a major role in making it easy to get good jobs.
+
+
While I am all about keeping old machines out of the landfill, I only really do that with C2D machines these days. I don't think it really makes sense to fix Pentium 4 machines when I can get C2D equipment. I'll fix it if I have a use case that needs it or it's more ideal(i.e. XP machines) but for the most part I will only fix C2D and up, and I will still use a 1st gen Core i series machines. They're definitely showing their age, but I can fix that with Linux if it comes to it. I have just had too many problems with the older Dell machines to justify continuing to repair them. I have used CRT's with these, too but once again I don't keep any CRT. I stick to Trinitron rebadges and good ones like the Compaq Business ones if it's not based on a Sony CRT.
This all more or less happened, because of all the problems I had with a Dimension XPS 5150 with Win98 FE back in the day, since Win 9x was known to be very, very unstable because of 16/32-bit code. If the 16-bit code or underlying DOS code crashed, you got a BSOD. This happened on a regular basis, so I had to fix this crap on a regular basis. I also took it apart years back too. This all happened 16 years as of the initial wring, and now at least 20. Once it gets that far, it's no longer a hobby. It's a career.
For your first question, I make the tutorials here I do for a few reasons
+
For your first question, the answer is actually very simple. It's because of the difficulty of finding service material. If I have my camera handy I may make a guide but at the same time, it has to make sense. I have a policy of 2007 and up being considered for guides only, since I consider this reasonable. I don't think it's really worth making a guide for a 2002 Dell, for example. It's going to get little to no use because after 10+ years that thing is going to be treated as eWaste.
+
Could I do it? Absolutely, and I have before in the past but these days I stick to 2007+ for guides, since these are almost always at least a C2D, which are far more useful today then any Pentium 4.
-
For starters, it's hard to find good service material for some of the hardware I use, and when I go ahead and upgrade it,I usually see it as a good chance to upgrade it and make a guide for others to do the same
+
Back when I wrote this, I was really only taking in small jobs on occasion, and this didn't happen a lot. These days, I can get them with little trouble and if I want an old system because it's going to be eWasted, it's almost always mine even without asking. This is because of my data destruction policies. My policies are HIPAA/privacy law cases get the drive back(this is a liability protection for both parties, and to help them stay in compliance. As soon as the drive leaves the door, it's a breach.), business cases are in multiple classes(they can ask for the drive at any level, too.) and home users have the choice entirely. These policies played a major role in making it easy to get good jobs.
-
Nobody else is making service manuals for the stuff I have made it for in the past, and some people can vouch for this too-whywould anyone make a CPU replacement guide for a 10 year old Dell?
+
While I am all about keeping old machines out of the landfill, I only really do that with C2D machines these days. I don't think it really makes sense to fix Pentium 4 machines when I can get C2D equipment. I'll fix it if I have a use case that needs it or it's more ideal(i.e. XP machines) but for the most part I will only fix C2D and up, and I will still use a 1st gen Core i series machine. I have just had too many problems with the older Dell machines to justify continuing to repair them. I have used CRT's with these, too but once again I don't keep any CRT. I stick to Trinitron rebadges and good ones like the Compaq Business ones if it's not based on a Sony CRT.
-
The feedback I get from doing IT is always pretty good-and as a result of my feedback and strong computer experience, I actually get small jobs in my school helping others do something with computers, sometimes I even get to open their machines up and fix them-these little jobs vary, and I'm self taught too, which would make it harder to get some jobs, but has worked to my benefit
-
-
It's all about keeping this older hardware that is still useful out of the landfill, especially if you can fix it easily and find a use
-
-
For example, my backup PC is not great(and from 2002), but it's a reliable computer
-
-
it has a 2.6 Celeron processor, 40GB HDD, 512MB RAM and WiFi card
-
-
It's a Dell 4500S if anyone is curious what kind
-
-
It's not powerful, but can get the job done in a pinch if I needed to do something quickly-I even use a CRT monitor with this Dell 4500S
-
-
If anyone is wondering when I got into computers, I got into it at 6 taking apart my old Dell Dimension XPS 5150 if I remember the model right-16 years later, it's no longer avoidable-it's a career
+
This all more or less happened, because of all the problems I had with a Dimension XPS 5150 with Win98 FE back in the day, since Win 9x was known to be very, very unstable because of 16/32-bit code. If the 16-bit code or underlying DOS code crashed, you got a BSOD. This happened on a regular basis, so I had to fix this crap on a regular basis. I also took it apart years back too. This all happened 16 years as of the initial wring, and now at least 20. Once it gets that far, it's no longer a hobby. It's a career.
For your first question, I make the tutorials here I do for a few reasons
For starters, it's hard to find good service material for some of the hardware I use, and when I go ahead and upgrade it, I usually see it as a good chance to upgrade it and make a guide for others to do the same
Nobody else is making service manuals for the stuff I have made it for in the past, and some people can vouch for this too-why would anyone make a CPU replacement guide for a 10 year old Dell?
The feedback I get from doing IT is always pretty good-and as a result of my feedback and strong computer experience, I actually get small jobs in my school helping others do something with computers, sometimes I even get to open their machines up and fix them-these little jobs vary, and I'm self taught too, which would make it harder to get some jobs, but has worked to my benefit
It's all about keeping this older hardware that is still useful out of the landfill, especially if you can fix it easily and find a use
For example, my backup PC is not great(and from 2002), but it's a reliable computer
it has a 2.6 Celeron processor, 40GB HDD, 512MB RAM and WiFi card
It's a Dell 4500S if anyone is curious what kind
It's not powerful, but can get the job done in a pinch if I needed to do something quickly-I even use a CRT monitor with this Dell 4500S
+
+
If anyone is wondering when I got into computers, I got into it at 6 taking apart my old Dell Dimension XPS 5150 if I remember the model right-16 years later, it's no longer avoidable-it's a career
For your first question, I make the tutorials here I do for a few reasons
For starters, it's hard to find good service material for some of the hardware I use, and when I go ahead and upgrade it, I usually see it as a good chance to upgrade it and make a guide for others to do the same
-
Nobody else is making service manuals for the stuff I have made it for in the past, and some people can vouch for this too
+
Nobody else is making service manuals for the stuff I have made it for in the past, and some people can vouch for this too-why would anyone make a CPU replacement guide for a 10 year old Dell?
The feedback I get from doing IT is always pretty good-and as a result of my feedback and strong computer experience, I actually get small jobs in my school helping others do something with computers, sometimes I even get to open their machines up and fix them-these little jobs vary, and I'm self taught too, which would make it harder to get some jobs, but has worked to my benefit
It's all about keeping this older hardware that is still useful out of the landfill, especially if you can fix it easily and find a use
For example, my backup PC is not great(and from 2002), but it's a reliable computer
it has a 2.6 Celeron processor, 40GB HDD, 512MB RAM and WiFi card
It's a Dell 4500S if anyone is curious what kind
It's not powerful, but can get the job done in a pinch if I needed to do something quickly-I even use a CRT monitor with this Dell 4500S
For your first question, I make the tutorials here I do for a few reasons
-
For starters, it's hard to find good service material for some of the hardware I use, and when I go ahead and upgrade it, I usually see it as a good chance to upgrade it
-
-
I also do it to show other people how to replace the CPU in a older Dell from 2002, and also help them know just how far you can upgrade the parts too
+
For starters, it's hard to find good service material for some of the hardware I use, and when I go ahead and upgrade it, I usually see it as a good chance to upgrade it and make a guide for others to do the same
Nobody else is making service manuals for the stuff I have made it for in the past, and some people can vouch for this too
The feedback I get from doing IT is always pretty good-and as a result of my feedback and strong computer experience, I actually get small jobs in my school helping others do something with computers, sometimes I even get to open their machines up and fix them-these little jobs vary, and I'm self taught too, which would make it harder to get some jobs, but has worked to my benefit
It's all about keeping this older hardware that is still useful out of the landfill, especially if you can fix it easily and find a use
For example, my backup PC is not great(and from 2002), but it's a reliable computer
it has a 2.6 Celeron processor, 40GB HDD, 512MB RAM and WiFi card
It's a Dell 4500S if anyone is curious what kind
It's not powerful, but can get the job done in a pinch if I needed to do something quickly-I even use a CRT monitor with this Dell 4500S
For your first question, I make the tutorials here I do for a few reasons
For starters, it's hard to find good service material for some of the hardware I use, and when I go ahead and upgrade it, I usually see it as a good chance to upgrade it
I also do it to show other people how to replace the CPU in a older Dell from 2002, and also help them know just how far you can upgrade the parts too
Nobody else is making service manuals for the stuff I have made it for in the past, and some people can vouch for this too
-
The feedback I get from doing IT is always pretty good-and as a result of my feedback and strong computer experience, I actually get small jobs in my school helping others do something with computers, sometimes I even get to open their machines up and fix them-these little jobs vary, and I'm self taught too
+
The feedback I get from doing IT is always pretty good-and as a result of my feedback and strong computer experience, I actually get small jobs in my school helping others do something with computers, sometimes I even get to open their machines up and fix them-these little jobs vary, and I'm self taught too, which would make it harder to get some jobs, but has worked to my benefit
It's all about keeping this older hardware that is still useful out of the landfill, especially if you can fix it easily and find a use
For example, my backup PC is not great(and from 2002), but it's a reliable computer
it has a 2.6 Celeron processor, 40GB HDD, 512MB RAM and WiFi card
It's a Dell 4500S if anyone is curious what kind
It's not powerful, but can get the job done in a pinch if I needed to do something quickly-I even use a CRT monitor with this Dell 4500S
For your first question, I make the tutorials here I do for a few reasons
For starters, it's hard to find good service material for some of the hardware I use, and when I go ahead and upgrade it, I usually see it as a good chance to upgrade it
I also do it to show other people how to replace the CPU in a older Dell from 2002, and also help them know just how far you can upgrade the parts too
Nobody else is making service manuals for the stuff I have made it for in the past, and some people can vouch for this too
-
The feedback I get from doing IT is always pretty good-and as a result of my feedback and strong computer experience, I actually get small jobs in my school helping others do something with computers, sometimes I even get to open their machines up and fix them-these little jobs vary
+
The feedback I get from doing IT is always pretty good-and as a result of my feedback and strong computer experience, I actually get small jobs in my school helping others do something with computers, sometimes I even get to open their machines up and fix them-these little jobs vary, and I'm self taught too
It's all about keeping this older hardware that is still useful out of the landfill, especially if you can fix it easily and find a use
For example, my backup PC is not great(and from 2002), but it's a reliable computer
it has a 2.6 Celeron processor, 40GB HDD, 512MB RAM and WiFi card
It's a Dell 4500S if anyone is curious what kind
It's not powerful, but can get the job done in a pinch if I needed to do something quickly-I even use a CRT monitor with this Dell 4500S
For your first question, I make the tutorials here I do for a few reasons
For starters, it's hard to find good service material for some of the hardware I use, and when I go ahead and upgrade it, I usually see it as a good chance to upgrade it
I also do it to show other people how to replace the CPU in a older Dell from 2002, and also help them know just how far you can upgrade the parts too
Nobody else is making service manuals for the stuff I have made it for in the past, and some people can vouch for this too
The feedback I get from doing IT is always pretty good-and as a result of my feedback and strong computer experience, I actually get small jobs in my school helping others do something with computers, sometimes I even get to open their machines up and fix them-these little jobs vary
It's all about keeping this older hardware that is still useful out of the landfill, especially if you can fix it easily and find a use
For example, my backup PC is not great(and from 2002), but it's a reliable computer
it has a 2.6 Celeron processor, 40GB HDD, 512MB RAM and WiFi card
It's a Dell 4500S if anyone is curious what kind
It's not powerful, but can get the job done in a pinch if I needed to do something quickly-I even use a CRT monitor with this Dell 4500S
