Can't Run W2KSP4_EN.EXE (prog. too big)

  • Thread starter Thread starter Hughy
  • Start date Start date
H

Hughy

I downloaded the 130 MByte network version rather than run the express
install. Currently running SP2 (on a P3-500MHz), with several security
patches (inc. blaster) previously installed.

When I try to run W2KSP4_EN.EXE, a dos window appears momentarily with
the message "Program too big to fit in memory". Machine has 256 MBytes
RAM, with much of that being allocated to caching according to monitors.

I've spent hours unsuccessfully trying to figure out what I'm doing
wrong. A 2nd PC (home network), also acts the same way.

Regards,
HM
 
Hello Hughy,

Copy MSConfig.exe from Windows XP to Windows 2000 and run it, use
Diagnostic Startup then click Ok. This will give you a "Clean Boot". Now
try to install SP4. If the installation of SP4 is successful then go back
into MSConfig and set it back to Normal Startup and click Ok and you should
be up and running.

Robert S Ross, 2000 MCSA/MCSE
Windows 9x/NT/2000/XP/2003 Server Group

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi Robert,

I'll give it a try. Thanks for taking the time to help me out, I
appreciate it.

Regards,
Hughy.
--
I can be found at airways underscore electronics at bigpond d_o_t c_o_m.


"Robert Ross [MSFT]" said:
Hello Hughy,

Copy MSConfig.exe from Windows XP to Windows 2000 and run it, use
Diagnostic Startup then click Ok. This will give you a "Clean Boot". Now
try to install SP4. If the installation of SP4 is successful then go back
into MSConfig and set it back to Normal Startup and click Ok and you should
be up and running.

Robert S Ross, 2000 MCSA/MCSE
Windows 9x/NT/2000/XP/2003 Server Group

This posting is provided "AS IS" with no warranties, and confers no
rights.
 
"Robert Ross [MSFT]" said:
Hello Hughy,

Copy MSConfig.exe from Windows XP to Windows 2000 and run it, use
Diagnostic Startup then click Ok. This will give you a "Clean Boot".Now
try to install SP4. If the installation of SP4 is successful then go back
into MSConfig and set it back to Normal Startup and click Ok and you should
be up and running.

Robert S Ross, 2000 MCSA/MCSE
Windows 9x/NT/2000/XP/2003 Server Group

This posting is provided "AS IS" with no warranties, and confers no
rights.


Hi Robert,

Thanks again for previous response.

Procedure carried out as advised, executed MSConfig.exe (borrowed from
XP) and selected diagnostic mode startup. Rebooted.

W2KSP4_EN.EXE still wouldn't execute, message still the same (Program too
big to fit in memory). The message doesn't actually display long
enough to be read - so I redirect the O/P of the command to a filename.

Whilst still running in diagnostic mode, executed SysInformation from
Norton Utilities, this reported around 38 MBytes of memory being used
(approx 15%). Again executed MSConfig, normal boot selected, rebooted
and back to normal.

It seems extraordinary that I have a second machine (P4 - 1.9 GHz) with
512 MBytes RAM (a video editor) that also responds with "program too big
to fit in memory", but I didn't try the MSConfig solution on it when the
first machine didn't respond.

Are there any alternate procedures? (I searched the MS knowledgebase,
nothing obvious, but perhaps I didn't construct the best search phrase).

Regards,
Hughy.
 
"Robert Ross [MSFT]" said:
Hello Hughy,

Copy MSConfig.exe from Windows XP to Windows 2000 and run it, use
Diagnostic Startup then click Ok. This will give you a "Clean
Boot".
Now
try to install SP4. If the installation of SP4 is successful then go back
into MSConfig and set it back to Normal Startup and click Ok and you should
be up and running.

Robert S Ross, 2000 MCSA/MCSE
Windows 9x/NT/2000/XP/2003 Server Group

This posting is provided "AS IS" with no warranties, and confers no
rights.


Hi Robert,

Thanks again for previous response.

Procedure carried out as advised, executed MSConfig.exe (borrowed from
XP) and selected diagnostic mode startup. Rebooted.

W2KSP4_EN.EXE still wouldn't execute, message still the same (Program too
big to fit in memory). The message doesn't actually display long
enough to be read - so I redirect the O/P of the command to a filename.

Whilst still running in diagnostic mode, executed SysInformation from
Norton Utilities, this reported around 38 MBytes of memory being used
(approx 15%). Again executed MSConfig, normal boot selected, rebooted
and back to normal.

It seems extraordinary that I have a second machine (P4 - 1.9 GHz) with
512 MBytes RAM (a video editor) that also responds with "program too big
to fit in memory", but I didn't try the MSConfig solution on it when the
first machine didn't respond.

Are there any alternate procedures? (I searched the MS knowledgebase,
nothing obvious, but perhaps I didn't construct the best search phrase).

Regards,
Hughy.
 
Back
Top