Cant bypass setupfile
Hi all
I have prob with Nero 7.
Everytime i try to start/launch the nero.msi, its says, " the installer has to be started with SetupX.exe file.
Second if i try to use the setupx.exe file and run it silent , = path\setupx.exe /qb ADDLOCAL="ALL"
it start to install, but in the end it popup, and says dll faild to register.
The 2 dll´s which failed to register is :
Program files\common files\ahead\lib\Nero3DMenuEffects.dll
AND
Program files\common files\ahead\lib\NSG_dxFilter.dll
Can anyone tell how to fix above probs.
thnx
I have prob with Nero 7.
Everytime i try to start/launch the nero.msi, its says, " the installer has to be started with SetupX.exe file.
Second if i try to use the setupx.exe file and run it silent , = path\setupx.exe /qb ADDLOCAL="ALL"
it start to install, but in the end it popup, and says dll faild to register.
The 2 dll´s which failed to register is :
Program files\common files\ahead\lib\Nero3DMenuEffects.dll
AND
Program files\common files\ahead\lib\NSG_dxFilter.dll
Can anyone tell how to fix above probs.
thnx
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
India_Repackaging
13 years ago
Hi Kashif,
Kindly take a verbose log of the installation and chekc which CA is related to the setupX.exe I suspect. I have not worked on Nero however I suggest you can manually capture the registry information and of the two .dll files and subsequently remove the entries of the files from the SelfReg table.
Kindly take a verbose log of the installation and chekc which CA is related to the setupX.exe I suspect. I have not worked on Nero however I suggest you can manually capture the registry information and of the two .dll files and subsequently remove the entries of the files from the SelfReg table.
Posted by:
SKS
13 years ago
Hi Rajit
I will try to make a verbose log and see what happens. I think that i will be able to capture the dll entry , but the prob is also that i cant run it, the msi with mst.
I will try and get back with info.
I will try to make a verbose log and see what happens. I think that i will be able to capture the dll entry , but the prob is also that i cant run it, the msi with mst.
I will try and get back with info.
Posted by:
anonymous_9363
13 years ago
As is often the case, there's plenty of help already on AppDeploy http://itninja.com/link/techical-guide:-silent-install-for-storagecentral-srm-5.07
Posted by:
SKS
13 years ago
I have been through the link u sent, but nothin helped, so thts why i posted it in the forum.
Posted by:
SKS
13 years ago
1) i am just saying that it didnt worked for me, maybe i did somethin wrong.
2) who said about everyone was wrong, dont say somethin which i didnt said.
3) Thnx for ur info
/sks
2) who said about everyone was wrong, dont say somethin which i didnt said.
3) Thnx for ur info
/sks
Posted by:
India_Repackaging
13 years ago
Hi Kashif,
I think that one must mention all things that he/she tries before they post, so people on the forum can suggest other things that could be done.
Anyways, I had suggested to create a verbose log file. Analyse the log file for any CAs that do call the setup file. You can also search for the term 'Return Value 3' related to CAs which signify if the CA has failed. I dont know if this could be the case with your package (but you can always give it a shot).
Also as I had suggested earlier you can manually add the captured registries from the dll files explicitly to the mst by adding a new component or adding to an already existing one. Manually registries can be captured your the WiseComCapture tool shipped with Wise.
I think that one must mention all things that he/she tries before they post, so people on the forum can suggest other things that could be done.
Anyways, I had suggested to create a verbose log file. Analyse the log file for any CAs that do call the setup file. You can also search for the term 'Return Value 3' related to CAs which signify if the CA has failed. I dont know if this could be the case with your package (but you can always give it a shot).
Also as I had suggested earlier you can manually add the captured registries from the dll files explicitly to the mst by adding a new component or adding to an already existing one. Manually registries can be captured your the WiseComCapture tool shipped with Wise.
Posted by:
SKS
13 years ago
Hi mate
I logged the installation, and it was a CA, so now i can bypass the setupx.exe file
about the registry, i have capture that, will get back to u laterz, with the result, just have to test it.
/sks
I logged the installation, and it was a CA, so now i can bypass the setupx.exe file
about the registry, i have capture that, will get back to u laterz, with the result, just have to test it.
/sks
Posted by:
anonymous_9363
13 years ago
OK, so 1) it would have saved some time if you'd said that; 2) have you tried ALL the methods in the various notes and 3) is it possible that EVERYONE who specified the DONOTRUNSETUPX="1" and/or STARTPARAM="CallFromExe" is wrong?
I don't think it's unreasonable to assume that, since the last entry in the KB was over 2 years ago, the contents are good.
As per Duncan Ballantyne, "Ahm oot."
I don't think it's unreasonable to assume that, since the last entry in the KB was over 2 years ago, the contents are good.
As per Duncan Ballantyne, "Ahm oot."
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.