MSFN Forum: Run once cmds in nlite GUI - MSFN Forum

Jump to content



If you are having issues with Windows after removing components and have come to ask for help, please attach (not paste) your Last Session.ini file to your post to facilitate quicker assistance.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Run once cmds in nlite GUI They don't work; no effects at all Rate Topic: -----

#1 User is offline   hahahafr 

  • Group: Members
  • Posts: 2
  • Joined: 24-June 09

  Posted 10 July 2009 - 02:13 PM

Hi,
I recently created a nlited windows-xp-sp3-fra cd. All the modifications I made are succesfully applied, except the gui run once cmds integrated in nlite.
Here are my cmds :

COPY /Y /V %SOURCE%\PLUS\wpa.dbl %SYSTEMROOT%\system32
regedit /s %SOURCE%\PLUS\scnotificationsfix.reg
regedit /s %SOURCE%\PLUS\ieconnectionsfix.reg
regedit /s %SOURCE%\PLUS\cmdpromptmenufix.reg
%SOURCE%\PLUS\toggleql 1
%SYSTEMDRIVE%\Program Files\Internet Explorer\IEXPLORE.EXE" "http://www.microsoft.com/genuine/validate/?displaylang=fr

Is there something wrong with this cmds ? They don't produce any effect at all on the first login.

This post has been edited by hahahafr: 10 July 2009 - 02:14 PM



#2 User is offline   johnhc 

  • MSFN Junkie
  • PipPipPipPipPipPipPipPipPip
  • Group: Members
  • Posts: 3,246
  • Joined: 02-March 08
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 10 July 2009 - 02:24 PM

hahahafr, the %Source% variable has a trailing backslash (\), so now you have two. %SYSTEMDRIVE% does not have the trailing backslash, so I would have expected the last command to have worked. Oops, just noticed you have screwed up quotes on the last one. If you have more questions/problems, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

#3 User is offline   hahahafr 

  • Group: Members
  • Posts: 2
  • Joined: 24-June 09

Posted 10 July 2009 - 03:23 PM

Yes I just noticed that nlite use the SourcePath String located in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup and this string has a backslash.

The code used in NLITE.CMD :
for /f "tokens=3" %%i IN ('reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup /v "SourcePath" ^| findstr "REG_SZ"') do set SOURCE=%%i

::your commands using %SOURCE%

EXIT


Going to try with the quotemarks and the backslash problems fixed.

This post has been edited by hahahafr: 10 July 2009 - 03:24 PM


Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy