Archived from groups: comp.sys.laptops (More info?)
I know a lot of people do it, but...
1) is it easy?
2) does it invalidate my warranty?
3) what do i need watch-out for when i'm putting in the RAM so that i
don't screw up my notebook.
4) recommend going to a certified technician?
Archived from groups: comp.sys.laptops (More info?)
On 5/9/2005 12:41 PM, BCeizure wrote:
> I know a lot of people do it, but...
>
> 1) is it easy?
> 2) does it invalidate my warranty?
> 3) what do i need watch-out for when i'm putting in the RAM so that i
> don't screw up my notebook.
> 4) recommend going to a certified technician?
>
> The laptop that I have is a IBM T42.
>
Your manual should describe how to update the RAM. Make sure you buy
the right kind (www.crucial.com has a nice model lookup); that's the
hardest part. And it should invalidate the warranty.
Archived from groups: comp.sys.laptops (More info?)
On 5/9/2005 12:41 PM, BCeizure wrote:
> I know a lot of people do it, but...
>
> 1) is it easy?
> 2) does it invalidate my warranty?
> 3) what do i need watch-out for when i'm putting in the RAM so that i
> don't screw up my notebook.
> 4) recommend going to a certified technician?
>
> The laptop that I have is a IBM T42.
>
Your manual should describe how to update the RAM. Make sure you buy
the right kind (www.crucial.com has a nice model lookup); that's the
hardest part. And it should invalidate the warranty.
Did not you mean to say "should not invalidate the warranty" ? As long
as the right type of memory is installed ... And as worst, one can
always put back the originam memory.
Archived from groups: comp.sys.laptops (More info?)
BCeizure wrote:
> I know a lot of people do it, but...
>
> 1) is it easy?
> 2) does it invalidate my warranty?
> 3) what do i need watch-out for when i'm putting in the RAM so that i
> don't screw up my notebook.
> 4) recommend going to a certified technician?
>
> The laptop that I have is a IBM T42.
Archived from groups: comp.sys.laptops (More info?)
On Mon, 09 May 2005 20:33:56 GMT, John Doue <notwobe@yahoo.com> wrote:
>On 5/9/2005 12:41 PM, BCeizure wrote:
>> I know a lot of people do it, but...
>>
>> 1) is it easy?
>> 2) does it invalidate my warranty?
>> 3) what do i need watch-out for when i'm putting in the RAM so that i
>> don't screw up my notebook.
>> 4) recommend going to a certified technician?
>>
>> The laptop that I have is a IBM T42.
>>
>
>Your manual should describe how to update the RAM. Make sure you buy
>the right kind (www.crucial.com has a nice model lookup); that's the
>hardest part. And it should invalidate the warranty.
Did you mean to say should not?
>Did not you mean to say "should not invalidate the warranty" ?
You asking yourself?
>As long
>as the right type of memory is installed ... And as worst, one can
>always put back the originam memory.
Archived from groups: comp.sys.laptops (More info?)
BCeizure wrote:
> I know a lot of people do it, but...
>
> 1) is it easy?
Very. For the memory slot under the computer, one small phillips head
screwdriver and about 30 seconds are all you need. Really very simple.
The slot under the keyboard (which is where the memory that came
installed with your T42 is plugged in) is a little more complicated, but
the manual
(http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-46464
works for me) explains how to do it quite well. About a 5 minute job.
> 2) does it invalidate my warranty?
No.
> 3) what do i need watch-out for when i'm putting in the RAM so that i
> don't screw up my notebook.
When you reboot, either look at the BIOS to tell you how much RAM, or
wait till Windows starts, and run Control Panel -> System to verify the
amount of memory you think you should have. If your machine doesn't
start, then chances are you haven't seated the memory module in its
little plug properly, so redo it. You can't hurt the computer.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.