If you think additional problems should be listed in this file, please contact the authors, or send mail to "grnbugs" from within GRn. 1) "I can't get GRn to execute SendMail or PostNews". Hmm. This shouldn't happen anymore on 1.16f, UNLESS you don't have the directory where SendMail and PostNews are in the Workbench path when you started GRn. Try quiting GRn, "loadwb newpath" and then restarting GRn. If that doesn't work, then: 1) Put GRn in the same directory with the other programs (normally uucp:c). 2) Explicitly name the full pathnames to the programs in your uulib:config file. or: 3) Set the environment variables SENDMAIL and POSTNEWS to point to the full pathnames of the programs in your uulib:config file. 2) "GRn doesn't open on my custom/public/whatever screen" As a Workbench user, you simply need to edit the tooltypes in GRn's icon (grn.info) to set LEFT, TOP, HEIGHT, WIDTH, and PUBSCREEN. Then, GRn will use your existing screen UNLESS GRN WILL NOT FIT. GRn requires a minimum screen size of 600x400. As a Shell user, just pass these as arguments when you start GRn. 3) "GRn doesn't use my custom font" As a Workbench user, you simple need to edit the tooltypes in GRn's icon (grn.info) to set MSGFONT and MSGFONTSIZE. The MSGFONT must be in the "anyfont.font" style, or GRn will fail. As a Shell user, just pass these are arguments when you start GRn. 4) "GRn doesn't scroll properly with my custom font" Well, I thought I fixed this problem. Maybe not. Send me your font, and I'll try to fix the problem. Make sure you tell me what size screen you are using GRn on, and whether you are PAL or NTSC. 5) "GRn doesn't use my custom font in the gadgets" True. It's a pretty big bother to have variable sized gadgets. At this time, I've decided against them. If enough people ask for them, I can probably be convinced to change my mind. 7) "How do I use GRn with C-News?" Use environment variables: USERNAME - the login name of the user running GRn REALNAME - the full name of the user running GRn NEWSEDITOR - the program to run to Edit outgoing News MAILEDITOR - the program to run to Edit outgoing Mail SENDMAIL - the program that submits Mail to UUCP POSTNEWS - the program that submits News to UUCP You STILL must have a directory named UUNEWS:, which is the directory where the top-level news directories exists. You must also have a UULIB: directory that contains signature files, etc. It may contain a file named CONFIG that contains standard AmigaUUCP configuration information. GRn will use those redirections, if they exist, for UULIB and UUNEWS. GRn will first check environment variables before opening the CONFIG file. Read GRn.man. 8) "How do I use GRn with NNTP?" It's pretty easy. Why didn't you read GRn.man? Use environment variables: USERNAME - the login name of the user running GRn REALNAME - the full name of the user running GRn NEWSEDITOR - the program to run to Edit outgoing News MAILEDITOR - the program to run to Edit outgoing Mail SENDMAIL - the program that submits Mail to UUCP GRn still uses the UULib: directory to look for the username.grnrc and username.signature, etc. It may contain a file named UULib:Config that contains standard AmigaUUCP configuration information. If you haven't set the UULIB environment variables, but HAVE redirected in that file, GRn will use those redirections, if they exist. Read GRn.man. If you are using the serial port, also read GRn-Term.man. 9) "I'm using GRn with C-News, and GRn doesn't seem to notice new articles in some newsgroups. What can I do?" The C-News EXPIRE program can leave "holes" in article numbers. This is not a bug, just a different way that the C-News EXPIRE works. To minimize this problem, ensure that "GRn CNEWS UPDATERC" is executed BEFORE each EXPIRE run. This will make sure that GRn is as up-to-date as possible, and that there are as few holes as possible. GRn tries to compensate by checking for up to 10 "holes". However, if there are more than this GRn will not be able to find new articles. You must then Junk the newsgroup (unsubscribe) and then resubscribe. GRn will handle this differently in version 1.16g, to avoid this problem.