Automating Pro/E Install 1

[mavsol]

Hi,
I am trying to automate the Pro/E install since I have to setup new user's machines quite frequently. I have tried the command line procedure in :

http://www.appdeploy.com/packages/detail.asp?id=797.

Here is my single install line in my batch file:
R:\Installers\ProE_4\SETUP.EXE -nographics -uitrail myinstall2.txt

Here is myinstall2.txt:

! UI trail file version 1
! Application name `ps`
HIDE_SPLASH
~ Activate `ptcsetup` `NextBtn`
~ Activate `ptcsetup` `ScreenWelcome.AcceptBtn` \
1
~ Activate `ptcsetup` `NextBtn`
~ Activate `ptcsetup` `ScreenWelcome.ProdButton.1`
~ Activate `ptcsetup` `NextBtn`
~ Activate `ptcsetup` `ptcsetup`
~ Activate `ptcsetup` `ScreenLicList.PushButton1`
~ FocusIn `ps_lic_serv` `HostnameInput`
~ Input `ps_lic_serv` `HostnameInput` \
`g`
~ Input `ps_lic_serv` `HostnameInput` \
`go`
~ Input `ps_lic_serv` `HostnameInput` \
`gol`
~ Input `ps_lic_serv` `HostnameInput` \
`gold`
~ Input `ps_lic_serv` `HostnameInput` \
`goldm`
~ Input `ps_lic_serv` `HostnameInput` \
`goldmi`
~ Input `ps_lic_serv` `HostnameInput` \
`goldmin`
~ Input `ps_lic_serv` `HostnameInput` \
`goldmine`
~ Update `ps_lic_serv` `HostnameInput` \
`goldmine`
~ FocusOut `ps_lic_serv` `HostnameInput`
~ Activate `ps_lic_serv` `StdOK`
~ Activate `ptcsetup` `NextBtn`
~ Activate `ptcsetup` `ScreenWindows.ScDesktop` \
1
~ Activate `ptcsetup` `ScreenWindows.ScStartMenu` \
1
~ FocusIn `ptcsetup` `ScreenWindows.StartInDir`
~ Input `ptcsetup` `ScreenWindows.StartInDir` \
`C:\\Documents and Settings\\m\\My Documents`
~ Input `ptcsetup` `ScreenWindows.StartInDir` \
`C:\\Documents and Settings\\my\\My Documents`
~ Input `ptcsetup` `ScreenWindows.StartInDir` \
`C:\\Documents and Settings\\myu\\My Documents`
~ Input `ptcsetup` `ScreenWindows.StartInDir` \
`C:\\Documents and Settings\\myus\\My Documents`
~ Input `ptcsetup` `ScreenWindows.StartInDir` \
`C:\\Documents and Settings\\myuse\\My Documents`
~ Input `ptcsetup` `ScreenWindows.StartInDir` \
`C:\\Documents and Settings\\myuser\\My Documents`
~ FocusOut `ptcsetup` `ScreenWindows.StartInDir`
~ Activate `ptcsetup` `NextBtn`
~ Activate `ptcsetup` `ScreenLpcfg.LCB.LpcfgCmdList` \
1
~ Activate `ptcsetup` `NextBtn`
~ Activate `ptcsetup` `LpcfgCmdList.cmd_add`
~ FocusOut `ps_lic_sel` `CmdDesc1`
~ FocusIn `ps_lic_sel` `CmdName1`
~ Input `ps_lic_sel` `CmdName1` \
`proe`
~ Input `ps_lic_sel` `CmdName1` \
`proe_`
~ Input `ps_lic_sel` `CmdName1` \
`proe_m`
~ Input `ps_lic_sel` `CmdName1` \
`proe_me`
~ Input `ps_lic_sel` `CmdName1` \
`proe_mec`
~ Input `ps_lic_sel` `CmdName1` \
`proe_mech`
~ Input `ps_lic_sel` `CmdName1` \
`proe_mecha`
~ Input `ps_lic_sel` `CmdName1` \
`proe_mechan`
~ Input `ps_lic_sel` `CmdName1` \
`proe_mechani`
~ Input `ps_lic_sel` `CmdName1` \
`proe_mechanis`
~ Input `ps_lic_sel` `CmdName1` \
`proe_mechanism`
~ Update `ps_lic_sel` `CmdName1` \
`proe_mechanism`
~ FocusOut `ps_lic_sel` `CmdName1`
~ FocusIn `ps_lic_sel` `CmdDesc1`
~ Input `ps_lic_sel` `CmdDesc1` \
`P`
~ Input `ps_lic_sel` `CmdDesc1` \
`Pr`
~ Input `ps_lic_sel` `CmdDesc1` \
`Pro`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe `
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe E`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe `
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E `
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E M`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Me`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mec`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mech`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mecha`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechan`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechani`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechania`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechaniam`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechaniam `
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechaniam D`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechaniam De`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechaniam Des`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechaniam Desi`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechaniam Desig`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechaniam Design`
~ Update `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechaniam Design`
~ FocusOut `ps_lic_sel` `CmdDesc1`
~ Select `ps_lic_sel` `List3` \
1 `127`
~ Activate `ps_lic_sel` `MoveToOut`
~ FocusIn `ps_lic_sel` `CmdName1`
~ FocusOut `ps_lic_sel` `CmdName1`
~ Activate `ps_lic_sel` `StdOK`
~ Select `ptcsetup` `LpcfgCmdList.CmdList` \
1 `1`
~ Activate `ptcsetup` `LpcfgCmdList.cmd_edit`
~ Input `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechanism Design`
~ Update `ps_lic_sel` `CmdDesc1` \
`Proe/E Mechanism Design`
~ FocusOut `ps_lic_sel` `CmdDesc1`
~ Activate `ps_lic_sel` `StdOK`
~ Activate `ptcsetup` `NextBtn`
INSTALL_THREAD
~ Activate `ptcsetup` `ptcsetup`
~ Activate `ptcsetup` `ptcsetup`
~ Activate `ptcsetup` `ptcsetup`
~ Activate `ptcsetup` `ptcsetup`
~ Activate `ptcsetup` `NextBtn`
~ Activate `ptcsetup` `ExitBtn`
! Message Dialog: Question
! : Confirm exit from PTC.Setup
~ Activate `UI Message Dialog` `yes`


However, the command only runs for a few minutes then closes with no error message.

Thanks in advance for any advice or comments.

 

[dgallup]

Once you have one machine setup properly you can just copy the files, no need to use ptcsetup. Or do what I do, just install Pro/E on a server and put a shortcut on the users desktop.

 

[mavsol]

dgallup,

Thanks for your response. Sorry it took me so long to get back to this. Are there any steps needed to associate proe files with the program in windows? For example running "proe /regserver" or something along those lines?

Thanks again!

 

[dgallup]

I don't associate Pro/E files in windoze. For one thing, windoze has incredibly poor file association capabilities. It can only look at the characters after the last dot (.). When I was a HPUX sys admin I could write my own association rules so I could match a *.prt.* file to a part, etc. The way PTC does it in windoze is to create every possible association for *.1, *.2, *.3 all the way to *.999. This creates 999 file types all with the same association. Ridiculous! Then, PTC associates the files with a crappy file viewer that only runs in a crappy browser (internet explorer) that I don't use. Since the file associations do nothing useful I keep them off the system.

The only extra step I do is add the path to the Pro/E bin directory in the PATH environment variable.

 

[mavsol]

Thanks again. Sorry for the slow response again. I wasn't able to get back to this task until now.

If you wanted to automate some of the associations such as just ".prt" you could use the following.

http://support.microsoft.com/kb/184082

 

[dgallup]

That does not work in windoze for Pro/E because windoze only makes file associations with the characters after the last dot in the file name. There is no way to make an association to *.prt.* or *.asm.* or *.drw.*.

 

[mavsol]

I understand it doesn't work fully but IMHO at least doing the ".prt", ".drw" and so on without the numeric parts might be enough of an attempt to make some friends among the users.

BTW - I too was sad to hear that Pro/E was no longer supported on Linux when we started using it at Wildfire 3.