Archived from groups: alt.games.half-life.counterstrike (More info?)
I'm having problems installing Counter Strike. My 13-year old bought the
retail product. The CPU pegs at 100% as soon as I hit install.
We've tried to install on three machines. Here's what happens on two
machines:
Machine 1
Gateway P4, XPHome, SP2, 1.6gHz, 80gb, 256mb ram, NEC CD-R, Plextor 716a
DVD -/+ RW
Insert CD in EITHER drive, and it autostarts to the install screen just
fine. When we press install, the drive(s) still spins, but sounds
different. We wait and wait and wait, while the install screen sits on
the screen, and nothing happens, except we hear a spinning drive. A
ctrl-alt-del to Taskmanager shows the drive not responding, and the CPU
at 100%, with explorer.exe as the highest mem usage. If we continue to
wait for about 7 minutes, the game will begin to install, but very, very
slowly. Once installed, we played it for a while, and then it locked. We
uninstalled, and then went to reinstall, but have the same problem...the
CD not responding for about 7 minutes, and eventually installs very
slowly, and then locks during play.
Machine 2
Dell P4, XPHome, SP2, 2.4gHz, 1gb ram, Hitachi CD-R, Plextor 708a DVD -/+
RW
Exact same problem as Machine 1, in EITHER drive
At this point, I took the game CD back to BestBuy got another one.
Perhaps a bad CD. Nope, same problems as above.
Machine 3
We decided to try to install the game on an ancient machine in the
garage. 1997 Local PC shop assembled P1, Win98 FE, 200mHz, 192mb ram,
Toshiba CD-R.
It autoran, and the install screen came up, and when we hit install, it
began to install right away.
I cruised the Counter Strike forums, and googled for clues, but no
mention of this problem.
BTW, Machines 1 and 2 install and play other video games, i.e. Halo 1 and
Doom 3, just fine.
I tried it on two Dell Optiplexes, XP Professional SP1 machines at work,
and the older vintage machine (P3, 600mHz, 256mb ram) CPU got pegged at
100%, but did install after about 10 minutes of waiting, and the newer
machine (P4, 3gHz, 1gb ram) worked fine.
Does this sound like a memory allocation setting problem?
TIA
I'm having problems installing Counter Strike. My 13-year old bought the
retail product. The CPU pegs at 100% as soon as I hit install.
We've tried to install on three machines. Here's what happens on two
machines:
Machine 1
Gateway P4, XPHome, SP2, 1.6gHz, 80gb, 256mb ram, NEC CD-R, Plextor 716a
DVD -/+ RW
Insert CD in EITHER drive, and it autostarts to the install screen just
fine. When we press install, the drive(s) still spins, but sounds
different. We wait and wait and wait, while the install screen sits on
the screen, and nothing happens, except we hear a spinning drive. A
ctrl-alt-del to Taskmanager shows the drive not responding, and the CPU
at 100%, with explorer.exe as the highest mem usage. If we continue to
wait for about 7 minutes, the game will begin to install, but very, very
slowly. Once installed, we played it for a while, and then it locked. We
uninstalled, and then went to reinstall, but have the same problem...the
CD not responding for about 7 minutes, and eventually installs very
slowly, and then locks during play.
Machine 2
Dell P4, XPHome, SP2, 2.4gHz, 1gb ram, Hitachi CD-R, Plextor 708a DVD -/+
RW
Exact same problem as Machine 1, in EITHER drive
At this point, I took the game CD back to BestBuy got another one.
Perhaps a bad CD. Nope, same problems as above.
Machine 3
We decided to try to install the game on an ancient machine in the
garage. 1997 Local PC shop assembled P1, Win98 FE, 200mHz, 192mb ram,
Toshiba CD-R.
It autoran, and the install screen came up, and when we hit install, it
began to install right away.
I cruised the Counter Strike forums, and googled for clues, but no
mention of this problem.
BTW, Machines 1 and 2 install and play other video games, i.e. Halo 1 and
Doom 3, just fine.
I tried it on two Dell Optiplexes, XP Professional SP1 machines at work,
and the older vintage machine (P3, 600mHz, 256mb ram) CPU got pegged at
100%, but did install after about 10 minutes of waiting, and the newer
machine (P4, 3gHz, 1gb ram) worked fine.
Does this sound like a memory allocation setting problem?
TIA