Jump to content

DizzyDen

Member
 View Profile  See their activity

  • Posts

    11

  • Joined

  • Last visited

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Posts posted by DizzyDen

    Win xp sp3 build 3244

    in Windows XP

    Posted

    [ProductInstall.GlobalRegistryChanges.Install]

    DelReg=Product.Del.Reg

    AddReg=Product.Add.Reg

    which key I have to look permissions?

    now search the same inf file you saw this in for [Product.Del.Reg] and [Product.Add.Reg]

    Those sections will tell you what registery entries are trying to be deleted and added/modified. Make sure you have permissions to those registery keys via regedit.

    0

    $NtUninstall Cleanup

    in Windows XP

    Posted

    To repeat what has been said before, why would you want to use DELTREE which is not included in Windows XP, when you can simply use RD or RMDIR instead, which does the same? :rolleyes:

    The purpose I see in it is that by simply adding a 17kB file to $OEM$\$$\SYSTEM32 the files and folders can be removed by one very fast process.

    DL.'s cmd is very effective, I just think that it is nice to do it with one command that can be completed faster than the first attrib command can be.

    It is truly a matter of preferences.

    I personally don't see the need for any flaming, we're all here to present different ideas to get the job done.

    0

    $NtUninstall Cleanup

    in Windows XP

    Posted · Edited by DizzyDen

    At the risk of being flamed (again) let me state that I still use "Deltree.exe" from Windows ME.

    It's one DOS command that was left out in Windows XP.

    With that command tucked away in my C:\windows\system32 folder, I can run this single command in a batch file to clean up those uninstall files on any computer.

    deltree /y "C:\windows\$Nt*$\"

    There is also a log file for each one of those uninstall files.

    It uses this format, "KB32968.log"

    Just look in your windows folder and you'll find them.

    This line takes care of those too:

    deltree /y "C:\windows\KB*.log"

    I use the deltree.exe from Windows98 still, and have it, along with 3 cmd files tucked in my system32 folder:

    clrups.cmd:

    @echo off
    deltree /Y %systemroot%\$*.* > nul
    deltree /Y %systemroot%\KB*.* > nul

    clrtmp.cmd:

    @echo off
    deltree /Y %temp%\*.* > nul

    and

    clrall.cmd

    @echo off
    deltree /Y %temp%\*.* > nul
    deltree /Y %systemroot%\$*.* > nul
    deltree /Y %systemroot%\KB*.* > nul

    Every Win CD I make have these with use of $OEM and I can choose to clear the temp folders, the updates, or all of them. If you'd prefer to keep the $hf_mig$ folder, simply change the $*.* to $NT*.*

    0

    Simple question - how to copy a file during unattended install

    in Unattended Windows 2000/XP/2003

    Posted · Edited by DizzyDen

    I tried using instructions I found in the .inf collection on here which suggests the commands below :

    In the $OEM$ Folder add (line3) to :

    CMDLINES.TXT

    [Commands]

    "rundll32 advpack.dll,LaunchINFSection nLite.inf,U"

    "rundll32 advpack.dll,LaunchINFSectionEx nLite.inf,U,,4,N"

    "REGEDIT /S XP_CD.REG"

    Create :

    XP_CDREG.TXT

    Windows Registry Editor Version 5.00

    [HKEY_CURRENT_USER\Control Panel\Desktop]

    "WallPaper"="C:\\Windows\\Web\\Wallpaper\\Crystal.jpg"

    [HKEY_CURRENT_USER\Software\Microsoft\Search Assistant]

    "Actor"=""

    "SocialUI"=dword:00000000

    "UsageCount"=dword:00000000

    "UseAdvancedSearchAlways"=dword:00000001

    This doesn't seem to execute though.

    However, if I run it manually it does set things up correctly.

    The filename should be XP_CD.REG... remove the ".txt"

    Something else I found in my reading was to use the command below :

    In WINNT.SIF :

    [GuiRunOnce]

    "%SystemRoot%\System32\nLite.cmd"

    However, after I added this, windows complains that it cannot find nLite.cmd.

    So two questions, how can I execute the registry punch (or set background, etc, during install) and how does Windows know which files to copy during the install (or if I just place a file called nLite.cmd in the I386 folder, does windows just naturally copy *.* from that folder?)

    you can actually run any cmd file you want from that section of winnt.sif, but you have to create the cmd file and tell it what to do. No, windows will not just copy the files, however anything in the $oem$ folders will get copied. With $oem$\$$ being the windows folder.

    0

    What more to remove?

    in nLite

    Posted

    Can you post the list of the removed things?

    If you compare the .jpg with your options, removed is anything listed in your's and not in the .jpg.

    If you remove something, then start nLite again after writing the changes, options that are no longer there are removed from the list.

    0

    What more to remove?

    in nLite

    Posted · Edited by DizzyDen

    You can remove:

    Languages: more of them if you click the + sign, only keep the ones you really need

    Multimedia: DirectX diagnostic tool- not needed for DirectX to function

    Network: NWLINK IPX/SPX/NetBIOS protocol unless your on a newtware network

    Operating System Options: Disk Cleanup and ZIP Folders (if you use another program like winrar, winzip, 7zip)

    Services: Beep Driver, Secondary Login (unless you use fast user switching), TCP/IP NetBIOS helper (very old from win3x days)

    Personally, I'd keep the Command Line Tools, and play with 16 Bit Support. If you find no games that need the 16 bit support during testing, then leave it out.

    Alternatively, copy the command line tools you want to keep to $OEM$\$$\SYSTEM32 folder of your CD from a working system and remove them in nLite. Ping for one is very handy to have for gaming. One way of making sure of 16 bit support, keep an eye on task manager while using your system, look for anything listed under 16 bit subsyste, and for WOW (Windows on Windows).

    0
×
×
  • Create New...