Alanoll

ok...... now that you've told us what you did (sort of), what and where is the error?

out of curiousity.....you're not assuming the disc is busted just because teh resolution isn't changing in VMware are you?

so what you're saying is that I'm right in the WU doesn't properly detect the install, and WFP doesn't see them as valid? There already is a excellent pack for hotfixes by RyanVM. nLite also automates the process (for post-sp2 hotfixes). Also... How is that the best option? I take it you're meaning to replace the files in the SP2 network install, then integrate the files? SP2 integrate SHOULD detect the improper files and error out (CRC checking) and if it doesn't, you're back to the problem you currently have. WU doesn't detect the install, and WFP doesn't see them as valid.

nice!

http://www.msfn.org/board/index.php?showto...ched+Program%22 http://www.msfn.org/board/index.php?showto...5&hl=play+music One of those should get you started. Both of which brought up with a search @alkmie Read his second paragraph

indeed. If she is one of those people that clutter their desktop, put the file in %systemroot%\system32 or somethign where she wouldn't go. Then it'd just be as simple as either using the Task Scheduler, or adding a rightclick entry to My Computer, that then executes the CMD file

funilly enough....it's the EXACT same process Well, it's slightly different as kick starting the install process is different, but as for what to use...it's the same. 1. Batch Script 2. RunOnceEX from CD (you'll need the rundll32 command to prevent a reboot) 3. WPI 4. WIHU 5. XPLODE All will suit your needs. Just choose what you like. (I suggest Batch Script till your get the hang of the switches). If you want the CD to autoinstall the programs upon insertion [Autorun] open=batch.cmd With batch.cmd being your batch code, or if you use any others, replace batch.cmd with the proper line.

you have STILL failed to prove you have searched for what you're looking for.... However, bare in mind that some of those won't have switches. You'll also have to cross check with the different TYPES of installers listed on the site.

wow, I thought I still had 8 stars....never noticed the 9th getting added Moving to general discussion

you should have those files on your ORIGINAL XP CD. If you don't have one, get one.

Now let's go through and see what's wrong with this pack.... A. CAT files are not installed and as such WFP will not recognize them B. Registry entries not added where neccesary. WU will still show them.

makecab is how you repack them, but you'll need to generate a listing of all the files to included.

Posting Tips When making a post, there are a number of things to remember. Don't use all Capital letters Don't demand an answer Be polite NO WAREZ! If you were to use all Capital letters, it'd be considered shouting and as such turn AWAY many of the people that would be able to help you. Being polite and not demanding an answer really do go together. If you're polite and wait patiently for someone to answer you will get an answer. If however you demand an answer or repeatedly post in your thread to get people's attention, you will most likely NEVER recieve your answer. Above ALL else, NO WAREZ!. It's Rule #1 of this forum, and is grounds for an immediate and PERMANENT BAN from this forum. So don't do it. Now on to the topic of titles. Please use a descriptive title instead of "I need help" or "Please Help me!" The below is a list of titles to avoid using: Where as Is EXTREMELY helpful for others to know whether or not they'll be able to help. It's sorta of like advertising. You want to get others attentions by using a BRIEF description of your problem. Be aware that there is a limit to the topic title length, so BRIEF is a key.

Some are. Not many.

Indeed... Because then no installers will have to be executed to apply the hotfixes, they become part of the regular installation! but doesn't using the /integrate also add entries to SVCPACK.INF so that the hotfix runs during setup and applies the registry entries. The /integrate jsut updates the source files as well incase a file gets deleted and is restored from CD. Fastest is probally RyanVM's driver pack as no EXE is ever executed at all.

if it's called Owner, I'd assume he's using XP Home.

by using the OEMPnPDriversPath, which you have done. Just ignore the box in VMware. If you have your drivers set to install for a real system,you won't get the box.

http://unattended.msfn.org/advanced/cosmetics/logon.htm

why did you not post in it's threaD?

I have no idea of the problem. you keep getting a reboot box right? from WHERE? how did you apply the hotfixes? When does the box appear? DETAILS

http://unattended.msfn.org/advanced/cosmetics/bootscreen.htm

in nLite its located under Services

@bmn and kelsenellenelvian That SAME program relates to KERNEL BOOT SCREENS. This is the SETUP BILLBOARD section, meaning the screens you see DURING SETUP. I knew there was a reason I requested the forum title change from "Setup Bootscreen" to "Setup BIllboard"

seems so, unless you can get the sysoc.inf to run another inf which in turn executes the msn messenger's MSI with switches. And all 3 files need to be copied over during setup (through txtsetup.sif). now THAT part is easy. I was working with RyanVM awhile to find a way to get a few batch files to be executed from an INF. MSI isn't any different.

Option A - Import a registry tweak at CMDLINES.TXT with the tweak to disable the service (look in the registry tweak thread or BlackViper's site) Option B - Once finding the registry entry, open up the hive***.inf files in your I386 directory and then change the proper entry to disable it from the start. Problem with Option B, is that Setup might reset it during setup. Problem with Option A is that it might be active untill the end of setup (not sure on this one)