Hi Guys

I am currently working on a massive application called OrCAD by Cadence. This aplication is a setup and contains about 62000+ files and 5000 registries. The application could not be captured by Wise 7.0. I tried doing it but to no avail I have not made a single MSI in the last 10 hrs. The app requires over 30 mins to install and its really trying my patience.

Can anyone help me with tips in case they have come up with similar apps?

Cheers
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
read about "componentization" in your sdk

this one of the adventages of windows installer technology

during a capture choose custom and select features to install

carry on with another capture and choose custom features to install

once you have captured all your msi's install one at a time (DO NOT NEST)

this might be an option
Answered 07/05/2010 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
...or be extremely patient. Sometimes, Wise *can* seem to have stalled but it gets there in the end. I've only encountered one app which choked Wise and that seemed to be the number of registry entries which caused that.

...or switch to InstallShield. It seems to have no such hangups.
Answered 07/05/2010 by: VBScab
Red Belt

Please log in to comment
0
Yes, I tried capturing the application in parts. But the app has 3 features and one of them is tied to another. So least I can do is capture 2 during the first time and 1 during the second one. However the first capture tends to put in 51000 files and its the same case.

I have tried to be extremely patient and waiting for Wise to do its thing. I tend to get a wsi but the compile takes ages to make the msi and it eventually fails.

I am going to try and use InstallShield to capture it but I dont know if a evaluation version will let me capture (I mean no reduced functionality I hope). Any idea about this, because I dont have a license for it [:@]
Answered 07/06/2010 by: India_Repackaging
Blue Belt

Please log in to comment
0
The trial version (just like Wise's) is fully functional. However, if you get a WSI successfully, why not try removing a portion of the files captured, compiling, then adding the files back and re-compiling? You could do the same with the registry (easier to export then import a .REG, of course) if you find that the issue is with that part.

I reported a bug to Wise eons ago concerning a particular package which I managed to compile doing exactly that. Once it had compiled the MSI once, it was happy to do it as many times thereafter as I needed. Weird...
Answered 07/06/2010 by: VBScab
Red Belt

Please log in to comment
0
I once had an app just containing too many files. It wasn't even the size of the app that was killing Wise, but the amount of files. If the app just has massive data directory where nothing special happens (like files being registered, ini files, etc..), you could also add the data directory to some self extracting zip or any other format you like, which can be uncompressed silently again by a CA or something like that. Not winning any beauty contests with that, but it worked.
Answered 07/06/2010 by: Rheuvel
Brown Belt

Please log in to comment
0
I did 16.2 for a while and decided to use a silent setup instead of capturing it.
I can't imagine that 16.3 differs that much from 16.2 so here are some notes.
No license info was added, the customer wanted to used it in "demo" mode.

* Create an answer-/response-file
(D:\Source\DVD\Disk1\)
setup.exe /r
this will generate the setup.iss file under C:\Windows.

* Install
setup.exe -s -f1"<full path to setup.iss>" -SMS

Note:
During install the license dialog still display and halt for button click.
Before executing the setup I launched a vbscript that listened for start of the LicenseClientConfiguration.exe process and just kill it.
If you want to add license information you need to find a working solution instead.

* Update
Hotfix_ORCAD16.20.002_wint_1of1.exe -s -f1"<full path to update.iss>" -SMS

* Fix vendor crap
During first launch the application wants to create some COM-Component registry which will not happen
if the launching user is a standard-user.

I just imported the missing registry after the installation.
(Root keys under HKLM\SOFTWARE\Classes)

.dat
.OPJ
.ses
AdvancedAnalysisProfile
AppID\{143925E1-D64C-11D1-89D6-00AA0064549F}
AppID\{F0B71F93-4081-11D6-807E-0010B5FA1373}
AppID\PSpiceExplorerServer.EXE
AppID\SimServer.EXE
Cadence.PSpice.IAASimMgrLink.16.2.0
Cadence.PSpice.IAAUIInterface.16.2.0
Cadence.PSpice.ISimMgrInterface.16.2.0
Cadence.PSpice.SimCtrl.SimObjSink.16.2.0
Capture.Application
Cct.Session
CLSID\{0EC2A139-5566-45F5-A8BB-D3FA4F84EC53}
CLSID\{1AF59124-B258-4BB9-A381-D70542EA4A95}
CLSID\{1EA3FAE8-7D33-427B-90DA-F66463937E1C}
CLSID\{1EBD9817-FBDF-47AF-9B59-3424479A1A60}
CLSID\{2D18123B-8A47-457F-9C26-9568E937907D}
CLSID\{3FEAEC08-6D00-4C82-B24E-902E7F39D4A2}
CLSID\{4B99ECA9-69B0-4A19-80D6-32858B24AFDA}
CLSID\{5D8F834D-20BC-4125-B84B-B8B4157C5A52}
CLSID\{5D313287-2A4C-4FF1-BD72-63824D31D01D}
CLSID\{6E18101C-09E9-4625-ABC8-966A955B0087}
CLSID\{7E372B0C-266D-44F0-86C0-6C99B9409FF3}
CLSID\{9AA361C7-BA66-4A2C-9EE7-FBF86C6E03B1}
CLSID\{13E05AB5-3281-4B9E-A7B9-902168DCECB9}
CLSID\{35F9330E-9AA7-41D6-8DE0-5BD1E68ABC41}
CLSID\{39EFF241-8C46-4D6E-9B25-F314DD8B63CD}
CLSID\{46F07608-69C6-4F47-91E5-0B1F473D3112}
CLSID\{53A19BDB-3811-448A-B956-D292A8B25A32}
CLSID\{64A64D23-3028-44AF-9D56-5A616DD782DD}
CLSID\{77F2F20E-FE17-4314-BE4E-2C288BEBE760}
CLSID\{86EBCCB5-34AC-4DED-A20D-7EB667E1F921}
CLSID\{88EBA7F1-D232-4F60-B789-6162522C081C}
CLSID\{123C44B9-728B-404C-9275-A9AAFF4A2A70}
CLSID\{275DBBA0-805A-11CF-91F7-C2863C385E30}
CLSID\{381E56B9-317F-4643-B6A9-EBBE43E3270C}
CLSID\{400C7D99-73C1-4C93-95B8-62B4B644CCA7}
CLSID\{599A5F07-F7A9-4F54-99D3-692CDB64C3AD}
CLSID\{693AD293-CBDE-4DCC-99FF-F22989123549}
CLSID\{762EE862-0D08-446F-8FBD-02540681D47C}
CLSID\{935D3DC1-5C39-44EA-9816-1E58F9F51CB5}
CLSID\{1744EAD4-78AB-4080-B5BC-F2FED1DA8D6D}
CLSID\{4066E397-AC89-4FDE-9227-59040D2D57DC}
CLSID\{6262D3A0-531B-11CF-91F6-C2863C385E30}
CLSID\{6319EEA0-531B-11CF-91F6-C2863C385E30}
CLSID\{8263AE65-4BA0-4626-ACC2-DDEFCDC24E75}
CLSID\{641203DD-660A-484A-AA5E-D559F2AACFA6}
CLSID\{A0E7A965-300B-48C9-AA91-632D254807F4}
CLSID\{AE00EA34-FEC5-4B04-A1D0-12CC2E4103F4}
CLSID\{B2C37C52-83CA-462E-8E14-63AB91605303}
CLSID\{B486B1E7-1D3B-4698-A727-CE81F4C40884}
CLSID\{B7481715-0C34-4E12-97A5-27AA71D87107}
CLSID\{BC864E69-6976-4C87-853C-E74E0A608AED}
CLSID\{C1CA1658-BD41-4268-8A34-1BFFE5FFCD74}
CLSID\{C726B724-C00F-4ABC-AEA4-E75ACCA90C07}
CLSID\{CD2425E4-8141-11D0-8CE4-444553540000}
CLSID\{D1FEFC21-CFDC-4D10-961D-E9CE758AAFBD}
CLSID\{DB2D5854-0B7A-468D-8E7F-1F328DD4D4A9}
CLSID\{E1D8BDD8-1437-417B-B671-614128A1903E}
CLSID\{E7F8FBD3-8987-4C57-8EB1-732EE22F2C3B}
CLSID\{E108D664-A9F0-4455-8A39-15B1EFA2FDB4}
CLSID\{EAA07A1E-F355-4CC3-8695-BF81E5D3D61B}
CLSID\{EB0DEA2E-EF40-44CD-A2B0-2B66C03C3762}
CLSID\{EC1CA5E8-3989-43C0-AD43-24DB7C62021F}
CLSID\{EE7A85F5-0F0C-46E7-979B-D67757C931DD}
Interface\{0F59278B-CD59-467C-AD93-F8056683F480}
Interface\{2DF7AE20-1992-4353-ACDC-3429F92923C2}
Interface\{4F4BBC4A-9720-42EC-9072-A41FA48F370A}
Interface\{5F4DF280-531B-11CF-91F6-C2863C385E30}
Interface\{7AAC3B41-38A6-4261-9493-05FA6AC4719A}
Interface\{8FDCF0F5-C3F9-4225-B013-87E11B317501}
Interface\{9F6AA700-D188-11CD-AD48-00AA003C9CB6}
Interface\{462CB6D0-F3DC-11D3-960A-006008938C82}
Interface\{462CB6D1-F3DC-11D3-960A-006008938C82}
Interface\{462CB6D2-F3DC-11D3-960A-006008938C82}
Interface\{462CB6D3-F3DC-11D3-960A-006008938C82}
Interface\{462CB6D4-F3DC-11D3-960A-006008938C82}
Interface\{462CB6D5-F3DC-11D3-960A-006008938C82}
Interface\{462CB6D6-F3DC-11D3-960A-006008938C82}
Interface\{462CB6D7-F3DC-11D3-960A-006008938C82}
Interface\{462CB6D8-F3DC-11D3-960A-006008938C82}
Interface\{462CB6D9-F3DC-11D3-960A-006008938C82}
Interface\{483B75C1-95E5-46DB-9DB1-B5B018834443}
Interface\{563BC8E4-C6A4-47D1-86A2-CABDF35473ED}
Interface\{2334D2B1-713E-11CF-8AE5-00AA00C00905}
Interface\{2334D2B3-713E-11CF-8AE5-00AA00C00905}
Interface\{3489C1EF-D65F-411C-A959-5288178D9550}
Interface\{4594A153-4C85-49F2-B987-B2413479AEDD}
Interface\{4729DE68-788D-451A-AEFE-FCBA76FF6FAA}
Interface\{5850AFA1-58D8-4C6C-9CDE-68CBED290B4D}
Interface\{20370F9C-8DAF-411A-A780-907A65C649C2}
Interface\{98845E9F-830E-46AD-9A81-713B664C5A4B}
Interface\{609602E0-531B-11CF-91F6-C2863C385E30}
Interface\{649738C3-4AFB-4B4B-A432-D548FC795C8F}
Interface\{3719615C-3BFA-4AE5-9BE5-9406E0C2632F}
Interface\{3859326D-78E8-49EB-B7F1-7ED512D1C299}
Interface\{BDB99EC0-9B0B-4C6D-AB55-F770224590EC}
Interface\{C27220E4-ACBE-4552-B15C-B16653129E45}
Interface\{D6D6240C-2BEC-49CB-B5D6-1E1C611E4037}
Interface\{E04FEE7C-98D7-4641-95D7-4DE62767ADC0}
Interface\{E50AF054-4CD2-4A27-9F86-C01FBC5807C2}
Interface\{EFA757A6-A142-4C70-B47B-DDCA1419750F}
Interface\{F7ED2028-4329-40C2-BA2C-C8C3B2107FE5}
LAYOUTREUSE.LayoutReuseCtrl16.2.0
MECEdit.Document
MSFlexGridLib.MSFlexGrid
MSFlexGridLib.MSFlexGrid.1
OrCAD.Capture.OrEditorSpecificProjectManager
OrCAD.Capture.OrEditorSpecificProjectManager.16.2.0
OrCAD.Capture.OrEditorSpecificSchematic
OrCAD.Capture.OrEditorSpecificSchematic.16.2.0
OrCAD.CSPlugin
OrCAD.CISPlugin.16.2.0
OrCAD.CISPlugin.EventInterestProjectManager
OrCAD.CISPlugin.EventInterestProjectManager.16.2.0
OrCAD.CISPlugin.EventInterestSchematic
OrCAD.CISPlugin.EventInterestSchematic.16.2.0
OrCAD.CISPlugin.UIAdvise
OrCAD.CISPlugin.UIAdvise.16.2.0
OrCAD.EvalGoalFunction.16.2.0
OrCAD.FPGAPlugin
OrCAD.FPGAPlugin.16.2.0
OrCAD.FPGAPlugin.CustomItemProfileProjectManager
OrCAD.FPGAPlugin.CustomItemProfileProjectManager.16.2.0
OrCAD.FPGAPlugin.MenuAdditionsProfile
OrCAD.FPGAPlugin.MenuAdditionsProfile.16.2.0
OrCAD.FPGAPlugin.ToolbarAdditionsProjectManager
OrCAD.FPGAPlugin.ToolbarAdditionsProjectManager.16.2.0
OrCAD.OrCustomCapture
OrCAD.OrCustomCapture.16.2.0
OrCAD.OrPSpiceVersionInfo.16.2.0
OrCAD.PSpiceAdvancedRun.16.2.0
OrCAD.PSPICEEXPLORERSRVR
OrCAD.PSPICEEXPLORERSRVR.16.2.0
OrCAD.PSpiceIpcLink.16.2.0
OrCAD.PSpiceMeasurements.16.2.0
OrCAD.PSpicePlugin
OrCAD.PSpicePlugin.16.2.0
OrCAD.PSpiceUserInterface.16.2.0
OrCAD.PSpiceUserInterfaceNotify.16.2.0
OrCAD.SimObj
OrCAD.SimObj.16.2.0
OrCAD.SimObjSink.16.2.0
OrcadDesign-FileType
OrcadLibrary-FileType
OrcadProject-FileType
OrCADPSpiceAD10.5.0.dat
piCIS.CisAutomation
piCIS.CisAutomation.1
PSpice.RegUpdateTest\TEST
PXLLITE.BackAnnotationPropPage16.2.0
PXLLITE.NetlistCtrl16.2.0
TRUEREUSE.TrueReuseCtrl16.2.0
Verilog-FileType
VHDL-FileType


The install does not create the "%ProgramFiles%\Cadence Switch Release" folder required for "Cadence Switch Release" (shortcut)
so you need to create that.

* Set permissions for the Build-in "Users" group
SetACL.exe -on "%SystemDrive%\OrCAD_Data" -ot file -actn ace -ace "n:S-1-5-32-545;p:change;s:y"
The "%SystemDrive%\OrCAD_Data" (C:\OrCAD_Data) is the "Workingdir" which was entered during the install response file generation.
SetACL.exe -on "%ProgramFiles%\Cadence\OrCAD_Demo" -ot file -actn ace -ace "n:S-1-5-32-545;p:change;s:y"
SetACL.exe -on "%ProgramFiles%\Cadence Switch Release" -ot file -actn ace -ace "n:S-1-5-32-545;p:change;s:y"


* Reboot required
Don't know why the different applications didn't work after starting before a reboot; you get a lot of missing DLLs, crashes and so on.
A reboot did get everything working, I just couldn't find out why it was required as nothing related to OrCAD was changed after the reboot which was quite annoying.



* Uninstall
Note: to create the uninstall response-file use setup.exe -uninst /r

setup.exe -s -f1"<full path to unsetup.iss>" -SMS -uninst

* Clean-up
(remove the below folders if exists)
"%ProgramFiles%\Cadence\OrCAD_Demo"
"%ProgramFiles%\Cadence Switch Release"
(remove the below folders if empty so no other Cadence products exists in this folder)
"%ProgramFiles%\Cadence"

Delete the imported registry
Note: I decided not to delete the imported ".dat" registry but just to do a quick-fix.
REG ADD "HKLM\SOFTWARE\Classes\.dat" /ve /d "" /f
REG DELETE "HKLM\SOFTWARE\Classes\.dat\ShellNew" /f



Hope that helps.
Answered 07/07/2010 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity