JohnKaufmann Posted September 26, 2012 Author Share Posted September 26, 2012 (edited) Yeah. Rabbit holes are deep. .Isn't there another choice besides red pills and blue pills? Thanks for that final present,JohnLight Blue Ribbon Campaign for Freedom of Skin Edited September 26, 2012 by JohnKaufmann Link to comment Share on other sites More sharing options...
JohnKaufmann Posted September 27, 2012 Author Share Posted September 27, 2012 (edited) ... what I ALWAYS do and suggest ... is (JFYI):NEVER use a path with spacesNEVER use (unless really, really and I mean really) needed any filename that is not conforming toi the good ol' DOS 8+3 convention ...As I was assembling a PE, I thought about this comment and wondered if you have a solution for subdirectory names like "Application Data" and "Local Settings" -- for which (as noted earlier in the thread) there are corresponding registry values, but which apparently have no corresponding WinNT.SIF (or other PE) setting. Likewise, do you remove settings like "Personalized" and "PersonalizedName" from the desktop.ini files? -- or just remove desktop.ini files altogether? Is there a way to control this from the PE?John Edited September 27, 2012 by JohnKaufmann Link to comment Share on other sites More sharing options...
jaclaz Posted September 27, 2012 Share Posted September 27, 2012 You can call me "coward" as you like , but what I ALWAYS do and suggest (in the "better be safe" than sorry approach ) is (JFYI):NEVER use a path with spacesNEVER use (unless really, really and I mean really) needed any filename that is not conforming toi the good ol' DOS 8+3 conventionNEVER use either the "desktop" or an user profile(talking about drivers/programs, etc. connected with setup)Of course whatever is already in the "standard" setup is tested and works OK "as is" (no need to change it) BUT, if you want to make changes/additions, if you follow the given advice you have less risks of having a "botched" install or to find later issues when using the program or burning a CD or Example (obviously exaggerated), if you install (unattended or attended) a program, if it is in:C:\Programs\myprogramand the executable is called nice_app.exeyou have a "safer" approach than having it in:C:\Program Files\my semselessly long name for a directory\another senselessly named sub-directory\this is the actual directory when the program is\here I am a very smart and modern program that foos and bars really nicely.exePossibly everything will work OK nonetheless , but is there a real reason to risk it?jaclaz Link to comment Share on other sites More sharing options...
JohnKaufmann Posted September 27, 2012 Author Share Posted September 27, 2012 You can call me "coward" as you like ...No. I'd call you a teacher. Thanks again for the quick reply.JohnLight Blue Ribbon Campaign for Freedom of Skin Link to comment Share on other sites More sharing options...
jaclaz Posted October 3, 2012 Share Posted October 3, 2012 There are many similar directory settings in the registry (like AppData, AllUsersPath, DefaultUsersPath, HomeDrive, HomePath, MediaPath, ProgramFilesPath, ...) that presumably have deployment antecedents, but the for most part I have not found those antecedents. That's the kind of reference I was seeking. Though I have learned a lot of good stuff, I have to conclude that the reference I just described does not exist.JFYI:page__view__findpost__p__1013624jaclaz Link to comment Share on other sites More sharing options...
tomasz86 Posted October 3, 2012 Share Posted October 3, 2012 (edited) Thanks jaclaz for quoting me I haven't tested it yet but I think that it should be possible to set all variables in HIVEDEF.INF including %programfiles%, etc. Edited October 3, 2012 by tomasz86 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