Miranda NG Official Community Forum
Forum for English speaking Miranda NG users => Support/Help => Topic started by: wor123 on 19 01 2015, 01:20:42
-
I've noticed that every time I turning on my computer, when Miranda NG loaded, it don't automatically login into my accounts, and that I've needs to do this manually. Miranda NG setted to login automatically at startup.
My current Miranda NG version: v0.95.4 alpha build #11871.
Why this is happening.
-
You need either KeepStatus (http://wiki.miranda-ng.org/index.php?title=Plugin:KeepStatus/en) or StartupStatus (http://wiki.miranda-ng.org/index.php?title=Plugin:StartupStatus/en) plugin. I prefer the former - it's more functional.
-
I've KeepStatus plugin, but it don't works when Miranda NG loaded at startup, until I login manually.
-
wor123, because keepstatus is for reconnecting. Use startupstatus or just set global status (from tray icon) to online - this will work as well.
-
I have KeepStatus, and it always keep me connected. Regardless of circumstances.
-
AnrDaemon, KeepStatus does not connect you on Miranda start, you may think that it does, but it's not. You may have just set global status online.
-
Rather, I never set it offline. KeepStatus tracking the changes to protocol statuses and only stop reconnecting, if the change was manual.
-
AnrDaemon, once again - keepstatus DOES NOT set Miranda statuses online on start - stop misinforming other users.
-
I know it doesn't do that. However, it will keep trying to restore last manually set status. Which, in my case, amounts for the same effect.
-
NO!!! You are not right. Keepstatus doesn't restore last status at startup. it restore connection when it lost it.
-
Where in my posts do you see "last status" ?
I specificaly said "last manually set status". And it doesn't do that on startup, it do that continuously, regardless of the startups.
-
coz this topic about Windows startup and you write that for you keepstatus doing something, it is not right. If so you can write here about tabsrmm for example...
-
May be you could stop trying to disapprove so fervently, and start reading?
I'll try to explain it very slow.
1. Miranda startup has nothing to do with Windows startup. It don't know, neither care, if the system was just started, or was running for weeks.
2. KeepStatus has nothing to do with setting protocol status on Miranda startup. KeepStatus doing exactly what is implied from the name. It is trying to keep last manually set status for selected protocols. If that means changing their status, it will do so.
3. When Miranda shutdown (manually, or due to closed user session), the status change is not recognized as manually set, even though Miranda will try to set all protocols offline before exit.
4. When you next start Miranda, it will try to set protocols to a last known status once. By itself. Or at least that was the behavior back in the days.
5. Regardless of that happening, KeepStatus will check protocols and try to restore their status. Continuously.
-
4. When you next start Miranda, it will try to set protocols to a last known status once. By itself. Or at least that was the behavior back in the days.
It does not do that. Startupstatus does exactly that.
-
ahaha)))
for what you write about keepstatus here?
for protocol connection on startup you should use StartupStatus plugin or use global status. You don't know how miranda work...
-
I downloaded StartupStatus, and setted my protocols to connected. I hope that this will solve the problem.
-
ahaha)))
for what you write about keepstatus here?
For you to stop putting your words into my mouth. And to stop arguing about things you don't know.
for protocol connection on startup you should use StartupStatus plugin or use global status. You don't know how miranda work...
It does not do that. Startupstatus does exactly that.
Let's take this to real ground.
Fresh downloaded Miranda from official site (portable 32-bit installation).
VersionInfo
CPU: Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz [x86 Family 6 Model 58 Stepping 9] [DEP Enabled]
Installed RAM: 2048 MBytes
Operating System: Microsoft Windows XP Professional Service Pack 3 (build 2600)
Internet Explorer: 8.0.6001.18702 (build 86001)
Administrator privileges: Yes
OS Languages: (UI | Locale (User/System)) : Russian/Russian | Russian/Russian
Free disk space on Miranda partition: 1679 MBytes
Miranda NG Version: 0.95.3 build #11706
Build time: 1 Jan 2015 17:15:52
Profile: C:\Documents and Settings\anrdaemon\Мои документы\miranda-ng-v0.95.3\Profiles\Daemon\Daemon.dat
Profile size: 131072 Bytes
Profile creation date: 20 Jan 2015 14:56:01
Language pack: No language pack installed
Service Mode: No
Active Plugins (12):
AdvaImg.dll v.0.11.0.1 [1 Jan 2015 17:08:36] - Miranda image services
AVS.dll v.0.95.3.4 [1 Jan 2015 17:07:38] - Avatar service
CrashDumper.dll v.0.0.5.2 [1 Jan 2015 17:11:16] - Crash dumper
DbChecker.dll v.0.95.3.1 [1 Jan 2015 17:11:32] - Database checker
Dbx_mmap.dll v.0.95.3.1 [1 Jan 2015 17:07:43] - Miranda NG mmap database driver
ICQ.dll v.0.11.2.6 [1 Jan 2015 17:08:23] - IcqOscarJ protocol
Import.dll v.0.95.3.4 [1 Jan 2015 17:07:38] - Import contacts and messages
IRC.dll v.0.11.0.2 [1 Jan 2015 17:08:13] - IRC protocol
Jabber.dll v.0.11.0.4 [1 Jan 2015 17:08:32] - Jabber protocol
PluginUpdater.dll v.0.1.2.4 [1 Jan 2015 17:11:48] - Plugin updater
TabSRMM.dll v.3.4.0.7 [1 Jan 2015 17:07:55] - TabSRMM
TopToolBar.dll v.0.8.0.4 [1 Jan 2015 17:10:14] - TopToolBar
Protocols and Accounts:
-------------------------------------------------------------------------------
ICQ 0 - Enabled 0 - Disabled Loaded
IRC 0 - Enabled 0 - Disabled Loaded
JABBER 1 - Enabled 0 - Disabled Loaded
MetaContacts 1 - Enabled 0 - Disabled Loaded
Icon Packs:
-------------------------------------------------------------------------------
Proto_AIM.dll [1 Jan 2015 17:10:17]
Proto_Facebook.dll [1 Jan 2015 17:10:15]
Proto_GG.dll [1 Jan 2015 17:10:17]
Proto_ICQ.dll [1 Jan 2015 17:10:18]
Proto_IRC.dll [1 Jan 2015 17:10:18]
Proto_Jabber.dll [1 Jan 2015 17:10:19]
Proto_MetaContacts.dll [1 Jan 2015 17:14:59]
Proto_MSN.dll [1 Jan 2015 17:10:19]
Proto_Yahoo.dll [1 Jan 2015 17:10:21]
TabSRMM_icons.dll [1 Jan 2015 17:12:05]
Toolbar_icons.dll [1 Jan 2015 17:10:22]
xStatus_ICQ.dll [1 Jan 2015 17:08:36]
xStatus_Jabber.dll [1 Jan 2015 17:08:37]
Start, configure one protocol, set global status to N/A through system tray icon.
Close, open - status - N/A.
Disconnect the cable. Miranda goes offline. Close Miranda.
Connect the cable. Start Miranda. Status? You guess. N/A.
Set protocol status to Online. Exit - start - status - N/A. Predictable, if you think about it for a moment. We didn't change global status.
Let's add KeepStatus to the mix.
VersionInfo
CPU: Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz [x86 Family 6 Model 58 Stepping 9] [DEP Enabled]
Installed RAM: 2048 MBytes
Operating System: Microsoft Windows XP Professional Service Pack 3 (build 2600)
Internet Explorer: 8.0.6001.18702 (build 86001)
Administrator privileges: Yes
OS Languages: (UI | Locale (User/System)) : Russian/Russian | Russian/Russian
Free disk space on Miranda partition: 1679 MBytes
Miranda NG Version: 0.95.3 build #11706
Build time: 1 Jan 2015 17:15:52
Profile: C:\Documents and Settings\anrdaemon\Мои документы\miranda-ng-v0.95.3\Profiles\Daemon\Daemon.dat
Profile size: 131072 Bytes
Profile creation date: 20 Jan 2015 14:56:01
Language pack: No language pack installed
Service Mode: No
Active Plugins (13):
AdvaImg.dll v.0.11.0.1 [1 Jan 2015 17:08:36] - Miranda image services
AVS.dll v.0.95.3.4 [1 Jan 2015 17:07:38] - Avatar service
CrashDumper.dll v.0.0.5.2 [1 Jan 2015 17:11:16] - Crash dumper
DbChecker.dll v.0.95.3.1 [1 Jan 2015 17:11:32] - Database checker
Dbx_mmap.dll v.0.95.3.1 [1 Jan 2015 17:07:43] - Miranda NG mmap database driver
ICQ.dll v.0.11.2.6 [1 Jan 2015 17:08:23] - IcqOscarJ protocol
Import.dll v.0.95.3.4 [1 Jan 2015 17:07:38] - Import contacts and messages
IRC.dll v.0.11.0.2 [1 Jan 2015 17:08:13] - IRC protocol
Jabber.dll v.0.11.0.4 [1 Jan 2015 17:08:32] - Jabber protocol
KeepStatus.dll v.0.9.0.2 [1 Jan 2015 15:09:26] - Keep status
PluginUpdater.dll v.0.1.2.4 [1 Jan 2015 17:11:48] - Plugin updater
TabSRMM.dll v.3.4.0.7 [1 Jan 2015 17:07:55] - TabSRMM
TopToolBar.dll v.0.8.0.4 [1 Jan 2015 17:10:14] - TopToolBar
Protocols and Accounts:
-------------------------------------------------------------------------------
ICQ 0 - Enabled 0 - Disabled Loaded
IRC 0 - Enabled 0 - Disabled Loaded
JABBER 1 - Enabled 0 - Disabled Loaded
MetaContacts 1 - Enabled 0 - Disabled Loaded
Icon Packs:
-------------------------------------------------------------------------------
Proto_AIM.dll [1 Jan 2015 17:10:17]
Proto_Facebook.dll [1 Jan 2015 17:10:15]
Proto_GG.dll [1 Jan 2015 17:10:17]
Proto_ICQ.dll [1 Jan 2015 17:10:18]
Proto_IRC.dll [1 Jan 2015 17:10:18]
Proto_Jabber.dll [1 Jan 2015 17:10:19]
Proto_MetaContacts.dll [1 Jan 2015 17:14:59]
Proto_MSN.dll [1 Jan 2015 17:10:19]
Proto_Yahoo.dll [1 Jan 2015 17:10:21]
TabSRMM_icons.dll [1 Jan 2015 17:12:05]
Toolbar_icons.dll [1 Jan 2015 17:10:22]
xStatus_ICQ.dll [1 Jan 2015 17:08:36]
xStatus_Jabber.dll [1 Jan 2015 17:08:37]
Basic setup to enable it (it is not enabled by default) - values are very low for testing purposes, I do not recommend doing it for production setups:
- Check connection; 0 retry; 10 delay
Select the account you have configured.
Dialup functions disabled.
Advanced setup:
All disabled except - Set account to offline before connection attempt.
Disconnect cable. Miranda goes offline. Connect cable. After 15-20 sec, Miranda spring online with the same N/A status.
Change protocol status to online. Disconnect cable. Miranda goes offline. Connect cable. After 15-20 sec, Miranda spring online with Online both global and protocol statuses.
I didn't touch the global status. I think this a bug in KeepStatus protocol, that I didn't find earlier, since I hardly ever use separate account statuses. But this is debatable in case of a single protocol. Should Miranda reflect the status of its only configured protocol in global status?
-
AnrDaemon, question is - why are you suggesting keepstatus to people that want auto-login on miranda startup? It is totally wrong.
-
KeepStatus is for reconnecting accounts, StartupStatus is for connecting accounts on Miranda start. For bugs there is a bug tracker. This topic is closed.
-
AnrDaemon, question is - why are you suggesting keepstatus to people that want auto-login on miranda startup? It is totally wrong.
I actually understood him. You need no "StartupStatus" to make your Miranda connect at startup. Miranda does that automatically in a way that when you set global status before exitting, Miranda will set this last used global status automatically at next start.
I'm not sure about this particular user who started this thread, but common problem is this:
a) When your Miranda is started at windows startup, occasionally you may not have internet connection yet (Miranda started too quickly before system started connecting), so Miranda automatically setting last status will fail immediatelly because no internet connection. And it won't try to connect again when you have internet connection back.
b) Similar thing is when hibernating your computer. Miranda sometimes reconnect automatically after waking up computer from hibernation and sometimes doesn't - I think it's same problem as (a).
As a result, you can use StartupStatus for this problem, BUT you need to start x seconds delay so you can except you'll have internet at that moment. But it's not correct solution for my issue above.
Better solution is KeepStatus which doesn't set Miranda status at startup, BUT it does Miranda itself (as stated above) so in case of failing (internet not available) KeepStatus just tries again and again after few seconds, which precisely solve this problem :-)
Conclusion: You both are right. Watcher responded exactly to OP's problem, but AnrDaemon correctly presented different solution from different point of view (which require correct use of global status, which user wasn't aware of or didn't worked for him in first place).