Do what I did. Modify NTOSKRNL.EXE. Copy the file into your exploded service pack.
If applicable, integrate the necessary hotfixes into your service pack. Apply the
"modified" service pack and
reboot.
Now, the file will always be repaired with your modified file. No need to turn off
SFC. Ta da!
______________
Edgar Torres
-----Original Message-----
From: Steve Kelsay [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 12:00 PM
To: NT System Admin Issues
Subject: RE: Repair files location?
Yeah, I was hoping I would not have to do that. I was hoping I could have just let it
repair the new file with another copy of the repair file. All to get our logo on the
boot screen. ARGH!!! Thanks
for the help!
Steve Kelsay
Network Administration Group
South Carolina Department of Revenue
301 Gervais Street
Columbia, SC 29201
(803) 898-5522
>>> [EMAIL PROTECTED] 09/06/01 11:56AM >>>
Sorry, buddy, it's not that simple. You'll have to turn off SFC, which can be done
via the registry. Check http://www.littlewhitedog.com/reviews_other_00021.asp.
______________
Edgar Torres
-----Original Message-----
From: Steve Kelsay [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 11:49 AM
To: NT System Admin Issues
Subject: Repair files location?
Where are the system files stored that are replaced during the repair process?
I need to replace the NTOSKRNL.EXE file after editing the bootup logo bitmap, and
don;t want the original to return. I presume if I replace the repair copy and the
system32 copy, it will be ok?
(Some Managers just think I have all the tie in the world!)
Steve Kelsay
Network Administration Group
South Carolina Department of Revenue
301 Gervais Street
Columbia, SC 29201
(803) 898-5522
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
