Sidetrack

Thanx Once again iceman for all the help.. ur great.. Keep it up!!!.. (later u can help me convert apex to linux. ) lol.. (no folks I am not that good yet.. by any means. linux has given me fits upon fits. but I am determined to win..!

Can someone please translate this so we can help this user?

Mirage, please send me, if you have a copy of it, the kick message in a PM here. IF you feel it needs investigating. I am working on developing TGO ver. 3 currently. This will take a couple of months most likely. due to the huge change, I have built a custom server, running a *nix distro, with a *nix based hubsoft (no details on purpose atm) to make TGO take another big step toward support. I have not been around TGO much recently due to the work trying to fix a bug in TGO ver. 2. Its now fixed and we can move back to work on TGO version 3. Alot more features will be added to it.

Thats just someone melted ur face off. looks like a sci fi situation... would you constitute as a blind mute?

"Crise is my coder, I shall not want, He maketh me downloads in bigger hubs; He leadeth me to superseeded files; He restoreth my code: he leadeth me in the paths of development for Apex name's sake. Yea, though I walk thru the valley of the shadow of Apex, I will be enlightened, my client and my download speeds overwhelm me; Thou preparest a beta before me in the presence of testers & subscribers: thou anointest my client with extra features; my cup runneth over. Surely goodness and mercy shall follow Apex all the days of my life: BUT, I will dwell in the house of the LORD for ever." Amen :)

Guys. I am not sure if this is a related issue or not. but the connection that TGO, the dev hub and a couple others are on, is experiencing some major line issues since the last storm we had. I have had issues with the remote terminal before and recognize the issue. I am calling our telco today to address it. I also have a new modem coming, should be here friday. I hope this helps to resolve some of the issues. I ran line tests yesterday, and even though the count in TechGeeks was impressive, it was definitely not what it should have been able to hold without dropping half of the hub. The Lag was horrible and many more issues. Thus the point to call my telco today. Hope this helps. However, this should not in anyway affect other hubs that I do not host.

first off I will apologize for 2 things, first off the numerous issues your having with the new Beta. When your coding a software and adding as many new implementations as has been completed, it is possible to overlook areas. Because the software is being customized, its hard at times to narrow down certain features, that work for most, and crash for others. This is mainly because things can be modified so much. The operating system, tweaks, etc. can all make a difference on how the client runs. the information provided will be helpful in attaining and hopefully resolving the problem. As for TechGeeks, its there mainly because, so many ppl are new to DC and are installing this client for the first time. TechGeeks is the support hub for Apex to help sort out any problems and client issues, before you go off gallivanting around DC. to make your overall DC experience even better. To my knowledge no other client on DC, has a hub dedicated to helping in a similar fashion. HOWEVER, do make note. BEFORE you move any files into your updated client, actually start the client, and put something in for the settings, don't have to be much, just enough to get you going, close and reopen, it should automatically start the TechGeeks hub to help you if needed. IF not, simply close the client and copy your settings into your updated client. this so far has worked every time since the beginning of PWDC. But make sure you get to the hub FIRST. the initial client creates everything needed (xml files) AFTER you fill out the information. so if you update prior to first launch, it WILL auto overwrite. Hope this helps

it should attempt to force a connection, this is also known as hammering at times, however, its placed in, for the purpose of being able to connect between the standard wait times. Such as if your IP changed and you just put it in the settings. Then use the force attempt to try to get the connect. no it should NOT be removing the user from the queue. as far as I know.

ok, we HAD that one fixed. maybe the clean up "unfixed it" Crise, hehe looks like you may have some work to do.. Good Job Aztek..

that looks like a video issue. more than bug. only GOD knows with vista. Maybe one of the other members can post ideas on it..

Good Job. I have not had much chance lately.. to work on raw commands, and frankly its not my skill, I can, but I have to crack down on it hard to get it. thats part of the things I have forgotten and with all the blasted changes recently. its NOT fun.. on the protocol commands and such.. lol.. sorry GS

thats MY job.. and my goal.. its theirs to help change it

Thats the problem. there is NO standard, as I delve into this project, I am finding so many variations. I am frankly surpised there is only afew issues. nmdc/nmdc extended/adc then there is the issue of z-itself, there is zline, zport, and zpipe. then there is DC++ team variations, my goals is to get them all working together, create the standard that makes dc itself better, and quits all this crap thats going on. unity will allow DC to prosper, dividing, will kill it..

You know, I have thought over and over, What makes the idea of the OP client vs the standard client so much more beneficial, Crise, this part is for you. Maybe a MERGE of the 2 clients WOULD be possible, AND beneficial. I have been using apex, since before PWDC 2 was released, (before it was apex). It has come along way. alot of features have been added including some new features in the MOST recent Beta's. But we are or MAY be looking @ this totally wrong. Why have a separate client all together. Bragging Rights? In the current version of Apex, try logging in as a Regular User, Look @ your Client Side RC set. they are different than if you have keys. Because, the client recogizes that you are an OP or higher. IF Apex was able to keep the size down, and put in ALL of the Op Features Planned, then lock them down (via code, not user option) Then we would have a new idea in DC wouldnt we. A client everyone can use, from new users, to OPs, and as they progress in DC, and start to become OP, they would find MORE options are available to them automatically. This would require the client to recognize if the user has keys or not, but it does that already.. So why NOT? Apex is evolving into something far better than what is currently out there, on all fronts. why not make it a totally new idea. The client actually evolves WITH the user, not making him/her upgrade to another client, if they get keys somewhere. Regarding the NMDC/ADC filelists issue. Personally I think WE all are looking at this entirely wrong, There are 2 totally different ideas about how DC should be done, its not the clients, its not the bots or the hubsofts, but HOW the protocol itself should be changed. any source software, that is required to support BOTH of these will be bloated badly. and lag, and be slow, and be.. (insert your comment here). WE as members of the community, both OP, Admins, owners, developers, creators, and evermore, need to work on getting a new standard set and locked in place, THAT is the problem, the teams involved in changing the Protocol itself, are not working together but are splitting it up, which only makes it harder for coders to write. Then they are forced into politics. "Well if you dont choose ADC, you cant access my hubsoft, or my files", "If you choose NMDC extended, then you can do this or that, but not this" etc. DCC was best because all clients worked together, all hubsofts worked together, it wasnt like most other p2p softwares because it allowed choice, yet, used same protocol so everything simply Worked. MOST of the older Op Clients, DCDM, rmDC, MCDC, R2++ etc.. are dead projects, or not getting much work. MOST are based on source .401, which is NOT even nmdc extended. We need to push as a community for a STANDARD in DC protocol. I for one am working on this. Many devs already know this. I dont care which protocol layout is used, just freaking pick one, and make it the best it can be. MORE info on this project will come as the resources are setup. IF your interested in participating. Please send me a PM here. ! (typical Sidey book, sorry guys)

3dFX, I know you been asking about this for a while. I had 2 users that deleted their hash.dat and queue.xml.bak files, (should be NO relevance to each other) and rehashed the files, and it worked. cant say thats the cause or the solution, but its an option.. I believe the hash.dat file is rebuilt if its missing. others may be able to confirm...