Automatic Install of ProE Wildfire 4.0

[ocorten-2]

Hi,

I am trying to create an automated install of ProE Wildfire 4.0 M220 x64 by running a trail file through the setup.
So I created a trail file with the -uilog option and am now running it with the -uitrail option.

The trailfile runs ok, but it keeps hanging at the beginning when it starts copying files. A manual install is no problem.

Maybe the problem is that I unzipped all 5 archives into one folder.
Has anyone been able to create an automated setup for WF4 with all zip files unpacked in one folder?


Kind regards,

Olaf Corten




Olaf Corten
CAD/PLM Manager
Besi Netherlands B.V.
Ratio 6, Duiven
Phone: +31 26 3196215
Mobile: +31 644548554
www.besi.com




Confidentiality Notice:
This Email, and any attachments, may contain internal or confidential information and is intended solely for the individual to whom it is addressed. It may contain sensitive or protectively marked material and should be handled accordingly. If this Email has been misdirected, please notify the author immediately. If you are not the intended recipient you must not disclose, distribute, copy, print or rely on any of the information contained in it or attached, and all copies must be deleted immediately.
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[ocorten-2]

Menso Heij from CE Masters pointed me in the right direction:
You must first use the setup to create a Custom Installation if you have combined the five zip files into one folder.

In that custom installation folder you will be able to use the -uilog and -uitrail installation routine.

Thanks a lot Menso.


Kind regards,

Olaf Corten




Olaf Corten
CAD/PLM Manager
Besi Netherlands B.V.
Ratio 6, Duiven
Phone: +31 26 3196215
Mobile: +31 644548554
www.besi.com






From: Olaf Corten <->
To: -
Date: 04-12-2013 11:55
Subject: [proesys] - Automatic Install of ProE Wildfire 4.0



Hi,

I am trying to create an automated install of ProE Wildfire 4.0 M220 x64 by running a trail file through the setup.
So I created a trail file with the -uilog option and am now running it with the -uitrail option.

The trailfile runs ok, but it keeps hanging at the beginning when it starts copying files. A manual install is no problem.

Maybe the problem is that I unzipped all 5 archives into one folder.
Has anyone been able to create an automated setup for WF4 with all zip files unpacked in one folder?


Kind regards,

Olaf Corten




Olaf Corten
CAD/PLM Manager
Besi Netherlands B.V.
Ratio 6, Duiven
Phone: +31 26 3196215
Mobile: +31 644548554
www.besi.com




Confidentiality Notice:
This Email, and any attachments, may contain internal or confidential information and is intended solely for the individual to whom it is addressed. It may contain sensitive or protectively marked material and should be handled accordingly. If this Email has been misdirected, please notify the author immediately. If you are not the intended recipient you must not disclose, distribute, copy, print or rely on any of the information contained in it or attached, and all copies must be deleted immediately.


Attachment Links: blankfilename.txt (2 k) blankfilename.txt (1 k)
Site Links: View post online View mailing list online Start new thread via email Unsubscribe from this mailing list Manage your subscription

Use of this email content is governed by the terms of service at:

[dgschaefer]

Olaf,

I unzipped each into its own folder named "disk1", "disk2", etc. and ran the install and created the trail file. Every time it asked for the location of the next disk, I just changed the number in the path. Installing by trail file then worked fine. I wasn't able to install both the software and the help at one time; I had to create separate trail files for each, but it worked that way.

--