Errius wrote:What exactly are you trying to do? How are you planning to use variables in your script?
At the moment I'm only planning to use one variable and it's going to be in the autoexec portion of the DOSBox configuration files.
I like to make up custom config files for each game that have a menu allowing you to boot the game, run the game's setup and change various options. For example, my menu for the Redneck Rampage games allows you to boot any of the three games (the original, Rides Again and Route 66), run the setup (settings are then copied to all three games), enable/disable the CD music and enable/disable the Cusspack.
Something I've wanted to do for a while now is add an option to adjust the volume of the CD music, since the in-game volume options don't work. Recent testing shows that the DOSBox Mixer command will accept a variable, so I just needed a way to increase or decrease the value of that variable. If xset works the way it says, I can just add a small routine to increase or decrease the variable when the proper menu key is pressed (with a min/max check so that it rolls over at each extreme). This way I don't need to edit the config file if I want to change the volume setting.
BinaryDemon wrote:From what I read 'xset' would work, but I've never tried it.
Thanks, from reading the docs, xset looks like exactly what I was looking for!
BinaryDemon wrote:I've also used a ton of IF statements on occasion but it usually gets the the point where you ask yourself, why am I doing this in BATCH when I could be using QBASIC or an even more complex language.
As above I need to put it in the DOSBox config file. It runs all other DOS commands and external programs, so I'm hoping that it will also work with a program like xset. If it doesn't, then nothing will and I'll have to do it the long way.
Thanks again. 😀