Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | XP SP2 Installation Problems |
|---|---|
| Date: | Thu, 12 Aug 2004 19:33:18 -0400 |
Here is the resubmission as requested: Hello, I've done three installs of Windows XP SP2 now and have run across two problems. 1) NMAP 3.55 with WinPCap 3.1 beta 3 stopped working after the upgrade even after the firewall is disabled. I'm not overly shocked here, but I thought I'd mention it. 2) The VS.NET 2003 Pro installer fails when installing the prereq "MS FrontPage 2000 Web Extensions Client" on a freshly imaged machine with SP2. I believe that my trouble was caused by the fact that I elected not to install IIS on the machine. My typical install process is to skip the IIS step while installing the prereqs. The install then proceeds to succeed for everything but the Frontpage 2000 Web Client Extensions. <Error from the event log:> Product: Microsoft FrontPage Client - English -- Error 1933.The Windows Installer service cannot update one or more protected Windows files. SFP Error: 21. List of protected files:\r\nc:\program files\common files\microsoft shared\web server extensions\40\bin\fpencode.dll c:\program files\common files\microsoft shared\web server extensions\40\bin\fp4awel.dll To get around this problem, I ended up having to copy the extracted SP2 Frontpage extensions over manually as outlined in this KB: http://support.microsoft.com/default.aspx?scid=kb;EN-US;811122 After the files were in place, I was able to re-run the VS.NET installer and successfully get past the Pre-Requisites Install Step for the FrontPage web extensions. IMO: A simple fix might be for Microsoft to release an updated version of the weccom.msi which is the installer for the FrontPage extensions. This way an Admin could just update their VS.NET install point and hopefully avoid this problem. Sincerely, Mark Reis Computer Network Engineer UVa Computer Science Department ----- NTBugtraq Editor's Note: Want to reply to the person who sent this message? This list is configured such that just hitting reply is going to result in the message coming to the list, not to the individual who sent the message. This was done to help reduce the number of Out of Office messages posters received. So if you want to send a reply just to the poster, you'll have to copy their email address out of the message and place it in your TO: field. -----
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XP SP2 - Statement of the NTBugtraq list, Nick FitzGerald |
|---|---|
| Next by Date: | Re: XP SP2 nmap incompatibility, Nick Johannes |
| Previous by Thread: | MyDoom/Zindos removal tool offered erroneously via AutomaticUpdates?, Glenn Turner |
| Next by Thread: | XP SP2 via BitTorrent, Russ |
| Indexes: | [Date] [Thread] [Top] [All Lists] |