He's talking about IORRT for Office 2010 VL IORRT is suppose to be accessable when only office 2010 VL is installed Also Trilogy shoudn't run unless as admin which is only time I saw stuff just fly by like wizardofoss said happened Trilogy has all error checks so IR5 doesn't run on XP or Vista
Please, try this line in a command prompt and report what happens. Code: schtasks /query | findstr /I "IORRT"
Thanks!! You're my hero It seems i didn't have 'schtasks.exe' on my pc. Downloaded it and now IORRT works like a charm; installation went well, status works (now remaining: 43200 minutes) and i even have a hidden IORRT-folder in my root Thanks for helping me out!
I'm glad it worked. One question: XP language is dutch or after was added? If was added, which the original language?
I guess I'm a bit late but, all Windows XP Home versions do not contain SCHTASKS. This is one of the differences between the Home edition and the Pro edition. The fix would be to manually create the task through Task Scheduler (might not be easy for beginners) or to get a copy of SCHTASKS.EXE from another source (preferably from a en-us version of XP which will help with the language bug). Note: I have not tested this myself as I have never used the Home edition.
I tried switching the language in my en-us copy of XP and found that the language of the GUI's changed but SCHTASKS does not get affected. I think the only way we can determine if a non-English XP has the Schtasks bug if to do a full install of the non-English version. With all the possible languages of XP out there, it would not be plausible solution to obtain and install different versions just for testing the Schtasks bug. It looks like we'll just have to wait and see who reports issues.
I agree with you but...If you can do a full install of a non-English XP would be good (a Turkish, German or other that have the bug and we don't know yet)...Because i have a full install of a Portuguese-Brazil XP and i have the language bug (in my case, /daily parameter). @Second have a Polish XP and have a language bug too (in his case, /daily and /onstart parameter). I think we don't need to do more tests to determine that bug...We can conclude that exist a bug on XP Professional Edition with some parameters of schtasks.exe command related to non-English XP Professional versions. With respect to the trouble of wizardofoss and what you said, we can conclude too that IORRT is not compatable with XP Home Edition. I suggest a possible solution (final decision of timesurfer): Code: if not exist "%WinDir%\system32\schtasks.exe" ( cls echo You don't have schtasks.exe installed! echo IORRT is not compatable with XP Home Edition. echo Upgrade to Professional Edition or download the file. ping -n 10 127.0.0.1 >NUL goto IORRT1 ) Is there still some bug in XP that we don't know yet?! I don't know what we can do more...
Actually, I know the bug exists in the German language version of XP. I just can't test it and I'm not sure it's worth the time to find a copy, download it, and install it just to verify. If there are no non-English users which are reporting problems, I think it's best, from a time perspective, to just to leave it as is. I think this sounds like a good idea. I can't think of anything else at this time but who knows. There are just too many possibilities which are not the easiest to test.
I don't think there's anything wrong with supporting forum users but, how I see it, it is different if there are no reported issues from the users. If it's going to take a hour or more to determine if a specific language (out of about 50 or more) will cause a problem, I just don't think it's worth the time/effort. We can add reported language issues when they come up but if there are no reports, maybe we should just leave it until there are some reported issues. As the saying goes: "Help us help you."
So we should just ditch the variable for languages? I can't test any of this stuff so let me know logically what's best to do and show me your interpretation of the correct code here
Its your project, so the final say goes to you. I think we can leave it in and just add new languages when they are reported and we can determine the translated "fix". I just don't think we should bother trying to go installing localized versions of XP just to see if there is a problem with a certain language. It'll be just too time consuming and, as I said, if there are no users reporting the problem, then finding extra languages, via the install route, would be a complete waste of time.
Lets just add stuff If that discussion is over then let me reiterate an discussion about IR5 Are you ready?
So we leave Trilogy as it last stands and I start IR5 discussion? I want 2010 to be over except for additions languages before I start IR5 controversy
Unless further "developments" come up, I think we can move on to IR5 discussions. If you like, you can wait to hear what others have to say first before doing so.