how do I download it?

By r_erdmann ·
how do I download it? I have any luck click on anything to download this.

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

How do you download what? What are we mind readers?

by ManiacMan In reply to how do I download it?

Please be specific when you ask for help.

Collapse -

How To Download:

by reloader3 In reply to How do you download what? ...

The majority of downloads are processed the same! Why not tell the person to watch for the notice, "if download etc. in so much time does not open, press here" Then save or open. I think Mman can express the procedure better than I. I'm pretty new.

Collapse -


by Ed Woychowsky In reply to How do you download what? ...

Since I don?t have a Johnny Carson-style Karnac hat I?ll have to say that it depends on what you?re trying to download. Many things can be downloaded from a browser just by clicking on it, although some a right-click. Bittorrent requires a Bittorrent client, which can be found online for free. And, although most browsers can handle FTP it might be a good idea to get a free FTP client from

Collapse -

Well generally you open a Web Site

by OH Smeg In reply to how do I download it?

and select Download Now. That generally works to download something.

Perhaps you should read this

Before asking a technical question by e-mail, or in a newsgroup, or on a website chat board, do the following:

Try to find an answer by searching the archives of the forum you plan to post to.

Try to find an answer by searching the Web.

Try to find an answer by reading the manual.

Try to find an answer by reading a FAQ.

Try to find an answer by inspection or experimentation.

Try to find an answer by asking a skilled friend.

If you're a programmer, try to find an answer by reading the source code.

When you ask your question, display the fact that you have done these things first; this will help establish that you're not being a lazy sponge and wasting people's time. Better yet, display what you have learned from doing these things. We like answering questions for people who have demonstrated they can learn from the answers.

Use tactics like doing a Google search on the text of whatever error message you get (searching Google groups as well as Web pages). This might well take you straight to fix documentation or a mailing list thread answering your question. Even if it doesn't, saying ?I googled on the following phrase but didn't get anything that looked promising? is a good thing to do in e-mail or news postings requesting help, if only because it records what searches won't help.

Take your time. Do not expect to be able to solve a complicated problem with a few seconds of Googling. Read and understand the FAQs, sit back, relax and give the problem some thought before approaching experts. Trust us, they will be able to tell from your questions how much reading and thinking you did, and will be more willing to help if you come prepared. Don't instantly fire your whole arsenal of questions just because your first search turned up no answers (or too many).

Prepare your question. Think it through. Hasty-sounding questions get hasty answers, or none at all. The more you do to demonstrate that having put thought and effort into solving your problem before seeking help, the more likely you are to actually get help.

Beware of asking the wrong question. If you ask one that is based on faulty assumptions, J. Random Hacker is quite likely to reply with a uselessly literal answer while thinking ?Stupid question...?, and hoping the experience of getting what you asked for rather than what you needed will teach you a lesson.

Never assume you are entitled to an answer. You are not; you aren't, after all, paying for the service. You will earn an answer, if you earn it, by asking a substantial, interesting, and thought-provoking question ? one that implicitly contributes to the experience of the community rather than merely passively demanding knowledge from others.

On the other hand, making it clear that you are able and willing to help in the process of developing the solution is a very good start. ?Would someone provide a pointer??, ?What is my example missing??, and ?What site should I have checked?? are more likely to get answered than ?Please post the exact procedure I should use.? because you're making it clear that you're truly willing to complete the process if someone can just point you in the right direction.

Be sensitive in choosing where you ask your question. You are likely to be ignored, or written off as a loser, if you:

post your question to a forum where it's off topic

post a very elementary question to a forum where advanced technical questions are expected, or vice-versa

cross-post to too many different newsgroups

post a personal e-mail to somebody who is neither an acquaintance of yours nor personally responsible for solving your problem

Hackers **** off questions that are inappropriately targeted in order to try to protect their communications channels from being drowned in irrelevance. You don't want this to happen to you.

The first step, therefore, is to find the right forum. Again, Google and other Web-searching methods are your friend. Use them to find the project webpage most closely associated with the hardware or software giving you difficulties. Usually it will have links to a FAQ (Frequently Asked Questions) list, and to project mailing lists and their archives. These mailing lists are the final places to go for help, if your own efforts (including reading those FAQs you found) do not find you a solution. The project page may also describe a bug-reporting procedure, or have a link to one; if so, follow it.

Shooting off an e-mail to a person or forum which you are not familiar with is risky at best. For example, do not assume that the author of an informative webpage wants to be your free consultant. Do not make optimistic guesses about whether your question will be welcome ? if you're unsure, send it elsewhere, or refrain from sending it at all.

When selecting a Web forum, newsgroup or mailing list, don't trust the name by itself too far; look for a FAQ or charter to verify your question is on-topic. Read some of the back traffic before posting so you'll get a feel for how things are done there. In fact, it's a very good idea to do a keyword search for words relating to your problem on the newsgroup or mailing list archives before you post. It may find you an answer, and if not it will help you formulate a better question.

Don't shotgun-blast all the available help channels at once, that's like yelling and irritates people. Step through them.

Know what your topic is! One of the classic mistakes is asking questions about the Unix or Windows programming interface in a forum devoted to a language or library or tool portable across both. If you don't understand why this is a blunder, you'd be best off not asking any questions at all until you get it.

In general, questions to a well-selected public forum are more likely to get useful answers than equivalent questions to a private one. There are multiple reasons for this. One is simply the size of the pool of potential respondents. Another is the size of the audience; hackers would rather answer questions that educate many people than questions serving only a few.

Understandably, skilled hackers and authors of popular software are already receiving more than their fair share of mis-targeted messages. By adding to the flood, you could in extreme cases even be the straw that breaks the

The above is from this Web Site and called How To Ask Questions.

Collapse -


by boxfiddler Moderator In reply to Well generally you open a ...

you expect us to actually work to find an answer to our questions before we ask here?
Big ol' meanies.

edit typo: guess you actually expect us to be able to spell, too?

Collapse -

TR Downloads?

by TheChas In reply to how do I download it?

If you are referring to Tech Republic downloads, the biggest issue is the things you must enable.

Most of the downloads fall into 2 categories, ZIP archives and PDF documents.

In order to download these you MUST:

Allow Pop-Ups

Allow a number of CNET sites to place cookies on your system.

This includes CNET, Tech Republic, and maybe more.

At one time, they were using a Java Script as part of the download sequence, so you may need to open up the security settings on your browser.


Back to Desktop Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums