not a techie wrote:
> Thanks Pegasus, but, did you notice my name "not a techie"? Take my what and
> do what with it??
> I take it I have to open up the back of cpu and look for something.

Yes:

> What does it look like

A long narrow circuit board (or two), on the motherboard, with a bunch
of chips lined up.

This is a pic of memory sticks, but not necessarily the type you use,
just the first page I selected:
http://www.crucial.com/store/listmod...SDRAM%2C+PC133

> and can I screw it up??

Yes, so:

- Shut down the computer.
- Turn power strip off, but leave the computer plugged in. If no power
strip, unplug the computer.
- Open the case.
- Don't wear a sweater, don't move around excessively. Touch the case
occasionally.
- Remove the memory stick/s by depressing the two plastic levers at
either end of the stick.
- Press it back in being careful not to bend the stick excessively.

Close the case, plug back in, and try again.

> "Pegasus (MVP)" wrote:
>
>> "not a techie" <notatechie@discussions.microsoft.com> wrote in message
>> news:9817C504-A86A-4C8D-A4EA-104A31190A87@microsoft.com...
>>> Not sure if this is proper to do, but my original question went
>>> unanswered,
>>> then a zillion others appeared, burying mine! I was worried no one would
>>> ever
>>> see it!!
>>> Repeat question....
>>> At first I got this message when I tried to open an email attachment. Now
>>> it's happening when I try to open the net. I have to restart my computer
>>> to
>>> get on the net. Can anyone please help me solve this?? This is the error
>>> message:
>>> The instruction at "0x00f02d22" referenced memory at "0x00f02d22". The
>>> memory could not be "read".
>>> Click on OK to terminate the program.
>>>
>>> Appreciate any and all help!
>>>
>>> Sorry if I breached etiquette here!
>> No breach of etiquette!
>>
>> You might have a flawed memory chip or a marginal
>> contact. Open your PC, then remove your RAM
>> module(s) and put it/them back in again. If the problem
>> persists then you may have to ask your friendly computer
>> dealer to try a new memory module.

--
Joe =o)