Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Me too. I didn't document very well what's going on, but it's coming back now. There are some things that Need FixingI'm interested in learning at least. Maybe I can even contribute...I admit near-total ignorance with respect to the scripting language, although I'm somewhat familiar with assembly, so I can kinda figure out what's going on. I'm looking at the code and can't figure out for the life of me how some of it works.
I see where you're getting the data out of the text fields/checkboxes, but I don't see how you're writing the "username=" before the "Mohonri" in the client.cfg
FileWrite $9 $R8[/url]
which writes a string with something like "unhappy_mage
33
yes
no
maybe" (what you'd type if you manually answered the questions!) into "$INSTDIR\client-input.txt" (as determined at the beginning of CheckConfig). Then, back in Section -Post, I write "install_service.bat" with this in it: "$\"$INSTDIR\$CONSOLENAME$\" -configonly < $\"$clientcfg$\"$\r$\npause" and then execute it. So an example of what this would expand to is "C:\fah\fah5.exe -configonly < client-input.txt
pause". The < tells Windows to connect stdin to the specified file instead of the console, so as far as FAH is concerned there's a user answering the questions. That way you can guarantee that the client.cfg file has something valid in it - even if the format of the questions asked by the installer changes, it'll still write something to client.cfg. For example, try "fah5.exe -configonly < emptyfile.txt" - it should write a default config file.
Yes, but the -forceasm switch is recommended for general usage, so it adds that part in.Ah, I didn't catch that part. Here's another question: how come the install script manually adds the service registry key? Doesn't the client do that itself?
That part is already partially implemented, but it's not terribly easy as it stands. Notice the third line of the source has a semicolon at the beginning - remove that and the installer will always use unhappy_mage/33, regardless of what you enter in the config pages. What would have to be added to get a quick borg tool? A check if CONFIG is defined, and if it is, skip the config pages. This would be, basically:It would also be nice to make a short version of the installer for purely unattended setups--just a double-click and you're done. Each borger would have to roll their own installer, but it would make borging soooooo much easier.
!ifndef CONFIG
; do config pages
!endif
Ah, I see now.Yes, but the -forceasm switch is recommended for general usage, so it adds that part in.
My thought was to just create a basic "single-core machine borging kit" with basically all the defaults except for username and team. You see, I have several family members with unborged single-core computers, and I want to make it really easy for them...Generating a pre-defined config might not be the best idea, though; you'd have to figure out which config values need to change on a per-machine basis and separate them out. For example, you want to install 2 instances on a dual-core box and one on a single-core box, and might want advmethods on or off, that sort of thing. There's gonna have to be a lot of reworking to get it really flexible.