... <local_name> can be anything, but is often based on user name (I use "CalcHub", for example. The main idea is that you provide something unique.) You can ignore the -s and -p options almost always; they default to what's necessary to connect to the server Kerm's set up.
(To clarify: <local_name> refers to what's after -l.) To use DirectUSB, you are correct in using "-d direct", but note that "-d d" also works and is shorter
Bit of a necropost, but my first time seeing the topic. Nice. Not surprising that TI would implement clearing programs in the Archive by deleting the ones listed in the VAT. It doesn't seem like it'd protect apps, though, because even after resetting RAM while holding [Clear] they still show up, right?
No. Bad. Don't do that. That code will jump to the address r1+r2 with hl=r2*r1 because ret/Return takes the address that's most recently been pushed. What you instead want to do is replace Asm(E5) with Asm(E3E5) (ex (sp),hl \ push hl) and do that for all extra values. That way the return address is in the right place when you return. When the subroutine does return Asm(E1) is still the proper way to get those extra values off of the stack.
To my knowledge sending a message takes the form "PRIVMSG #channel :message", where #channel is the channel and message is the message. You need that colon there unless your message has no spaces. Same for the "real name" field of the USER command (the last one). (You also don't put a space after the colon.) graphmastur: when you receive a message of the form "PING stuff", the proper reply is "PONG stuff", replying with the same stuff. Some servers send them in the form ":server PING stuff", in which case you just ignore what's before the command. For everyone who wants to see the official documentation, here's a link to RFC 2812.
Show Posts
At what point is a topic considered dead, then?
