This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Slient & Console mode installer on MACOS X
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Jan 06, 2009
06:07 AM
Slient & Console mode installer on MACOS X
Hi,
I was trying to execute an installer created by installanywhere 2008 to run in silent and console mode on Macos platform. But it seems it doesn't work
please anyone can confirm whether silent and console mode installers created by installanywhere are supported by MAC OS or not.
thanks
Malkesh
I was trying to execute an installer created by installanywhere 2008 to run in silent and console mode on Macos platform. But it seems it doesn't work
please anyone can confirm whether silent and console mode installers created by installanywhere are supported by MAC OS or not.
thanks
Malkesh
(1) Reply
Jan 06, 2009
10:10 PM
hi malkesh123,
To the best of my knowledge, the console and silent installers still faces some issues on the MAC OS. However the GUI mode is working fine.
Can you please post us the exact issues that you are facing. We would need the following things.
1) The steps used to reproduce this issue.
2) The exception traces if any.
3) Please capture the stdout and stderr by redirecting to a file.
4) Also in Project > Config (JAva VM arguements), Please pass the following arguements
-Dlax.debug.all=true -Dlax.debug.level=3
5) This would generate a more complete stderr file.
Thanks,
Jiju
To the best of my knowledge, the console and silent installers still faces some issues on the MAC OS. However the GUI mode is working fine.
Can you please post us the exact issues that you are facing. We would need the following things.
1) The steps used to reproduce this issue.
2) The exception traces if any.
3) Please capture the stdout and stderr by redirecting to a file.
4) Also in Project > Config (JAva VM arguements), Please pass the following arguements
-Dlax.debug.all=true -Dlax.debug.level=3
5) This would generate a more complete stderr file.
Thanks,
Jiju