prathapml

Probably because we were a bit off our rockers? (no offense meant, just playing along....)

Please don't say things which could start a flame, or could be dis-respectful to others, no matter what it is that you see as being bad. Thanks

here If that's what you are looking for! The other method is an AIO-tool which some people use - is considered warez, and not an allowed topic of discussion.

LOL, a yes to that, I'd say.And also, Hello ropera! Welcome to the MSFN forums and have a nice time with clean fun.

Top-class one I tell ya. I'm a true guy all right. :lol: Best find in months. Now what was that joke about the guy who has Alzheimer's disease and cancer ?

I have my PCs running on Windows (2k/XP) for days on end, without any problems or memory leakages. You need to check up if there's any beta/pseudo-beta app installed, which is contributing to instability. Okay, nevermind, this thread wasn't about unstable windows.As for the rest of you.... you aren't talking of "weird". I'd call it tragedy. My sympathies are with you. CD-drives these days.... getting too fast to spin discs without breaking, and CD-media getting too low-quality to spin fast without breaking. Personally, I don't remember what it was that was weirdest.... Ah, when Prince 1 (on DOS, yeah LONG time ago) would start acting up. Sometimes it would start up fine, and sometimes not - was such a mystery in those days. Now I know that it was probably shortage of memory that caused it, but there you have it - my weirdest #puter-related thing that happened.

The one about hell was good. I'd like to know about Saturday and Sunday though......

Fantastic. ROFL! Best I've heard in some time.

MCT is true about that. But, for ease of use and a no-bugs-to-fix result, I'd suggest to use the guide located here - http://unattended.msfn.org/xp/office2003_advanced.htm

Wow! Now that's news to me. So it looks like no matter what your CD is, nLite still can do its job of slimming down your XP install. Cool! (remember that the ability to slip-stream an SP into install source is only supplementary, its not the main reason why nLite exists).

Post date is 11th....

Hello JuPy, And welcome to the forums.

Hah! That's nothing. Keep checking back here - by the end of a week, I'm sure you'd see that its going to be a landslide win for XPlode. Many hundreds (don't know about thousands ) use that buddy!

This one's already known (a link to it could be found to it on the frontpage) - since the 10th or so... Anyway.... Thanks for drawing attention to the fact that SP2 for WinXP really is out. And welcome to the MSFN forums.

(belated) Happy Birthday Tristan! Have a nice day.

You have 3 options: 1. Either use the guide here: Official unattended guide That's the best option. But that will modify your install source. If you want to use the same set of files as you've been using all along, see the options below. 2. Specify a property at command-line: You would already be carrying out a command which installs Office XP (thru group policy). Just add this property to the switches: PIDKEY=[string, your key without spaces]For example, you'd get it working by running this command (its all one line): \\network_drive\directoryname\OXP_install_folder\setup.exe /QB PIDKEY=1234512345123451234512345 3. Edit setup.ini (the simplest option) Edit the file "setup.ini" found in Office XP's directory, look in the folder structure "\FILES\SETUP\setup.ini" You will see this section: [Options] ; The option section is used for specifying individual Installer Properties. ;USERNAME=Customer ;COMPANYNAME=my company ;INSTALLLOCATION=C:\Program Files\MyApp OWC10EXISTS=1 Add the PIDKEY to it - that is, after adding it you will see that section is like this: [Options] ; The option section is used for specifying individual Installer Properties. ;USERNAME=Customer ;COMPANYNAME=my company ;INSTALLLOCATION=C:\Program Files\MyApp OWC10EXISTS=1 PIDKEY=1234512345123451234512345 Do post back on how it goes.

That's what you need to do jakdos. I hope it works fine for you now. BTW, it would be nice if registry sections where properly set apart as (CODE) on the boards. Easy on the eyes, and quicker to find what you are looking for. Do it like this: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\O&O\O&O Defrag\6.0\Pro] "User"="InsertName" "Company"="InsertCompanyName" "SerialNo"="InsertSerial" Nicer isn't it ? Thanks for following that guideline.

Exactly.Desist from older boot-screen .EXEs. Make new ones, or use utilities like StyleXP or bootskin to do what you need.

There's more of 'em too waiting to know a solution to this. heh heh.... :hint: :hint:

So you think you are a 1337 person ? (What is leet? - click here) Here's MSFN in your own language: n00bish : http://l33t.0pointer.de/?skill=1&url=http%...%2Fwww.msfn.org m3h : http://l33t.0pointer.de/?skill=2&url=http%...%2Fwww.msfn.org Serious l33t : http://l33t.0pointer.de/?skill=3&url=http%...%2Fwww.msfn.org Deadly l33t : http://l33t.0pointer.de/?skill=4&url=http%...%2Fwww.msfn.org Amazing Sucidial l33t : http://l33t.0pointer.de/?skill=5&url=http%...%2Fwww.msfn.org Instant Death l33t : http://l33t.0pointer.de/?skill=6&url=http%...%2Fwww.msfn.org (there's higher levels for those wanting to - check the links) * Also, if you didnt realize, all the links are "l33t3d" too, LOL You can search any of your favourite websites with this great language that is swelling its number of loyal speakers: http://0pointer.de/lennart/l33t/ If you like it, do come back after seeing the links, and say which level of leet-ness describes you.

The MST has to be in the same folder as the MSI to which it applies. So, your Unattended.MST is to be present in "%systemdrive%\apps\Office2003" directory.

XPlode for me. Why? Looks good (since I use it for XP), easy to set it up, merges into the setup screens, and does all I need. : Yay to wraith. I also use WIHU when dealing with a win2k install. For the same reasons as above. Keep it up Benjamin. It's been ages since I've used a plain .CMD install. I do use batch-files in conjunction with other tools, but not stand-alone (as mentioned in the official guide). Started out with .CMD, but moved on because there were too many negatives.

Or rename to "netfw.cab" and use winrar to extract. It contains a text file called "netfw.inf".

*clicks the link* #sees its a file needing to be downloaded# Oh shucks! Nevermind that. I'll just read the replies and find out what it is all about.

As for that SP2 keys (VLK) blacklist [posted by gabriel above], yes those are the ones. You might also like to know, that there's *NO* PIDs blocked for retail/OEM, so all those people who illegally used generated keys are happy. (bad for MS commercially ) My post above has been edited just now... Also, a note to the ones concerned about legality of this (probably warez???). Since this doesn't exactly discuss cracking... etc. (we've all along been telling you to use only licensed copies of your OS) - it may not come under that classification. @all- And we'd like to keep it that way (i.e., no warez-related posts).