Alanoll

oops, i left off the / on the /s

woot. i think you didn't get many hits as some peopel might not have been awake or were going to not be awake yeah commandline support as a side note, Mac, you may want to add an INI file C:\Windows\winamp.ini [WinampReg] NeedReg=0 just those two lines. That will prevent the "registration" page comming up upon first run. Thought you should know. Doesn't work with a normal Winamp install from Nullsoft as it overwrites that file. and your Winamp folder you're creating in the Startmenu has a lowercase 'w'

-R only works for Installshield installers. DeadAIM using the Windows Installer. You are using the correct switches, however whenever you use silent switches the default installation path is used, and in this case it is the JDennis folder. EDIT: try this.... DEADAIM.EXE s /v"INSTALLDIR=%PROGRAMFILES%\AIM /qn" if that doesn't work, try DEADAIM.EXE s /v"INSTALLDIR=[ProgramFilesFolder]\AIM /qn"

but he isn't creating two users, only one. mrpop

Winzip: http://www.msfn.org/board/index.php?showto...12657&hl=winzip Download Accelerator: http://unattended.msfn.org/xp/applications/wise.htm

two things, post in the right forum please. perform a search. i believe atleast the first two have been answered before, I dunno about ICQ

well, i know your autologon regtweak won't work. what you should do on your own, if no one get's here first.... eliminate the possibilities. remove all instances of execution, so remove everything from cmdlines.txt. See if your SVCPACK.INF works. if it does, add a line in cmdlines.txt. Do so untill you find the culprit. If it's somewhere in RunOnce for some god awful reason, comment out each section with REM and do the same process.

you could always try the diskemu part of CDShell. It's included with teh distrobution. just diskemu \win95.img or something. You need the diskemu.csm file in the modules subfolder.

oh i didn't say there was anything wrong with your way. The idea obviously works. but alittle caution is waranted. MSI's are somewhat like ISOs. Modify them directly too much and they end up corrupt.

did you happen to change your boot screen?

i don't think most people who make DVDs use Windows 95 anymore. SO there isn't much need from most of us. It could be that Windows 95 is just too old. Have you tried copying the setup files from Win95 setup dir to a folder on the harddrive, and then starting setup?

i'm not saying that there isn't a valid reason to modify them, but it's just not a good idea to directly modify them. You may change a single setting without knowing and cause the whole thing to not work. That's why microsoft design MST files to be used in conjunction. And they're easy to make and apply. msiexec /i installmsi /t transform.mst

before your reseal the computer, go through the registry and run a search on start.cmd the key isn't getting deleted. Delete the key that contains it, and it should run again. I think it's somewhere in HKLM>Software>Windows>CurrentVersion>Run or some RunOnce or something.

C:\Windows\Cache\Adobe Reader 6.0 you could also go to the unattended website under application switches

gooood

i still say go witht eh commandline option, it's definately easier

as we need is a bootstrap the supports the /settings switch then in the ini you can define properties, like i have already setup. But it's that bootstrap that's a problem. the SDK one is an internet download one and doesn't support it. I'll see if Adobe's does.

Mac, the frontpage links on winamp.com point to 5.0.3a also, i can't find the right bootstrap. So right now, the only way to do it easily is via commandline.

directly modifying your MSI is not always a good idea. That is why there are MST files.

he's describing InstallScript in cunjunction with MSI, as well as using a Custom Action to read the INI file.

i think I've almost got the INI thing figured out. I got a hold of the Windows Installer SDK (it be nice.....) and there is a bootstrap in there. basically it will go like such... SETUP.EXE /settings=setup.ini /QB and then in the ini, it specifies the MSI to use, and then it has the property things like before, but not all on the command line. Just gotta install VS again to compile a few things

5.03 i think he made most of it before 5.03a came out. In anycase, the ONLY file that i found that has changed is winamp.exe and that should be simple to replace. a better question would be whether he used basic or full to make the msi?

hmm... ini would be quite easy with Inno Setup.......like K-Lite uses, but i dunno about MSI. I'll read up on it too, i agree it would be neater then all on the commandline. just browsing alittle, shouldn't be too hard to implement... all we need is a bootstrap setup.exe file to go with the msi.

maybe it's just me...but... as far as I'm aware it's April 1st, so um... I think i'll wait before passing judgement. but then again, if there is going to be a RC2, then why create files to remove stuff from RC1 when you're going to have to redo it for RC2? just WAIT

please remember to post in the right forum.... Application Switches