Installing 2003 SDK Causes Buffer Overrun

  • Thread starter Thread starter Eric Renken
  • Start date Start date
E

Eric Renken

When I install the 2003 SDK I get a buffer overrun when it is running the
CScript. I am running this on a AMD 64 3400+ with Windows XP SP2. I tried
disabling Data Execution Protection for CScript, but that didn't help. The
error pops up in C++

The CScript window has this text:

Opening file [C:\Program File\Windows CE Tools\wce420\POCKET PC
2003\install_files\Microsoft.PocketPC2003.1.0.Template.xsl]...


Here is the error:
---------------------------
Microsoft Visual C++ Runtime Library
---------------------------
Buffer overrun detected!

Program: C:\WINDOWS\system32\cscript.exe

A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
 
Not sure if this helps but I just discovered that there is something quirky
with the way you disable DEP on Athlon64 systems (I have nForce 250 MSI
board with Athlon 3500+). Apparently (and this is contrary to what KB says)
in order to completely disable DEP (not per process, but altogether) you
need to specify /execute in the boot.ini.
 
Well that didn't fix it.

I don't think this is DEP that is causing the problem. this isn't the
normal DEP error message/dialog that I have seen. The error is coming up
saying C++ runtime error.

--
Eric Renken



Alex Feinman said:
Not sure if this helps but I just discovered that there is something
quirky with the way you disable DEP on Athlon64 systems (I have nForce 250
MSI board with Athlon 3500+). Apparently (and this is contrary to what KB
says) in order to completely disable DEP (not per process, but altogether)
you need to specify /execute in the boot.ini.

--
Alex Feinman
---
Visit http://www.opennetcf.org
Eric Renken said:
When I install the 2003 SDK I get a buffer overrun when it is running the
CScript. I am running this on a AMD 64 3400+ with Windows XP SP2. I
tried disabling Data Execution Protection for CScript, but that didn't
help. The error pops up in C++

The CScript window has this text:

Opening file [C:\Program File\Windows CE Tools\wce420\POCKET PC
2003\install_files\Microsoft.PocketPC2003.1.0.Template.xsl]...


Here is the error:
---------------------------
Microsoft Visual C++ Runtime Library
---------------------------
Buffer overrun detected!

Program: C:\WINDOWS\system32\cscript.exe

A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
Click to expand...
Click to expand...
 
I had the same problem. Latest version of Windows Script (5.6) solved it.

Alexander Aristov

Eric Renken said:
Well that didn't fix it.

I don't think this is DEP that is causing the problem. this isn't the
normal DEP error message/dialog that I have seen. The error is coming up
saying C++ runtime error.

--
Eric Renken



Alex Feinman said:
Not sure if this helps but I just discovered that there is something
quirky with the way you disable DEP on Athlon64 systems (I have nForce
250 MSI board with Athlon 3500+). Apparently (and this is contrary to
what KB says) in order to completely disable DEP (not per process, but
altogether) you need to specify /execute in the boot.ini.

--
Alex Feinman
---
Visit http://www.opennetcf.org
Eric Renken said:
When I install the 2003 SDK I get a buffer overrun when it is running
the CScript. I am running this on a AMD 64 3400+ with Windows XP SP2.
I tried disabling Data Execution Protection for CScript, but that didn't
help. The error pops up in C++

The CScript window has this text:

Opening file [C:\Program File\Windows CE Tools\wce420\POCKET PC
2003\install_files\Microsoft.PocketPC2003.1.0.Template.xsl]...


Here is the error:
---------------------------
Microsoft Visual C++ Runtime Library
---------------------------
Buffer overrun detected!

Program: C:\WINDOWS\system32\cscript.exe

A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top