Windows Vista files repair

In Windows Vista, it can happen that suddenly, inexplicably, for error messages. The reason for these error messages can be modified or even deleted Windows files that were not important.
In Windows Vista, you have the option to repair the damaged files.








At the bottom left icon on vista Proceed to Run (or press the Windows key and R) and type cmd.



In the opened window, type the following: sfc / scannow


If the corrupted file is found, you will be asked the Windows Vista DVD back into drive.
If the message does not appear integrity violations found, then the inspection and repair is completed.

Please run through a Windows Update, it updated your system data...

»»  read more

Patching Windows 7 to Speed Up PC

Patching of Windows 7 actually works just like Windows Vista. With Windows 7, the repair programs but immediately written to disk, so that this press run from the boot manager (F8 after the BIOS) can be. Advantage here is that Windows 7 does not require any repair CD or DVD. Does the repair console / repair partition is also no longer remain the way from the installation DVD to start. After selecting the language and keyboard layout to the next screen, click Repair your "computer" or "Repair your computer". Now, all the detected Windows installations appears. Here now we will select one and click Next.

It will now offer 7 different Windows repair options:
- Startup Repair - Home Repair
Here is the Windows tries-7 Setup program will automatically find errors that prevent that Windows can be started. These are then also repaired the same.

- System Restore - System Restore Windows 7
Here, the system can be restored to a previous restore point.

- System Image Recovery - Windows 7 Image recreating
Here you can restore his system with the help of an images. To do this, however, must have created an image in Windows.

- Windows Memory Diagnostic - Windows 7 Memory Diagnostic
With this tool you can have check the memory for errors.

- Command Prompt - Windows 7 Repair Console
Herewith you start the command prompt to manually perform repairs on the system to run.

»»  read more

General information about HTTP status codes

When calling a Web browser via the HTTP protocol in a URI, then the web server that is responsible for the requested domain or IP address that request. He identified the required data on the server machine and sends them - again using the HTTP protocol - the waiting web browser. Depending on the requirement of the web browser was and what the result came out when determining the data on the server computer, the server sends the HTTP headers for the response a specific number to the calling browser. This figure represents a status code and tells you that the relationship between what the server delivers it to data that is at the desired requirement. In this way, error messages are sent, but also notes how "the requested data is access-protected." The browser can evaluate these status codes that represent the user and respond accordingly. The Web server writes the HTTP status code of the request also, if configured into its log files.

HTTP status codes are of interest to you as a web service providers in the following locations:

* In the side of the web server log files, you can check on what errors and problems lately appeared remarkably often. Also, most web site statistics projects breakdown of the totals by including HTTP status codes. It is helpful to the individual status codes, know its meaning and possible causes for its occurrence.
* CGI scripts can generate its own HTTP headers. You can also record HTTP status codes that are to be sent in response to the calling browser. The web server then goes through the data to the browser. How something works in a CGI script in Perl, is the section page for details Extended HTTP headers and HTML file header (described in connection with the CGI module in Perl).

The HTTP status codes belong to the specification of the HTTP protocol. Responsible for the specification of the W3 Consortium. The specification takes the form of page Requests for Comments (RFCs).

»»  read more

Permitted instructions. Htaccess files

You can record in an. Htaccess file exactly the same instructions found in the central configuration file, use - with a few exceptions. For example, you may download any additional side modules do not change the server name and ask for no extra memory (the DocumentRoot). -Container sind generell in so einer dezentralen Konfigurationsdatei ebensowenig zulässig wie Festlegungen für neue virtuelle Hosts." onmouseover="this.style.backgroundColor='#ebeff9'" onmouseout="this.style.backgroundColor='#fff'"> Containers are also generally in such a distributed configuration file any more acceptable as requirements for new virtual hosts. If you have such desires, please contact your provider or webmaster related - or if you have a site locally installed Apache, you change the page httpd.conf. Otherwise you have very broad freedoms. Thus it is quite possible that you may use instructions contained in the central configuration file is not present, such as language or for specific character sets or MIME types. Basically, you can configure it all yourself. But remember that there is only one in each directory. Can give htaccess file in which you must write down all the things you want to configure. To structure and hence easier to read for you is appropriate to the economical use of a few comment lines.

Despite these many opportunities in principle, but it can sometimes be drastic restrictions. What instructions will actually be available will depend on how extensive are the rights that gives you the server administrator using the AllowOverride directive in the central configuration file.

»»  read more

General Information. Htaccess files

Web servers that are compatible with the NCSA server, understand the concept of. Htaccess files. Today is one such especially on the increasingly dominant and the de facto standard-setting in the Web server Apache. When running on your server machine, ie a page Apache Web server, then you can use the technique. Htaccess files. But also for other Web servers, there are similar concepts, for example, to realize an access protection. If you do not know what is running web server software on the machine where your web hosting project, please contact your ISP or webmaster.

. htaccess files are server configuration files for directories that belong to your web site. Thus. Htaccess technique is for example the usual way to allow only certain users access to certain data. . htaccess is the answer to the frequently asked question of a "real" password protection. But with. Htaccess files, you can do much more than protect data with passwords. You can also automatically lock out all user groups (without password access) or all but certain to keep out below. You can set options for the so-called downward directory browsing (web browser calls a directory in which no default file such as index.htm is set). You can set automatic page redirects or create their own rules for the case of downward HTTP error messages. You can even offer subject to certain conditions down alternative content such as Web pages with different languages depending on the language of the used web browser - no CGI, no JavaScript. Finally, you can even set whether data is compressed to the calling browser can be transferred or whether to divert calls to individual belonging to your project addresses a different URL page.

Files with the name. Htaccess (the first sign is a point) are components of the Web server configuration. The functioning of the Web server is defined with the help of one (or several) central configuration file (s) - httpd.conf page. But these lies and are usually within the program directory of the Web server itself, to which users, which a web project management, will usually not have access. The server administrator sets in this central configuration, what permissions he wants to admit which users or which web offerings (virtual hosts). Only when a user is given the right to define the guidelines from the central configuration to override new and individually, is it the use of. Htaccess files allowed. . htaccess files can he create in the directory and edit the field in which his Web is offering. Where you care for your HTML files, graphics files, etc., so you can take it. Htaccess files, if your provider gives you this opportunity. The use of. Htaccess in Apache means that the web server to check every single page view of the requested document from recursively all directories must determine whether such a file somewhere. And this information he should not cache - because of. Htaccess files are configured server settings should be directly valid in the same moment that exists. Htaccess file, without restarting the computer. The decentralization of the configuration would cost a little computing power.

That the name. Htaccess starts with a dot, is a tradition from the Unix world. There, many directory-specific configuration files beginning with a dot, making them labeled as "hidden". Known example is the file. Profile. Files whose name starts with a dot, will be listed by the Unix console command "ls" only if the option "-a" is explicitly specified, show hidden files. Put the management of your website a graphical FTP, a client, it can happen to you, therefore, that one. Htaccess file that you uploaded just suddenly does not exist anymore. And finally, the name must also not necessarily. Htaccess loud, this name has only enforced as a convention. In the central configuration of Apache can be set also any other file name.

. htaccess files are plain text files that can be edited with a text editor. If you telnet or SSH access to that server computer has, which hosts your Web offer, you can create such files directly on the server and edit it by calling find a suitable text editor (on Unix systems, for example, the vi Editor). If you only have FTP access to the server machine, you can create such a file on your local PC using a text editor and then upload. On a Windows system, you may, however, those file names that begin with a dot, not directly given, as Windows sees the point differently. You need in your text editor, select "Save As" choose and make sure that the editor automatically makes this the name of the file name. Htaccess.txt.

. htaccess files will always apply to the directory in which they are stored, and all subdirectories thereof, and for its subdirectories. If you live in one of the subdirectories want other arrangements, you must then pass a turn. Htaccess file. The particulars of the current file, overwrite the data from. Htaccess files in directories above it.

The concept. Htaccess files to use, although one almost from the beginning to the Apache, however, the number of allowed instructions from one version to the larger, which is also the scope of what can be configured in a. Htaccess file, stable Advanced. If one of the examples mentioned here do not work for you, so please inform yourself about the version of the web server set up and beat you to the German side Apache documentation to determine whether the statement can be used in your Apache version already.

The subject matter is considerably more extensive than is shown here in a brief outline. There you can be appointed only the most important areas for which. Htaccess files can be used.

»»  read more

General information about Server Side Includes

Using Server Side Includes (also known by the acronym SSI), you can directly within HTML files, dynamic information, such as Date and time integrated. You can also run CGI programs, and include their issues, such as a counter with the number of accesses to the current file in the HTML file. Or enter the current contents of various side CGI environment variables directly in HTML off - without having to go through a separate CGI script. Server Side Includes are generally intended for smaller parts of an HTML page dynamically integrate.

Server side includes are executed only if the Web browser, the HTML file on a Web server installed calls, so with a URI of type http:// .... Condition is also that the installed Web server, the Server Side Includes supported. Not all web servers do this, others interpret some of the possible indications. If the server does not know server-side includes, do the instructions in the HTML file. When testing with a locally installed Web server, you read this, please consult the documentation of the server. When used on a public web server, ask your provider if the Web server supports Server Side Includes.

In order for a Web server now detects if an HTML file containing SSI directives, it is customary to characterize such HTML files with a specific filename extension. Usually the file extensions. Loud shtml,. Or shtm. Sht. Most servers ignore SSI directives if they have html in a normal HTML file with the extension. Htm or.!


Server Side Includes, you need to record in an HTML file within a page commentary. There are several server side include statements, beginning with a pound # sign. In the above example, the statements # echo # exec and do occur. Behind the statement is usually followed an indication of the type Type = "value". In connection with the instruction # echo For example, the indication var = "allows variable" where "variable" a certain name should be permitted. It can be acting on behalf of CGI environment variables or special server side include variable names (see below list of known server-side includes, below). With the # exec who runs a program on the server computer, you have the type of program (in the example above: cgi) and as the value of the address of the executable program (in the above example: "/ cgi-bin/plapper. pl "state).

»»  read more

Our own web server

Many PC users with Internet access combined with the term "web server" a kind of mainframe computers on which are the data that can be seen on the Internet. Actually, a Web server, however, a not particularly great software that can run on any computer, in principle, not only on server computers on the Internet, but also on any PC. It is not even an Internet connection is required to operate a web server. There have only TCP / IP sockets are supported (Windows, for example, the file is) winsock.dll responsible. If your operating system ie TCP / IP sockets support, have already met all the prerequisites to a Web server offline and run without connection expenses. Browsers and Web servers will run on the same machine, but can then communicate with each other, as is customary on-line connections to the Internet.

Your own Web server, you should be treated here in relation to install locally on your PC to a CGI interface to have. For CGI works only when a Web server is available. Much of what is possible on the WWW with CGI, you can create complete locally on your PC. So you can test your own CGI scripts during the construction phase alone and without on-line costs. You can then work the same way as you have HTML files or JavaScripts are accustomed. In addition, you tend to get a feel for the collaboration between browsers and web servers.

Even if you yourself are provider, a leased connection to the Internet and have run a public web server, it makes sense to set up on a separate machine to work on a local Web server. So, do not burden the public computer while you create CGI scripts and test.

A locally installed Web server does not affect your existing Internet access. He uses only the TCP / IP protocol on your computer (eg winsock.dll) die. Settings that are important for your online connection to the Internet, not interested in the Web server and can remain unchanged.

An installed Web server is reachable when an Internet connection via the Web, if you have not run the PC into a secure local area network or equipped with additional protection software (firewall software). Because every time you connect to the internet you are registered with a unique IP address. Either you get from your provider has a fixed IP address, or IP address when dialing into the Internet dynamically assigned by the dial-in server. On Windows (Windows 9x) you can when an Internet connection in the Windows directory, the program winipcfg.exe call to see your own IP address, from Windows 2000 to use) the cmd.exe (command prompt and enter ipconfig to view the Windows IP can display configuration. Suppose you are registered with the IP address 145,233,101,211, then your local web server running on the Internet at the address http://145.233.101.211/ reach. This address must be a foreign user to know, of course, for now. But if he or she knows, they may on your PC in the directory area which is defined by the web server, "surf". This can have advantages and disadvantages. On the one hand, you can show other people this way your Web pages without having to upload them to a public computer to have. The other hand, an uninvited visitor could try to herumzuspionieren on your PC.

after obennach below
Applicable Products

Fortunately, there are several web servers on the Internet for downloading, which are freeware or shareware, that is, These products do not cost anything or require only after a free trial, a small registration fee. For local use of these products are sufficient. The Internet most popular English-language web site apache is also available for typical PC operating systems like Windows. Given the fact that this product is already serving on the majority of servers on the Internet their service, it is probably the most recommendable product.

In the link directory of the online offer of SELFHTML currently see a product overview with links to the vendors:

Online server side SELFHTML-Link Directory: Software

On the provider side, you can download the products in general.

after obennach below
Basic settings for the local operation

A web server is not a program with "desktop". By invoking the executable program file, simply restart the server operation. Your browser is then able to communicate with the server on your computer, just as the browser can communicate with any public web server. Before the work properly, you must set up your web server, however, that is, important basic settings.

Some Web servers can dialog-After starting up (eg OmniHTTPd Quid Pro Quo for Windows or Macintosh), and for other products set up the Web server before the first start by editing configuration files (in this example, Apache is the httpd.conf file in the Programmunterverzeichnis conf). Some products run on Windows in a DOS window (eg Apache), but can be set as background services on more modern environments. Search in doubt after installing the web server in the program directory for help files. There should be documented, as you can set up your web server. All settings remain stored in any case. If your Web server so only work one time, you will need him even more by starting and stopping the program file on and off. You can usually even with the help of some generated during the installation messages reach the start menu.

The following important information you need to set as desired or correct:

* IP address and hostname of the server
For local operation, you need to here usually the reserved IP address 127.0.0.1 or localhost adding the reserved host. If the details do not work, try to find the help file for details, or contact the product provider of the Web server on its home page (for e-mail address search!) In combination. When working the details, you can switch the browser to the web server locally stored HTML files on the Internet site addresses http://127.0.0.1/ or http://localhost/.
* Port of the server
It is usually entered 80th Ports are numbers for TCP / IP services on the computer in question. For frequently used services so-called Well Known Ports are set. This means that these port numbers are used by clients such as browsers and FTP clients default, unless explicitly stated otherwise. For the FTP service are, say, 20 and 21, the default port numbers for the HTTP service, it is 80 Read the documentation for safety but for the web server, which number you should enter here.
* HTTP root directory for HTML files (document root)
You specify your operating system according to the syntax of the pathname, below which are your local HTML files. If you use Windows, you could be here, for example type c: \ www \ data - depending on where you put your local HTML file entry. If you MyHome.htm in this directory, for example a file, you can save this file when turned on web server with your browser through the HTTP protocol on http://127.0.0.1/myhome.htm or http://localhost/myhome.htm . Call
* Default HTML file name for directories
The most common name for it is index.html or index.htm. If there is an HTML file with the appropriate name in a directory that is enough for a URI, for example http://127.0.0.1/verzeichnis/ is then loaded with http://127.0.0.1/verzeichnis/index.html.
* Physical and virtual directory for CGI scripts
As a physical directory, type according to the syntax of your operating system pathname of the directory in which you want to drop executable CGI scripts. The usual name for this directory is cgi-bin. Example, if you use Windows, you could be here, for example c: \ www \ cgi-bin type - depending on where you want to put the CGI scripts. The directory in question you have. Create You must also specify at most a virtual web server CGI directory. Wear this best / cgi-bin. If you for example, a Perl script called guestbook.pl in the c: \ www \ cgi-bin store, you can do it with http://127.0.0.1/cgi-bin/guestbook.pl or http://localhost / run cgi-bin/guestbook.pl.
* Perl interpreter and other interpreters
In order to Perl scripts as CGI scripts are running, you must specify the full pathname of the Perl interpreter executable file. On Windows, you must, for example c: \ program files \ perl \ bin \ perl.exe enter, depending on where you will find the executable. You need to install Perl side or the Perl interpreter.
* Log Files
Most web servers run "logs" of all HTTP requests to files or CGI programs. These are the standard side log files. There are two important log files: one for the logging of accesses (access.log) and an error.log for error logging (). Wear a best of these typical names, if your web server has no standard definitions for it. These files, you can present any issues with a file viewer or text editor, they show you important information if you have any problems during the current server operation.
* Timeouts
There are time limits for how long the browser wait for a response from the server, and how long the server tries to send data to the browser. The information shall normally be in the form of a second. Enter for example for sending and receiving 60 (= one minute) a.
* MIME types
Page MIME types set in this context, the file formats that knows the web server and is willing to transfer to the calling browser. Other file types than those listed above does not send the server with the correct MIME type, or text with the adjusted standard MIME-type (/ eg plain). Normally preconfigured all major file types. To add a specific file type (eg, Excel files), you must specify a MIME type name (eg, application / ms-excel) and a typical filename extension (eg. Xls). Then the server is ready to transfer files, even those with the correct MIME type to the browser. The browser needs to know, of course, what to do with that file type (see the section page references to arbitrary files on the Internet.

»»  read more

The Apache HTTP - Webserver

General

Today (early 2007) the world's most widely used Web server was first published in April 1995 in a version 0.6.2. It was the result of cooperation between a small group of developers who had set itself the goal to create some bugfixes and patches for already in the NCSA (National Center for Supercomputing Applications) at the University of Illinois, the software used. This first collection of patches, the software also owes its name: a patch--e. The association that the name of the server might be derived from the name of an Indian tribe, while most will have been dragged into the calculus.

The 90s of the last century in the onset of explosion of the Internet encouraged further work by the developer at the same time offered enormous and conditions to ensure that the needs for the use of reliable server software rose drastically. In addition, because the Apache from the beginning an open-source development, everyone should be free and available. The developer community grew rapidly, so it was finally, in 1999 establishing the English-language page Apache Software Foundation. The development work is continually pursued.

The Apache enstammt the UNIX world, though there have long been ported to other computer architectures and platforms, including of course, for Windows systems. Since Windows 95, 98 and ME are not Mehrbenutzerbetriebssyteme are familiar with and therefore no special rights for different users, is discouraged by the Apache Software Foundation, Apache on a mission of such systems in the public service in English page. Do you need to use for public functions is a Windows system, you use one of the more modern NT-based systems (Windows NT, 2000, XP or 2003). In addition, you should use an Apache for Windows version 2, since it uses the corresponding English page multiprocessing module (MPM) and thus significantly more stable, more reliable and run faster than the older Apache 1.3.x. If you only need a web server in the private sector or on a single computer to test your scripts, you can also use one of the older systems as well as the older version of Apache, if you nothing else is available.
Note:

If you try to Apache 2.0.x or 2.2.x to install Windows Vista, can it ever come to the installed version in your system (Home, Basic, Enterprise, or Ultimate) in unexpected problems. Try to log in before installation, as an administrator or use the "Run as administrator", then should a seemingly non-existing problems such as configuration file or the message "can not be set up as a service can be avoided."

after obennach below
The Apache Modules

For each platform can be either pre-compiled package for Windows (for example, download msi installation packages) as well as complete source code, so each user can decide how he wants to "build his" Apache. This would require already requires some experience in dealing with a C compiler and Makefiles. But precisely because it is also possible to make only limited statements about a "standard" installation. The server itself is usually only a relatively small executable file. However, it can appeal to a wide range depending on the configuration of modules, with some very extensive additional features - and it may be that you are such modules like themselves "solid" would like to include into the executable. This modular approach has enormous benefits in itself, and has probably prevailed only because the Apache from the beginning, just nothing much more than a collection of patches around a main executable file was.

The modular concept was from the beginning part of the "construction" of the Apache and is regarded as one of its great strengths. There are currently some minor differences between the two "branches": the younger version of Apache 2.xx consistently uses the use of English-language page multi-processing modules (MPM), which were designed to ensure that the Apache idiosyncrasies of the platform, at which it is used may take into consideration. Same time, this MPM control a number of central German side instructions that are almost always needed in the Apache configuration. The older version of Apache 1.3.x is not yet a modular structure with the same rigor. It is still on many servers distributed on the Internet, but will be gradually replaced by the younger version.

There are different groups of modules: basic modules (or core modules) and other modules. Another group assignment can be made according to the state - so according to the manner in which they are compiled: multiprocessing module (MPM), base modules, expansion modules, experimental and external modules. Particularly interesting are the MPM, which is only for Apache 2.xx, there (Apache 1.3.x follows another, older module concept). Although in several sources of such modules are available, is always one and only one is needed that is tailored to the application platform. On a Windows machine can therefore be used only mpm_winnt. This has to do with the fact that Windows has no real multi-process system, and can be started for the Apache only two processes - the actual server process and a "child" process. On a Linux machine, however, can different "child" processes run parallel.

The server is running the core modules (and possibly statically compiled modules are always) available. There are currently only three core modules, but which have enormous significance:

* Core (only Apache 2.xx) - allows the use of containers in the httpd.conf, the response of server directories and files, setting ServerRoot and DocumentRoot, the creation of log files, the response of a port, aliases ... in short, the really important features that one wants to define as an administrator in the httpd.conf, so that possible in the first.
* Http_core - is responsible for KeepAlive and thus for the lifetime of HTTP connections. In Apache 1.3.x responsible for all the core statements.
* Mod_so - allows access to other modules to find the LoadModule statement as a DSO using
* (+ MP module in Apache 2.0.x)

»»  read more

Troglodyte Lyrics

Note: While there is a pounding beat in the background, the
song is spoken rather than sung

What we're gonna do right here is go back, way back, back into time.
When the only people that existed were troglodytes...cave men...
cave women...Neanderthal...troglodytes. Let's take the average
cave man at home, listening to his stereo. Sometimes he'd get up,
try to do his thing. He'd begin to move, something like this:
"Dance...dance". When he got tired of dancing alone, he'd look
in the mirror: "Gotta find a woman gotta find a woman gotta find a
woman gotta find a woman". He'd go down to the lake where all the
woman would be swimming or washing clothes or something. He'd look
around and just reach in and grab one. "Come here...come here".
He'd grab her by the hair. You can't do that today, fellas, cause
it might come off. You'd have a piece of hair in your hand and she'd
be swimming away from you (ha-ha). This one woman just lay there,
wet and frightened. He said: "Move...move". She got up. She was a
big woman. BIG woman. Her name was Bertha. Bertha Butt. She was one
of the Butt sisters. He didn't care. He looked up at her and said:
"Sock it to me sock it to me sock it to me sock it to me sock it to me
sock it to me sock it to me sock it to me!". She looked down on him.
She was ready to crush him, but she began to like him. She said
(falsetto):
"I'll sock it to ya, Daddy". He said: "Wha?". She said (falsetto):
"I'll sock it to ya, Daddy". You know what he said? He started it way
back then. I wouldn't lie to you. When she said (falsetto)
"I'll sock it to ya, Daddy" he said "Right on! Right on! Hotpants!
Hotpants! Ugh...ugh...ugh".

»»  read more

The Troglodyte / Caveman

A caveman or troglodyte is a popular stock character based upon popular concepts of the way in which early prehistoric humans may have looked and behaved. The archetype of "cavemen" originates with the discovery of Neanderthal remains. The term caveman, sometimes used colloquially to refer to Neanderthal or Cro-Magnon people, originates out of assumptions about the association between early humans and caves, most clearly demonstrated in cave painting.

Archetype
Popular conceptions of cavemen can be seen as reflecting either the brutal savage image of the 17th-century philosopher Thomas Hobbes, who famously held that the life of the human being without civilization was "...poore, nasty, brutish and short"; or, on the other hand, the noble savage vision of uncivilized man, popularly associated with Rousseau.

Caveman-like Heraldic "wild men" were found in European iconography for hundreds of years. During the Middle Ages, these creatures were generally depicted in art and literature as bearded and covered in hair, and often wielding clubs and dwelling in caves. While wild men were always depicted as living outside of civilization, there was an ongoing debate as to whether they were human or animal.

Cavemen are portrayed as wearing shaggy animal hides, and armed with rocks or cattle bone clubs, unintelligent, and aggressive. Cavemen are often shown as living in caves, possibly because that is where the proponderance of ritual paintings and artifacts have been found. Although it is probable that neanderthals and early humans lived elsewhere as well as in caves, artifacts proving this would have been destroyed over millenia, while that which had been left in caves survived to be discovered. Nevertheless, expressions such as "living in a cave" have become cultural metaphors for a modern human who supposedly displays traits of brutishness or extreme ignorance. See also troglodyte.

*wikipedia

»»  read more