-
No. Do you thnk that would be an issue? And how does one upgrade to a newer version of nlite btw?
-
After the initial reboot of the target machine; I receive a dialog box with the message "Windows cannot find the file c:\windows\system32\nlite.cmd" You can search fro the file using Start...." Press OK to continue. This box shows up before RunOnceCmd creator kicks off. I am using nlite versioin 1.35. Up until this build I did not get this error. Sorry aobut my closed mind
-
Am getting cannot find c:\windows\system32\nlite.cmd make sure that you typed the name correctly and then try again.. what gives?
-
-
Thanks NOTS3W (Ray) ! Your answer made my life and now back on track. Learned something new about cab file creation. Dexx, Glad to hear you are back on track too.
-
Dexx, I don't have a definitive answer for you. Look in your source file location under I386 for the file nlite.cm_, apparently this is used to build the nlite.cmd file on build. My problem with my build is that I can't get the runonce items that I put into it, out of it as I moved to RunOnceEx.cmd. I'll keep you posted if I find out anything today, as I will try to remove nlite from the machine and reinstall it. I do know you need nlite.cmd for the installs as I deliberately removed it yesterday to see if I could get around my issues.
-
Can one edit this file? Seems to me that this is where one of my problems lie. On unattended install this file runs on the target machine and bombs as I have removed the runonce items in the unattended install. Also I noticed if I delete nlite.cm_ (by mistake) the program does not regenerate it. Is this normal. How does one regenerate it if possible? Thanks in advance.
-
You're welcome. You may want to invest some time in studying the how to guide on this forum. Also look at the RunOnceEx command stuff.
-
Am using nlite to build my Win2003 Server R2. Seems to be working for the most part. It will not state that it is R2.
-
All, new to nlite so here goes. I initially setup an unattended installation with nlite. I used unattended option in nlite and specifically used some commands in the RunOnce tab. Subsequently, have moved to RunOnceEx creator for installing programs. My problem is that the old RunOnce commands from within nlite are poping up during install even though I have removed the commands from the tab in nlite on builds. Is this a bug? Also, every time I generate an ISO the build seems to grow by leaps and bounds to the point that I have to use a DVD to burn the images, even though I am not adding programs. What gives here? Thanks in Advance.