Welcome to www.minisinbox.com

Some Beginner Tips for Writing a Book (writing a book) Before you begin your book writing adventure, you must research your idea and see if it will fly. Who is going to read it? Who are you trying to appeal to with your words? You must have a general idea of who your intended audience will be. Check out other books. Is there a book already published that resembles your book? What will make your book unique from theirs? If there are similar books already out there, what is going to make your book different and make people want to buy it? If you are still reading, then it is safe to assume that you have your idea under control and are ready to more on in writing a book. Decide on a schedule that is best for you, one that you will be able to stick to. It will be very frustrating to you if have unrealistic expectations and then are unable to stick to them. Your schedule should begin before your research and carry through to the book being ready for publication. Make a detailed outline with the main plot, events leading to that plot, and explicit detail about the characters. By having more information about the character you will be able to become them as you are writing. By having background on them, even if it is irrelevant to the story, it may help while choosing their actions, dialogue, and feelings through out the book. An outline is also a good reference point to come back to double check your timelines and details. You may want to turn of you editing software for your first draft. While writing a book the first draft is when you begin meshing the plot, the characters, and everything together. Grammar, spelling, and punctuation can be fixed later. Remember books do not necessarily have to be written front to back. By writing different chapters or events it may be easier for you to come back and connect them later. Sometimes having the words on the paper and reading will make it easier to fill in the blanks. You are on a role and rough draft is finished. Now is the time to read it. When writing a book reading the rough draft will allow you to make sure that there are no errors in the timeline, that plots link with the characters, and that it all makes sense and flows together. Once you have accomplished that turn your editing software back on. It is time to fix your grammar, spelling, and punctuation mistakes. Now put you book aside. Let it sit for about two weeks or so before you pick it up again. This will give your mind time to be clear and fresh. Now read the book again. Does it still flow and make sense? Do you need to add something or change it? Now is the time. Choose someone to proofread your book for you. If at all possible you should hire a professional editor to do this. But if you cannot ask a colleague or maybe someone else you know with a writing or English background. While giving professional advice they will also be able to offer you and unbiased opinion. They will be able to see if there is a jump in the timeline you didn’t notice or if you had a character in the beginning and they just disappeared. The last thing to do while writing a book is creating the final draft. The final draft should be error free. This is your last chance to change anything before it goes to the publisher. Now is when all that time you spent writing a book comes together to make its trip to publication.

Web Hosting - Redundancy and Failover Among the more useful innovations in computing, actually invented decades ago, are the twin ideas of redundancy and failover. These fancy words name very common sense concepts. When one computer (or part) fails, switch to another. Doing that seamlessly and quickly versus slowly with disruption defines one difference between good hosting and bad. Network redundancy is the most widely used example. The Internet is just that, an inter-connected set of networks. Between and within networks are paths that make possible page requests, file transfers and data movement from one spot (called a 'node') to the next. If you have two or more paths between a user's computer and the server, one becoming unavailable is not much of a problem. Closing one street is not so bad, if you can drive down another just as easily. Of course, there's the catch: 'just as easily'. When one path fails, the total load (the amount of data requested and by how many within what time frame) doesn't change. Now the same number of 'cars' are using fewer 'roads'. That can lead to traffic jams. A very different, but related, phenomenon occurs when there suddenly become more 'cars', as happens in a massively widespread virus attack, for example. Then, a large number of useless and destructive programs are running around flooding the network. Making the situation worse, at a certain point, parts of the networks may shut down to prevent further spread, producing more 'cars' on now-fewer 'roads'. A related form of redundancy and failover can be carried out with servers, which are in essence the 'end-nodes' of a network path. Servers can fail because of a hard drive failure, motherboard overheating, memory malfunction, operating system bug, web server software overload or any of a hundred other causes. Whatever the cause, when two or more servers are configured so that another can take up the slack from one that's failed, that is redundancy. That is more difficult to achieve than network redundancy, but it is still very common. Not as common as it should be, since many times a failed server is just re-booted or replaced or repaired with another piece of hardware. But, more sophisticated web hosting companies will have such redundancy in place. And that's one lesson for anyone considering which web hosting company may offer superior service over another (similarly priced) company. Look at which company can offer competent assistance when things fail, as they always do sooner or later. One company may have a habit of simply re-booting. Others may have redundant disk arrays. Hardware containing multiple disk drives to which the server has access allows for one or more drives to fail without bringing the system down. The failed drive is replaced and no one but the administrator is even aware there was a problem. Still other companies may have still more sophisticated systems in place. Failover servers that take up the load of a crashed computer, without the end-user seeing anything are possible. In fact, in better installations, they're the norm. When they're in place, the user has at most only to refresh his or her browser and, bingo, everything is fine. The more a web site owner knows about redundancy and failover, the better he or she can understand why things go wrong, and what options are available when they do. That knowledge can lead to better choices for a better web site experience.

Web Hosting - Email Issues When you build a web site, you often provide a means for users to communicate with you. One of the most common 'add-ons' to a web site is the addition of some kind of email access. Email is used to sign users up for newsletters, provide communication for administrative issues and a hundred other uses. But, as everyone sadly knows, email problems can occur. Virus infection is among the most common, though the situation is actually better today than in the past. Huge efforts, and some progress, has been made over the past 10 years to reduce the number and severity of virus attacks. Hackers haven't surrendered, far from it. But they're on the defensive like never before. Many of those viruses were (and are) spread through email, usually in the form of email attachments. That's the source of the now-common advice never to open an attachment from someone you don't know. Professionals will often extend that advice to suggest you never open an attachment that's unexpected, even if it's from someone you know. Well-meaning, but computer-challenged friends often accidentally forward virus infected emails. Spam has taken over the top spot for email annoyances. It's estimated by various different professional sources that 92-97% of all email sent today is spam. While the definition varies, spam is generally regarded as any unwanted commercial email sent by someone whom the recipient doesn't know or have a business relationship with. Spam clutters email inboxes, requires people to sift through to find valid messages, and often contains offensive messages in some form. But, it's a fact of life and isn't going away anytime soon. Even though laws are in place, thousands of spammers continue to risk fines or jail for the chance of making money from that small percentage who will open the unwanted email. Other forms of email problems are even more severe for many web site owners. When the mechanisms fail that they rely on to send and receive messages to and from their users, that's a problem. Dealing with those problems can range from sending an email or instant message to an administrator, to tracking down the right person to get your site removed from a blacklist. Email is the communications vehicle of choice for millions everyday. When the system burps, someone has to take time to do something about it. Often, that means relying on a person who is already overburdened with too many issues to resolve. So, besides pointing out some sad facts or complaining, what's the point? All of the above shows just one more area you should look at when selecting a web host or deciding whether to move to another. Just as with server or network administration, companies vary in their ability to deal with email-related issues. Some are responsive and super-competent. Others, are simply indifferent or worse. And many are in between. Email administration, like server maintenance or network management, is a professional specialty. Skill in one does not necessarily mean quality work in another. Finding a web hosting company and/or system that has few email problems, and solves them quickly when they occur, is an important task. Spend some time researching who provides superior support in email. You'll be happy you did.