I guess we can try again with günlük and see what happens. @ Stackoverflow - in case we also need a translation for onstart, any ideas what that would be? Maybe "başla".
Actually, what I was suggesting was just a possibility but with the posted pic, I think the previous 041f might be OK. Most likely, the problem is that we do need günlük. I would probably try changing back to 041f and use günlük. If that works then we can see if Microsoft translated onstart or not. @timesurfer - did you post twice? I had the same thing happen earlier and thought it was a problem with my internet connection. Maybe it's with vB4 instead.
lol...Yea initially but the Turk guy never came back so I left it It's really up to user to provide translations Then I do builds till it works for them Which I'm happy to provide support I suggest getting W7 to avoid IORRT XP language bug problems
If my XP wasn't English, I'd take that as a shot at me. Maybe I'll take it as a half-shoot at me for still using XP.
I believe (correct me if I'm wrong, JC) that the AT API is what was used prior to schtasks. Schtasks is supposed to be the better, new improved version (that is if MS didn't screw up the languages part).
AT is universal programatically script method to add scheduled tasks for Windows, .NET, C++, C have API for add the tasks, scripting coding isn't recomendable use of Schtasks, because variables with language ... Schtasks is GUI for AT, translated with OS, depends on the AT for work... With AT, have REG, NET and more...
Wouldn't say impossible. We just need to do more testing to determine what the proper translations are. Just in case it works (although I heard it doesn't), can you open up a command prompt and type in "schtasks /?" without the quotes and see what is returned.