j_stam_84

@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

Indeed there was a slight miscalculation from my side in CollectData.exe Fixed it and updated the link in the first post

@Boooggy (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 ?

Seems nobody is interested.. Never mind, was just an idea

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 !

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 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

@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

Hi Bâshrat, Do you have any documentation/guidelines/flowcharts about how the integration of your driverpacks work ? If you could send this to me or put it on your website, I could find the 'bug' myself. I know you're a busy man This would help you out aswell Grtz!

Hi Bâshrat, Yes I did slipstream the DriverPacks after nLite & RyanVM's UpdatePacks... I tried to slipstream them to a clean UWXPCD (removed RyanVM's UpdatePack) and it still wouldn't work. After a couple of more times trying (different settings, without S2, etc.) I thought I'd give Method 1 a go (which I use up until now) and I didn't get any errors when the driverpacks were slipstreamed. My computer at home is installing right now so when I come home, I can see if it works. So it seems to me that Method 3 is broken ? Do you have ANY idea how this could be ? I sure would like to use Method 3 p.s. If everything worked, the installation will be stopped at the error that states it can't find some files for the ATI Rage driver. I'll post the filenames for you as I promised Edit: Installation finished as I expected it to. The missing files for the Rage Fury pro are: * ativdaxx.ax * ativmvxx.ax I CAN continue the installation of the driver without these files and it seems to work. So maybe a way to ignore the messages would be sufficient ?

Hi Bâshrat The UWXPCD I applied the driverpacks to is an NLite-modified source with SP2 and RyanVM's Windows XP Post-SP2 Update Pack (April 2005 - Dutch version ofcourse ) I read somewhere that the Update Pack from Ryan could have some issues regarding the DriverPacks. Could that be the problem in this case ? Do you want me to post the "lastsession.ini" file (with NLite's options) ? Thanks in advance!

Hi everyone! I'm getting the following errors while using method 3 : _ [M3] DriverPacks slipstreamed... [method 3] _ [M3] necessary files copied... $OEM$\$1\D\G\M\1\Matrox.PowerDesk.PanelDe.resources.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\G\M\1\Matrox.PowerDesk.SetupWizardDe.resources.dll - Het systeem kanhet opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidSvCs.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidSvHu.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidSvPl.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidSvRu.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidWizardCs.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidWizardHu.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidWizardIt.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidWizardPl.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidWizardRu.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvSataConnectionCS.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvSataConnectionHU.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvSataConnectionPL.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvSataConnectionRU.dll - Het systeem kan het opgegeven bestand niet vinden. _ [M3] OemPnPDriversPath added to WINNT.SIF... _ [M3] WINNT.SIF file updated with method 3 entries... $OEM$\$1\D\M\N\NvRaidSvCs.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidSvHu.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidSvPl.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidSvRu.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidWizardCs.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidWizardHu.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidWizardIt.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidWizardPl.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvRaidWizardRu.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvSataConnectionCS.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvSataConnectionHU.dll - Het systeem kan het opgegeven bestand nie vinden. $OEM$\$1\D\M\N\NvSataConnectionPL.dll - Het systeem kan het opgegeven bestand niet vinden. $OEM$\$1\D\M\N\NvSataConnectionRU.dll - Het systeem kan het opgegeven bestand niet vinden. After the batchscript is done, $OEM$\$1\D\G\M\1looks like this : $OEM\1\D\M\N\ Contains some files aswell (sorry.. no filelist.. anybody interested? I'll add it later) and a couple of other files still remain in the root of the disc (batch files etc.). It looks like the cleanup doesn't work like it should. Does anybody have any idea why these files remain behind after the integration of the DriverPacks and why the batchscript generates the above "File not found" errors? Thank you in advance, Greetings, J. Stam @Bâshrat the Sneaky Couple of weeks (?) ago I posted that the drivers for the Matrox MGA-200 were incomplete and I promised you a list of the missing files.. sorry but I haven't been able to make one (my MGA card died ).. I'll try to borrow the hardware from a friend of mine but it could be a couple of days before I get it.. p.s. found out that the ATI Rage driver is incomplete aswell (missing two .ax files).. I can retrieve those filenames easily so that shouldn't take long

Yes I am Problem is, I already installed the driver manually... (other source) So I can't generate a list of the missing files anymore... I'm working on a new Unattended XP DVD and when it's finished, I'll reinstall and make a list for you.. (it's almost ready so I'll probably post it this weekend) Grtz!

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!

Hi all! Apologies in advance if this is the wrong topic The Matrox MGA(-200) driver doesn't work.. Keeps complaining that it's missing a bunch of files (Mostly .sys and .hlp files). I haven't got a list here... if you need it, I'll post it for you.... The rest of the hardware is detected and installed correctly and the batchfile to 'slipstream' the drivers didn't give an error... so I presume an incomplete driver? Thus far I'm VERY impressed with your work!!! Keep it up!!! Regards, Jan Jaap

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.!

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