Slipstreaming Office 2003 Service Pack 1


Recommended Posts

Instead of running setup /a you could copy the cd contents to your hard drive, slipstream the SP and write everything to a new CD-R.

Then I either end up with an error about setup. But I think its coz some files on the CD are hidden.

Going to try again and see what I end up with :rolleyes:

I used the office 2003 resource kit to create a quiet installer that set up all of my options for Office 2003 Professional ( @ work ) This worked great! one of the reasons I love office 2003 is that it will keep the installation source local to the computer, so when the next user logs in, he/she won't have to pull the source cabs across the network... VERY nice....

Service pack one rolls along, so I did the setup.exe /a and did the administrative install point. Now when a user logs on, it begins to search for the install source.... which isn't what I had in mind, since regular users on this network dont have access to the source.....

If anyone could offer a hand of advice!

  • 4 weeks later...
sp1 is only 72.1MB in total :blink:

It's the SP1 version of Office 2003, FrontPage 2003, Visio 2003, Project 2003, and OneNote 2003 all combined into an All in One package. This is why it's so large. It is strange that this one will not fit on a CD, whereas without the service pack it does, but you can still burn it to a DVD.

Yeah, all 4 Service Pack's I would accept adding on about 300MB but 400MB + seems quite worrying...in Slipstreaming it you would expect most files to be slipstreamed unless these are all new files needed for updates. Oh well we are all getting the same size so it doesn't matter...just buy a DVD burner and a few blanks :p

  • 3 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I literally tried to install it on my PC today and it crashed upon every start up. I tried all the tricks, terminate and remove cache, uninstall, reinstall, reboot, install via winget.. in the end I had my call with Brad Wardell on Google Meet. Oh I also tried Teams on the web, and got no video or audio (yes I allowed mic and camera).
    • Microsoft explains how it made Teams so much faster in 2026 by Usama Jawad Microsoft Teams is Redmond's flagship online communication and collaboration tool, primarily used in enterprise, government, and school environments. It regularly receives updates, with Microsoft frequently revealing features currently in development as well, such as Efficiency Mode and a dedicated app for meeting recaps. Now, the company has shed some light on the backend enhancements it has made to its popular software in 2026. During the first half of 2026, switching between chats has become 20% faster on desktop and web, which is especially great for less powerful devices or hardware on weak networks. Microsoft explains that it tracks two types of chat switches. The first is a warm switch, which relates to returning to a recent chat, in which case it is most likely already present in memory and should load extremely fast. The other is a cold switch where a chat that hasn't been opened recently is now opened. Naturally, the second type of chat switch was causing the most notable latency spikes. Microsoft realized that this was happening because of three reasons. First, the query to fetch conversation data was being fired too late. Next, queries were being sent sequentially, increasing the overall round-trip time. Finally, there was no handling of response priority, which meant that non-critical responses would sometimes block the main thread. Microsoft solved all of these problems by firing the data query immediately, bundling queries to be sent together so that they wouldn't create a "waterfall" effect, and enabling faster painting of the frame. As a result, warm and cold switches now have almost the same latency, and the only distinguishable difference between them is due to the data layer response time. Next, Microsoft focused on reducing app hangs and freezes on macOS and iOS by 35%. On macOS, the company has a health monitor thread running in the background that does exactly what it says on the tin. The tech firm built a dedicated StackDecoder tool to analyze health monitor's output at scale. Through this combination, it decided to move several error reporting and monitoring threads either to the background or treated them as an asynchronous call so that they wouldn't block the main thread, causing Teams to freeze. On iOS, the same result was accomplished through optimization of computations, caching, offloading operations from the main thread, refactoring database access behaviors, deferring non-critical tasks, and more. On a related note, it also made people search 25% on iOS by optimizing the query pipeline, and efficient database task queuing and scheduling. However, Microsoft has emphasized that improving Teams' performance is an ongoing endeavor, and that it hopes that these efforts will continue to make the software a reliable partner in online communication scenarios. On a related note, Microsoft recently unveiled some upcoming performance upgrades for OneDrive on macOS too, and you can check those out here.
  • Recent Achievements

    • First Post
      StaticMatrix earned a badge
      First Post
    • Week One Done
      StaticMatrix earned a badge
      Week One Done
    • Rookie
      lamborghiniv10 went up a rank
      Rookie
    • One Month Later
      pinnclepd earned a badge
      One Month Later
    • First Post
      X-No-file earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      520
    2. 2
      PsYcHoKiLLa
      210
    3. 3
      +Edouard
      147
    4. 4
      Steven P.
      96
    5. 5
      ATLien_0
      84
  • Tell a friend

    Love Neowin? Tell a friend!