aPOCALYPSE Production Crew 1998 - XdCC OfferBot Pack List ---------------------------------------------------------- -=-=-=-=-= Last Updated: 30 July 1998 09:27 EDT =-=-=-=-=- ---------------------------------------------------------- -=-=-=-=-=-=-=-=-=-=-=-=-=-= FAQ =-=-=-=-=-=-=-=-=-=-=-=-= Created & Updated by tarkap / Last Update: 13 July 1998 09:13 1. "Why is the list in this stupid ass .wri format?" It's not hehe. I only put the .wri extension, cause most people have .nfo and .txt associated with notepad which doesn't like the UNIX text formatting. in UNIX newline is just a CR, but in Windows/DOS newline is CRLF, so when notepad doesn't see CRLF, it thinks its not a newline, so it garbles everything. Wordpad can see this, so it displays it correctly. :) 2. "Why the fuck can't you dcc resume on these bots?" You *can* resume on *some* of the offerbots. Any of the bots running BitchX75p1 can resume. I cannot guarantee any other xdcc's will resume. Also dcc resume *only* works when you are in mIRC. I have not tested it with any other clients, but since the code in bitchx is called 'MIRC_BROKEN_RESUME' or something, I assume it only works with mirc. One word of warning, this mIRC resume feature sometimes does not complete cleanly for unknown reasons. It sometimes times out at like 100% and never says dcc get completed. This usually corrupts the files. That is why I have included the sfv2 files for every cd that is offered on these xdcc's so you can make sure the file is correct and not fucked up. PLEASE use these sfv2 files and the SFV program to check your mp3s!! If you don't you risk spreading bad mp3s around, which defeats the purpose of aPC. Also I suggest *not* dcc resuming the one big zip files due to the possible corruption by BitchX. Just get a fast shell and d/l to there. DO NOT download the onebigzip files from a 56K or lower modem connection. I would love to set a 3KB/s limit on them, but the stupid BitchX doesn't do the speed limits correctly. To resume, just re-get the file and select resume when the mIRC message box appears. Not that hard eh? Sometimes, typing /msg xdcc resume #x is needed to help it along. I don't know why, but for some reason it needs this little push. Also, don't be impatient. If the bot does *not* resume *and* the dcc get times out, then MSG tarkap about it, with the number of the xdcc bot and the pack you are trying to resume. I can't guarantee anything will be done about it, but u never know :) 3. "Hey dude what are those stupid .sfv2 files on some of the xdcc's?!?!" Well, they are plaintext files with unique crc codes next to them that were generated using SFV32, a program that allows you to create those CRC files for any type of file, and you can also use these CRC files to validate the files you downloaded are an *exact* copy of the file that was ripped. This gives you assurance that the file you got was not screwed up along the way. SFV is for Windows95/98/NT *and* Linux/Unix. So both type of people can use them. You can get this program from aPCDCCSFV on EfNet where you get the mp3s :) 4. "How come bot XX isn't up?" Please don't ask if the bots are up and down, like all of life, shit happens. The most likely reasons that the bots is down is that the shell it was on is down, or the mp3s on it are being changed. If you must ask, ask NICELY! No evil tongue needs to be spoken to get help. 5. "Can you put you bots in channel #?????" I have heard so many damn people bug me about that. Here is the answer: NO. Unless you want to supply us with shells to run xdcc's off of, don't even bother to ask anybody about that. I will just ignore you, and if you bug too much I'll ban you from the channel! I'm sick of hearing this every damn day I am on irc. 6. "What can I do to help you guys?" 1. Don't piss of the bots by trying to grab all the packs they're offering at once, it only makes them ignore you because it thinks you're flooding it, and remember, you're not the only person on irc. 2. Give us some xdcc-able shells, or run some yourself. It's easy, all you need is to be able to run 3 xdcc's or more to join aPC. If you're a lazy ass ( like a couple people :P ) Then you can just give us access to the accounts and we can run xdcc's from there. You'd still get in aPC and get all the same priveledges, just I would have more work on top of maintaining about 20 xdcc's as is :P 3. Don't be an ignorant ass in the channel. If something is wrong, be nice about it. Don't go into #aPC and bitch your ass off because something is wrong. 7. "What's this XDCC CDINFO command, and why do only some of the bots have it?" Well, I got tired of seeing the bots flood off every couple mins and all those lame asses using IRC FileTool and other such pathetic devices to leech mp3s easier than the normal population, so I went and edited BitchX to meet aPC's needs. The XDCC CDINFO command is one of those additions. It tells you what CD the bot is offering, in case it got changed before I updated this list again. And, yes you can /msg #aPC xdcc cdinfo, since it won't cause the bots to flood off. Just DO NOT /msg #aPC xdcc list, or you *WILL* be kbanned! 8. "Where do I send comments to about the bots?" E-mail tarkap@usa.net with your comments. I do not guarantee a resoponse though. 9. "Hey these bots won't send anything" Try /ctcp cdcc send #x The aPC|DCC5x bots all only respond to ctcp's 10. "How come when I mIRC resume files on these bots, they don't complete correctly, and time out at 100% sometimes?" It's a bug in the MIRC_BROKEN_RESUME feature in BitchX. But not to fear, when you download those huge ass tar files, even timing out with the dcc, the files should still come out okay. Just I would advise against resuming the smaller mp3s since they are not tarred and tend to get corrupted with the dcc timeouts. 11. "What the hell are these .tar files?" tar is a unix 'compression' program. tar actually only takes multpiple files and archives them together into one file, with *NO* compression. For all you windows users, WinZip should open these with no problem.