upgrade processor/memory -> problems

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

On my CUSL@-C board (running win2K) I removed the socket
370 Piii/866 and 2x256 PC100 ram and replaced it with a
PIII/1000 and 2x256 PC133 RAM.

When I powered up I

- changed the BIOS settings (jumperless) to the new
processor speed,
- noted that the faster memory was recognized
- noted that the display settings seem to have changed
(i.e. screen font sizes and such that one sets in the
display properties) perhaps back to deafult values as they
are much smaller (I use 1600x1200)
- was disappointed to see certain utilities fail to start
(e.g. zone alarm and other startup apps) and eventually
the machine rebooted on its own after almost making it
through the complete bootup (it rebooted as it was
starting up the startup apps).

Has anyone an idea as to why all should not work fine
after simply upgrading processor and memory?

If there is a better forum for the question, please
suggest it.

Thanks
 
As my system is working like a dream at present, I am reluctant to do a
repair unless I have an idea in advance why the upgrade didn't work as done
and what the repair will do. I moved back to the previous h/w and presently
everything is fine.

Are you able to provide more info on why the upgrade wouldn't simply work,
Bob?
 
It seems that Win2K "remembers" or optimizes itself for the hardware. I
suspect it's a timing issue as sometimes a memory "upgrade" will work
and sometimes it will need a "repair". Hence my comment "You "almost"
got away with it"
 
I am not blaming Bob for the following.

The repair didn't work. In fact it made things much worse in that after
reverting to the old h/w, after finding that the 'repair' did not work, my
system was cooked. I have (had) a dual boot (2 separate W2K installations)
setup. Prior to trying a repair I even took an image of my more important
installation with Drive Image. Unfortunately, once I realized the 'repair'
didn't, and restored the image, something was messed up in the assignment of
drive letters to the logical (boot) drives. D was C and C was D. Partition
magic choked with error messages when I tried to flip them. so although I
have the image it appears useless to me. Adding to the fun, the shortcut
properties show the paths as a mix of C and D; i.e. it's a mess.

At present, I am using the other, less vital, installation which does, in
fact, have the correct letters asigned to the logical drives.

Does anyone have an understanding of what's going on and how it can be
fixed?

Ken
 
Sorry to hear that things went to hell in a hand basket. I'm really
puzzled about the repair not working. Is there somewhere you can check
the memory and the CPU seperately? I am wondering if there is actually
something wrong with one of them. Are you mixing the 2 operating systems
and cross installing apps on two partitions to get that mix of C and D
shortcuts?
 
It sounds to me like he did the "Repair" option rather than the "Install,
find existing installation, then repair it" option. i.e.,

http://groups.google.com/groups?q=windows+2000
+memory+upgrade+repair&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=4uHX7.259366%
243d2.12191655%40bgtnsc06-news.ops.worldnet.att.net&rnum=2

or

http://tinyurl.com/oe1d

It's an important detail and not following the instructions described
above can lead to exactly this kind of braiding in links and what-not.
If I were faced with this situation I would cut my losses, get the data I
needed off the drive, save any configuration files for apps, reformat the
disk and reinstall everything again with the new hardware installed.

-Bill Asher

p.s. Ken: at this point things are so hosed up on your system it
probably wouldn't hurt to try the Install/Repair option on the original
partition. Before you do that however, you might also use Google/Groups
to search and see if someone else has figured out a way to solve the
problem.
 
If a system becomes unstable after a memory upgrade, the memory is the
problem.

I don't see how a repair install can possible fix such a problem, it would
only cause more corruption of your OS volume.

| Sorry to hear that things went to hell in a hand basket. I'm really
| puzzled about the repair not working. Is there somewhere you can check
| the memory and the CPU seperately? I am wondering if there is actually
| something wrong with one of them. Are you mixing the 2 operating systems
| and cross installing apps on two partitions to get that mix of C and D
| shortcuts?
|
| Unc Unc wrote:
|
| > I am not blaming Bob for the following.
| >
| > The repair didn't work. In fact it made things much worse in that after
| > reverting to the old h/w, after finding that the 'repair' did not work, my
| > system was cooked. I have (had) a dual boot (2 separate W2K installations)
| > setup. Prior to trying a repair I even took an image of my more important
| > installation with Drive Image. Unfortunately, once I realized the 'repair'
| > didn't, and restored the image, something was messed up in the assignment
of
| > drive letters to the logical (boot) drives. D was C and C was D. Partition
| > magic choked with error messages when I tried to flip them. so although I
| > have the image it appears useless to me. Adding to the fun, the shortcut
| > properties show the paths as a mix of C and D; i.e. it's a mess.
| >
 
The BIOS was not the problem on the CUSL2-C. Or, should I say that I had the
current BIOS installed. Anyway I gave up on trying to get the PIII 1G
installed on the ASUS board and just swapped boards, so I now have a QDI
board.

Once on the QDI board, I had additional problems. When I tried to install my
FireGL 8800 video card and Maya was locking up on me, I was looking for
answers. Along that troubleshooting path I downloaded the newer VIA chipset
drivers, installed them and now everything 'appears' to be working fine.

Live, learn and get more gray hairs in the process.
 
Back
Top