Jump to content

Peregrine7

Member
  • Posts

    5
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Peregrine7

  1. Thanks. I'm familiar with the idea, though I haven't done it frequently. I'll give it a shot!
  2. *shrug* I did, and it was. (I have since uninstalled XPize, as I was getting no benefit from it.) I take it, then, that there are no known issues with XPize 4.6 final and Windows Server 2003 SP2? If so, I will consider my experience to be user error and give it another try.
  3. I have installed SP2 on my Windows Server 2003 (x32) system, and it killed the XPize themes. I uninstalled and reinstalled XPIze 4.6 final, and still no go. Help!
  4. Well, it didn't work. No errors on the install, but no MSOCache either. [Edit] Ok. After some research, I get it. You can't get the MSOCache from an administrative install point, because the admin install decompresses the CAB files on the CD, and those CAB files are what gets copied to the MSOCache. So you are left with using the method in this thread: http://www.msfn.org/board/index.php?showtopic=51225 to slipstream SP and updates and get the MSOCache. Oh, well.
  5. The problem with the administrative install is that you need to add MSINODISABLEMEDIA=1 to your command line when setting up the administrative install point, like so: y:\setup.exe /a MSINODISABLEMEDIA=1 http://office.microsoft.com/en-us/assistan...1401931033.aspx After that, add ENFORCECACHE to setup.ini as per Microsoft. However, there is still a problem. The setup looks for PRO11.XML to know what files to copy to the local installation source. It looks for the file in \files\setup in your administrative install point, and that file does not normally exist in an admin install point from what I've seen. I'm going to try copying PRO11.XML from the original CD to \files\setup and see if that works. I haven't tried that methond, but looking it over, it creates the appropriate *.xml files. However, you need to use CDIMAGE with the -o switch to get an AIO Office 2003 CD, as that switch causes CDIMAGE to make a single copy of duplicate files and save pointers to those files elsewhere, the idea being that, in an AIO Office 2003 install, there are many duplicated files across the various CDs, and the -o switch will reduce the resulting image down to less than 700 MB. At least, that's the claim; like I said, i haven't tried it myself.
×
×
  • Create New...