yes. like i said, you need first run the update with an /? to take the proper install commands, like this:

http://img385.images...command2eu7.gif
of course, this kb is in my own language, but you may get the idea. so, to do an silent install for WindowsXP-KB938464-x86-PTB.exe, you should have and command line like this:
WindowsXP-KB938464-x86-PTB.exe /quiet /norestart /overwriteoem
the problem: you need run each update with an /? argument to be sure that each one works with /quiet /norestart /overwriteoem or at least, trust in your own luck, because sometimes they change the command line. of course, you could take the proper command line from an older version of autopatcher xp sp2, but seems that you have renamed each update for MS08_025.EXE, that will give you an headache to match each one with our modules.
also i already said, with an .bat file, it's impossible to you set an condition to the update be installed. so, if by any reason any of those updates that you are trying to install is already installed in any machine, it will be installed again, because with an .bat file, the you can't set an condition. also, you will need run this .bat file manually in every machine from your network, because if you set it in a logon script, it will be run every single time that the machine turns on, unless you manage a way to set this .bat file to run only one time. also, you may have another issue: if, by any reason, any of the machines that you intent to run this .bat file is running in low rights mode, your efforts will be in vain.
because those issues that i've told to you 2-3 times already, i believe that an .bat file to install the updates is almost a waste of time. you even can run windows update in local mode through an network (ms has the documentation for that), that will do the job nicely too.
[]s