OverFlow

Member
  • Content count

    30
  • Joined

  • Last visited

Community Reputation

0 Neutral

About OverFlow

  • Rank
    Contributor
  • Birthday 06/01/1963

Contact Methods

  • Website URL
    http://
  1. does you version of office have infopath included? did you try to redownload the patch?
  2. Bump First post and SlipOff.cmd updated (slipstream Office 2003 command script)
  3. The information is accurate but is is spread out over multiple pages and has confused at least one user. It also doesn't address office sp3 because of its age. Does that count as depreciated?
  4. i condensed this thread here --> http://www.msfn.org/board/Office-Patchers-...oad-t89038.html that might have saved you PS yes it works with SP3 however the infopath fix still needs to be applied.
  5. Based on your very limited info and description i have to make a guess here ("%~dp0") Returns the drive letter that the script is run from so if your script (this line --> "for /f "delims=: tokens=1" %%i in ("%~dp0") do set drive=%%i:") is run from the C drive which apparently it is... then DUH! that script only works if it is run from the drive that WPI resides on my guess is cmdlines.txt is calling a .cmd file on the c drive that contains this line
  6. Thanks for the quick response ! If i find anything myself ill report back.
  7. I have seen a post about this somewhere else but i can't find it now. I am using RyanVM nLite DriverPacks and WPI 6.2 if i deselect office it doesn't give the error
  8. TITU Post 25 in this thread - Monnezza posted that fix last year. As a matter of fact it looks like you cut and pasted it.
  9. Sorry i missed the double post... Ohotfix.exe and freinds are included in every hotfix package, my script deletes them each time a hotfix is extracted so the next package will be able to extract them again and be deleted again. We don't need these files at all, They are just taking up space. What I suspect is happening is that the write caching on your drive is causeing just enough of a delay that the next extraction is still finding the last Ohotfix.exe file that was supposed to be deleted already but is pending deleteion by write caching on the drive. when the next hotfix begins extraction it finds the file and complains. since we are only going to delete this file anyway it not a problem. Some hotfix packages contain more than one installation package so you may get more patches than you downloaded. Check the *.log files to see what was done. (that is why i have it create them) the name and number of logs should match the total installed. I could add a small delay in the script between extractions or a test to make sure it is deleted before continuing. but as far as i know this is the only time it has occured and since we dont need the files its only a nusiance not a problem.
  10. No because they were not "installed" they were part of the original package. think about it... (I Don't create an uninstaller I just add the keys MU is looking for) if it is your intention to split the updaters then don't use Microsoft Updates, use Windows Updates.
  11. It is great to hear that! (I'm quite sure I speak for all of us.)
  12. Full Credit goes to : monnezza's Post here: http://www.msfn.org/board/index.php?s=&amp...st&p=558964 Glad to help
  13. To the best of my knowledge you may only update "administrative installation points" in office 2003 and I belive you must enter a Licence Key to create one. If there is a way to prompt for your key after you have created an administrative install I am unaware of it.
  14. The script will extract all hotfixes and the most recent Service Pack that are in the same folder as SlipOff.cmd. The files will be extracted into the same folder that the patches and the command file are currently in. If service packs exist in the folder it will extract and slipstream the latest Service Pack first then do the remaining hotfixes. Since each Service Pack includes all previous Service Packs only the latest one will be used. Simply put SlipOff.cmd in the folder with the downloaded xxx-FullFile-xxx.exe updates and run it. Only "FullFile" Service Packs and hotfixes will work for slipstreaming! Office 2003 SP3 Administrative update download (Office2003SP3-KB923618-FullFile-ENU.exe) --> http://www.microsoft.com/downloads/details...;DisplayLang=en Other Office downloads here (for getting post SP updates) --> http://office.microsoft.com/en-us/download...033.aspx?stt=11 Optionally run it with an argument specifying your office 2003 administrative installation folder (IE "SlipOff.cmd d:\My Office") The default c:\office will be checked if you don't specify a folder. If your source is not found you will be prompted for the administrative installation folder location. It will also create log files with the same name as the hotfix for trouble-shooting and give an elapsed time. Be sure to read monnezza's Post here: http://www.msfn.org/board/index.php?s=&amp...st&p=558964 After slipstreaming Update for InfoPath 2003 (KB920103) into Office 2003 Professional with SP2 there are two errors in PRO11.MSI. (really nice info and documentation!) The summary of his post is attached below as a text file. Sadly this problem was not fixed in Office Service Pack 3 and must still be done It is still neccessary to create a *.reg file since Microsoft Updates is blind to slipstreamed updates. I install office to a virtual machine, run MS update, and then export the "patches" key to a file named 'Office.reg'. My key is located at. > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Patches] Sample attached Just export the entire Key and then execute the resulting .REG file after installing the slipstreamed office (and before using Microsoft Update). I run the Office.reg file from my office.mst (*.MST's are 'transforms'. Switchless installers created by the using office 2003 resource kit) Hint: Use Microsoft Office update to see if your office is current and if your hotfixes were installed correctly. --> http://office.microsoft.com/en-us/downloads/maincatalog.aspx original post and release Oct 27 2006, 03:51 PM here --> http://www.msfn.org/board/index.php?s=&amp...st&p=578482 Script updated 12/09/07 to support Service Pack 3 It will skip previous Service Packs if they are accidentally put in the folder since only the most recent one is needed. Have a Great Day! --- Jeff --- office.reg InfoPathfix.txt SlipOff.cmd
  15. feel free to look at it and use my source if you like... that is what it's there for. I have had several good experiences with Signet so it could only be better for everyone... My code is a lot more complete and versatile, so run with it if it pleases you. just mention me in the credits ;P Be sure to read monnezza's Post here: http://www.msfn.org/board/index.php?s=&amp...st&p=558964 After slipstreaming Update for InfoPath 2003 (KB920103) into Office 2003 Professional with SP2 there are two errors in PRO11.MSI. (really nice info and documentation!) Sorry TomCat - done --> http://www.msfn.org/board/index.php?s=&amp...st&p=601340