[Aficionado]

Dear all,

It is a known fact that though useful to clear redundant notifications, the ScaryBear combo of:
1) ScaryBear Clear Notification Fix and
2) ScaryBear Check Notification,
especially the latter allows u to delete whole notifications completely, despite some of which are ill-advised to do so :omg:.

This is especially so for the notification event, 'repllog.exe', which tells your desktop serial device driver to look out for an incoming RS232 cable = time to ActiveSync. Still, some bros/sisters unknowingly deleted this and were consequently unable to ActiveSync with their desktop = hard-reset.

Fret not, for those bros/sisters with itchy fingers while using the ScaryBear Combo, Bro fattyfattybombom has conjured up a workable method (LINK: CLICK ME), which I'll now help to surmise.

How to ActiveSync again after deleting the notification event 'repllog.exe':
Phase #1: (Force a one-time sync)
1) Connect your device to your desktop (doesnt matter if your ActiveSync is dead).
2) Press-and-hold the 'Action' hardware button.
3) Tap the clock at the top-taskbar.
4) Release stylus and button.
5) Under the popup menu, select 'Run'.
6) Type in: \windows\repllog.exe
Note:
- Conversely, for Step #2 to Step #6, u can tap on the repllog.exe in your '\Windows\' folder.

Phase #2: (Create a new notification queue event)
1) U'll need to install shareware 'MemMaid by DinarSoft', which has a option of creating new notification event (doesnt matter if u just use the trial version).
2) Open 'MemMaid' and go to the 'Notification Queue' tab (i.e. 2nd tab).
3) Tap the icon 'Add...'.
4) Under the 'Add Notificaion>Program' field, tap on the '...' icon.
5) Under the folder tree, scroll to \windows\repllog.exe and tap on it.
6) Under the 'Add Notificaion>Event' field, select ' An RS232 connection was made'.
7) Tap on the 'Add' icon.
8) Exit the program and soft-reset your device.
9) ActiveSync as normal.

Hope this can help save some bros/sisters from hard-resetting their devices after ScaryBear accidents. Thanks to Bro fattyfattybombom again.

:smile:.

[dsclaymr]

Thanks man, you saved me from another hard reset!

Ok, but the same problem came back!
Scarybear worked well on my 6960 for the 1st day.
Then on the 2nd day, I did the same thing and it deleted some events NOT marked in red!
I could not sync anymore and had to do the above.

I just tried to run Clear Notifications again - I made sure the 2 boxes were ticked.
And I saw about 20 notifications (2 in red).
When I clicked claer - it cleaned out those even in black and left me with only 7 notifications.

LtoManager
calipd
clock
clock
repllog
CALENDAR
TimeChangeEvent

All the rest were cleared!
And I could not sync! AGAIN!

Can anyone help to explain why is this happening?
I installed Scarybear in my storage card.

TIA!

[dsclaymr]

Sorry guys, one more query.

I am on a mac and uses missing sync. Can anyone advice on how to revive the sync?

Thanks again!

[Wongster]

Hi, dsclaymr,

Did you manage to find a solution?

I hard resetted my 838pro and it worked well for a day till I use scarybear again. The 2 checkboxes were checked but all notifications were cleared!!! :confused:

Looks like I've to do another hard reset.... :cry:

[dsclaymr]

I followed the steps above.
Then I removed my Missing Sync (using Remove Programme).
So the next time I connected to my Mac, Missing Sync was reinstalled.
Everything was ok.

As what you did, I tried to reinstall Scary Bear, check the 2 boxes and did a scan and clear -> The BLOODY same thing happened! All my notifications were deleted (less the 7 mentioned above)!

Re-did the above and gave up on Scary Bear.
Now using Memmaid. No problem for the past 3 days
But I think after 15 days, I'll have to buy it (trial will expire).

Hope I answered your question.
And I still do not know why Scary Bear behaved that way, even when I installed it in my device rather than the storage card.

Cheers!

[Wongster]

Thanks. Scarybear scares me... I give up...

One thing I realised after using memmaid. I've never encounter any duplicated notifications though scarybear flagged out quite a few.

I'm going to leave it alone for a while till better solutions appear.

[Dumblord]

Hi Wongster and dsclaymr, you are advised not to check the box for removing duplicate notifications. If you do that, it will delete some of the other notifications that are needed by your device to sync properly. Example is the repllog.exe. There are actually 4 of such and out of that 2-3 of it is needed to sync with AS. Checking the remove duplicate box might cause them to be deleted and thus unable to sync with AS.

[dsclaymr]

Really???

I read in the older threads that we are supposed to do that.
Hence all the heartaches!
Sigh...

At least there is an alternative now to paying for memmaid

Thanks Dumblord!

This post has been edited by dsclaymr: 23 May 2007 - 08:12 PM

[Dumblord]

dsclaymr, on May 23 2007, 08:11 PM, said:

Really???

I read in the older threads that we are supposed to do that.
Hence all the heartaches!
Sigh...

At least there is an alternative now to paying for memmaid

Thanks Dumblord!

No problem bro. It is recommended when using wm2003, however, in wm5, such a problem exists.

[g3r41d]

Ok. Something to add on to this wonderful thread that helped me get back my syncing capabilities.

There are 2 repllog.exe notification entry that is required for you to do syncing.

1) repllog.exe
When: An RS232 connection was made.
Argument: AppRunAtRs232Detect

2) repllog.exe
Argument: AppRunAfterRndisFnDetected

If you deleted the repllog.exe (AppRunAfterRndisFnDetected) entry, please do the following:

You will need to create this item in notification by running FixASRunAt.exe on your ppc from the link below

http://www.cs.pitt.e.../FixASRunAt.zip

This will create the repllog.exe with AppRunAfterRndisFnDetected item in your notification queue. Use your memmaid to check that this entry is recreated.

Information obtained from http://www.cs.pitt.e...ry051203-201515

For the repllog.exe (AppRunAtRs232Detect), you can manually enter the repllog.exe (AppRunAtRs232Detect) using memmaid using the method described by Aficionado in phase 2.