[NoisySniper]

Great program!
Slipstreamed SP3 + hotfixes and all seems fine, but when I run setup and have one (1) mst-file in root, I still get question if I want to run custom install. Please tell me how to use a mst-file in completely silent mode. Have tried some switches but none of them are working....

This post has been edited by NoisySniper: 25 June 2008 - 03:08 PM

[mara-]

NoisySniper, on Jun 25 2008, 10:46 PM, said:

Great program!
Slipstreamed SP3 + hotfixes and all seems fine, but when I run setup and have one (1) mst-file in root, I still get question if I want to run custom install. Please tell me how to use a mst-file in completely silent mode. Have tried some switches but none of them are working....

If you use switches like qb, qn, qf prompt should not appear. I just tested with qb- switch and I did not get a prompt.

Cheers

[Pascal]

the program crashes when i try to slipstream this hotfixes: office2003-KB943985-v2-FullFile-FRA.exe

[mara-]

Pascal, on Jul 4 2008, 04:29 AM, said:

the program crashes when i try to slipstream this hotfixes: office2003-KB943985-v2-FullFile-FRA.exe

Please upload log file for me, located in root folder of tool or in root\log history folder.

Cheers

EDIT: I just tried to slipstream KB943985 to my Office and no crash. I even tested with French KB943985 and not crash (I tried to slipstream into English Office and worked). Until you upload log file I can't help.

This post has been edited by mara-: 04 July 2008 - 05:54 AM

[Pascal]

well i'm sorry i must have made a mistake that caused this error.

not a great first post!

but here's to you for your great program

[dkl42]

Thanks for the nice Tool.

Maybe I've found another problem, where you can help me:

Testcase:
the current drive is c:, the DVD with the created office 2003 version is in drive d:

I try to start the setup with the following commandline: "d:\office2k3\office\setup.exe" TRANSFORMS=InstFull.exe /qb- /noreboot

Your new setup-application will be started, and stoped after some seconds.

If I chnange the current drive to d: before I use the commandline it's works fine.

Maybe you can help me and find a solution to fix the problem. Thanks very much.

This post has been edited by dkl42: 05 July 2008 - 04:55 AM

[mara-]

Pascal, on Jul 4 2008, 10:25 PM, said:

well i'm sorry i must have made a mistake that caused this error.

not a great first post!

but here's to you for your great program

OK, I'm glad that you solved problem.

dkl42, on Jul 5 2008, 12:54 PM, said:

Thanks for the nice Tool.

Maybe I've found another problem, where you can help me:

Testcase:
the current drive is c:, the DVD with the created office 2003 version is in drive d:

I try to start the setup with the following commandline: "d:\office2k3\office\setup.exe" TRANSFORMS=InstFull.exe /qb- /noreboot

Your new setup-application will be started, and stoped after some seconds.

If I chnange the current drive to d: before I use the commandline it's works fine.

Maybe you can help me and find a solution to fix the problem. Thanks very much.

I would help, but it seems that I don't understand this part with with changing drives. Also you commandline is not correct. You can not write InstFull.exe, you need to write InstFull.mst. Maybe this is just a typo in post, but can you give me example of command line that works and that don't works for you. Also, what happens to setup, any error, do you see any windows with progress bar?

Cheers

[dkl42]

You're right, the command line was wrong, but that's doesn't change the problem.

I get an office 2003 version, the service pack and some hotfixes and generate an DVD Image with your office slipstreamer 1.6.2
In the next step I've burned it to an DVD-R.

And now the testcase: I've put this DVD in the DVD drive (drive d: in my virtual PC) and starts a command shell (cmd.exe).

If I use the command shell (or change with c: to the first hard drive) than I get the wrong result.
If I change the current drive ( with the input d: on the DOS prompt) to the DVD than the commandline from my prvious posting works.

It looks for me, that your setup searched the orginal MS Setup-Programm on the current drive. If I don't change the current drive your programm looks at c: where isn't any orginal setup programm. If I chnage to d: before I call your setup, then your setup looks for the orginal on drive d:. And found it.

Can you check the function (inside your setup programm), which builds (or expand) the commandline for the call of the orginal setup programm.
Maybe you forget to forward the drive letter, maybe.

PS: For your information: I work since over 20 years as a system analyst and senior developer with DOS, Unix and some other operatin systems. Pls apologize me if I use the terminology for DOS or win32 developer without to declare them.

[damian666]

hi Mara, i will translate this to dutch for you man

very nice tool man
and in Autoit huh? nice ...

see ya around, i will let you know about the trans man

damian666

[mara-]

dkl42, on Jul 6 2008, 10:06 AM, said:

You're right, the command line was wrong, but that's doesn't change the problem.

I get an office 2003 version, the service pack and some hotfixes and generate an DVD Image with your office slipstreamer 1.6.2
In the next step I've burned it to an DVD-R.

And now the testcase: I've put this DVD in the DVD drive (drive d: in my virtual PC) and starts a command shell (cmd.exe).

If I use the command shell (or change with c: to the first hard drive) than I get the wrong result.
If I change the current drive ( with the input d: on the DOS prompt) to the DVD than the commandline from my prvious posting works.

It looks for me, that your setup searched the orginal MS Setup-Programm on the current drive. If I don't change the current drive your programm looks at c: where isn't any orginal setup programm. If I chnage to d: before I call your setup, then your setup looks for the orginal on drive d:. And found it.

Can you check the function (inside your setup programm), which builds (or expand) the commandline for the call of the orginal setup programm.
Maybe you forget to forward the drive letter, maybe.

PS: For your information: I work since over 20 years as a system analyst and senior developer with DOS, Unix and some other operatin systems. Pls apologize me if I use the terminology for DOS or win32 developer without to declare them.

OK, I think that I understand the problem now. I'll investigate. It was not problem in terminology, I just did not figured situations in which you got errors. And I did not forget to forward the letter, but we'll see.

damian666, on Jul 6 2008, 11:24 AM, said:

hi Mara, i will translate this to dutch for you man

very nice tool man
and in Autoit huh? nice ...

see ya around, i will let you know about the trans man

damian666

Thanks man, yes AutoIt code

Cheers

[xenon2050]

Hey, thanks for this awesome tool... Thought I would try to help out a bit and mention that a new Office 2003 update has been released...
Heres the info:
Update for Microsoft Office Outlook 2003 (KB953432)
http://www.microsoft.com/downloads/details...;DisplayLang=en

And one more...
Update for Microsoft Office Outlook 2003 Junk Email Filter (KB953465)
http://www.microsoft.com/downloads/details...;DisplayLang=en

This post has been edited by xenon2050: 10 July 2008 - 01:15 PM

[mara-]

Thanks for the info, I'm sure that it will be useful for the people, because I'm working very much on new version of Slipstreamer and I don't have time to update the list. Also, I'm going on vacation next week and I'm trying to finish it so I can publish it and that you guys have something to play with.

Cheers

[PDL707]

I found this to be very informative and interesting.

http://blogs.technet...ed_engineering/

[Tolek81]

Language Polish (update to 1.6.2)

Attached File(s)

•  polish.7z (2.16K)
  Number of downloads: 2

[BuonaDomenica]

I'm trying to slipstream Office 2007 Enterprise Edition and SP1 but it seems like nothing ever happens. The log file says files have been copied but the service pack has not been applied. Not sure what's wrong here?

Slipstream Office 2003 with SP3 worked without any problems and the CD works perfectly.

Could anybody give me some insights on how to do it with Office 2007 Enterprise Edition the slipstreaming process. I was able to do it with Expression Web to slipstream SP1 but no luck with Office 2007


thanks
BD

This post has been edited by BuonaDomenica: 15 July 2008 - 12:25 PM

[zdravo]

Thanks for this mara-
I will try this one soon

[mara-]

Tolek81, on Jul 13 2008, 12:17 AM, said:

Language Polish (update to 1.6.2)

Thanks!

BuonaDomenica, on Jul 14 2008, 06:36 PM, said:

I'm trying to slipstream Office 2007 Enterprise Edition and SP1 but it seems like nothing ever happens. The log file says files have been copied but the service pack has not been applied. Not sure what's wrong here?

Slipstream Office 2003 with SP3 worked without any problems and the CD works perfectly.

Could anybody give me some insights on how to do it with Office 2007 Enterprise Edition the slipstreaming process. I was able to do it with Expression Web to slipstream SP1 but no luck with Office 2007


thanks
BD

I'll check it, and see what is going on.

zdravo, on Jul 14 2008, 07:15 PM, said:

Thanks for this mara-
I will try this one soon

You are welcome.

Cheers

[NoisySniper]

First of all; Great Program!
Is there a problem when running this via RunOnceEx? (Strange if it is..) When I run manually it works perfectly, but runnning via RunOnceEx, the setup seems to start and then it just stops....
Command-line: "F:\Install\MSOffice2003\SETUP.exe" /qb-! TRANSFORMS="F:\Install\MSOffice2003\OfficeEN.MST"
I've tried different cmd-line alternatives, except one without specifying transform.

When I ran this earlier with "original" setup all worked well...

Anyone who got it to work,- and how?

[Marsha]

Hello, I'm new to this great tool and can't get it to work. I'm just trying to make a new CD of Office 2003 S&T edition with SP3 slipstreamed.

I'm using version 1.6.2 and copied the contents of my CD to a file and downloaded Office2003SP3-KB923618

I get an error almost immediately in the log that indicates a bad product key - and I've checked it repeatedly (it's also installed on another computer)

The log is:

2008-07-19 20:59:50 : Logging started.
2008-07-19 20:59:50 : -
2008-07-19 21:00:13 : Setup File Description: Microsoft Setup Bootstrapper
2008-07-19 21:00:13 : Location of Setup file: G:\Office2003\SETUP.EXE
2008-07-19 21:00:13 : Product: Microsoft Office Standard Edition 2003 v11.0.5614.0
2008-07-19 21:00:13 : Edition type: Retail/OEM
2008-07-19 21:00:13 : Language: English - United States
2008-07-19 21:00:13 : MSI Files: OWC10.MSI|OWC11.MSI|STD11N.MSI
2008-07-19 21:00:13 : Installation type: Standard
2008-07-19 21:01:58 : Location of service pack: G:\Office Updates\Office2003SP3-KB923618-FullFile-ENU.exe
2008-07-19 21:01:58 : Selected Pack: Office 2003 Service Pack 3 (SP3)
2008-07-19 21:02:01 : Retail/OEM edition detected. Performing necessary steps to enable administrative installation creation...
2008-07-19 21:02:01 : Enabling administrative installation...
2008-07-19 21:02:04 : Finished. Administrative installation is enabled.
2008-07-19 21:02:04 : Creating Administrative install.
2008-07-19 21:02:06 : Error with creating admin install: Probably valid product key is not entered.
2008-07-19 21:02:06 : Directory size:0
2008-07-19 21:02:06 : Creation of administrative installation failed.

Can someone give me some guidance, please.

Marsha

[mara-]

Well, if it reports that wrong cd key is entered than the following could happen:

- You did not enter the correct key (if you have it on computer use copy-paste)
- Enabling admin install failed (even if the program said that it enabled it, in this case try again - by default admin install is not allowed by Microsoft, but tool is removing that limitation)
- You or someone else altered setup.ini located in folder FILES\SETUP and because of that program is detecting your Office as Retail/OEM, and maybe is other edition. Are you sure that displayed edition is correct?

Cheers