PDL707

Member
  • Content count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About PDL707

  1. I did an admin Slipstream of Office 2003 using version 1.7.3. The "update" installation problem is fixed and appears to be perfect. Thanks.
  2. I did an Office 2003 installation with SP3 only (no hot fixes) to see want hot fixes I needed. MS update came back with 15 critical hot fixes. I did an admin Slipstream of Office 2003 using version 1.7.1 with SP3 and the 15 hot fixes. I used the new CD to update the prior office installation. MS Update says I still need the 15 updates. I uninstalled Office and then installed it with the same new CD. MS Update is happy – no updates available. So it appears that the new hot fixes do not get installed, or at least the registry does not get updated, when the slipstreamed CD is used to update a prior Office installation. I did the same thing with Office 2007 Pro Plus SP1 and have the same exact problem. The only difference is that 2007 has 12 hot fixes.
  3. For Office 2003 you need SP3 and the following Hot Fixes for an up to date installation. MS has revised KB948988 since its Aug 12, 2008 release, without changing the file name. KB907417 KB921598 KB943649 KB943973 KB945185 KB945432 KB947355 KB948988 KB950213 KB951548 KB953432 KB954464 KB955434 KB955439
  4. This is the log.log file (renamed) I get with version 1.6.2. After a clean Office 2003 install, MS update says I need to install KB948988. log.txt
  5. The files are in a folder on my hard drive. I had to change the file ext from .log to .txt to up load it. log.txt
  6. With version 1.7 beta 3 and Office 2003, the destination folder Browse Button still stays grayed out. I am doing the exact same thing that worked with version 1.6.2. I go back to version 1.6.2 and it still works.
  7. I am trying to slipstream Office 2003. With version 1.6, after browsing to setup.exe, the Location for the Admin Install Browse Button goes from gray to available. With version 1.7 b2, the destination folder Browse Button just stays grayed out forever making the program unusable.
  8. Attached is the Office2007FileList.txt file for Office Ultimate 2007. Ult_Office2007FileList.txt
  9. Attached is the Office2007FileList.txt file for Office Professional Plus 2007. ProPlus_Office2007FileList.txt
  10. I found this to be very informative and interesting. http://blogs.technet.com/office_sustained_engineering/
  11. After reading the change log, I incorrectly assumed that the Slipstreamer fixed the SemiTrust.dll problem automatically. I see now, after your reply, that it is not automatic but has to be run. I tried again and it does work. Sorry about that.
  12. I slipstreamed Office 2003 Professional Edition (SP3 + 10 HF’s) using version 1.6 final. It works fine except your “Office.Interop.InfoPath.SemiTrust.dll Fix” does not work. The installation fails and it wants a different disk. The only way that I have found to fix this problem is to edit the PRO11.msi file using Orca. This method works. I expected your fix to edit this file, but it does not.
  13. excel2007-kb946974-fullfile-x86-glb.exe office2007-kb946691-fullfile-x86-glb.exe office2007-kb947801-fullfile-x86-glb.exe office2007-kb950378-fullfile-x86-glb.exe office2007-kb951808-fullfile-x86-glb.exe outlook2007-kb946983-fullfile-x86-glb.exe publisher2007-kb950114-fullfile-x86-glb.exe word2007-kb950113-fullfile-x86-glb.exe
  14. Your updates.rar file needs updating for Office 2003 Word: add KB950241; remove KB943983 Publisher: add KB950213; remove KB946254 Junk E-mail Filter: add KB950380; remove KB949044
  15. I am running win XP SP3 RTM and CA Anti-Virus. When I run nLite 1.4.5 beta 2, CA Anti Virus says that file C:\Program Files\nLite\NHELPER.EX_is infected with Win32/Rewas!generic infection. CA then deletes “NHELPER.EX_”. Then nLite will not run because “NHELPER.EX_” is missing. I’ve uninstalled nLite, performed a full computer virus scan, and reinstalled nLite from a fresh down load and I get the same results. Apparently CA recently updated their virus signature to include this virus because I did not have this problem 4 days ago.