bryanh Posted April 7, 2005 Author Posted April 7, 2005 I am still having problems with the 'already installed' feature. These items can still be selected and WAIT tries to reinstall them. The DoNotInstallAlreadyInstalledApps" flag that was introduced in version .18 does not work in version .19a. It generates an error when WaitCfg.exe runs, and it is removed from the .ini file.This was by design - you can select an already installed item therefore allowing it to be re-installed. I thought the DoNotInstallAlreadyInstalledApps flag was too restricting. You can accomplish the same thing by detecting that it's installed and also putting the same file checks into the "Hide if" section. This will hide already installed app therefore making it impossible to select it and reinstalling it.WAIT also tries to install items that are hidden via HideIf. Not sure about this one. I will start digging into the code. I think (thought) this could not happen.And, if HideIf items are hidden because a file is not found (the '-' prefix is used), and the hidden item 'Excludes' other programs, the excluded items can not be selected when Select All is used.<{POST_SNAPBACK}>I will look into this as wellthank you
bryanh Posted April 7, 2005 Author Posted April 7, 2005 And, if HideIf items are hidden because a file is not found (the '-' prefix is used), and the hidden item 'Excludes' other programs, the excluded items can not be selected when Select All is used.<{POST_SNAPBACK}>This only happens of the item is not only hidden but also installed. This is also by design. It the item is installed then there is no way you should be allowed to install something that it "Excludes"Make sense?
bonedaddy Posted April 7, 2005 Posted April 7, 2005 @BryanHthe button problem is well behind now..... great fix, and simple to change over,just rename wait.ini three times and do some selecting, very nice...........thanksBD
bryanh Posted April 7, 2005 Author Posted April 7, 2005 There is now a section on the Wait forums for discussions around AutoIt. Come on over and take a look.Bryan
bryanh Posted April 21, 2005 Author Posted April 21, 2005 version 21 is up to address your bug.You know where to find it
bryanh Posted May 1, 2005 Author Posted May 1, 2005 posted a new bug at the wait forums.<{POST_SNAPBACK}>The solution to your problem is posted on the WAIT forums.Let me know how it goes.Thank you
Ben.Hahlen Posted May 1, 2005 Posted May 1, 2005 Could someone explain to me how to use W.A.I.T. from cmdlines.txt?This seems my "perfect" way of installing.And is there some kind of "setup-guide"?
a06lp Posted May 2, 2005 Posted May 2, 2005 The solution to your problem is posted on the WAIT forums.Let me know how it goes.<{POST_SNAPBACK}>I'll try it on my next burn.
Ben.Hahlen Posted May 2, 2005 Posted May 2, 2005 Could someone explain to me how to use W.A.I.T. from cmdlines.txt?This seems my "perfect" way of installing.And is there some kind of "setup-guide"?<{POST_SNAPBACK}>Anyone for these? I've tried to run from cmdlines.txt and that's the part that works, but it doesn't install any programs... Furthermore, I've posted a few requests and a (possible) bug on the WAIT forums.Thanks in advance.
Ben.Hahlen Posted May 2, 2005 Posted May 2, 2005 Just found another bug (Thread at WAIT forums):WAIT adds the keys for RunOnceEx as the "folder" 000x (don't know what it's called in the registry) and then a key 000x with the command to run.The problem is that somehow, Windows doesn't accept the FOUR digits, but it DOES accept THREE digits.Would you be able to change that? (I don't believe anyhow that anyone would have more than 999 programs to be installed...).Thanks in advance.
bryanh Posted May 3, 2005 Author Posted May 3, 2005 Ben, I am working on your bug report as well as your request. I have been having the same problem as you. When using WAIT with CMDLINES.TXT it puts all the lines in the registry, but nothing installs. Personally, I have only been using the internal installer and GUIRUNONE. This has worked with no issues. And, using the internal installer gives you some advantages (logging and timeout's). As soon as I figure out what's going on with the CMDLINES.TXT issue I will post a new version. I am also working on a setup guide.Thank you for your supportBryan
Ben.Hahlen Posted May 3, 2005 Posted May 3, 2005 The reason that I'm using WAIT from cmdlines.txt, is that I would like to be able to "leave" my computer to it as much as possible. Pretty much the same reason -I- gave.If you would be able to implement the requests I've made, I think I'll love you forever
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