Forum Home
Press F1
Thread ID: 47120	2004-07-16 10:01:00	Sticky: How To Get Effective Help on PF1. Comments Please.	Murray P (44)	Press F1

Post ID	Timestamp	Content	User
252805	2004-07-16 10:01:00	Ok people, here is the proposed sticky for the Press F1 main forum board as discussed the other week. The idea is to have a very short advisory and a link to this in the Post A New Topic page. There is a companion FAQ to this sticky which will be linked to from here once there is URL to link to so don't worry yourselves about the odd [Link]* that you see, it'll be sorted in time. If you see any glaring errors or omissions please point them out. That goes for the FAQ 101 which will be posted shortly. If your are interested in the original topic or want to refresh your memory go Here (pressf1.pcworld.co.nz) Sticky: How To Get Effective Help on PF1. Help Us to Help You. If you are new to the Press F1 Help Forum, then welcome, and we look forward to helping you. These notes are guidelines on the effective usage of Press F1, not rules, and this document is intended to help you get the best out of Press F1 and its members. Don’t forget to use the links provided as well as the Press F1 FAQ page and the Forum Search function too, because you may find your problem has already been discussed and resolved. Read On. 1) Your Topic Title (the subject of discussion): Try and make the topic of your post as specific as possible to the problem or issue you want resolved. If a particular programme or hardware device is causing you trouble, or you want to know something about it, put its name or error message in the topic. For example: “Internet Explorer, Page not found”, “PC won’t start, Invalid System Disk”, or “File not found”. If you don’t know what is causing your problem, try to describe it as best you can in as few words as possible. Single word topics such as Help, Urgent, Please, etc, are not descriptions of your problem and will not get you any closer to resolving it. Most people do not have time to read every post on the forum and will bypass threads that do not have an easy to understand description to attract their attention, interest, and more importantly, expertise. 2) Your Question: Again, be as specific as you can. Include any error messages you receive, and briefly describe the pop up boxes or things that are not what you expect or want to happen. If you can, please include the name, model and/or version of the software or hardware that is causing the problem. If you are unsure, just ask, or follow this [Link to FAQ 101] for more detailed advice. 3) What were you doing (or attempting to do) at the time, or just before the problem occurred? Tell us what program you were using or trying to access, or what other computer function you were engaged in when you first realised you had a problem. 4) What operating system (OS) is installed on the computer? For example: Windows 98SE version XX.XXX or Windows XP Service Pack 1. If you don’t know all the information, say so, then ask. You will find the version information for the program you have open by clicking “Help” at the top of the screen then choosing “About [program name]”. 5) What type is your computer? Include the make, model and system specification, if you know them. For example: HP Pavilion 714a, Pentium 4, 2.4Ghz. If you can, also include how much RAM you have installed, size of hard drive, CD drive type etc. For Internet or email problems give us your ISP company name (Xtra, Ihug or Orcon etc), modem brand and connection type (56K dial-up, Jetstream, Woosh wireless, etc). Please supply as much information as you are able. 6) What if I don’t have any idea what is causing the problem with my operating system/software/hardware? Don’t worry, just do the best you can. Someone will be able to assist you in getting the required information as long as they have somewhere to start. However, if you don’t tell us anything and you don’t ask either, you will get a very short reply, if any at all. We recommend that you look at this [Link] for tips on gathering information from your computer. 7) What have you tried so far? Explain what you have tried so far to fix the problem, or what you have done to find the information you need. Don’t forget to search on Google for any error message you are getting, you may find your answer straight away. 8) You don’t need to write a book, but: If you can supply all of the above in clear, succinct English then great, you will get helpful replies, but please do not worry if you cannot supply all the detail right now. Diagnosing computer problems is often a process of elimination through a series of Q & A. Unfortunately we cannot see what you have on your screen, but we may well recognise it if you can describe it to us. 9) Let’s all speak the same language, it helps avoid confusion: Please do not use txt, 1337 speak or other abbreviated/coded language. 10) Please try the services already available first: To help you find the information yourself and assist you to get the very best out of Press F1, click on [This Link]*. There is also a very good Press F1 FAQ section at LINK (pressf1.pcworld.co.nz) that has common computer problems, things you could try and a number of useful How-To’s. 11) Keep your questions all in one place: Please keep all questions related to your problem in the one topic thread. If you get no answers to your problem or it does not appear to be getting resolved DO NOT start a new thread on the same problem. Just add another post in your original thread to say that you still need help. Maybe you need to add or modify the information to help people understand your problem (See the above FAQ Link). Not every problem gets solved, but people here do have a good crack at what they can. Cheers, Murray P et al. With special thanks to Billy T, debugging and stress-testing department.	Murray P (44)
252806	2004-07-16 19:38:00	Sounds like a lot on nonsense to me. Leave things as they are. Jack	JJJJJ (528)
252807	2004-07-16 20:49:00	It all sounds good to me, a decent guide on how to post a problem is probably needed . However, as with other similar proposals in the past, the problem is getting peoples to RTFM, so don't be too disappointed if postings dont change all that much .	Terry Porritt (14)
252808	2004-07-16 20:52:00	If it even helps a few people get useful answers faster, it can't be too bad . Those that know what it says can ignore it . Based on the "you can't please all the people all the time" theory, those that need to take note of it the most probably won't read it . They never do . And to be honest, those that think about it make it as easy as possible for people to help them . There are those that forget (like I did once, where I forgot to mention OS when it was kind of fundamental to the problem) . We are only human (most of us) . As long as it doesn't pop-up over what you are trying to read intrusively, it shouldn't offend . robo .	robo (205)
252809	2004-07-16 23:20:00	Geat idea Murray P and good on you for putting in the hard yakka but really it's too long. People being who we are and comp users particularly want it all and we want it now. Needs to be more succinct. maybe just use the bold title bits and skip the elaboration. Disclaimer: If there is allowance in your sticky for a short vesion I confess I ddin't see it because I didn't read the whole thing. Which kind of proves my point really eh? :D	mark c (247)
252810	2004-07-17 01:11:00	I think its a pretty good length, but could do with just a little more abbreviation for the Sticky version. Otherwise, Ive gotta say it shows you've put in some long hard hours, very well done! Good on ya!! Chill.	Chilling_Silence (9)
252811	2004-07-17 02:05:00	It's hard to be shorter without resorting to text language and bullet points. I still wonder how many will read it. but it's worth a try. robo.	robo (205)
252812	2004-07-17 02:49:00	Looks good, but I'd have to agree with the others. Too long. I struggled trying to finish reading it. I do believe heaps of examples we could do without, one or maximum of two will do fine. At the start you said, "Try and make..." I'd just have Make! More emphasis, greater impact. Instead of listing all the parts you want details to, I think 'specifications' will do just fine. I've just had a talk to a few non-PC people, and they seem to know what I want with the word specification. If they don't, I guess they won't even know what RAM is and how much they have, what it does.... Just little details like that I believe will shorten it down. I think you could half it. I will give it a try later on when I may have more time. Not sure what you others think, but thats my opinion anyway. Other wise, the main points seem to have been covered quite well, well done! ;-)	~~~~~ s y ~~~~~ (2054)
252813	2004-07-17 03:02:00	Good effort Murray bit I think it is too long . Rather than stop there, I have copied your post below and edited (hacked?) it for brevity . Hope I haven't ruined the message . Here goes : ______________________________________________ How To Get Effective Help on PF1 . Help Us Help You . Welcome to the Press F1 Help Forum . The following guidelines should help you get the best out of Press F1 . Don’t forget to use the links provided or to try the Press F1 FAQ page, the Press F1 Forum Search function as well as Google - you may find your problem has previously been discussed and resolved on Press F1 or other help forums . 1) The Topic Title : Make the topic title as specific as possible to the problem or issue you want resolved . If a particular programme or hardware device is causing you trouble then put its name or error message in the topic . For example: “Internet Explorer, Page not found”, “PC won’t start, Invalid System Disk” etc . If you don’t know what is causing the problem, describe it as best and as briefly as you can . Single word topics such as "Help", "Urgent" etc . are not descriptive of your problem and may not get answered, given most people do not have time to read every topic . 2) The Question : Be as specific as you can . Include any error messages you receive, any pop up boxes or any unexpected outcomes . Include details of the software and/or hardware that is causing the problem . If you are unsure, just ask, or follow this [Link to FAQ 101] for more detailed advice . Include details of what you were doing (or attempting to do) at the time the problem occurred . Include the operating system (OS) installed on your computer (e . g . Windows 98SE version XX . XXX or Windows XP Service Pack 1 etc . ) and the version number of the problematic software . Also include details of how you have tried to fix the problem so far . Include details of the make, model and specifications of your computer or the specific hardware item that is causing the problem . For Internet or email-related problems give the name of the ISP, modem brand and connection type (Dial-up, Jetstream, wireless etc) . ' The more information you provide helps us to help you, but don't write a book . 3) What if I don’t know what is causing the problem? Just do the best you can . Someone will be able to assist you . However, if you don’t provide any information and don’t ask any questions, then you may not get a reply . We recommend that you look at this [Link] for tips on gathering information from your computer . Diagnosing and resolving computer problems is often a process of elimination through a series of Q & A . 4) Forum Etiquette : To avoid confusion, do not use txt, 1337 speak or other abbreviated/coded language . To avoid repeating topics already discussed, review the Press F1 FAQ's and use the search function . To help you find the information yourself and assist you to get the very best out of Press F1, click on [This Link]* . Keep all questions related to your problem in the one topic . If you do not get any answers to your problem, do not start a new topic on the same problem . If you add another post into your original topic (stating either the current status or additional information) then the topic will appear at the top of the topic list and is more likely to be seen . Don't overdo it because not every problem gets solved, although every attempt will be made to resolve your problem . ________________________________ Murray - I hope I haven't destroyed your original message or intention but I think the original was too long to read for a newbie . I followed your previous thread but previously I passed on reading the details cos it was too long . HTH Andrew	andrew93 (249)
252814	2004-07-17 03:23:00	> Murray - I hope I haven't destroyed your original > message or intention but I think the original was too > long to read for a newbie . I have to agree with andrew93 here, his(andrew93) is a lot better then yours, Plus if there are in a rush or other thing Andrew one is a lot better :) Sorry Murray :8}	stu120404 (268)
1 2 3 4 5 6