Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country


Everything posted by gilles_gros

  1. Hi, If I get it correctly,when OSver = Win8, then getOSver()!="Win8" || getOSver()!="Win8.1" is true, because False or True ==> True I think you need to write getOSver()!="Win8" && getOSver()!="Win8.1" Regards. Gilles
  2. Hello all, For those who might be interested in the solution: cmds[pn]=['{JSCRIPT}=RunCmd(\'"\' + RegKeyValue("HKLM\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Adobe Flash Player ActiveX\\UninstallString")+\'"\'%comma%0%comma%1);']This run the uninstall command stored in the registry. Cheers, Gilles
  3. Hi all, I am trying to run a command that is build on reading the registry thru JSCRIPT I tryed the following with no result cmds[pn]=['{JSCRIPT}=RunCmd(RegKeyValue("HKLM\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Adobe Flash Player ActiveX\\UninstallString") %comma% false %comma% true);']; or even cmds[pn]=['{JSCRIPT}=RunCmd(RegKeyValue("HKLM\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Adobe Flash Player ActiveX\\UninstallString").replace(/\\/gi %comma% "\\\\") %comma% false %comma% true);']; none do work. I know that cmds[pn]=['{JSCRIPT}=alert ("myvalue = " + RegKeyValue("HKLM\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Adobe Flash Player ActiveX\\UninstallString"));']; it shows a message box with the correct value C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_13_0_0_206_ActiveX.exe -maintain activex Please advise on how to get it working. Regards. Gilles
  4. Hi all, After looking into that issue, I came to the conclusion, that I need 2 REGEDIT command patern as on a 64 bit system, such as Windows 7 I need to include registry key either in the standard hive (64 bits) or in the 32 bit hive (Wow6432Node). To achieve that I have created a REGEDIT32 patern to force usage of 32 bits entry on a 64 bit system As I do not use the UI to set my config file I have not looked into the changes that need to be made. In file installer.js add and replace the case REGEDIT statement by case 'REGEDIT32' : if (FileExists(cmd)) { if (cmd.indexOf(" ") != - 1 && cmd.substr(0, 1) != '"') cmd = '"'+cmd+'"'; cmd='"'+sysPath32+'RegEdit" /S ' + cmd; fsoCmd=true; } else cmd = getText(txtErrorRegEditFileExists); break;case 'REGEDIT' : if (FileExists(cmd)) { if (cmd.indexOf(" ") != - 1 && cmd.substr(0, 1) != '"') cmd = '"'+cmd+'"'; if (OSBits==64) cmd='"'+windir+'\\RegEdit" /S ' + cmd; else cmd='"'+sysPath32+'RegEdit" /S ' + cmd; fsoCmd=true; } else cmd = getText(txtErrorRegEditFileExists); breakHope this helps someone. Regards. Gilles
  5. Anyone can help ? Beside creating a REGEDIT32 and REGEDIT64, I do not see a clean solution. Regards Gilles
  6. Hi, I just upgrade to 8.7.2 release. I did not bump into bit64 problem. I mean, I remove all line bit64[pn] form my config.js file. But I ran into a problem with REGEDIT command. Before I was using WPI 8.6.3 my config file was : prog[pn]=['Activer Windows Update'];uid[pn]=['WUx64'];desc[pn]=['Activer les parammétres de WindowsUpdate'];dflt[pn]=['no'];forc[pn]=['no'];bit64[pn]=['yes'];cat[pn]=['Finalisation'];configs[pn]=['Win7,Licence Free'];cmds[pn]=['{REGEDIT} "%wpipath%\\..\\Windows Seven\\Astuces - Windows 7\\Activer WindowsUpdate - Windows Seven.reg"'];cond[pn]=['getOSver()=="Win7" && FileExists("%wpipath%\\..\\Windows Seven\\Astuces - Windows 7\\Activer WindowsUpdate - Windows Seven.reg")'];pn++;it was using as REGEDIT C:\Windows\system32\RegEdt32.exeNow with WPI 8.7.2 it is using C:\Windows\sysWOW64\regedit.exe(I suppose the difference is related to sysPath32 and sysPath64) and unfortunately with my .reg file il does not work. Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]"AUOptions"=dword:00000002"IncludeRecommendedUpdates"=dword:00000001"ElevateNonAdmins"=dword:00000001Thanks for any help provided. Regards, Gilles
  7. Hi all, After posting on wincert a fix for my usage, I propose you the following change. I was willing to use an IF statement as a cmd iun WPI. And it did not work. cmds[pn]=[' "%wpipath%\\PathToExe\\MainExe.exe" /s /v/qn', '{CMD} IF EXIST "%wpipath%\\PathToExe\\ExeFile.exe" start "Title" /WAIT "%wpipath%\\PathToExe\\ExeFile.exe" /s /v/qn']; cond[pn]=['FileExists("%wpipath%\\PathToExe\\MainExe.exe")']; I track done a change in installer.js (on line 1080 WPI 8.6.3) case 'CMD': cmd="CMD /C " + cmd; fsoCmd=true; break; As added by myselfidem, to add the possibility to choose the CMD command in WPI menu, the following changes are needed in configwizard.js on line 363: CommandsMenuBar.addNewChild("cmd_dos2", 11, "dos_cmd", "Cmd", false, "", ""); on line 632: case 'dos_cmd': HandleCommandsSelectionMenu("{CMD} "); break; Regards.
  8. Hi All, Bumping into that problem, I come up with a simple solution. Only in the case of a {X86} or {X64} command, you might have after 1 other command. I did not code the full solution, but a solution that I think fixes most of the cases. Based on that fact, I modified installer.js file initial code : case '{X86}': if (getBits()==64) cmd="SKIP0"; cmd=cmd.replace(/{x86} /gi,''); fsoCmd=false; break; case '{X64}': if (getBits()==32) cmd="SKIP0"; cmd=cmd.replace(/{x64} /gi,''); fsoCmd=false; break; Modified code case '{X86}': if (getBits()==64) cmd="SKIP0"; else { cmd=cmd.replace(/{x86} /gi,''); handleCommand(cmd,item,cmdNum); } fsoCmd=false; break; case '{X64}': if (getBits()==32) cmd="SKIP0"; else { cmd=cmd.replace(/{x64} /gi,''); cmd=handleCommand(cmd,item,cmdNum); } fsoCmd=false; break; Hope this helps some of you. Gilles
  9. Yes, it doesn't solve my problem. In the last_session.ini file a blank line appears each time I mark the remote Assistance. Can anyone confirm if it is a bug, or a problem with my setup. Regards. Gilles
  10. Hi, Using nLite 1.3.5, either French or english language, the tweak "allow receiving Remote Assistance" is not saved in the .ini file It is not applied in the .iso created (as far as I checked). Regards. Gilles
  11. I once had a similar problem. It was related to the computer name that I set thru nLite. It was already used in my network. Hope it will give you an hint. Gilles
  12. Hi, I bumped into a problem an after quite a time spend investigating, I finally got the solution that I want to share. I setup a nLite CD with the following parameters as unattented parameters : ; ; nLite unattended settings ; (don't post it on the net, it's not important for debugging) AdminPassword = "admin" CDKey = "you don't need to know that" ComputerName = INSTALL FullName = "NAME" OrgName = "OrgName" Language = Français (France) Locale = Français (France) Keyboard = Fran‡ais DomainAdmin = DomainPass = JoinDomain = JoinWorkgroup = WORKGROUP Every run fine, until I tested it in VirtualPC. Around T-30 minutes, just after network setup, the Computer reboots, restarting the installation. This is beacuse I do have, on my network, another computer that has the same "ComputerName". Based on that, my advice would be not to set "ComputerName" on an unattented setup. Hope it helps someone. Gilles
  13. Hi, I started playing around with nLite no that long ago. I bumped into the very same problem, and finally fixed it. Your are trying to set up a computer with a "ComputerName" that is already connected on your network. In your unattented parameters unset "ComputerName" Gilles

  • Create New...