thebrian

After removing all internet Explorer related stuff from the winnt.sif, the setup completed successfully with the correct IE7 icon, and the icon functions correctly. I removed: [Branding] BrandIEUsingUnattended=Yes [URL] Search_Page=http://google.com/ [Proxy] Proxy_Enable=0 Use_Same_Proxy=1 [FavoritesEx] Title1="Help Desk.url" URL1="http://help.server.com/" Title2="Web Mail.url" URL2="http://webmail.server.com/" Title3="Intranet.url" URL3="http://int1/" Although I'm guessing I don't really need to remove the favorites because those are just files. It may even be just one of the other 3 things, but they're not that important to me, so I'm not going to worry about researching those on my own. I will probably retry the favorites again though.

Getting rid of the unattended setup fixed it, so it's something with how windows handles the unattended installation, or something with the options in the winnt.sif file. I did have it in the winnt.sif file to set an IE search path and some preset favorites. I'm going to get rid of those and see if it will run unattended.

My comment didn't make it through his "moderation" censorship. Leave him be in his own little world. He is not worth our time. Anyone who can't make their domain work without www in front of it and calls people who know more than him about something ignorant isn't worth the time.

No, I still had the problem with HFSLIP 1.4.5. The only time I didn't was when I wasn't doing an unattended install. Let me try running it without the unattended install and see what happens, although I'm not too sure what unattended would do differently.

Unfortunately, even after adding the MSOOBE patch and getting rid of the stuff in the svcpack folder of the source, I'm still having the problem. Attached is my hfslip.log if you can find anything in it that could be causing the problem.HFSLIP.zip

I was not using the MSOOBE patch, because I didn't want OOB to run, but I put the patch in there now. Also, I did find the IE patch in my source's svcpack folder, and removed it (cleared out the whole folder). The source I was using was the latest XP downloadable image from MS Volume Licensing. I'm slipstreaming a new image now, and will try installing on MS Virtual PC once it's done, and let you know if that did the trick.

I just started having this problem with the U.S. English XP SP2 slipstreamed, and IE7 (at T-13). I have not found the fix for it yet, but I have found that running the IE7 install again afterwords does fix the IE problem. I was not having this problem before I changed 2 things though: 1)Started using an unattended install through microsoft's setupmgr.exe. 2)Started installing the .NET framework 1.1, 2.0, and J# through 0_dotNET11SP120-VJ1120.exe at T-13 Are you doing either of these or anything similiar Charley? I will experiment with this a bit and let you know if changing the way either of these are done fixes it for me.