Well I eventually got around tidying up Who Sent It a bit and am now at a stage where it would be useful to get more people to test it.

It's a received file organiser, that by default just moves files into folders of the email address of the sender, but you can hard-code names instead.

In the future tags will be supported, eg for mongth etc.

Can't remember if file type filters are working, I'll test them later.

It's still an early version but let me know what you think.

Feedback/ideas etc etc welcome.

EDIT:  Updated to version 0.7.1

ChangeLog
0.7.1

• Moved code from Initalise to SigninReady, should fix problems for some users.
• Updated to use CreateHardLink API

Fehler: 'xniff' ist Null oder kein Objekt (Code: -2146823281)
       Datei: FileTransferLib.js. Zeile: 54.
Funktion OnEvent_SigninReady meldete einen Fehler. Code: -2147352567

--

Who Sent It? Debug
loading new xniff
new xniff success
GetIP
IP:  192.168.0.254
FileTransferInitialize
xniff.Start
Error in xniff.Start():   [object Error]

Sorting doesn't work here, no folders created, files still all in main folder.

quote:

---

Originally posted by mynetx
Who Sent It? Debug
loading new xniff
new xniff success
GetIP
IP:  192.168.0.254
FileTransferInitialize
xniff.Start
Error in xniff.Start():   [object Error]

---

Not at all.
I'm using Windows XP Home Edition SP2, 5.0.2600, and a version of Messenger Plus! Live bigger than 4.50.312 (public forums ).

mynetx: Register the Xniff.dll using regsvr32.

Xniff.ocx, you mean? Done, but after next script restart:

quote:

---

Originally posted by Debug
Who Sent It? Debug
loading new xniff
new xniff success
GetIP
IP:  192.168.0.254
FileTransferInitialize
xniff.Start
Error in xniff.Start():   [object Error]

---

quote:

---

Originally posted by vikke
mynetx: Register the Xniff.dll using regsvr32.

---

Is it a wireless network card you are using?

Its working fine here and i'm using windows vista. Suggestion: Know the viruses that say:

Check out my new pc.

Then sends a file?

Well what would be great is a protection that cancels all files that has one of the phrases before that.

Yes, wireless card => router => cable modem => web

quote:

---

Originally posted by john-t
Suggestion: Know the viruses that say:

Check out my new pc.

Then sends a file?

Well what would be great is a protection that cancels all files that has one of the phrases before that.

---

quote:

---

Originally posted by mynetx
Yes, wireless card => router => cable modem => web

---

code:

---

Script is starting
Script is now loaded and ready
Function called: OnEvent_Initialize


Who Sent It? Debug
loading new xniff
Error in new xniff:   [object Error]
Error registering xniff:   [object Error]
GetIP
Error in GetIP:   [object Error]
DoInit Returned Errors

Who Sent It Startup Failed
Function called: OnGetScriptMenu

---

xniff... so this won't work with wireless networks then

quote:

---

Originally posted by aNILEator
xniff... so this won't work with wireless networks then

---

quote:

---

Originally posted by Dempsey

quote:

---

Originally posted by aNILEator
xniff... so this won't work with wireless networks then

---

Yea it can do, depends on if its built-in or external and drivers used etc, my wireless works

---

I have a built-in wireless card

code:

---

Intel(R) Wireless WiFi Link 4965AGN

---

I'll test it when I get back within the next 2 hours. I'm on wired now, but I'll retest my wireless as I'm pretty certain it works with Xniff. Got some ideas to try out on it as well, but I'll just post this here to remind me what they are, and then I'll D/L this version to try them out in

We have to add each contact?

It would be nice if this plugin is activated, it does it itself.

No, it does one action by default, but you can still specify per contacts sorting methods if desired.

Xniff? ai... 

It has troubles with Vista and it contains a big bug where it will internally crash Plus!/Messenger on exit. See notes: CookieRevised's reply to [Release] Xniff (ActiveX Packet Sniffer) - Examples inside

And it does crash Messenger/Plus! internally when you try to update Plus!.

Also, when people have other scripts with Xniff, they can even get in trouble when they simply uninstall some of those scripts (since you can only register one file at the time. All other scripts will start using that file in the new location. Removing that file means that all other scripts will stop working and will produce errors).

And, what about: CookieRevised's reply to Protocol (Using Xniff)?

anyways, background reading material for people having problems:
Packet sniffer that supports all wirelless connections.


-----------------



As for the script (not considering the problems with Xniff itself).

The method for starting up is a faulty. So even if the rest of the script works 100% already, it wouldn't even start properly...

The error checks you do in OnEvent_Initialize aren't done in OnEvent_SignInReady. However, the checks in OnEvent_Initialize are not executed when the user starts Messenger (since he didn't signed in yet). For example DoInit is never called (unless the user installs or actually restarts the script while he is signed in), which is the most crucial function for this script.

Maybe you better put everything (all the error checking and initializing and calling DoInit) in OnEvent_SignInReady and simply direct OnEvent_Initialize to OnEvent_SignInReady (or don't even use OnEvent_Initialize since it makes no sense to use this script while you're signed out anyways).

thus:

quote:

---

Originally posted by Dempsey

quote:

---

Originally posted by vikke
mynetx: Register the Xniff.dll using regsvr32.

---

It doesn't need registering, the script tries that itself if it has an error loading xniff.

---

quote:

---

Originally posted by riahc4
We have to add each contact?

It would be nice if this plugin is activated, it does it itself.

---

quote:

---

Originally posted by CookieRevised
Maybe you better put everything (all the error checking and initializing and calling DoInit) in OnEvent_SignInReady and simply direct OnEvent_Initialize to OnEvent_SignInReady (or don't even use OnEvent_Initialize since it makes no sense to use this script while you're signed out anyways).

---

quote:

---

Originally posted by CookieRevised
PS: the hardlink creation is a nice touch, although I would personally rather see this as an option.

---

quote:

---

Originally posted by CookieRevised
Or device a scheme where the hardlink is only there as long as the conversation window is open or something.

---

quote:

---

Originally posted by CookieRevised
And IIRC hard links can only be created on the same volume. So if the user decides to have directories on another volume (to save space?) than Messenger's received files folder, the link can't be created

---

quote:

---

Originally posted by CookieRevised
(plus it is not supported on fat32 of course).

---

quote:

---

Originally posted by CookieRevised

EDIT: Oh, and the Windows API for creating a hardlink is CreateHardlink(). It works  as easy (if not easier) than using a DOS Shell to FSutils.

---

Already loving it (besides the use of Xniff)

Maybe another suggestion for the interface:

When the user wants to add a contact, instead of having users to select one contact, and then showing another window to set/change the preferences for this contact, why not make it both in the same window: the list of contact and underneath the options. Much like how other similar stuff is done in Windows itself.

In that way you can also allow users to select multiple contacts and set/change their preferences all at once (eg: showing three-state checkboxes, etc) in one window. And then you don't need to present multiple windows to the user either (which is always a bit clumsy). And thus the script gets a bit shorter too. KIS (keep it simple).

Hello!
This is second script I've tried of this sort and it also worked only ONCE - meaning it only "move" files to a newly created folder and will not move anything to previously  created folder, which creates two identical files in "My Received  Files" folder. (user A@A.A sends a file (blah.txt), a new folder "A@A.A" created and hardlink created in that folder - good. After that user A@A.A sends second file (blah2.txt), however no hardlink inside folder "A@A.A" is being created, instead hardlink created inside "My Received Files" folder (blah2.txt and blah2(1).txt)
Anyone has this issue?

P.S. IMHO creating hardlinks is absolutely useless, what's the point? Besides it will "scare" most of the people who doesn't know that its hardlinks and not physical copy of the files. And finally if one want to see all files in all subfolders, simply search for *

The registration and use of Xniff is indeed very buggy in this script, which can partially explain why it only works once. After some heavy modifications, it works nicely here (for as far as anything with Xniff can work nicely of course).

Remember that this script is still in alpha stage....

quote:

---

Originally posted by CookieRevised
The registration and use of Xniff is indeed very buggy in this script, which can partially explain why it only works once. After some heavy modifications, it works nicely here (for as far as anything with Xniff can work nicely of course).

Remember that this script is still in alpha stage....

---

Believe me, it really does not. I have looked into Xniff quite a lot and how it is often used in scripts. I can give a whole list of issues with it and issues with how it is often implemented/initialized in scripts.

I know about the errors etc and the fact it actually crashes Plus! IIRC, but the results I get are quite promising, if I can fin an alternative to xniff

I'm not talking about the crashes now, I'm talking about how Xniff is actually used in scripts and how that quite often leads to Xniff only working for some time (eg: until you sign out for whatever reason, eg: hybernation) and not anymore afterwards (eg: when you've signed back in).

so, what is so "special" about xniff? why is so needed in this particular script?
I thought it would be simple enough to monitor wlm events and after it received a file just move it to a needed folder...isn't plus! provide such events?

quote:

---

Originally posted by V@no
so, what is so "special" about xniff? why is so needed in this particular script?

---

quote:

---

Originally posted by V@no
I thought it would be simple enough to monitor wlm events and after it received a file just move it to a needed folder...

---

quote:

---

Originally posted by V@no
isn't plus! provide such events?

---