Alanoll

i believe for INSTALLDIR to work correctly, it must be used by calling msiexec.exe /i winamp5.msi INSTALLDIR="PATH" /qb the INI won't work the way you have it (INSTALLDIR variable) simply because I didn't add functionality to it. I only added functionality for the switches I added. in my tests I always use msiexec.exe /i to start the MSI.....so....yeah. It's the proper way anyway. as for the CDDB issue, haven't had time this week to do much of anything with the MSI. switching to a new computer, and school is starting up (first couple weeks is supposed be pretty hectic). I'll see about getting to it this weekend.

wow.... someone just doesn't search..... http://flyakite.msfnhosting.com/ I've posted this before, and a guide on how to edit findcd.exe to look for a different file as well.....

http://greenmachine.msfnhosting.com/READING/addraid.htm

yes

my guess would be your paths are wrong in your RunOnceEX file. you start.cmd file has %systemdrive%\install\applications, where as %systemdrive%\install , so I would take a gander that you have your stuff in $OEM$\$1\Install\application

search for a key TaskbarXP in the registry. Export it after configuring your taskbar, and add it to your cmdlines.txt reg file.

SEARCH!! My giddy aunt. How could you NOT have found this? http://unattended.msfn.org/xp/applications/msjava.htm DVD Decrypter uses /S, seeing as it's a NSIS installer.

PowerDVD uses an InstallShield method. Start the setup.exe with -r on a computer, and it should ask for a serial during install. After installing, copy setup.iss to your powerdvd setup folder from C:\Windows You didn't even try with this one.... the original Winamp installer is a NSIS installer, so if you want EVERYTHING use /S. Otherwise, find the threads on selectable components using a javascript file, or the MSI file I created. In both threads there are instructions on what to do. should be a capital S. /S Alcohol 120% is in the massive switches thread. You need to search. It works, you just need to do what they said. Trillian can just be copied I think, but a search couldn't help. Daemon tools needs to be extracted (copy the setup file once starting the setup, search the switches thread). A really GOOD search will provide you with answers.

technically, the poster should NOT have posted the same thing again, if you want to get anal about it. But if you go through the forum, you'll find MANY threads that are the SAME thing over and over again, simply because people don't search (like the poster you linked to, both the winnt.sif issue and the OEMPreInstall=YES workaround ahve been posted about in previous threads discussing the subject). When I see such topics, if neither has been replied to, I either delete them, or I merge them. You'll find the latter solution to the afformentioned thread. If you wish, you can just send me a PM anytime you see this happen (with links preferably) and I'll get around to fixing it.

You could make a shortcut creator utility? (useful for people who put applications in $Progs and need their shortcuts in $Docs) isn't there already a utility somewhere attached to a thread, that can create shortcuts?

Purpose of a Volume License is for Companies to by XP in bulk and then not have to call Microsoft for EVERY copy installed. Why would a company want home? Professional alone sounds better to them even if they don't know the features.

Post edited, and tags added for formatting.

you could setup a seperate 4-5 gig partition on you harddrive and have VMware access it directy. THen you can modify anything you want considering the files. As for tips.... to speed up, if you allocate the entire disc space when creating the hdd image, it will speed up a big.

It is if Microsoft forces it down people's throats with Windows. Every hear of a monopoly? lol

and perhaps it's because the WPI thread states to post all problems in THAT thread, not seperate. It's no wonder you didn't get an answer No double posting

you could have used the wrong file format when creating the ISO. Normal ISO-9660 will turn the $OEM$ into _OEM_

Oh, I know you can. I purposely subscribed so I know what people post It's just alittle advice to actually check more often, as 3443 is alot of emails to go through I've also got some rules going to sort the MSFN stuff in outlook. Takes forever using Yahoo though.

I translated that from my INF where i can use variables. I don't know if you can in a normal regsitry key.

use InstallRite

start /wait "%systemdrive%\install\Applications\K-Lite Mega Codec\klmcodec101.exe" /Silent start /wait "%systemdrive%\install\Applications\Window Washer\windowwasher5setup.exe" /S should really and truly be start "" /wait "%systemdrive%\install\Applications\K-Lite Mega Codec\klmcodec101.exe" /Silent start "" /wait "%systemdrive%\install\Applications\Window Washer\windowwasher5setup.exe" /S Start makes the first quotes it encounters the title of the window.

1. You're the only one I see doing it. 2. It makes you looks either impatient or arrogant depending on how you look at it. 3. Bumping is not neccesary while it's STILL on the same page. Your post wasn't even 1 DAY OLD. Obviously, I'm not the only one who notices all your bumps.

The ONLY issues so far reported to have a problem with the original TCPIP.SYS are the ones that use the loopback addresses. There aren't many, and this patch is NOT intended for everyone. Blindly installing a patch you don't need is just plain stupid. However, thanks enuffsaid for patching the file if anyone needs it. I would still direct people to the other patched TCPIP.SYS if you do NOT have the loopback problems.

what did I tell you about bumping your won post?

Just a little tip for all of you.... be sure to check your email account you use for MSFN more then once a month Or don't post so much..... I sincerely regret not checking. 3443 messages in the box, all from MSFN. lol. No wonder I miss a few posts

add /log:#systemdrive#\xplode.log to the command call. Try again, and then post what's in xplode.log