Usenet groups can be accessed using variety of methods. One way is to use Google Groups to access them. But the disadvantage here is that you will see all the spams and its really difficult especially navigating comp.lang.lisp group. Here I'll show how to access them effectively without those stupid spams. Thanks to comp.lang.lisp guys for helping me get this clear.
1. You need to use a new reader client. You can choose anyone for eg. Thunderbird, Windows Live Mail, Microsoft OutLook etc.
Here I'll show how to use Windows Live Mail to access newsgroups.
2. If you are using Windows 7, you need to download Windows Live Mail.
3. When running Windows Live Mail for the first time it will ask for an email account. Configure it since an account is need to post to newsgroups.
4. Goto eternal-september.org and register there. Remember the username and password. We will be accessing newsgroups using this server. This server will effectively weed out spams and make out lives a lot more easier.
5. Next at the bottom of the Windows Live Mail you'll see the Newsgroup option. Click on it and on the left pane you will see 'add newsgroup'.
6. Click on it and a dialog pops up. Follow it till the end. Well, at first you need to enter a display name.
7. Next add the above email address.
8. Next add the news (NTTP) server as news.eternal-september.org and tick the box which says "My news group requires me to log in".
9. Next enter the username and password that you used to register at eternal-september.org
10. The rest will be taken care by the application. It will test the connection, download the list etc.
NB: After 150 days of inactivity eternal-september.org will sent you a warning message. Further inactivity will lead to deletion of your registered account.
Don't use top-posting. Read this guide on "How do I quote Correctly in Usenet?"
Tuesday, 1 June 2010
Running Visual Studio 2010 in Windows 7 64 bit gives messages "Cannot find or Open the PDB file" as show in the figure below. Its because you are running it as a normal user. You need to run it as an Administrator to stop showing the warning. For that right-click VS 2010 and choose Run as Administrator.