I do not know if you still are working on this project, but it happens to be what I used to do as part of our windows imaging - back from windows 2k and XP.
While I doubt this is useful to anyone, all this script really does is "wrap" SendKeys but gives you a way to pass a text file(s) as input, lets you have essentially variables in that text file. Deals with path resolution (like you needed) but also other stupid things like keeping the damn window focused.
There's also really bad attempt to use RC4 in there to let you have encrypted input. Just kinda ignore that - this was never intended for anything more than very basic obfuscation so that if you had say a Domain Admin password for auto-joining machines to the domain, it was at the very least not plain text if you somehow forgot to delete that file.
If anything you can laugh at how old school the structure is. Yea, I guess being taught "Structured Programming" on a TRS-80 in high school kinda shows.
Last note, this actually worked really well from NT to XP. For some reason win7 and later tends to drop keystrokes randomly when you blast input to them with sendkeys. Or it might just be fighting with the updates to the command windows. But it still worked 80% of the time and for me at least still was a life-saver when after we blasted a windows image out to blocks of 50 machines - this automated so much of the tedium of doing things like "first runs" on Office (to activate), web browsers, other stupid things like adding computer descriptions etc. This was important because we ran DeepFreeze (look up SteadyState too) which was a product that essentially gave your computer amnesia on reboot. So if you jacked it up, just reboot and it was like nothing happened. Unfortunately it also meant you would get all the annoying 1st run tutorials and other setup things every boot too unless you explicity did it before freezing.
Oh! just wanted to add. For those who do still mess with vbs, to get the script host back to the default of popping up windows after you run this (I set it to command host, but that's not default), run " cscript //H:WScript " at the command line.
Needless to say, Microsoft's official imaging solutions don't cover that.
Anyway, enough blabbing, more things for you to laugh at. Dump into a folder of it's own and run "runme.bat" Also it assumes Admin (i know, bad practice) but I do have some UAC wrappers somewhere for this - but I doubt anyone cares that much ;p
ADDED: To restore vbs back to the normal windows popup behavior, run "cscript //H:WScript" on the command line. Also if for some reason you do run this script in WScript mode you will go insane =D to escape Ctrl-C.... or at least try before the next windows popup.