JerichoJones Posted April 24, 2008 Share Posted April 24, 2008 (edited) Any chance we could change the default location of the LAST_SESSION.INI to be the OS build directory instead of nLite's installation directory? I am trying to manage multiple builds and sometimes I forget to load the INI file from the OS build location. Edited April 24, 2008 by JerichoJones Link to comment Share on other sites More sharing options...
JerichoJones Posted May 7, 2008 Author Share Posted May 7, 2008 BUMP Link to comment Share on other sites More sharing options...
danker Posted May 8, 2008 Share Posted May 8, 2008 Sorry! but i think i'm nit the only one how don't understood you!What do you wont exactly? Link to comment Share on other sites More sharing options...
Ponch Posted May 8, 2008 Share Posted May 8, 2008 He wants a choice wether nLites ALWAYS shows previous ini files from the nLite\presets\ folder or from the working directory.I don't think it's a usefull option as anyway, you have to choose the ini so you have to know where it is. Also if you have a list of more than one ini, you should normally know that you are in the nLite\preset\ directory and so not be confused. Unless you also keep a history of ini's on your media.One more thing, working from a CD on an other computer will have you use paths that are not present (drivers paths for instance). Anyway... Link to comment Share on other sites More sharing options...
burned Posted May 8, 2008 Share Posted May 8, 2008 Any chance we could change the default location of the LAST_SESSION.INI to be the OS build directory instead of nLite's installation directory? I am trying to manage multiple builds and sometimes I forget to load the INI file from the OS build location.I second that! I am having the same problem. Link to comment Share on other sites More sharing options...
JerichoJones Posted May 22, 2008 Author Share Posted May 22, 2008 When doing multiple builds nLite is difficult to manage because it uses the presets directory AND the LAST_SESSION.INIs cannot be distinguished except by date/time. I don't know about you guys but I can't remember the date and time that I worked on my WinXP build as opposed to my Win2K3 build. If the LAST_SESSION.INI was read from the OS build directory upon loading it would solve the problem. I don't understand how people creating multiple builds could think that using nLite\presets directory is a better idea. Please enlighten me. If LAST_SESSION.INI was appended with the OS build directory name that would be helpful if nlite\presets must persist. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now