[New office shrinkage tool "StripOffice"]

@Swampy

I'm sorry.. there seems to be a bug somewhere in the app.... I'll try to fix it this week..but since I'm very busy (preparing for school which starts in september.)

I'm thinking about just posting the sourcecode so you and/or other people can adjust StripOffice to your/their liking........

Regards

[New office shrinkage tool "StripOffice"]

Indeed there was a slight miscalculation from my side in CollectData.exe

Fixed it and updated the link in the first post

[New office shrinkage tool "StripOffice"]

@Boooggy

I'll add a binary (see this topic)which generates a log when running ShrinkOffice.

(You have to run it simultaneously with "setup TRANSFORMS=yourmst.mst /qb" <-- no "-" at the end!).If anybody is interested, download it and post the results (or problems ) here.

(And look at Swampy's posts)

@Swampy

What do you mean "Nothing seems to happen" ?

CollectData.exe only does what it's filename implies... it's not the tool itself (I'll post it later.) To prevent mass-flame-problem posting, I'd like the contents of the log from CollectData so I can see if I'm right.

About the log you posted:

Looks VERY promising..... but I only see the logmessage for the main setup window. Did you close CollectData before it was finished ? (or just maybe I posted the wrong binary I'll double-check that when I get home.. and if it's the wrong version, I'll update it ) If the full logfile contains the correct data StripOffice needs, I'll post StripOffice.exe and you can try it!

p.s. can you make a screenshot of the setup window and the error message (from the Office setup) if it doesn't work again??

p.s2. Maybe you can attach "Detect.log" (instead of posting it's contents) for space-saving purposes in this topic ?

[New office shrinkage tool "StripOffice"]

Seems nobody is interested..

Never mind, was just an idea

[buckeyeXP's Office Shrink Techniques?]

I believe this to be possible for sure!

Actually, I'm working on it right now.

The problem with ShrinkOffice is that it retrieves the handle for the window(s) based on the title and a piece of the text in the window ('cause the window titles are the same.. ). This approach has a couple of disadvantages :

- You need to define the window titles which differs per Office version

so when you want to support every setup, you'll need to manually add support

for it

- It's bound to Office and Office alone

This is actually but a guess... Since the sourcecode isn't available (well... I couldn't find it anyway), there's no way to tell for sure... But if you're familiar with AutoIT

you'll agree with me.

The version I'm working on, written from scratch ofcourse, takes different approach to retrieve those handles and thus avoiding the problem with

the difference in Office versions and languages...

It already works for Office XP Professional (Dutch) and it'll soon be tested on Office 2K3 Professional (Dutch aswell)... But since I don't have more Office versions I'll add a binary (see this topic)which generates a log when running ShrinkOffice.

(You have to run it simultaneously with "setup TRANSFORMS=yourmst.mst /qb" <-- no "-" at the end!).If anybody is interested, download it and post the results (or problems ) here.

That way I can check if I'm right and if it'll work on every setup. I *think*

that it won't work for Pre-2K versions (if they can be installed in the same way first of all) but you're welcome to try .

If that's the case, I'll finish the script and try to add support for a Universal Shrinkage Tool.

Heck, if anybody is interested in helping out, I'll even post the sourcecode in a couple of days/weeks so anybody can contribute !

[New office shrinkage tool "StripOffice"]

Hi everybody!

From this topic I understand that BuckEyeXP is no longer around (or just won't reply in the section for ShrinkOffice???).

Since ShrinkOffice didn't work well for my Office XP Professional setup I decided to take matters into my own hands and rebuild ShrinkOffice from scratch. It works like a charm for my setup and I since I created it with a slightly different approach, I believe it should work for every Office version and most languages around (>2K) and could be easily "ported" to work with programs that have similair installers.

My post in the other topic

I believe this to be possible for sure!

Actually, I'm working on it right now.

The problem with ShrinkOffice is that it retrieves the handle for the window(s) based on the title and a piece of the text in the window ('cause the window titles are the same..  ). This approach has a couple of disadvantages :

- You need to define the window titles which differs per Office version

  so when you want to support every setup, you'll need to manually add support

  for it

- It's bound to Office and Office alone

This is actually but a guess... Since the sourcecode isn't available (well... I couldn't find it anyway), there's no way to tell for sure... But if you're familiar with AutoIT

you'll agree with me.

The version I'm working on, written from scratch ofcourse, takes different approach to retrieve those handles and thus avoiding the problem with

the difference in Office versions and languages...

It already works for Office XP Professional (Dutch) and it'll soon be tested on Office 2K3 Professional (Dutch aswell)... But since I don't have more Office versions I'll add a binary (see this topic)which generates a log when running ShrinkOffice.

(You have to run it simultaneously with "setup TRANSFORMS=yourmst.mst /qb" <-- no "-" at the end!).If anybody is interested, download it and post the results (or problems ) here.

That way I can check if I'm right and if it'll work on every setup. I *think*

that it won't work for Pre-2K versions (if they can be installed in the same way first of all) but you're welcome to try .

If that's the case, I'll finish the script and try to add support for a Universal Shrinkage Tool.

Heck, if anybody is interested in helping out, I'll even post the sourcecode in a couple of days/weeks so anybody can contribute !

Ps. In NO WAY is this topic a way to offend BuckEye... If he's still actively working on OfficeShrink, I'll just post the sourcecode and be "outta here"

Edit: Download the tool CollectData.exe here

[Office Shrinker [reduce source of o2k3/xp/2k]]

@BuckeyeXP

Hi!!

OfficeShrink is a really cool idea

AutoIT is indeed the perfect tool for this

Just a thought.. why don't you post the sourcecode so we all can post

our modifications. Maybe this would lead to a real "Universal Office Shrinkage Tool"

Tell me what you think!!

grtz!

JJ

[Microsoft Office 2003 Problem]

For everyone having the same problem :

Just check "Disable SFC Protection" in Nlite!

When NLite asks if you want to start the process, click "No".

Then, save your configuration, exit NLite and open the just saved

.ini file.

Under the [Keep] section, add framedyn.dll and srclient.dll.

(When I don't, Windows gives me errors about these files when logging on).

Restart NLite and load configuration. Resume process as normal.

Now, Office installs correctly

greetings!

[Microsoft Office 2003 Problem]

hmm okay... let me get this straight.....

Because NLite edited the source files in the I386 folder, WFP kicks in when checking for the correct

(unedited) files on the DVD ?

I checked the unattended forum as you suggested and found various posts on the subject.

They all state the replacement of SFC_OS.DLL to disable WFP.

If I would do this, the edited files in the I386 folder would be ignored and installation of Office 2003 would proceed as normal?

The odd thing is; you say WFP can't be disabled....... what do you mean by it? According to various posts on this forum, it can (although all of the download links to SFC_OS.DLL don't work anymore..:S)

About your second point; the location of the source files (I386 folder) isn't relevant right? I mean... it seems to me that it doesn't make a difference to change it ... WFP will still not accept those files... Or am I missing something here (which, ofcourse, is very likely )

Thanks for your reply and your help btw.!

[Microsoft Office 2003 Problem]

Hi all!

First of all; great forum!

A couple of days ago I started experimenting with an unattended XP installation DVD.

The thing works like a charm except for one thing; Office XP (2003) installation

Installation comes to Microsoft Office 2003 and when it starts copying files, an error shows.

The error contains the title "Microsoft bestandsbeveiliging" (Fileprotection) and the message states

that the Windows XP installation CD is needed to copy some files. It will only continue when I insert the source CD from which I build the Unattended CD and if I cancel, it will roll back the installation procedure.

I took these steps to create the Installation CD.

1) Used NLite to slipstream SP2 into the installation and strip the installation CD.

2) Edited winnt.sif for automatic partitioning

3) Created RunOnceEx.cmd, $oem$, etc.

4) Used this tutorial to create an unattended installation

5) Added the final setup command to RunOnceEx.cmd

6) Built the CD.

Could it be that NLite stripped the I386 too much and deleted some files that are needed for Microsoft Office XP installation ? Am I missing some post-SP2 (essential) updates ?

I haven't got a clue what it could be. The problem is, I can only guess what it might be; except for the error message, no additional information is supplied.

Can't find anything on the subject. Does anybody have an idea ?

Thanks in advance!

Regards,

Japie