//"bothan25" wrote:
//
//> i was in the middle of installing a game when it failed and requested i
//> install again. i then went to a blue screen, i believe the error was
//> 0x0000007 or something to that effect. i powered down to reboot, got the
//> normal system beep but got the following error: windows could not start
//> because the folloing file is missing or corrupt
//> \windows\system32\config\system...and to repair by using the windows
setup
//> cd. has this thing just completely crapped out? any solutions? please
advise..
did it tell you which system file was corrupt? . btw, 0x0000007 is USELESS
unless you get the WHOLE message. its telling you that either 1- the
information it was looking for was not at the specified memory address or
2-it tried to write to a reserved or protected address.
(dont worry if that means nothing to you)
did you get this game from the internet? (im not the FBI i dont give a f*k
if you d/led it)
but if you did, do you have DEP? or anti-virus? (dep=data execution
prevention)
this sounds like a buffer/heap overrun. it could just be a poorly (and very
poorly at that) debugged program. if it caused an error that critical (did it
fail to turn off? or did it fail to start windows?).
the reason i ask where you got the file from is:
bufferoverruns can be engineered to cause overruns and change return
addresses to pointers they shouldnt be allowed to access (because while
executing c windows doesnt allocate the size of memory locations when an
array is declared)
array sizes can be exceeded, and non-program memory rewritten to allot for
this data. the problem occurs when the return address of the called algorithm
is changed to a system memory address. thats just where the problems begin.
now imagine, that the author has engineered this overrun to overwrite windows
system areas or the MBR or MTF, and the algorithm that is running is purly
malicuous. for example, a engineered program can alter several single values,
and as a result completely disrupt the operation of the O/S...
the folder you discribe C:\windows\system32\config\systemprofile\
is the INCOMPLETE path of the corrupted file.
without actually being there, or seeing every message you saw it isnt
possible (or timly) to write every single possible solution.
it could just be that the artictecture on your computer is incompatible with
the files (or system files operate differantly then expected) or youve
downloaded a virus
my suggestion: attempt recovery using XP cd
check game manufacturer website
if that doesnt work,
if you have more then one computer, back up personal files (either over
network if possible, or physical removable of hard-drive) followed
by complete reinstallation of windows...
and btw, yes it did crap out on you, and get used to it. it is windows...
