Jump to content

Office 2000/XP/2003 Slipstreamer Version 1.4 Final


mara-

Recommended Posts

@mara-

I have been attempting to use your Slipstreamer and am consistently getting the following error: "Version you selected is not supported"

The page 1 info does not clearly state any Office version limitations (or I missed it) so I have assumed (perhaps dangerously) this would permit slipstreaming SP3 into and earlier retail source version.

I have tried with Office 2003 Pro and Office 2003 Std and gotten the same error when clicking the "Create Admin Install" button - I know that Microsoft only supports Admin installs from the Enterprise edition...so, I was assuming that your slipstreamer was working around that limitation...hence, the value of your tool.

Does your Slipstreamer function only for the Enterprise Edition? If so then that explains the error message. If it works with Pro, Std, and other SKUs then I am at a complete loss as to how to use it. I would have thought that copying the entire CD to disk and selecting the setup file from that would have been the meaning of the first data box but, I must be too stupid to figure it out..... :blink:

Thanks in advance for any guidance :hello:

Edited by galileo
Link to comment
Share on other sites


It very strange why you are getting that message. I implement that message only for versions which are not supported. Can you please make a screen shot of your Office files located on the CD? Also, run slipstreamer and select setup.exe from CD and then make a screen shot of Office Slipstreamer.

I definite need to make a log function for this things.

Cheers ;)

Link to comment
Share on other sites

@mara-

Thanks for replying. I had tried running the slipstreamer using the CD as the source also...and had gotten the same error. I have done it again per your request and attached the screenshots.

Thanks again for any help.

post-61268-1200578614_thumb.png

post-61268-1200578639_thumb.png

Link to comment
Share on other sites

I checked on Microsoft web, and I'm sorry but you can not create administrative install. I'm using switch /a to create install. You can try manually this, and if it work I'll add support, but I doubt it will. Click Start- Run and type this:

r:\setup.exe /a

If you know for some workaround to overcome this, I'll be glad to hear it.

@mikesw

I'll see what can I do.

Cheers ;)

Link to comment
Share on other sites

@mara-

Hmmm....I thought that was the case.

Just a suggestion for you: Please add in very clear terms and very obvious text in your original (first page) post that your slipstreamer ONLY works with the Enterprise Edition (i.e. Volume License) version since that is the only version that supports running an Admin Install. Currently, there is nothing in your explanations that clearly indicates that other versions (i.e. retail versions) do not work. I noted in my original post that I had tried both the Pro and Std versions of O2K3 and that those did not work...which was a hint that the Enterprise Edition was probably all that was supported. MS literature notes that Admin installs are supported only on the Enterprise version.

However...there is a technique which requires using "Orca" to edit the PRO11N.msi, or STD11N.msi, or other the relevant .msi to change certain switches such that admin installs can be performed. There are also some other techniques for slipstreaming SPs and hotfixes - you can find them here on MSFN. But, all of these are somewhat "messy" and require manual extractions and/or individual integrations. If you read through the forum posts you may be able to find a methodology to employ in your slipstreamer.

For now apparently, the slipstreamer is only useful to those folks who have the Volume License Enterprise Edition.

Thanks for replying to my posts. :hello:

Link to comment
Share on other sites

File is uploaded in first post. Note that updated file is for new version which I'll publish soon, although it still can be used with old one, but "Extra" part will be still in English.

Cheers ;)

Link to comment
Share on other sites

  • 2 weeks later...

Hi,

I've used version 1.4 Beta1 and I was not able to integrate more than 1 update. First Update was integrated without problems, but next one failed. I found out, that the temp folder (C:\Users\USERNAME\AppData\Local\Temp\officeupdates) was unreadable. I was not able to see the security settings of this folder and I was not able to change the permissions.

Only solution is to close your tool after every update and restart it and select the next update. But this is annoying.

Second thing is, that the QFE Updates from MS have different names, so they are hidden inside the OpenFileDialog. You also should add this name schema: office2003-KBXXXXXX-GLB.exe

Could you please fix this?

Link to comment
Share on other sites

Hi,

Can you tell me which Office did you used? Pro or Standard? And does Slipstreamer give any error when reach to second update?

And I'll fix that for Updates.

Cheers ;)

Edited by mara-
Link to comment
Share on other sites

OK, I done some test and I can't reproduce what's happening to you. I'm in progress of making new version, and I done some changes, also there is an log function now which can help me to see what is going on. New version is not yet ready for publishing, but if you agree, I can PM you with new version so you can test it and you can send me a log.

Cheers ;)

Edited by mara-
Link to comment
Share on other sites

Then how is detected? Can you give more details what is happening? Please take a screen shot of Office Slipstreamer when you load your office and a screen shot of root folder of your 2 CD's and post it here so I can see what is wrong.

Cheers ;)

Link to comment
Share on other sites

Then how is detected? Can you give more details what is happening? Please take a screen shot of Office Slipstreamer when you load your office and a screen shot of root folder of your 2 CD's and post it here so I can see what is wrong.

Cheers ;)

screens

0802010813472217194.jpg

0802010814352217205.jpg

it's same CD I use to instal office 2003 in all pc and it work fine...

I try too with cd image and daemon tool and that's not work too....

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...