Vincula Questions

Good day everyone ...

I have a few questions about the "Vincula" connection.

===QUESTIONS===

1) How can i add a buffer to Vincula so that it becomes more stable when there is a flood. I know it would require ALOT of editing to add it .. but if there's an easy way to add a buffer i'd be more than greatfull for any help..

2) How can i hide the "Status" windows or how can i make it so vincula uses one status window for all the rooms..instead of open a new status for every room i join ((it fills the switchbar)).

=============

i hope someone knows the answer to either one of the questions .. and if you know both answers don't hold back

--

If i have any more questions i'll drop them in this post

If you do a buffer, you'll have to do a buffer overrun which would require ALOT of editing. To hide the status window, use /window h. Still shows in the windows list, but, not the actual switchbar. So ...

window h @winname

Example:

window h @MSN MyNickname

EDIT .. used -h which would highlights the window button if its currently minimized.

shoot @ the buffer :$

--

I think i read somewhere on mirc.com 's forum that Khaleed intentionally made it so the "/window h" wouldn't work ..

so i think its vincula that needs to keep the same status open for every join instead of a new one ...

is that do-able ?!! ...

no .. its an ocx vincula .. i tried an OCXless one made by "Warrior" but it had too many bugs and errors..

===

ok ... i was looking at the vincula's "room joiner"

elseif (613 == $2) {
   if ($hget(msn.999)) { 
   echo $color(info) -at 8• $msn.get(999,fullroom) found, joining... (Lookup time: $calc(($ticks - %msnc.looktime) / 1000) seconds)
   unset %msnc.looktime
   socklisten msn.mirc.in $rand(10000,30000)
   if (%msnc.newcon) scid %msnc.newcon server 127.0.0.1 $sock(msn.mirc.in).port
   else server -m 127.0.0.1 $sock(msn.mirc.in).port
   hadd msn.roomip $msn.get(999,room) $right($4,-1)
   writeini ips.ini roomips $msn.get(999,room) $right($4,-1)
   sockopen msn.server.999 $right($4-,-1)
   var %port = $rand(2000,9000)
   while (!$portfree(%port)) inc %port
   socklisten msn.client.rmc %port
}

and i noticed

%msnc.newcon

so i looked that up

if ($server == $null) %msnc.newcon = $cid

so i was wondering ... is there a way to edit those codes so that it doesn't open a new status ?

====

when i type /join %#----- for example .. i get this in the window i typed it ((in this case a room))

( 07:36p ) • %#---- found, joining... (Lookup time: 0.328 seconds)

and then a new status open and this comes up

( 07:36p ) * Connecting to 127.0.0.1 (24650)

-

1 0 GateKeeper,NTLM 512 *

-

127.0.0.1 AUTH GateKeeperPassport S GKSSP\0a\0\0\0\0\0\0\0¤×08wCÚ¨

-

127.0.0.1 AUTH GateKeeperPassport S OK

-

127.0.0.1 AUTH GateKeeperPassport * 28BFF4BBF69C2CCE@GateKeeperPassport 0

-

so there must be a way in the actual connection to stop a new status opening up ...

FAHAD I THOUGH U KNEW EVERYTHING

baby

i should of never commented about u being a "Waste of Space"

personally i think its more stable to have a status window for each chan than it is to only have 1

personally i think its more stable to have a status window for each chan than it is to only have 1

well .. you'd think so .. but i use two different scripts .. one using "Vincula" and one using "R3" .. R3 has one status and never disconnects when there's heavy flooding in the room ... vincula on the other hand .. it can handle a flood....but not for long

look on the bright side, when u disconnect on vincula, it should be that room only, but other cons u will disconnect from all chans lol

i use vin to.. it seems to do better if u use less sockwrites during floods.. its slower yeah but seems better though

look on the bright side, when u disconnect on vincula, it should be that room only, but other cons u will disconnect from all chans lol

i use vin to.. it seems to do better if u use less sockwrites during floods.. its slower yeah but seems better though

true .. with vincula i just disconnect from the one room .. but i find that the vincula i use works better with floods when i make the prots sockread than none ...

i just tested the non-subscriber kick with and without the sockread and i disconnected when it was removed and was able to kick all 100 when sockread was added to it ...

could try adding the ss alias to it mmeh i dunno lol.. i just add deny anyways let everyone else kick

egh .. there must be a way to make vincula a one server instead of a multi-server connection :'(

i know for a fact V.5 the vincula eXonyte never got around to finish was an option between "Multi and One server" .. and it had a buffer...

pitty he never finished

egh .. there must be a way to make vincula a one server instead of a multi-server connection :'(

 

i know for a fact V.5 the vincula eXonyte never got around to finish was an option between "Multi and One server" .. and it had a buffer...

 

pitty he never finished

Forgive me for bumping an old thread but:

1) There is no way to change Vincula 4 to single-server without a LOT of work. It would involve a nearly complete rewrite, like Vincula 5 was going to have.

2) I never had a problem with it flooding offline, but I have a feeling it's because Vincula's sockread is a loop, while most other scripts are not. This could actually cause it to get disconnected if it keeps recieving for too long without sending any required responses. It can be modified to not be a loop, which should solve the problem. Off the top of my head, it would be a matter of deleting about three lines in the sockread. I can't be bothered to find out exactly which three at the moment, but it would basically be the "while () {", the matching "}", and the sockread right before the "}".

Hey eXonyte. Glad to see you again. With msn chat closing, why not jsut go ahead, and release Vincula5? I know it is not yet finished, but personally, I'd like to use it and see what it is like before msn chat closes.

in responce to exo's comment, i also believe it has to do with the timers that he uses. He resets the timers every time a sockread comes through, and i believe this plays a part in mIRC's incapability to handle the sockread more efficiently. But in saying that, MSN is virtually dead, who cares, move on.

Back to studying...