Post a reply to the thread: INI value wildcard
Click here to log in
What's the name of our main installation product (in uppercase letters), directly followed by the current year?
You may choose an icon for your message from this list
Will turn www.example.com into [URL]http://www.example.com[/URL].
Re: INI value wildcard We'll see if there is something we can do here. The development system (Clarion) handles this automatically, so I am not sure if we can fix it or if we need a fix from the development system vendor. Friedrich
Re: INI value wildcard
Re: INI value wildcard Perhaps the notification e-mail made it directly into the Spam folder, I don't know. The vBulletin system handles all this completely behind the scenes. Friedrich
Re: INI value wildcard See attached screenshot. I already answered on SATURDAY (July 29, 2017)!! The only email notice pertaining to this thread that I received on Saturday was posting #14. In #14 you simply said, "Thank you." No other email notices between your posting #14 and #24 were ever received so I assumed that the CRC issue had been forgotten.
Re: INI value wildcard Yes, but I already posted a solution 5 days ago! With regards to the July 15th question, the following comment by me was never responded to: When the user is in the Script Editor window and then changes the line height value to "1" via "Tools > Options > Editor", then clicks OK, then goes back and change it to "21" and clicks OK, the vertical scroll bar is missing *until* you take your mouse and click inside the Editor window.
Re: INI value wildcard Originally Posted by instrumentally I am still waiting for a response to my postings from July 14 and July 15, not to mention the following issue... Monday was 3 days ago. Yes, but I already posted a solution 5 days ago! See attached screenshot. I already answered on SATURDAY (July 29, 2017)!! Friedrich
Re: INI value wildcard Originally Posted by instrumentally I am still waiting for a response to my postings from July 14 and July 15, not to mention the following issue... BTW, this one is something that has nothing to do with SetupBuilder per-se and is some kind of consulting. I don't have an idea yet on how to handle it. And the solution to the "issue" you mentioned was posted on Saturday. http://www.lindersoft.com/forums/sho...8573#post88573 Friedrich
Re: INI value wildcard Here is the analysis from SATURDAY! http://www.lindersoft.com/forums/sho...8572#post88572 Friedrich
Re: INI value wildcard I have to give this some thoughts and get back to you... I am still waiting for a response to my postings from July 14 and July 15, not to mention the following issue... I am sorry for the delay in resolving this issue. It's my #1 priority for next Monday. Monday was 3 days ago.
Re: INI value wildcard Solution: change the "Host Directory" from deployment into demo/deployment, recompile, and you are done. Does this help? Friedrich
Re: INI value wildcard FOUND IT! See attached screenshot. The inword.exe in your inwordbible.com/deployment web folder is dated 2017/07/25. So IMO, all the files are dated 25-JUN-2017 and not 27-JUN-2017!!! I think you uploaded all the newer files to another location but you still point (in your download) to the old location (even from your inword.exe dated 2017/07/27). The inword.exe you sent me is dated 2017/07/27. As far as I can see, all your NEW files are located at http://inwordbible.com/demo/deployment but you still instruct the installer to download from (the OLD location) http://inwordbible.com/deployment. Just downloaded the inword.exe from your http://inwordbible.com/demo/deployment and it is the new one (dated 2017/07/27)! Friedrich
Forum Rules