Hi Mara-

Turkish translation updated for v1.7.2.

You might want to update "Help > Website" to point to version 1.7.2 instead of version 1.62 .

Thanks.



Done for next version. Thanks for pointing out on that.

Cheers

Hello Mara-,

First of all great job you've done here keep it that way.

Here's my problem, I have a Office 2007 enterprise cd and I want to direct slipstream service pack and hotfixes in it. But when I choose the "setup.exe" it changes from direct to admin slipstream with no possibility to choose direct again. I'm using version 1.7.2.

Do you have any idea on what may cause this ?

Thanks.

log file for mara-

Sorry, direct slipstream does not work for Office 2007.

Cheers

Too Bad . Maybe an another version.
Your job makes me save a lot of time. in that I'm thanking you

Cheers ;)

You are welcome. I would also like to find I way to directly slipstream Office 2007, but I still did not find the way.

Cheers ;)

Version 1.7.3 is out.

Cheers

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.

You are welcome. I'm glad that everything works fine now.

Cheers

Has made a translation into Russian. For some reason the program does not understand distrib Office 2003 prof. russian. Gives out the message "File you chose is not Office Setup file." Though about 2007 all it is normal.

Thanks for translation.

Can you open properties of setup.exe and tell me what is written under description and under file version?

Cheers

There are no problems,
the Version of a file: 11.0.5510.0
Description: the Loader (по русски загрузчик)

Having problems with slipstreaming a Office 2003 Small Business Slovenian edition with SP3 Slovenian service pack.

I receive the folowing error:



Log window after the crash looks like this:



and the settings window after the crash like this:



I am only able to select Direct Slipstream. Using v1.7.3 of the program.

I will be glad to help the author with fixing this problem.

Can you just try to load your Office into Slipstreamer, and then upload the log file. It's located in folder where Slipstreamer is installed



Please, upload log file for me.

Cheers

Log file, as you wont

OK, I'll try to add this description, but I does not know will it work, because of encoding. Do you want to test it for me when I add it? I'll PM you with test version if you want.

Cheers

Ok, I will test this version for you.

I am attaching log files from two attempts. Hope they will help you find the problem. Let me know if you need anything else.

OK, thanks. One user is having same problem. I sent him a test version so he can check if problem is solved. I forgot to answer on your second question. You can not use admin slipstream because Retail/OEM editions does not support it, only Enterprise.

Cheers

I am currently at work where I can test the procedure again. If you wish you can send me the test version and I'll run it again with same parameters.

PM sent.

Cheers

Can you make a non installer version?

Second link in first post is Self Extracting Archive, that is non installer version.

Cheers

Hi mara-, bad news,
sorry...

Unlike the previous version, with v1.7.3. there is no way, for me, to complete an unattended setup of Office 2003 Pro.

The installation is interrupted almost at the end, with an error message: "Impossible to complete MS Office setup".... reporting the problem to Microsoft...

In Event Viewer there is an "Event ID: 5000" - Office 11 Setup, containing the following information:

P1 : (90110410-6000-11d38cfe-0150048383c9)
P2 : 11.0.8173.0
P3 : iscachelockedfeaturestates
P4 : 0
P5, 6, 7 : x


Office 2003 setup(0001).txt says:

"Successfully launched MsiExec....
16/09/2008 21.29.11 Chained install return code: 1603
Exit code was an error.
Shutting down chained setup processing.
Error returned from install, removing cache.
Using Office Source Engine at path: W:\FILES\SETUP\OSE.EXE
Successfully started Office Source Engine in stand-alone mode.
Set Verbose logging for subsequent setup.
***** Setup exits
16/09/2008 21.29.11
(return = 1603) "

and Office 2003 setup(0001)_Task.txt:

=== Fine registrazione: 16/09/2008 21.29.11 ===
MSI © (18:8C) [21:29:11:453]: Note: 1: 1708
MSI © (18:8C) [21:29:11:453]: Prodotto: Microsoft Office Professional Edition 2003 -- Impossibile completare l'operazione di installazione.

MSI © (18:8C) [21:29:11:453]: Attempting to delete file I:\Temp\882d64.mst
MSI © (18:8C) [21:29:11:453]: Unable to delete the file. LastError = 32
MSI © (18:8C) [21:29:11:468]: Grabbed execution mutex.
MSI © (18:8C) [21:29:11:468]: Cleaning up uninstalled install packages, if any exist
MSI © (18:8C) [21:29:11:468]: MainEngineThread is returning 1603
=== Verbose logging stopped: 16/09/2008 21.29.11 ===


Ciao

Lions

Does only unattended way does not work, or even normal not work? Anyway, I found some issues before your report, so I think when I fix those issues everything will be fine. If you have time, I'll send you a test version tomorrow so you can try.

Cheers

I have tried only in unattended mode (in v. 1.7.2. was almost perfect....).

Two tests for each version, STD and PRO.
In the first case, with STD version, I had a different fault: in the middle of the setup an error message told me that the installation via "transform.mst" is not supported (strangely, because I had no problems and I have run smoothly from an admin install created with Slipstreamer v1.6.2).

Ok for the test version.

Ciao

Is there a list for Office2k updates? I have SR-1 and would like to know what updates I need, and if I need client or full?

I only see 2k3 list in first post...

OK, I'll PM you today, I still did not finish fixing the bug.

Cheers

It does not work with my copy of office2k, keeps asking for serial when my copy doesn't require one (pre-activated).

Since I don't have any original copy of Office2k, support for it is very low. But I can still try to help you. Where do you get prompt for CD key, from the Slipstreamer, or from Office 2000 setup? If from setup, then you need to enter it, since slipstreaming to Office 2k requires creation of administrative install, before slipstream.

Cheers

Slipstreamer won't continue without one entered, administrative install goes fine. Although maybe you could add an option for an already created one, which I did...

I can't make it optionally when I can't detect if your install is already administrative. I already mentioned that I don't have that edition. Now, I'm not sure that I understand about this cd key problem. When Slipstreamer ask for it, after creating admin install, or before?

Cheers

Don't want to interfere but since I tested both I only want to say.......keep up the pace with
further developing mara-. You are doing a great job.

Thanks for the support schakan. I really appreciate it. Thanks to Nexus_06, too.

Cheers

Is the list of updates current (i.e. up to date) as I have collected over recent months all these Office 2003 updates that WU tells me are needed. All POST SP3

KB943983
KB943985-v2
KB945432
KB946254
KB947355
KB947944
KB949044
KB950213
KB950241
KB950380
KB951476
KB953465
KB956077
KB953404
KB954478

Always useful to know what the current list is when rebuilding an image for backup

Some of the above are redundant.. didnt notice the MANY Outlook Junkmail Filter patches

My list in first post is not up to date. I was busy with fixing really annoying bug with Direct Slipstream, and it seems that I finally fixed it. As soon as I publish next version of Office Slipstreamer, I'll update the list.

Cheers

Off-topic posts removed.

Version 1.7.4 is out. This will be last release from me. From now I'll be working with Siginet and benners so we can make one, the best tool. Even if I work with them, you can always ask anything related to Office Slipsteamer. Also, I think I'll continue to do releases of new tool on MSFN forum and we'll provide support for it.

Cheers

Thanks for bug fixes mara-.

I look forward to the work on the combined efforts tool. Saves me a lot of scripting hassle.

I performed the following test cross:

1) - Office Integrator 1.0 build65> Integration with CAB RVMI 1.5.3> verification of MU no upgrade required.

2) - Office Integrator 1.0 build65> Integration with CAB nLite 1.4.9.1> verification of MU no upgrade required.

3) - Slipstreamer 1.7.4> Integration with CAB nLite 1.4.9.1> verification of MU requires all updates to Office 2003 post SP3

4) - Slipstreamer 1.7.4> Integration with CAB RVMI 1.5.3> verification of MU requires all updates to Office 2003 post SP3


May have mistaken the integration?

This is the screen with the log




With the release I had not had previous problem, I repeated the test twice with the same result.

I do not understand where mistake



Thank you

You did not do anything wrong. I never tried this as an addon, so I don't know will it works. As normal install everything will work fine. You can only check if .reg file is present in your addon. It should be located in folder FILES\SETUP.

Cheers

Hallo All!!

Little problem with version 1.7.4

slisptreaming office 2003 professional italian with sp3 and all patch, all good.

Installing the file FILE\SETUP\pro11.reg is not imported in registry
on windows xp no messages are shown during installation but patches are not found.
on windows 2000 sp4 during installation an error ocourse


Please help!
Click to view attachment

Click to view attachment

If I understood this good, everything is fine on Windows XP, right? Problem is with Windows 2000? Well, that could be because of command for importing the registry file. Does Windows 2000 support command regedit.exe /s ? If not that's why this problem exist.

Cheers

Thank you for prompt reply, Regedit /s works also for win2k.
.reg file is not added also for windows xp the only difference is that xp don't throw the error.
Bye

That's strange. I did not experience that problem. Anyway, you should use Office Integrator from here since I work with other members on it now, and I'm not working on Slipstreamer anymore.

Cheers ;)

Office Integratore WORKS!! Very Good Job!

Is it possible to shrink this as we used to do with office shrinker?
Thanks

The reason your .reg file doesn't work is it is probably made from xp , and is unicode. (Windows Registry Editor v5.00)

make a new .reg file with notepad, copy all the registry keys with cut/paste into the new file, and put at the top REGEDIT4.

make sure you save it as ANSI.

It should work then.