Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About yngdiego

  1. Quick Launch Classic 7 Tool 1.0.5

    I only want a script/program to create the quick launch bar on the left, and to do nothing else. No re-sizing icons, changing toolbar properties, etc. I appreciate the author's work, but I think he tried to do too much in one program without giving us any GUI options to chose what we do or do not want done.
  2. I found the issue. When in "audit" mode most of the OOBESystem directives are ignored, including any commands. The solution was to use step 6, AuditUser to add the commands, which are run in audit mode.
  3. I also tried a very simple command like "mkdir c:\test" in the OOBE system, and it does NOT get executed. However, it looks as though when the commands are in the specialize section, they DO get executed.
  4. I'm ripping my hair out trying to get dog gone firstlogoncommands to run during a Windows 7 Enterprise edition autounattend.xml installation in the OOBESystem section. Code excerpt is below: <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <Order>1</Order> <CommandLine>regedit /s c:\windows\setup\scripts\image_registry.reg</CommandLine> <Description>Configures registry settings</Description> <RequiresUserInput>false</RequiresUserInput> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <Order>2</Order> <Description>Image lockdown</Description> <RequiresUserInput>false</RequiresUserInput> <CommandLine>cmd.exe /c powershell.exe "c:\Windows\setup\scripts\image_lockdown.ps1 > c:\Windows\setup\scripts\image_lockdown.log"</CommandLine> </SynchronousCommand> </FirstLogonCommands> No matter what I do, these commands do not run. I've confimed the path to the registry file exists, as that's include in my $OEM$ directory. I can manually run the command after the system installs, and the registry value is changed. The powershell script is not running either, but that could be because the registry mod to set powershell security to remotesigned is not being set because command #1 is broke. Ideas? I've done a ton of research, and everything I've seen shows this should work without flaw. I've spent the better part of an entire day trying various things without any success.
  5. Ask your Seven xml ? here

    I keep getting "windows could not parse or process the unattended answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for the component [Microsoft-Windows-Deployment]. The section is below, and validates perfectly with WAIK 2.0. What's broke? <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunAsynchronous> <RunAsynchronousCommand wcm:action="add"> <Description>Enable Admin</Description> <Order>1</Order> <Path>cmd /c net user administrator /active:yes</Path> </RunAsynchronousCommand> <RunAsynchronousCommand wcm:action="add"> <Order>2</Order> <Description>Update hosts file</Description> <Path>echo crl.microsoft.com >> c:\windows\systerm32\drivers\etc\hosts</Path> </RunAsynchronousCommand> <RunAsynchronousCommand wcm:action="add"> <Order>3</Order> <Path>powershell set-executionpolicy remotesigned</Path> <Description>Config powershell</Description> </RunAsynchronousCommand> <RunAsynchronousCommand wcm:action="add"> <Order>4</Order> <Path>mkdir c:\windows\setup\scripts</Path> <Description>make directory</Description> </RunAsynchronousCommand> <RunAsynchronousCommand wcm:action="add"> <Order>5</Order> <Path>cmd /c reg add "HKLM\System\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f</Path> <Description>Enable remote desktop</Description> </RunAsynchronousCommand> </RunAsynchronous> </component>
  6. Van read this else ware, I tried that with the rt7lite integrated WIM, and it said there are no SP backup files. So I'm assuming either RT7lite didn't integrate it correctly, or automatically removed the backup files. I hope it's the latter and not the former.
  7. What is the command to do a disk cleanup?
  8. The long debate of slipstreaming IE7 and SP3

    Given that WM11 is not in SP3, I can't see how the hotfixes would be included.
  9. XP SP3 Integration broke on Vista x64

  10. nLite Security Advistory

    I just installed the Secunia Personal Software Inspector and it found a problem with a file included with the latest nLite beta. --Technical details Technical details about this installation of 7-Zip 4.x, you can use this information to determine why the Secunia PSI detected the program and the security state of it. Version Detected: Installation Path: c:\Program Files (x86)\nLite\7z.exe The non-vulnerable version is 4.57. Please include the non-vulnerable version in the next release.
  11. Windows Server 2008?

    I work for a Microsoft consulting company, and several of our people are running WS2008 on their laptops because Vista was such a slow, fat, and ugly pig. They are much happier with WS2008 than with Vista. Personally I still run Vista, but may upgrade to server myself.
  12. SP3 How to slipstream IE7 and WMP 11 first and then SP3 ?

    I had a SP2 ISO, added SP3 via slipstream, then IE7 via nlite. All works just fine.
  13. XP SP3 Integration broke on Vista x64

    My main computer is running Windows Vista Ultimate x64. I extracted my XP SP2 integrated ISO image to a folder and installed nLite 1.4.5b2 on my Vista PC. First of all, it seems nLite needs admin rights to run but doesn't trigger UAC, so I have to manually run it as administrator. However, I ran into a major showstopper. After I point nLIte to my XP folder, I get an unhandled exception, and it gets stuck on different files. If I click on Continue it says 'scanning' but never proceeds. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.IO.IOException: The process cannot access the file 'D:\XP\sfc_os.dll' because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) at System.IO.FileInfo.Open(FileMode mode, FileAccess access) at . .(String[] ) at . .() at . .WndProc(Message& ) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- nlite Assembly Version: Win32 Version: CodeBase: file:///C:/Program%20Files%20(x86)/nLite/nLite.exe ---------------------------------------- System Assembly Version: Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/ ---------------------------------------- nLite Assembly Version: Win32 Version: CodeBase: file:///C:/Program%20Files%20(x86)/nLite/nLite.exe ---------------------------------------- System.Windows.Forms Assembly Version: Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/ ---------------------------------------- System.Drawing Assembly Version: Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/ ---------------------------------------- nlgw Assembly Version: Win32 Version: CodeBase: file:///C:/Program%20Files%20(x86)/nLite/nLite.exe ---------------------------------------- MCDBNET2 Assembly Version: Win32 Version: CodeBase: file:///C:/Program%20Files%20(x86)/nLite/MCDBNET2.DLL ---------------------------------------- msvcm80 Assembly Version: 8.0.50727.1434 Win32 Version: 8.00.50727.1434 CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.1434_none_d08b6002442c891f/msvcm80.dll ---------------------------------------- cablib Assembly Version: Win32 Version: 8.1 CodeBase: file:///C:/Program%20Files%20(x86)/nLite/cablib.DLL ---------------------------------------- msvcm90 Assembly Version: 9.0.21022.8 Win32 Version: 9.00.21022.8 CodeBase: file:///C:/Program%20Files%20(x86)/nLite/msvcm90.DLL ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.