MarcL

It worked. runonce.cmd REG ADD %KEY%\080 /VE /D "Genuine Windows validation Tool" /f REG ADD %KEY%\080 /V 1 /D "%systemdrive%\install\LegitCheckControl\install.bat" /f REG ADD %KEY%\085 /VE /D "Microsoft Update Tool" /f REG ADD %KEY%\085 /V 1 /D "%systemdrive%\install\MUWEB_SITE\install.bat" /f then create $OEM$\$1\install\LegitCheckControl\install.bat COPY /Y %systemdrive%\install\LegitCheckControl\LegitCheckControl.inf %windir%\inf COPY /Y %systemdrive%\install\LegitCheckControl\LegitCheckControl.dll %windir%\system32 REGSVR32 /S LegitCheckControl.dll %systemdrive%\WINDOWS\System32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 %systemdrive%\install\LegitCheckControl\LegitCheckControl.inf and create $OEM$\$1\install\MUWEB_SITE\install.bat COPY /Y %systemdrive%\install\MUWEB_SITE\muweb.inf "%windir%\Downloaded Program Files" COPY /Y %systemdrive%\install\MUWEB_SITE\muweb.dll %windir%\system32 REGSVR32 /S muweb.dll Of course, you need to download the .CAB files and extract the DLL's to the correct locations.

Does anyone have a method to remove the Macromedia FLASH player from XP install Manually? (without using any of the third-party utilities). Thanks.

I can't use any of those tools.. Was looing for a way to do it manualy. Think I may have figured it out. Testing it now, will post if it works.

Anyone have a good method to slipstream the MUWEB and LegitCheckControl software? I see it can be done with the "HFSLIP" tool, and see it is being done there by piggy-backing the SYSOC.inf, but I am looking for a more direct way... Like a command-line that can be added to the last stage. Thanks

FWIW, I documented my changes well enough that I was able to start over with a Dell OEM XP-Pro CD and recreate the unattended install in about an hour. Was not as bad as I thought it was going to be..

So, your saying the only way to "legaly" do it is to start all over again with an OEM disk?! If you are making a statement such that you know how to do it but dont want to tell me, then I assume you are cofident that it is illegal?

Hey, I have spend a good amount of time modifying a legal version of XP-Pro which is the MS Volume License (no activation). However, I have a bunch of machines here that are NOT covered by the volume license, but instead were purchased from Dell with the OEM XP-Pro installed. Some of those machines need to be reinstalled, and I would love to make use of the unattended/slipstreamed/modified XP install I have, but want to keep the OEM license on these machines. I have heard of people converting OEM cd's in to VolLicence CD's (for the purposes of illegal things), but I want to go the other direction in order to stay legal. Can someone tell me what I need to do to make my VolLicence copy of XP-Pro in to an OEM version? Thanks

Anyone?? Anyone?? Beuler?

This seems to work: [COMMANDS] "CMD /C REGEDIT /S %systemdrive%\install\regtwks.reg" "RunOnce.cmd" What is odd, some regtweaks dont "stick". For example, this works fine when I do it from a command prompt.. but from cmdlines.txt, I still get the default "bliss.jpg" wallpaper [HKEY_CURRENT_USER\Control Panel\Desktop] "Wallpaper"="" and this: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "ClassicViewState"=dword:00000000 Is microsoft that set on forcing a default explorer style and wallpaper?!

I had the quotes before, but removed them thinking that ws the problem.. I will replace them. will it know to look in the path C:\install for it? I dont see how!

The following link seems to be broken: http://unattended.msfn.org/xp/hkcu_registry.htm ... and at one point, I thought this was explained pretty well there. But, anyway.. I have the following cmdlines.txt: [COMMANDS] REGEDIT /S %systemdrive%\install\regtwks.reg RunOnce.cmd But my reg tweaks never seem to make it in. If I cut and paste the "REGEDIT" command after the install is done, it works fine... But only for the current user. Why does this reg tweak not run during the install?? the RunOnce stuff does (now, after much time wasted chasing silly mistakes).

Ah! I just looked back at the entire thread and recall that I added "$OEM$" to the [OptionalSrcDirs] of DOSNET.INF in an effort to get the cmdlines.txt to copy. Just removed it, and testing it again now.

At this point, I broke something because the files in $OEM$\$1 and $OEM$\$$ dont copy anymore! I had this problem before: HERE But, moving the $OEM$ folder under i386 fixed the problem. I think I have changed everything back to the way it was before I tried to add the cmdlines.txt feature, but still nothing is copied. After the first reboot, I see the $OEM$ folder under $WIN_NT$.~ls... but it gets lost somewhere along the way. Maybe I will take the advice of seeing it it works from CD.. if it does, I will copy all of the $OEM$ stuff with a BAT file... Not as clean as I would like, but I am running out of options.

I understad what it is supposed to do, it is just not doing it! Burning CD's takes time, and installing of CD is slower than HD. This should be a valid way of doing unattended install.

XPCD\OEM$\ does not seem to copy to anywhere on C:

Bilou_Gateux: That did not work.. It caused the files in $OEM$ to not even be copied to the C Drive. gunsmokingman: Yes, I am using smartdrive, and for my testing I have been using FAT, not NTFS. Further testing shows: If I use winnt32.exe to kick off the install, it WORKS... But, does not work when using winnt.exe from DOS. It is as if the files in the root of $OEM$ are not copied by the DOS portion of the install (before the first reboot).. Maybe I need to modify DOSNET.INF? Or copy the files myself before starting winnt.exe?

gunsmokingman; You keep saying to use winnt32.exe, but I am installing from DOS. I did the following: \xpcd\i386\winnt.exe /u:\xpcd\i386\unattend.txt /t:C: /s:\xpcd\i386 And, it still did NOT run the cmdlines.txt I dont have a winnt.bat, besides.. when would this run? as of now, I still cant get it to work.

Your saying the directory you run winnt.exe (or winnt32.exe) matters?? I see you cmdlines.txt has quotes.. BTW, I got the initial information on this from: Microsoft As you see, they use quotes and the "./" stuff.. Also use "pause" in the example. In my case, it looks like maybe cmdlines.txt is not being copied to the target disk? (rememeber, I am not doing a CD install).

Found it.. ;Display detail on windows explorer [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams] "Settings"=hex:08,00,00,00,04,00,00,00,01,00,00,00,00,77,7e,13,73,35,cf,11,ae,69,08,00,2b,2e,12,62,04,00,00,00, 10,00,00,00,43,00,00,00

NFG.. Did not work again. cmdlines.txt never happens.

OK, trying this: [COMMANDS] CMD /C pause REGEDIT /S %systemdrive%\install\regtwks.reg" RunOnceEx.cmd CMD /C pause Will report back in a few. Thanks!

Um.. ok.. Any idea why cmdlines.txt never runs? Thanks.

NOT using a CD install (for testing), I moved th $OEM$ folder under i386 on the distribution. I kick of the install with: \xpcd\i386\UNATTEND.TXT \xpcd\i386\$oem$\cmdlines.txt As you can see, I put pause in there to see if it was running or not, and it is not. When the install is done, the files which are at the \xpcd\i386\$oem$\ level are NOT on the c drive, but items in $1 and $$ are. I am guessing this is another behavior difference bewteen installing from CD or a distribution? Is there a list of them somewhere? Marc

In those mile long threads about Reg Tweaks, I found some discussion on setting Explorer to show file details, but did not find a souluton that works. Is there one?

For testing, I have been using So, for it to work I need to move the $OEM$ folder under i386? Then, when I burn to CD I copy UNATTENDED.TXT to WINNT.SIF and move $OEM$ back to the root??