Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

kalavera

Member
  • Content Count

    79
  • Joined

  • Last visited

  • Donations

    $0.00 

Community Reputation

0 Neutral

About kalavera

Contact Methods

  • MSN
    kalavera@msn.com
  • Website URL
    http://
  1. I'm not 100% sure, but from the preliminar tests i have done ... only .msi has this problem, maybe because the way msiexec works. But like i told you ... not really sure of this. All the problems i had, was principally with .msi installations, and this fix was effective.
  2. And do you use runonceex to install your apps? Also i didnt told that winrar has any problem ... not at all. Its a general problem in sfx (7z or sfx) when executing the after extract command (they by default, dont wait to finish). Also i told that using Winrar sfx TempMode, winrar does this automatically, not needing to use "startx /w" for example. The reality is ... after changing the installers to use the technic i told, all worked perfect after that. No overlapping of running installers. And since this can be applied also to svcpack-able installers ... its a good practice to use it, since b
  3. This is not related with sfx. Its the "only-one instance" of WinRAR GUI option.
  4. After many time of workarounds and time spend in making windows installs, i have found the problem for some installations based on runonceex, not working 100%. I dont want to copy-paste the explanation, so i put a link to my post: http://www.msfn.org/board/index.php?s=&amp...st&p=558393 And from what i can see, many "runonceex-able" unattended installers aren't aware of this problem. So i ask to their makers, if they can apply the simple fixes i suggest in the post. In resume the solutions: 1 - Use WinRAR Sfx in TempMode, and then just call the command example: Setup=msistub.exe firef
  5. One again here i am But this time i found the problem and a solution. The problem: Like i thinked the problem is because of not waiting that the setup of a ware finishes before another one starts. Causing all the problems i mentioned, even the one with firefox. Its not a runonceex problem, because it always waits for the sfx to extract. The problem is inside the sfx. Also notices that there is no difference between having the items in runonceex, all in differente entries or using subcommands (like i used before). Searching this forums i found that someone had the same problem : http://www.ms
  6. But there isnt a way to create the shortcuts in All Users folder even during runonce? This way wouldnt be a problem. And about the add/remove entries ... its a normal behavior in your installers? Would be nice to have it. I dont like the svcpack method for applications :S So i have all my unattended apps installing in runonceex. Firefox keeps giving me that error and doesnt install :S A sidenote: why do you extract to %systemroot%\Installer instead of using TempMode from WinRAR sfx? For example using this sfx code : Setup=msistub.exe livemess.msi /qb TempMode Silent=1 Overwrite=1
  7. We were writing the reply and editing the post at the same time Please check the edit note in the previous post. Thanks. PS: Its not corporate version (i know it doesnt exists) ... just a modified version by me with some extra themes incorporated & tweaks.
  8. Hi ... thanks for the quick reply. I have tested again my runonceex, with those modifications you suggested (putting each ware in a different entry). The results continue ... none of your silent installers (live messenger or firefox) are installed. Maybe the problem is about the extraction to temp directory or something :S Also during firefox 1.5.0.7 installation there is an error popup "7-zip" "Can not delete output file".. Also note: now only this firefox error appears ... but messenger and firefox arent installed in the end! All the other ware's are installed correctly. But like i told in t
  9. I'm having problems with installing messenger during runonceex. I notice that if i put it before another installer (using also msi), your installer brokes the installation, because appears a message telling me that another install is in progress. Maybe you launch the installation of messenger but dont wait for it to finish, before continuing. This way the other installers crash. As a note, if i dont put your installer in my runonceex script, my installation is ok. Here it is a sample of my runonceex script: REG ADD %KEY%\011 /VE /D "Utilities Installation ..." /f REG ADD %KEY%\011 /V 1 /D "%CD
  10. Hi ZileXa, like you have found, the TileView "trick" is not done, or even possible to be used by a regtweak. I use a technic in .net to send a "change the desktop to a tileview" message. Currently is done by a timer (resending that message only when needed), since when the desktop needs to be refreshed, all changes done after that are lost. The deskview program is done in assembly win32 (xpize settings is done in .net 2.0), and uses a dll memory hack technic to implement the trick. About the transparency thing ... since xpizesettings also changed the icons desktop color, maybe this can be im
  11. Hi all. Sorry for the slow response. I have been very busy :S For the moment it isn't possible to do what you want. The settings are loaded based on the current user. So a Allusers approach isnt possible. If i have time, i can try to make a solution in this way: - if exists a XPizeSettings.AllUsers.dat, all other users settings will be ignored and those settings will be loaded. - i cant promise that it will work fully in a unattended environment (i'm thinking for example enabling autorun of xpizesettings, but i will take a look on it) Can't promise a timeline, but i will look for it soon. BTW:
  12. Strange ... since you are using the OS i also use ... i will try to investigate further this issue.
  13. I'm the creator of XPize Settings. Can you be more specific with the problems? what is the version of the program? OS? Its as been tested many times but in a 32-bit Windows Pro SP2. And since those features you mention are based on win32 system calls, maybe there is a OS incompatibility or something. A note ... some of the settings are just temporary (its a limitation of Windows), like the desktop view settings (tile, small icons, transparent background), so they need to be "refreshed" by enabled the choosen settings and the timer, and then keep running the program in the background. Sometimes
  14. New version of the same idea, a bit more "xpized"
×
×
  • Create New...