Hi! We will start on writing an automated install script for Trados on spare time, Friday next week. Up to then I have to prepared the script *in a way that a developer will understand what I want* and being responsible for testing it under Linux. Basically it will be an automated script which will be timed, i.e. if no install_ok after 20 min, it would be hanging somewhere and will abort and throw the log. If install OK after the two runs (Trados and license server installation), it will throw a sign that the install is OK. When prompted, the user will have each time 10 seconds to pick a choice, when after 10 seconds no choice is picked, the script will select the standard choice and continue. If there is a choice, between yes and no, selected answer will be no (usually it is a question about "xxx install failed, do you wish to continue") unless the user has selected otherwise during the 10 seconds. Now a couple of questions: -In which language is exactly the script? -What happens when the software is waiting for a prompt (like you have to click "next), is it written in unix or conform to the windows program as a dos prompt? Maybe there will be more questions in the course in the week but it's what I can think of to start with.
On Sat, Apr 5, 2008 at 11:23 PM, Timeout <wineforum-user at winehq.org> wrote:> We will start on writing an automated install script for Trados on spare time, Friday next week.Great. As a first approximation, I would suggest a simple one that does not try to automate GUI functions, only the easy stuff.> Up to then I have to prepared the script *in a way that a developer will > understand what I want* and being responsible for testing it under Linux. > > Basically it will be an automated script which will be timed, i.e. > if no install_ok after 20 min, it would be hanging somewhere and will abort and throw the log. > If install OK after the two runs (Trados and license server installation), it will throw a sign that the install is OK. > > When prompted, the user will have each time 10 seconds to pick a choice, when after 10 seconds no choice is picked, the script will select the standard choice and continue.Too fancy IMHO.> Now a couple of questions: > -In which language is exactly the script?I would start with a shell script. Don't even try to do anything GUI-like. Just have the script wipe the .wine directory and do all the winetricks steps neccessary, and start the windows installers.> -What happens when the software is waiting for a prompt (like you have to click "next), is it written in unix or conform to the windows program as a dos prompt?You could use 'read' in the shell, but it's better to not have anything like that. Your goal should not be "wonderful automated installer" but "bare minimum showing how to reproduce my problems". - Dan
> > Your goal should not be "wonderful automated installer" but > "bare minimum showing how to reproduce my problems". > >Reproducing the problem is one thing but for that I don't need to go that far (it will crash after 2 min). I may have to be usable when it goes through and the installshied requires user interaction. (Maybe I should add workarounds in comments) The automated installer will abort at the first problem. The manual user however should be able to have time to answer because he knows how to go around these problems because even if a part is failing, sometimes the next is ok. The whole GUI would be the one of the installshield. I think the only GUI I may ask for is: "Do you want to install MS Office" with yes/no and a button to click when office is through to start with Trados/abort button. Automatic install will then skip MS office, but for later use it's a pain if you install MS office after Trados, you have to add manuall the template in the start directory of office. I won't build my workaround in the script (like pressing esc 2-3 times at a certain stage) :-)
In this section:> > where are those dlls coming from -- did you copy them there from > a Windows installation? If so, can you replace the lines > > > wine regsvr32.exe msvcr70.dll > > wine regsvr32.exe mfc42.dll > > > with > winetricks vcrun6 vcrun2003 > ? >vcrun 2003 is installing msvcr71, which is not quite the same. I guess an empty file would do as well, it's just for the registration of fusion.dll. Later on all my logs msvcr80 or msvcp 80 are rather used. I take them from my Windows on dual booting.> Jetzt: Windows abfrage: > Why install Office 2003? Is that required to use Trados? If so, maybe > just do it no matter what. >Msoffice 2003 (or 2007 when it's working) are quite necessary. First in trados for the conversion of texts using Workbench. Any processing of files other than .ttx and .rtf are using Word in the background to transform the file to process it to rtf. SDLX is using Word in the background to convert any file (except rtf) to SDLX own's format (idf if I remember) and only then you will be able to process the file. Word (when it will be working properly) is enabling you to have a spell check which is crucial for a translator. Furthermore, Trados is said not only to use VBA, but even word's own script format. Using Open Office instead of Word on Trados is on the wish list of Trados' users but it's not likely to happen any time soon since from the point of view of SDL, OpenOffice is changing too often and even less documented than Word to base their software on it. Seems to be too much work to adapt the macros after every update.> > If you're providing this script for Wine developers, we > don't need any sort of "do you want to retry" option. >I know. But I won't get the script if I don't plan for my own use. And I know as long as it's not 100% perfect that I may have to intervene myself to get it installed. Seing from the point of view of my husband (I don't pay by the hour so I can ask for it to be more comfortable) - He has to be half of the night next week because of an update of his company and even watching TV is boring him at that time so I know I can ask more. My goal is to use it as end user too - that way I could also send the script to my colleagues.
Dan Kegel wrote:> > Can you please use 'winetricks vcrun2005' instead of grabbing from windows? >vcrun2005 is already part of Trados's installer. I don't need a winetrick for that.> > You might want to skip the interactive parts of your script and go > straight to a noninteractive install of everything. Trados documentation > for earlier versions said you could install it noninteractively like this: > msiexec.exe /i "<CompletePathTo'Trados.msi'>" /qn > Does that work with your version? >I heard someone did with cabextract to extract the trados.msi and started it so. It's however more complicated as an user to have to search for which of the 7 or 8 pieces installed by the installshield can be independently used from one another. At least more for me than showing each of the windows and writing what to enter in which window. Since SDL bought Trados, it's slowly but surely merging the functions of one into another. I guess the last trados to be independent from SDLX was 7.0 - won't be supported for long anyway since SDL announced they won't be supporting versions more than 3 years old and thus removed version 6.5 out of support.> > You might want to use the ideas in > http://wpkg.org/MS_Office_2003 > to offer a silent install rather than an interactive one for Office 2003. >To test the installer I don't need office. I will probably remove it at the moment. It's installing as it is at the moment anyway-
[/quote] Why would the user have to search for anything? The documentation I read (http://www.sml.hw.ac.uk/computing/documentation/trados/GST6_TM_en.pdf) said that adding /qn to the msiexec did a complete installation of the entire suite. [/quote] Does it mean I should write "wine tradosinstall.exe /qn " This will reduce the script pretty much.
> > if [ test -f filename ] > then > echo "file exists" > fi > >Thank you. I will add it for each dlls to add manually.> > You can't click buttons in a shell script. Are you expecting the user to > do all the button clicking, or do you want to automate that?I want to automate that so that like your valgrin test, you can enter the script test list and get at the end a log where you can see if a change is improving or breaking the installer. Every part which fails has a message that the component failed so answering no there would abort the installation and you see what failed and for the case it hangs I would like to add a timeout. In a later stage, I will try to give some time to the user to select at each window before the script comes into force.