--------------- FIDO MESSAGE AREA==> TOPIC: 239 C LANGUAGE Ref: F1G00009 Date: 01/11/98 From: BOB STOUT Time: 12:40pm \/To: ALL C_ECHO & C_PLUSPLUS (Read 0 times) Subj: moderation and the echos [Note: This message is being posted in both the C and C++ echos.] As some of you know, the C++ echo's last moderator of record, Jerry Coffin, has his FidoNet access cut rather abruptly recently when his BossNode BBS shut down. As of 1-Jan-98, the EchoList entry for the C++ echo has expired and the participants have one month to elect a new moderator. I've been in touch with Jerry, who encouraged me to conduct a new moderator election. This message is the first notice of the election. However, it's also new moderator election time in the C echo, which begs a significant question - is it time to rejoin these two echos? Some of you may remember that the C++ echo was born of the C echo about 8 years ago when FidoNet in general was a lot more robust than it has been lately. Over the years, there have been several suggestions to reintegrate the two, but nothing has come of it. Circumstances now suggest this is a time to put it to a vote. To this end, I suggest the following ground rules: 1. If the C++ echo continues, it will need a moderator. Based on experience, the qualifications should be: a) Candidates must have been active in the echo for the preceding month. b) Candidates must be either a FidoNet sysop or a point. If a point, the candidacy must be supported by the candidate's BossNode sysop. c) Candidates must have Internet Email access as well as FIdoNet access. 2. The election rules are as follows: a) Candidates may either be nominated without requiring a second, or may may volunteer, in which case a second will be required. b) The nominating period will run through 18-Jan-98. Nominations or volunteers may be posted in the C_PLUSPLUS echo or emailed to me at rbs@snippets.org. c) Nominations must be accepted. Those accepting nomination (as well as those volunteering) should email me rbs@snippets.org. d) The voting period will run through 31-Jan-98. Votes should be sent to me via NetMail to 1:106/2000.6 or email to rbs@snippets.org. 3. I suggest that both the C and C++ echo ballots should include a place to vote for reunification, yes or no. If the vote for reunification passes, the C_PLUSPLUS EchoList entry will be allowed to expire and the elected C_Echo moderator will become the moderator of the new combined echo. 4. Reuninfication must be approved by *both* echos. If either votes it down, then the C++ echo will either have to have a newly elected moderator or t will be allowed to die a natural death. 5. Auke Reitsma, the incumbent C_Echo moderator is conducting the election n the C echo. I will conduct it in the C++ echo since I have both the experience (I've moderatated both echos more than once and have conducted elections in both) and will not be a candidate in either. Barring any showstopping issues in either echo, the nominating period for C++ echo moderator is now open. --- QM v1.00 * Origin: MicroFirm : Down to the C in chips (1:106/2000.6) --------------- FIDO MESSAGE AREA==> TOPIC: 239 C LANGUAGE Ref: F1G00010 Date: 01/11/98 From: PAUL LENTZ Time: 03:03pm \/To: BOB STOUT (Read 0 times) Subj: Need help please Bob Stout wrote in a message to Paul Lentz: > Now the TSR stuff turns out harder than I thought! :-( BS> OK, here's my TSR FAQ... BS> With the ascendance of 32-bit OS's, writing TSR's is an BS> obsolescent (but not obsolete) skill. Writing a decent TSR BS> requires a lot more than the keep() function (which is just BS> a hook into DOS function 31h). Unless you're just doing it BS> for the education, use a library instead. Of course it's for the education! :-) Next thing I gotta learn is the dreaded assembly language though, so's I can modify PHONEV4 to include a file triggered boot. :-( Seriously, I looked at DSPCLOCK.C in snippets, and an excellant example TSR clock in my old POWERC manual (yup... I still use the powerc most the time) and I've gotten a grip on things... *sorta*. Thanks Guy! *Paul* --- timEd-B9 * Origin: Dumb Guy's!!! (1:124/5025) --------------- FIDO MESSAGE AREA==> TOPIC: 239 C LANGUAGE Ref: F1G00011 Date: 01/10/98 From: AUKE REITSMA Time: 08:29pm \/To: ALL (Read 0 times) Subj: Moderator nominations Nominated: - John Gardeniers, 3:631/391, no email (yet!) - Kurt Kuzba, 1:154/750, email unknown - Auke Reitsma, 2:281/400.20, Auke.Reitsma@net.hcc.nl I already asked, but: John and Kurt are you (or will you be) eligible and do you accept the nomination? As for me: I'm still hesitating to accept. Nominated and accepted or volunteered and seconded: - Roger Scudder, 1:273/404, rogers@usa.net - Tom Torfs, 2:292/516, tomtorfs@mail.dma.be Nominated but did not accept: - Frank Adam, 3:635/728.31, fadam@sensation.net.au Frank told me however that he'll continue to co-moderate for zone 3 as needed. The C_echo Moderator _____ /_|__| Auke Reitsma, Delft, The Netherlands. / | \ -------------------------------------- --- GEcho 1.00 * Origin: Home by the C (Auke.Reitsma@net.hcc.nl) (2:281/400.20) --------------- FIDO MESSAGE AREA==> TOPIC: 239 C LANGUAGE Ref: F1G00012 Date: 01/10/98 From: AUKE REITSMA Time: 08:29pm \/To: ALL (Read 0 times) Subj: Moderator election rules After a year of moderatorship it is time for someone else to do the job. In other words: it is election time. C_Echo Moderator Election Rules ------------------------------- 1. The nominating period will run from 2-Jan-1998 through 31-Jan-1998. 2. The voting period will run from 1-Feb-1998 through 28-Feb-1998. 3. The new moderator will be announced in the C_Echo on 1-Mar-1998 and will assume office on 8-Mar-1998 or earlier where feasible. 4. To be eligible for the post of moderator, a candidate must meet the following criteria: a. Candidates must be either a sysop or a point. If a point, the candidate must have the consent and approval of his/her BossNode sysop. b. Candidates must have posted messages in the C_Echo within the month of December, 1997. c. Candidates must have an Internet address as well as a FidoNet address, allowing them to be able to reliably send and receive Internet email as well as FidoNet NetMail. 5. Candidates may either be nominated or volunteer. If nominated, no seconding nomination is required. If volunteered, a seconding nomination will be required. 6. All candidates must explicitly accept their nomination. 7. Nominations and volunteers should be posted publicly in the C_Echo. Acceptance of nominations must be via email to Auke.Reitsma@net.hcc.nl. 8. Anyone who posted a message to the C_Echo within the month of December, 1997, is eligible to vote. 9. Votes should be sent directly to me via NetMail to 2:281/400.20 or email to Auke.Reitsma@net.hcc.nl. All voters should expect a confirming message. Please be aware that sometimes I have problems with NetMail. So use Internet email where possible. 10. If anyone has, or seems to have, any real problems getting their vote to me, they may, as a last resort, post their votes in the C_Echo. This obviously violates the concept of a secret ballot, and is therefore discouraged unless all other means of voting have been exhausted unsuccessfully. The C_echo Moderator _____ /_|__| Auke Reitsma, Delft, The Netherlands. / | \ -------------------------------------- Internet: Auke.Reitsma@net.hcc.nl FidoNet: 2:281/400.20 --- GEcho 1.00 * Origin: Home by the C (Auke.Reitsma@net.hcc.nl) (2:281/400.20) --------------- FIDO MESSAGE AREA==> TOPIC: 239 C LANGUAGE Ref: F1G00013 Date: 01/10/98 From: AUKE REITSMA Time: 08:44pm \/To: STEVEN HANCOCK (Read 0 times) Subj: Help needed.. Hi Steven, On 06 Jan 98, 01:30, you wrote to ALL SH> I have an internet mail program for my BBS that uses an ACCT.INI SH> file in the following format: SH> ACCTx=name@pop.host.com password SH> USERx=name@domain.com Is this a standard Windows (or OS/2) .INI file? I mean: has it sections starting with: [section_name] ? If so you can use my .ini file handler which I posted about five months ago -- and will post again or email on request. If not, you might be able to modify that .ini stuff or you might be able to use the CFG.* stuff in Snippets. The last however does not have writing capabilities. SH> /* ** This is an example of me writing a single user to a file ... SH> mail.number=1; SH> strcpy(mail.name,"gwar1"); SH> strcpy(mail.pophost,"pop.netaddress.com"); SH> strcpy(mail.password,"password"); SH> strcpy(mail.address,"gwar1@usa.net"); SH> f=fopen("ACCT.INI", "w"); /* I know, I should check the fopen SH> again, me thinking outloud */ SH> fprintf(f,"ACCT%d=%s@%s %s\r\n", ... Would work. You do not need the \r in the printf format in text mode though. And some of the example values contain duplicate info ... the '1' and the 'gwar' ... Greetings from _____ /_|__| Auke Reitsma, Delft, The Netherlands. / | \ -------------------------------------- --- GEcho 1.00 * Origin: Home by the C (Auke.Reitsma@net.hcc.nl) (2:281/400.20) --------------- FIDO MESSAGE AREA==> TOPIC: 239 C LANGUAGE Ref: F1G00014 Date: 01/10/98 From: AUKE REITSMA Time: 09:00pm \/To: DAVE KELLY (Read 0 times) Subj: comm routunes Hi Dave, On 09 Jan 98, 19:40, you wrote to Auke Reitsma AR> PM>> I was just wondering if people could give me some AR> PM>> information. How good is the outp and inp comm routines AR> PM>> that come with turbo c?? AR>> AR>> These functions are just standard asm OUT and IN instructions AR>> (byte verio or simple wrappers around these. Calling these AR>> 'comm routines' is therefo not exactly correct ;-) DK> Are you saying that the routines below will work? DK> #define unsigned char u_char DK> #define inp(x) (*((u_char *)x)) DK> #define outp(x,y) (*((u_char *)x) = ((u_char)y) NO! These are not functions anyway -- these are macros ... Note that he said turbo c ;-) Greetings from _____ /_|__| Auke Reitsma, Delft, The Netherlands.