catalinb

Member
  • Content count

    3
  • Joined

  • Last visited

About catalinb

  • Rank
    Newbie

Contact Methods

  • ICQ
    0
  1. You are right about this, with right click, and Run as administrator is the solution . But now, my question is: If i am the only user, logged with an administrator account, and when i start apex 1.1.0 , as well as ALL other programs i run from my desktop, UAC ( user account control) is asking me if i allow this program to run. Since 1.2.0, in vista , with the usual left double click , apex is not running with admin rights. Apex is the only program from my desktop not starting with full permissions, for this reason at first i excluded the permissions cause. Isn't this setting of the new apex a little unusual? For apex, all program developers deserve congratulations, i use apex frequently and "it's not bad at all"! Thank you for your support Crise!
  2. if you want to see for yourself how bad it is, i invite you to see in real time how apex works for me , you can contact me to catalinbombea@yahoo.com , and i will give you acces through teamviewer. My location is in Romania, so we have to schedule a teamviewer session. I have the same settings i had for apex 1.1.0, my connection is active, (firewall with upnp), search is working well.I atach 2 print screens with my advanced settings. The strangest thing is that if i uninstall apex 121, install it again, download and everything is working perfect till i quit current session. Next time i sstart a session, download is not working, it is starting and finishing in a continuous loop for the same file . Please contact me at undefined
  3. Same problem here! I have two laptops with Vista.With 1.1.0 there was no problem. When 1.2.0 was released, i upgraded, but the problem started.I downgraded back to 1.1.0, used it whithout problem, but at the release of 1.2.1 the problem with "download starting and finished" is back. Question: Why are you forcing users to upgrade to 1.2.1? I cannot return to 1.1.0, the working version for Vista! Please fix this issue, my only option now is to quit using Apex.