You Find Words 2001 v1.0 serial key or number

You Find Words 2001 v1.0 serial key or number

You Find Words 2001 v1.0 serial key or number

You Find Words 2001 v1.0 serial key or number

[Updated] Windows XP Product Keys Free for You – All Edition

Windows XP Product keys for free. Windows XP was developed by Microsoft and was released in 2001. It was succeeded by Windows Vista. Windows XP received positive reviews with its users, with critics noting increased performance, a more intuitive user interface, improved hardware support, and its expanded multimedia capabilities. It came with its Windows XP product key.

Despite some initial concerns over the new licensing model and product activation system, Windows XP eventually proved to be popular and widely used. As of January 2017, Windows XP desktop market share is 10.34% according to NetMarketshare. It is a 3rd most popular version of Windows. This comes with its Windows XP product keys.

We have also shared Windows 8 keys and Windows 7 product keys. Do check them!

[Working] Windows XP Product Keys Free

When you buy a genuine Windows XP, you get a genuine Windows product key. These free product key for Windows XP will help to make sure that you are using genuine Windows. When you receive this 25 digit Windows XP product keys, you have to follow a process to activate the windows in your system. Below you will find how you can activate your Windows XP with a free product key for Windows XP.


How to Activate Windows XP

Follow the steps correctly to activate Windows XP,

  1. Click on the start button on Windows XP after installation.
  2. Then in option, my computers go to properties and click on it.
  3. Check windows activation and click on change product key, then press ok.
  4. Then copy or type Windows XP product keys which are given as above and paste it into the activation box. Then press ok.
  5. Now you are done by entering your activation key.
  6. Press OK and restart the system to use your Windows XP uninterrupted.

Above is the process how you can use your genuine windows. It’s always better to use genuine windows than a copy, as genuine windows do not create any problems or interruption. Genuine Windows come with full support from its manufacturer Microsoft. So if your budget allows always go for genuine windows and genuine product keys which will help you to get the best out of the product.

Filed Under: Product Keys, Serial Number

Источник: []
, You Find Words 2001 v1.0 serial key or number

Chapter 3: Using PuTTY

Previous | Contents | Index | Next

This chapter provides a general introduction to some more advanced features of PuTTY. For extreme detail and reference purposes, chapter 4 is likely to contain more information.

3.1 During your session

A lot of PuTTY's complexity and features are in the configuration panel. Once you have worked your way through that and started a session, things should be reasonably simple after that. Nevertheless, there are a few more useful features available.

3.1.1 Copying and pasting text

Often in a PuTTY session you will find text on your terminal screen which you want to type in again. Like most other terminal emulators, PuTTY allows you to copy and paste the text rather than having to type it again. Also, copy and paste uses the Windows clipboard, so that you can paste (for example) URLs into a web browser, or paste from a word processor or spreadsheet into your terminal session.

PuTTY's copy and paste works entirely with the mouse. In order to copy text to the clipboard, you just click the left mouse button in the terminal window, and drag to select text. When you let go of the button, the text is automatically copied to the clipboard. You do not need to press Ctrl-C or Ctrl-Ins; in fact, if you do press Ctrl-C, PuTTY will send a Ctrl-C character down your session to the server where it will probably cause a process to be interrupted.

Pasting is done using the right button (or the middle mouse button, if you have a three-button mouse and have set it up; see section 4.11.2). (Pressing Shift-Ins, or selecting ‘Paste’ from the Ctrl+right-click context menu, have the same effect.) When you click the right mouse button, PuTTY will read whatever is in the Windows clipboard and paste it into your session, exactly as if it had been typed at the keyboard. (Therefore, be careful of pasting formatted text into an editor that does automatic indenting; you may find that the spaces pasted from the clipboard plus the spaces added by the editor add up to too many spaces and ruin the formatting. There is nothing PuTTY can do about this.)

If you double-click the left mouse button, PuTTY will select a whole word. If you double-click, hold down the second click, and drag the mouse, PuTTY will select a sequence of whole words. (You can adjust precisely what PuTTY considers to be part of a word; see section 4.11.5.) If you triple-click, or triple-click and drag, then PuTTY will select a whole line or sequence of lines.

If you want to select a rectangular region instead of selecting to the end of each line, you can do this by holding down Alt when you make your selection. You can also configure rectangular selection to be the default, and then holding down Alt gives the normal behaviour instead: see section 4.11.4 for details.

(In some Unix environments, Alt+drag is intercepted by the window manager. Shift+Alt+drag should work for rectangular selection as well, so you could try that instead.)

If you have a middle mouse button, then you can use it to adjust an existing selection if you selected something slightly wrong. (If you have configured the middle mouse button to paste, then the right mouse button does this instead.) Click the button on the screen, and you can pick up the nearest end of the selection and drag it to somewhere else.

It's possible for the server to ask to handle mouse clicks in the PuTTY window itself. If this happens, the mouse pointer will turn into an arrow, and using the mouse to copy and paste will only work if you hold down Shift. See section 4.6.2 and section 4.11.3 for details of this feature and how to configure it.

3.1.2 Scrolling the screen back

PuTTY keeps track of text that has scrolled up off the top of the terminal. So if something appears on the screen that you want to read, but it scrolls too fast and it's gone by the time you try to look for it, you can use the scrollbar on the right side of the window to look back up the session history and find it again.

As well as using the scrollbar, you can also page the scrollback up and down by pressing Shift-PgUp and Shift-PgDn. You can scroll a line at a time using Ctrl-PgUp and Ctrl-PgDn. These are still available if you configure the scrollbar to be invisible.

By default the last 2000 lines scrolled off the top are preserved for you to look at. You can increase (or decrease) this value using the configuration box; see section 4.7.3.

3.1.3 The System menu

If you click the left mouse button on the icon in the top left corner of PuTTY's terminal window, or click the right mouse button on the title bar, you will see the standard Windows system menu containing items like Minimise, Move, Size and Close.

PuTTY's system menu contains extra program features in addition to the Windows standard options. These extra menu commands are described below.

(These options are also available in a context menu brought up by holding Ctrl and clicking with the right mouse button anywhere in the PuTTY window.) The PuTTY Event Log

If you choose ‘Event Log’ from the system menu, a small window will pop up in which PuTTY logs significant events during the connection. Most of the events in the log will probably take place during session startup, but a few can occur at any point in the session, and one or two occur right at the end.

You can use the mouse to select one or more lines of the Event Log, and hit the Copy button to copy them to the clipboard. If you are reporting a bug, it's often useful to paste the contents of the Event Log into your bug report.

(The Event Log is not the same as the facility to create a log file of your session; that's described in section 3.2.) Special commands

Depending on the protocol used for the current session, there may be a submenu of ‘special commands’. These are protocol-specific tokens, such as a ‘break’ signal, that can be sent down a connection in addition to normal data. Their precise effect is usually up to the server. Currently only Telnet, SSH, and serial connections have special commands.

The ‘break’ signal can also be invoked from the keyboard with Ctrl-Break.

The following special commands are available in Telnet:

  • Are You There
  • Break
  • Synch
  • Erase Character

    PuTTY can also be configured to send this when the Backspace key is pressed; see section 4.16.3.

  • Erase Line
  • Go Ahead
  • No Operation

    Should have no effect.

  • Abort Process
  • Abort Output
  • Interrupt Process

    PuTTY can also be configured to send this when Ctrl-C is typed; see section 4.16.3.

  • Suspend Process

    PuTTY can also be configured to send this when Ctrl-Z is typed; see section 4.16.3.

  • End Of Record
  • End Of File

In an SSH connection, the following special commands are available:

  • IGNORE message

    Should have no effect.

  • Repeat key exchange

    Only available in SSH-2. Forces a repeat key exchange immediately (and resets associated timers and counters). For more information about repeat key exchanges, see section 4.19.2.

  • Cache new host key type

    Only available in SSH-2. This submenu appears only if the server has host keys of a type that PuTTY doesn't already have cached, and so won't consider. Selecting a key here will allow PuTTY to use that key now and in future: PuTTY will do a fresh key-exchange with the selected key, and immediately add that key to its permanent cache (relying on the host key used at the start of the connection to cross-certify the new key). That key will be used for the rest of the current session; it may not actually be used for future sessions, depending on your preferences (see section 4.20.1).

    Normally, PuTTY will carry on using a host key it already knows, even if the server offers key formats that PuTTY would otherwise prefer, to avoid host key prompts. As a result, if you've been using a server for some years, you may still be using an older key than a new user would use, due to server upgrades in the meantime. The SSH protocol unfortunately does not have organised facilities for host key migration and rollover, but this allows you to manually upgrade.

  • Break

    Only available in SSH-2, and only during a session. Optional extension; may not be supported by server. PuTTY requests the server's default break length.

  • Signals (SIGINT, SIGTERM etc)

    Only available in SSH-2, and only during a session. Sends various POSIX signals. Not honoured by all servers.

With a serial connection, the only available special command is ‘Break’. Starting new sessions

PuTTY's system menu provides some shortcut ways to start new sessions:

  • Selecting ‘New Session’ will start a completely new instance of PuTTY, and bring up the configuration box as normal.
  • Selecting ‘Duplicate Session’ will start a session in a new window with precisely the same options as your current one - connecting to the same host using the same protocol, with all the same terminal settings and everything.
  • In an inactive window, selecting ‘Restart Session’ will do the same as ‘Duplicate Session’, but in the current window.
  • The ‘Saved Sessions’ submenu gives you quick access to any sets of stored session details you have previously saved. See section 4.1.2 for details of how to create saved sessions. Changing your session settings

If you select ‘Change Settings’ from the system menu, PuTTY will display a cut-down version of its initial configuration box. This allows you to adjust most properties of your current session. You can change the terminal size, the font, the actions of various keypresses, the colours, and so on.

Some of the options that are available in the main configuration box are not shown in the cut-down Change Settings box. These are usually options which don't make sense to change in the middle of a session (for example, you can't switch from SSH to Telnet in mid-session).

You can save the current settings to a saved session for future use from this dialog box. See section 4.1.2 for more on saved sessions. Copy All to Clipboard

This system menu option provides a convenient way to copy the whole contents of the terminal screen (up to the last nonempty line) and scrollback to the clipboard in one go. Clearing and resetting the terminal

The ‘Clear Scrollback’ option on the system menu tells PuTTY to discard all the lines of text that have been kept after they scrolled off the top of the screen. This might be useful, for example, if you displayed sensitive information and wanted to make sure nobody could look over your shoulder and see it. (Note that this only prevents a casual user from using the scrollbar to view the information; the text is not guaranteed not to still be in PuTTY's memory.)

The ‘Reset Terminal’ option causes a full reset of the terminal emulation. A VT-series terminal is a complex piece of software and can easily get into a state where all the text printed becomes unreadable. (This can happen, for example, if you accidentally output a binary file to your terminal.) If this happens, selecting Reset Terminal should sort it out. Full screen mode

If you find the title bar on a maximised window to be ugly or distracting, you can select Full Screen mode to maximise PuTTY ‘even more’. When you select this, PuTTY will expand to fill the whole screen and its borders, title bar and scrollbar will disappear. (You can configure the scrollbar not to disappear in full-screen mode if you want to keep it; see section 4.7.3.)

When you are in full-screen mode, you can still access the system menu if you click the left mouse button in the extreme top left corner of the screen.

3.2 Creating a log file of your session

For some purposes you may find you want to log everything that appears on your screen. You can do this using the ‘Logging’ panel in the configuration box.

To begin a session log, select ‘Change Settings’ from the system menu and go to the Logging panel. Enter a log file name, and select a logging mode. (You can log all session output including the terminal control sequences, or you can just log the printable text. It depends what you want the log for.) Click ‘Apply’ and your log will be started. Later on, you can go back to the Logging panel and select ‘Logging turned off completely’ to stop logging; then PuTTY will close the log file and you can safely read it.

See section 4.2 for more details and options.

3.3 Altering your character set configuration

If you find that special characters (accented characters, for example, or line-drawing characters) are not being displayed correctly in your PuTTY session, it may be that PuTTY is interpreting the characters sent by the server according to the wrong character set. There are a lot of different character sets available, and no good way for PuTTY to know which to use, so it's entirely possible for this to happen.

If you click ‘Change Settings’ and look at the ‘Translation’ panel, you should see a large number of character sets which you can select, and other related options. Now all you need is to find out which of them you want! (See section 4.10 for more information.)

3.4 Using X11 forwarding in SSH

The SSH protocol has the ability to securely forward X Window System graphical applications over your encrypted SSH connection, so that you can run an application on the SSH server machine and have it put its windows up on your local machine without sending any X network traffic in the clear.

In order to use this feature, you will need an X display server for your Windows machine, such as Cygwin/X, X-Win32, or Exceed. This will probably install itself as display number 0 on your local machine; if it doesn't, the manual for the X server should tell you what it does do.

You should then tick the ‘Enable X11 forwarding’ box in the X11 panel (see section 4.25) before starting your SSH session. The ‘X display location’ box is blank by default, which means that PuTTY will try to use a sensible default such as , which is the usual display location where your X server will be installed. If that needs changing, then change it.

Now you should be able to log in to the SSH server as normal. To check that X forwarding has been successfully negotiated during connection startup, you can check the PuTTY Event Log (see section It should say something like this:

If the remote system is Unix or Unix-like, you should also be able to see that the environment variable has been set to point at display 10 or above on the SSH server machine itself:

If this works, you should then be able to run X applications in the remote session and have them display their windows on your PC.

For more options relating to X11 forwarding, see section 4.25.

3.5 Using port forwarding in SSH

The SSH protocol has the ability to forward arbitrary network (TCP) connections over your encrypted SSH connection, to avoid the network traffic being sent in clear. For example, you could use this to connect from your home computer to a POP-3 server on a remote machine without your POP-3 password being visible to network sniffers.

In order to use port forwarding to connect from your local machine to a port on a remote server, you need to:

  • Choose a port number on your local machine where PuTTY should listen for incoming connections. There are likely to be plenty of unused port numbers above 3000. (You can also use a local loopback address here; see below for more details.)
  • Now, before you start your SSH connection, go to the Tunnels panel (see section 4.26). Make sure the ‘Local’ radio button is set. Enter the local port number into the ‘Source port’ box. Enter the destination host name and port number into the ‘Destination’ box, separated by a colon (for example, to connect to a POP-3 server).
  • Now click the ‘Add’ button. The details of your port forwarding should appear in the list box.

Now start your session and log in. (Port forwarding will not be enabled until after you have logged in; otherwise it would be easy to perform completely anonymous network attacks, and gain access to anyone's virtual private network.) To check that PuTTY has set up the port forwarding correctly, you can look at the PuTTY Event Log (see section It should say something like this:

Now if you connect to the source port number on your local PC, you should find that it answers you exactly as if it were the service running on the destination machine. So in this example, you could then configure an e-mail client to use as a POP-3 server instead of . (Of course, the forwarding will stop happening when your PuTTY session closes down.)

You can also forward ports in the other direction: arrange for a particular port number on the server machine to be forwarded back to your PC as a connection to a service on your PC or near it. To do this, just select the ‘Remote’ radio button instead of the ‘Local’ one. The ‘Source port’ box will now specify a port number on the server (note that most servers will not allow you to use port numbers under 1024 for this purpose).

An alternative way to forward local connections to remote hosts is to use dynamic SOCKS proxying. In this mode, PuTTY acts as a SOCKS server, which SOCKS-aware programs can connect to and open forwarded connections to the destination of their choice, so this can be an alternative to long lists of static forwardings. To use this mode, you will need to select the ‘Dynamic’ radio button instead of ‘Local’, and then you should not enter anything into the ‘Destination’ box (it will be ignored). PuTTY will then listen for SOCKS connections on the port you have specified. Most web browsers can be configured to connect to this SOCKS proxy service; also, you can forward other PuTTY connections through it by setting up the Proxy control panel (see section 4.15 for details).

The source port for a forwarded connection usually does not accept connections from any machine except the SSH client or server machine itself (for local and remote forwardings respectively). There are controls in the Tunnels panel to change this:

  • The ‘Local ports accept connections from other hosts’ option allows you to set up local-to-remote port forwardings (including dynamic port forwardings) in such a way that machines other than your client PC can connect to the forwarded port.
  • The ‘Remote ports do the same’ option does the same thing for remote-to-local port forwardings (so that machines other than the SSH server machine can connect to the forwarded port.) Note that this feature is only available in the SSH-2 protocol, and not all SSH-2 servers honour it (in OpenSSH, for example, it's usually disabled by default).

You can also specify an IP address to listen on. Typically a Windows machine can be asked to listen on any single IP address in the range, and all of these are loopback addresses available only to the local machine. So if you forward (for example) to a remote machine's port, then you should be able to run commands such as . This can be useful if the program connecting to the forwarded port doesn't allow you to change the port number it uses. This feature is available for local-to-remote forwarded ports; SSH-1 is unable to support it for remote-to-local ports, while SSH-2 can support it in theory but servers will not necessarily cooperate.

(Note that if you're using Windows XP Service Pack 2, you may need to obtain a fix from Microsoft in order to use addresses like - see question A.7.20.)

For more options relating to port forwarding, see section 4.26.

If the connection you are forwarding over SSH is itself a second SSH connection made by another copy of PuTTY, you might find the ‘logical host name’ configuration option useful to warn PuTTY of which host key it should be expecting. See section 4.13.5 for details of this.

3.6 Making raw TCP connections

A lot of Internet protocols are composed of commands and responses in plain text. For example, SMTP (the protocol used to transfer e-mail), NNTP (the protocol used to transfer Usenet news), and HTTP (the protocol used to serve Web pages) all consist of commands in readable plain text.

Sometimes it can be useful to connect directly to one of these services and speak the protocol ‘by hand’, by typing protocol commands and watching the responses. On Unix machines, you can do this using the system's command to connect to the right port number. For example, might enable you to talk directly to the SMTP service running on a mail server.

Although the Unix program provides this functionality, the protocol being used is not really Telnet. Really there is no actual protocol at all; the bytes sent down the connection are exactly the ones you type, and the bytes shown on the screen are exactly the ones sent by the server. Unix will attempt to detect or guess whether the service it is talking to is a real Telnet service or not; PuTTY prefers to be told for certain.

In order to make a debugging connection to a service of this type, you simply select the fourth protocol name, ‘Raw’, from the ‘Protocol’ buttons in the ‘Session’ configuration panel. (See section 4.1.1.) You can then enter a host name and a port number, and make the connection.

3.7 Connecting to a local serial line

PuTTY can connect directly to a local serial line as an alternative to making a network connection. In this mode, text typed into the PuTTY window will be sent straight out of your computer's serial port, and data received through that port will be displayed in the PuTTY window. You might use this mode, for example, if your serial port is connected to another computer which has a serial connection.

To make a connection of this type, simply select ‘Serial’ from the ‘Connection type’ radio buttons on the ‘Session’ configuration panel (see section 4.1.1). The ‘Host Name’ and ‘Port’ boxes will transform into ‘Serial line’ and ‘Speed’, allowing you to specify which serial line to use (if your computer has more than one) and what speed (baud rate) to use when transferring data. For further configuration options (data bits, stop bits, parity, flow control), you can use the ‘Serial’ configuration panel (see section 4.28).

After you start up PuTTY in serial mode, you might find that you have to make the first move, by sending some data out of the serial line in order to notify the device at the other end that someone is there for it to talk to. This probably depends on the device. If you start up a PuTTY serial session and nothing appears in the window, try pressing Return a few times and see if that helps.

A serial line provides no well defined means for one end of the connection to notify the other that the connection is finished. Therefore, PuTTY in serial mode will remain connected until you close the window using the close button.

3.8 The PuTTY command line

PuTTY can be made to do various things without user intervention by supplying command-line arguments (e.g., from a command prompt window, or a Windows shortcut).

3.8.1 Starting a session from the command line

These options allow you to bypass the configuration window and launch straight into a session.

To start a connection to a server called :

If this syntax is used, settings are taken from the Default Settings (see section 4.1.2); overrides these settings if supplied. Also, you can specify a protocol, which will override the default protocol (see section

For telnet sessions, the following alternative syntax is supported (this makes PuTTY suitable for use as a URL handler for telnet URLs in web browsers):

To start a connection to a serial port, e.g. COM1:

In order to start an existing saved session called , use the option (described in section


If invoked with the option, rather than running as normal, PuTTY will remove its registry entries and random seed file from the local machine (after confirming with the user). It will also attempt to remove information about recently launched sessions stored in the ‘jump list’ on Windows 7 and up.

Note that on multi-user systems, only removes registry entries and files associated with the currently logged-in user.

3.8.3 Standard command-line options

PuTTY and its associated tools support a range of command-line options, most of which are consistent across all the tools. This section lists the available options in all tools. Options which are specific to a particular tool are covered in the chapter about that tool. : load a saved session

The option causes PuTTY to load configuration details out of a saved session. If these details include a host name, then this option is all you need to make PuTTY start a session.

You need double quotes around the session name if it contains spaces.

If you want to create a Windows shortcut to start a PuTTY saved session, this is the option you should use: your shortcut should call something like

(Note that PuTTY itself supports an alternative form of this option, for backwards compatibility. If you execute it will have the same effect as . With the form, no double quotes are required, and the sign must be the very first thing on the command line. This form of the option is deprecated.) Selecting a protocol: , , ,

To choose which protocol you want to connect with, you can use one of these options:

  • selects the SSH protocol.
  • selects the Telnet protocol.
  • selects the Rlogin protocol.
  • selects the raw protocol.
  • selects a serial connection.

These options are not available in the file transfer tools PSCP and PSFTP (which only work with the SSH protocol).

These options are equivalent to the protocol selection buttons in the Session panel of the PuTTY configuration box (see section 4.1.1). : increase verbosity

Most of the PuTTY tools can be made to tell you more about what they are doing by supplying the option. If you are having trouble when making a connection, or you're simply curious, you can turn this switch on and hope to find out more about what is happening. : specify a login name

You can specify the user name to log in as on the remote server using the option. For example, .

These options are equivalent to the username selection box in the Connection panel of the PuTTY configuration box (see section 4.14.1). , and : set up port forwardings

As well as setting up port forwardings in the PuTTY configuration (see section 4.26), you can also set up forwardings on the command line. The command-line options work just like the ones in Unix programs.

To forward a local port (say 5110) to a remote destination (say port 110), you can write something like one of these:

To forward a remote port to a local destination, just use the option instead of :

To specify an IP address for the listening end of the tunnel, prepend it to the argument:

To set up SOCKS-based dynamic port forwarding on a local port, use the option. For this one you only have to pass the port number:

For general information on port forwarding, see section 3.5.

These options are not available in the file transfer tools PSCP and PSFTP. : read a remote command or script from a file

The option performs a similar function to the ‘Remote command’ box in the SSH panel of the PuTTY configuration box (see section 4.18.1). However, the option expects to be given a local file name, and it will read a command from that file.

With some servers (particularly Unix systems), you can even put multiple lines in this file and execute more than one command in sequence, or a whole shell script; but this is arguably an abuse, and cannot be expected to work on all servers. In particular, it is known not to work with certain ‘embedded’ servers, such as Cisco routers.

This option is not available in the file transfer tools PSCP and PSFTP. : specify a port number

The option is used to specify the port number to connect to. If you have a Telnet server running on port 9696 of a machine instead of port 23, for example:

(Note that this option is more useful in Plink than in PuTTY, because in PuTTY you can write in any case.)

This option is equivalent to the port number control in the Session panel of the PuTTY configuration box (see section 4.1.1). : specify a password

A simple way to automate a remote login is to supply your password on the command line. This is not recommended for reasons of security. If you possibly can, we recommend you set up public-key authentication instead. See chapter 8 for details.

Note that the option only works when you are using the SSH protocol. Due to fundamental limitations of Telnet and Rlogin, these protocols do not support automated password authentication. and : control use of Pageant for authentication

The option turns on SSH authentication using Pageant, and turns it off. These options are only meaningful if you are using SSH.

See chapter 9 for general information on Pageant.

These options are equivalent to the agent authentication checkbox in the Auth panel of the PuTTY configuration box (see section 4.22.3). and : control agent forwarding

The option turns on SSH agent forwarding, and turns it off. These options are only meaningful if you are using SSH.

See chapter 9 for general information on Pageant, and section 9.4 for information on agent forwarding. Note that there is a security risk involved with enabling this option; see section 9.5 for details.

These options are equivalent to the agent forwarding checkbox in the Auth panel of the PuTTY configuration box (see section 4.22.6).

These options are not available in the file transfer tools PSCP and PSFTP. and : control X11 forwarding

The option turns on X11 forwarding in SSH, and turns it off. These options are only meaningful if you are using SSH.

For information on X11 forwarding, see section 3.4.

These options are equivalent to the X11 forwarding checkbox in the X11 panel of the PuTTY configuration box (see section 4.25).

These options are not available in the file transfer tools PSCP and PSFTP. and : control pseudo-terminal allocation

The option ensures PuTTY attempts to allocate a pseudo-terminal at the server, and stops it from allocating one. These options are only meaningful if you are using SSH.

These options are equivalent to the ‘Don't allocate a pseudo-terminal’ checkbox in the SSH panel of the PuTTY configuration box (see section 4.24.1).

These options are not available in the file transfer tools PSCP and PSFTP. : suppress starting a shell or command

The option prevents PuTTY from attempting to start a shell or command on the remote server. You might want to use this option if you are only using the SSH connection for port forwarding, and your user account on the server does not have the ability to run a shell.

This feature is only available in SSH protocol version 2 (since the version 1 protocol assumes you will always want to run a shell).

This option is equivalent to the ‘Don't start a shell or command at all’ checkbox in the SSH panel of the PuTTY configuration box (see section 4.18.2).

This option is not available in the file transfer tools PSCP and PSFTP. : make a remote network connection in place of a remote shell or command

The option prevents Plink (or PuTTY) from attempting to start a shell or command on the remote server. Instead, it will instruct the remote server to open a network connection to a host name and port number specified by you, and treat that network connection as if it were the main session.

You specify a host and port as an argument to the option, with a colon separating the host name from the port number, like this:

You might want to use this feature if you needed to make an SSH connection to a target host which you can only reach by going through a proxy host, and rather than using port forwarding you prefer to use the local proxy feature (see section 4.15.1 for more about local proxies). In this situation you might select ‘Local’ proxy type, set your local proxy command to be ‘’, enter the target host name on the Session panel, and enter the directly reachable proxy host name on the Proxy panel.

This feature is only available in SSH protocol version 2 (since the version 1 protocol assumes you will always want to run a shell). It is not available in the file transfer tools PSCP and PSFTP. It is available in PuTTY itself, although it is unlikely to be very useful in any tool other than Plink. Also, uses the same server functionality as port forwarding, so it will not work if your server administrator has disabled port forwarding.

(The option is named after the Unix program , short for ‘netcat’. The command ‘’ is very similar in functionality to ‘’, which invokes on the server and tells it to connect to the specified destination. However, Plink's built-in option does not depend on the program being installed on the server.) : enable compression

The option enables compression of the data sent across the network. This option is only meaningful if you are using SSH.

This option is equivalent to the ‘Enable compression’ checkbox in the SSH panel of the PuTTY configuration box (see section 4.18.3). and : specify an SSH protocol version

The and options force PuTTY to use version 1 or version 2 of the SSH protocol. These options are only meaningful if you are using SSH.

These options are equivalent to selecting the SSH protocol version in the SSH panel of the PuTTY configuration box (see section 4.18.4). and : specify an Internet protocol version

The and options force PuTTY to use the older Internet protocol IPv4 or the newer IPv6 for most outgoing connections.

These options are equivalent to selecting your preferred Internet protocol version as ‘IPv4’ or ‘IPv6’ in the Connection panel of the PuTTY configuration box (see section 4.13.4). : specify an SSH private key

The option allows you to specify the name of a private key file in format which PuTTY will use to authenticate with the server. This option is only meaningful if you are using SSH.

If you are using Pageant, you can also specify a public key file (in RFC 4716 or OpenSSH format) to identify a specific key file to use. (This won't work if you're not running Pageant, of course.)

For general information on public-key authentication, see chapter 8.

This option is equivalent to the ‘Private key file for authentication’ box in the Auth panel of the PuTTY configuration box (see section 4.22.8). : specify a logical host name

This option overrides PuTTY's normal SSH host key caching policy by telling it the name of the host you expect your connection to end up at (in cases where this differs from the location PuTTY thinks it's connecting to). It can be a plain host name, or a host name followed by a colon and a port number. See section 4.13.5 for more detail on this. : manually specify an expected host key

This option overrides PuTTY's normal SSH host key caching policy by telling it exactly what host key to expect, which can be useful if the normal automatic host key store in the Registry is unavailable. The argument to this option should be either a host key fingerprint, or an SSH-2 public key blob. See section 4.20.2 for more information.

You can specify this option more than once if you want to configure more than one key to be accepted. : display PGP key fingerprints

This option causes the PuTTY tools not to run as normal, but instead to display the fingerprints of the PuTTY PGP Master Keys, in order to aid with verifying new versions. See appendix E for more information. : specify serial port configuration

This option specifies the configuration parameters for the serial port (baud rate, stop bits etc). Its argument is interpreted as a comma-separated list of configuration options, which can be as follows:

  • Any single digit from 5 to 9 sets the number of data bits.
  • ‘’, ‘’ or ‘’ sets the number of stop bits.
  • Any other numeric string is interpreted as a baud rate.
  • A single lower-case letter specifies the parity: ‘’ for none, ‘’ for odd, ‘’ for even, ‘’ for mark and ‘’ for space.
  • A single upper-case letter specifies the flow control: ‘’ for none, ‘’ for XON/XOFF, ‘’ for RTS/CTS and ‘’ for DSR/DTR.

For example, ‘’ denotes a baud rate of 19200, 8 data bits, no parity, 1 stop bit and no flow control. , , : specify session logging

These options cause the PuTTY network tools to write out a log file. Each of them expects a file name as an argument, e.g. ‘’ causes an SSH packet log to be written to a file called ‘’. The three different options select different logging modes, all available from the GUI too:

  • selects ‘All session output’ logging mode.
  • selects ‘SSH packets’ logging mode.
  • selects ‘SSH packets and raw data’ logging mode.

For more information on logging configuration, see section 4.2. : specify a local proxy command

This option enables PuTTY's mode for running a command on the local machine and using it as a proxy for the network connection. It expects a shell command string as an argument.

See section 4.15.1 for more information on this, and on other proxy settings. In particular, note that since the special sequences described there are understood in the argument string, literal backslashes must be doubled (if you want in your command, you must put on the command line). : restrict the Windows process ACL

This option (on Windows only) causes PuTTY (or another PuTTY tool) to try to lock down the operating system's access control on its own process. If this succeeds, it should present an extra obstacle to malware that has managed to run under the same user id as the PuTTY process, by preventing it from attaching to PuTTY using the same interfaces debuggers use and either reading sensitive information out of its memory or hijacking its network session.

This option is not enabled by default, because this form of interaction between Windows programs has many legitimate uses, including accessibility software such as screen readers. Also, it cannot provide full security against this class of attack in any case, because PuTTY can only lock down its own ACL after it has started up, and malware could still get in if it attacks the process between startup and lockdown. So it trades away noticeable convenience, and delivers less real security than you might want. However, if you do want to make that tradeoff anyway, the option is available.

A PuTTY process started with will pass that on to any processes started with Duplicate Session, New Session etc. (However, if you're invoking PuTTY tools explicitly, for instance as a proxy command, you'll need to arrange to pass them the option yourself, if that's what you want.)

If you want to provide feedback on this manual or on the PuTTY tools themselves, see the Feedback page.

[PuTTY release 0.68]
Источник: []
You Find Words 2001 v1.0 serial key or number

Microsoft CD Keys, CD Key Generator, Genuine Advantage ValidationMicrosoft
CD Keys, CD Key Generator, Genuine Advantage Validation

If you want to make up your own key of the form nnn-nnnnnnn, it seems that the
first three digits can be any number you like while the last seven digits must
add up to a multiple of seven. A really boring (but easy to type key) is:
This key has been used successfully with:
  BackOffice 4.5 (Beta 2)
  Flight Simulator 98 (OEM)
  Liquid Motion 1.0
  Monster Truck Madness
  Office 97 Pro
  Plus! 98
  Publisher 98
  SQL Server Enterprise Edition
  Visual C++ 6.0 Standard Edition
  Visual Studio 6 (Enterprise and Pro) and 97
  Windows NT
  Word 97
I have also read that if you take an upgrade CD key and add one to the first set
of numbers (whether three or four digit) then the CD key will be for the full
If that didn't work, try this:
I am not sure what CD this is from, but I am compiling a list of all Microsoft
applications that this CD Key works with. It seems to have been the standard
with older CD's (95 thru 97). This key has been used successfully with:
  Flight Simulator 95
  Monster Truck Madness
  Office 98 for MacIntosh
  Office 2001 for MacIntosh
  Publisher 97
  Publisher 98 (with 0465 in first block)
  Sidewinder Game Pad CD
  Visual Basic 4.0 Enterprise
  Visual Basic 6.0a Professional Edition
  Visual C++ 4.0 and 5.0
  Visual C++ 4.0 Professional
  Visual C++ 5.0 Professional Edition
  Visual C++ 6.0 Pro
  Visual Studio 97
  Windows NT 4.0 Workstation
  Windows 95/98 Plus!
  Windows 95 Upgrade
  Windows 98 Beta 3
  Works 4.5

98 CD's seem to require a longer CD Key (extra digit). If you need four digits
for the first section, try:
This key has been used successfully with:
  MS Exchange Server 5.0 and 5.5.
So if the CD Key above did not work, try this:
This key has been used successfully with:
  Office 97
  Office 97 Pro
  Outlook 98
  Power Point 97 Upgrade
  Project 98
  Publisher 5.0 and 98
  Microsoft Works
  Word 97
If that one doesn't work for you, try this:
This key has been used successfully with:
  Access 97
  Front Page 98
  Office 97 Pro
  Outlook 98
  Project 98
  Publisher 98, English, Spanish Version
  Visual Basic 5.0 Professional and Enterprise Edition
  Word 97

The format for the nnnn-nnnnnnn. The first four digits seem to make a
difference, but even versus odd totals are rumored to indicate an OEM versus
upgrade CD (this hasn't been worked out). The last seven digits still must add
up to a multiple of seven, but certain combinations like all ones and anything
ending with a zero are disallowed. 4157-7777777 seems to work and is easier to

Windows 98
If your computer came with Windows 98 (i.e. you did not upgrade your computer to
Windows 98), you may need to use an OEM number which you find via this link.
With Windows 98, MS seems to have gone crazy with the length of the CD Key or
Product Key. There see to only be about three common families of CD keys, OEM,
full retail, and upgrade retail. The main thing seems to be just using a CD key
from the same family. Two less common families are corporate (which can
sometimes bypass the mandatory registration process) and academic.
Windows 98 Second Edition keys are broken out in a separate section below.
Some Windows 98 CD Keys you can try are:
  R3TQR-PQTKG-HBVQ9-YBFH3-CGCRT worked with German full, English full (OEM), UK
  Edition, Compaq English, Spanish Full, Dutch, Compaq and IBM Recovery CDs, and
  U.S. Second Edition (SE) OEM, Dell SE laptop, Toshiba 4100XDVD.
  Q2YHH-GYWV2-MDXCD-H9P2X-HYVMM worked with several versions including SE
  (Second Edition), UK Edition, and US OEM.
  R34DV-VB6WM-XMHHV-WM4Q2-WBB3Y is supposed to work with all version of first
  edition Windows 98 (4.10.98), UK Edition.
  T7J8Q-MH7RP-9H9J2-2HVFG-C3X2M worked with four U.S. retail versions
  (4.10.1998) as well as second edition version.
  JJK9P-G8JYJ-X24RC-XTFJ4-K9W4W worked with English retail version (CA), UK
  MMHK7-QPHQG-KMTP9-7GTJY-JQ6XM worked with English Retail Second Edition
  v4.10.2222A. Also, HP 4440 recovery disk, UK Edition.
  XB88B-9B96V-CRJPG-64882-GQBDD Full verison, not upgrade, also Second Edition,
  UK Edition
  DJK2X-6XFJB-Q9J7J-WGC7P-WMHYG Compaq, HP, IBM, etc., UK Edition
  MD97J-QC7R7-TQJGD-3V2WM-W7PVM came with English Developer's Connection
  Version. Seems to work with same CD's as T7J8Q... above. Also Japanese
  DCTB2-4RV9D-3TXP2-F89JK-26XWQ Universal key for all languages
  K4HVD-99TJ9-6CRXG-C9G68-R92D3 OEM French WIN98SE
  HBM43-PD86Y-9R8HM-4GM8H-TVG3Q UK Edition
  Q988C-P7VK2-K2K7R-QX9W9-7CDW3 UK Edition
Windows 98 Second Edition Upgrade CD Key that should bypass the requirement to
have Win95 installed:
  H26W6-897MW-6T4WY-P3G98-GR342 Win 98 Upgrade Second Edition, bypasses Win95
Windows 98 Second Edition (SE) CD Keys you can try are:
  RW9MG-QR4G3-2WRR9-TG7BH-33GXB Full Edition, English UK, French
  DKJQY-TMJGF-BYYPQ-Q2HB7-W2K3V Upgrade English, U.S. Version
  K4HVD-Q9TJ9-6CRX9-C9G68-RQ2D3 Win 98 Upgrade Second Edition, also 1st edition
  full retail
  HQ6K2-QPC42-3HWDM-BF4KJ-W4XWJ Win 98 Second Edition, also Danish, Norwegian
  and Norwegian OEM, UK Edition (product ID 16203-OEM-0000007-00651)
  JHD22-PY6C8-GGTJC-HYYWT-TF7MY Ver 4.10.2222A Retail
  HQ88R-P7JWC-4FYHY-DK6MV-HT3CD Plus SE U.S English Ver 4.10.2222A
  P767C-WKHX7-62TFV-H6XTP-JXFQM works with ver. 4.10.2222 English, UK Edition,
  also Packard Bell Master Recovery CD
  XQY3P-8MMD2-JC6M2-HJDYW-P6H7B, UK Edition
  d6xwh-xkvv6-t2f87-kb2kh-9h3yg from Compaq OEM system, UK Edition
  BBH2G-D2VK9-QD4M9-F63XB-43C33 Chinese Language, Full Installation
  J3R3W-VBVDF-2496X-46TQB-HH8BY Australian English. Product Key 792807368, UK
  TR9TQ-F4JRW-FXM4G-3H7V2-FH4J6 UK and Chinese Version
  W7XTC-2YWFB-K6BPT-GMHMV-B6FDY Second Edition English
  QMPMF-23D8R-83GV6-MMR3C-BQ7C3 UK Edition
  WTY8X-CQP24-MX9TD-GBBD9-JKCXP (upgrade)
  WGJTT-2Q9MV-3TB8B-DQ77Y-C6QKB UK Edition
  TVYGH-V683W-3CWT9-MQ468-G66WR Upgrade
  DBRCB-D43K3-VY4G4-KVG4H-6FK9M Australia, Compaq
  PRDDH-83JD9-G6PK4-684GF-6Y73B Dell OEM English and Dell upgrade

99 CD's have gone back to the shorter CD Key, but they have different formats
from the older keys. Try these:
This key is from MS Money 99. Both this key and the following have been used
with Visual Studio 6 Professional Edition. The above key has been used with
Visual Basic 6 Fundamentals.
This key is from MS Works 99.

A Serial Number for Visual Basic 6.0 Professional Edition is:
This serial number is also supposed to work with Visual C++, FoxPro, J++, ... as
the Product ID for the 6.0 Professional Edition.

A CD Key for Publisher 98:

A CD Key for Office 2000 and Office 10 beta is:
with product ID of:

CDs Key for Office 2000 are:
  DR674-KJWQW-HGQKT-WGDBG-4RKY3 with product ID of 450-5693453
  Q2CXY-QYYJ4-QPTBH-WPCTB-9J4MM Volume/Corporate CD Key
  RX2R4-4RDYW-269QY-7BC3J-XCFVB (Corporate CD Key)
  JFD4K-MKCDP-83R4H-7GFCQ-2C9KB Professional English SR1
  HQ6DG-JJ73M-C34Q7-W3G4H-CRB9Q UK Pro, Spanish Premium, and U.S. (standard
  upgrade) as well as Visio 2000
  R7WB4-KQDHY-YTVRF-77JXC-W7898 Spanish Premium
  C3KDQ-BJBMM-YVP9B-DQY7V-VBG9G English and Spanish SR-1, version 9.0.3821
Previously this list had included GC6J3-GTQ62-FP876-94FBR-D3DX8 but Office 2000
has invalidated all installations using this key whenever SR-1 or SR-1A is

CD Keys for Office 2000 Professional are:
  H4GW2-2M9C4-R8YWX-BYJFT-KKFQ3 Also works with Word portion of MS Works Suite
  2000 (english and swedish) and Word 2000 as well as Word 2000 (HP OEM and
  others), SR1 OEM.
  DT3FT-BFH4M-GYYH8-PG9C3-8K2FJ also premium, pre SP1
  DT3FT-BFH4M-9YYH8-PG963-8K2FJ (2nd Edition)
  RX2R4-4RDYW-S29QY-7BC3J-XCFV3 (Corporate CD Key)
  DFK97-PR8TC-9XMJJ-4JVCY-WHTP9 academic version, product ID 326-4662262

CD Keys that worked for Office 2000 Premium are:
  MP4F9-W6C8V-HTCCT-T7M7R-Y7K3Y (Also Office 10 Beta 2)
  CFGBV-3MC8H-KW2XJ-8CVP6-KBRM9 (Also SR-1, but needs registration then).

A CD Key that worked for Works Suite 2000 is:

CD Keys that worked for Office 2000 Small Business are:
  J3GX9-MDBXB-934FC-CTQJ3-KFRM8, Also Windows ME Upgrade, Works Suite 2000,
  Publisher 2000, Word 2000 (also SR-1 and OEM), Front Page 2000 and Office 2000
  Professional version (service release 1, English and Norwegian).
  W6FX3-77MJ3-JMVH2-VWP86-F4KMJ, Also Flight Simulator 2000, Works Suite 2000,
  and Word 2000 OEM.

CD Keys for Office 10 for Mac are:

A CD Key for Works 4.5a OEM version is:

This was just tried as a guess and worked. I would be interested if it worked
for any other MS applications.

CD Keys for Word 2000 are:
  BTB66-3JBDP-KJ67Q-G2CMR-7JMDX Also Access 2000 SR1 under Windows XP and Vista
  WPB69-HRK28-WYRJ9-FKK76-DGDC8 Also Works Suite 2000 and 2001
  PF64V-RVBCV-4QJJG-7Q9VC-3DVRW Canadian version

CD Keys for Front Page 2000 upgrade and full version are:
  DYQV3-XDB7C-T24YH-2Q93P-T4G7V Also Office 2000 Premium
  R6BRT-3DH6Y-22BWG-H8T6C-49BXV Also Project 2000 and Publisher 2000

CD Keys for Project 2000 Pro are:
  MDYB4-92JGJ-CV7KY-H2B39-9X4TT also worked with Visio 2000

A CD Key for Visio 2000 is:
  61000-111111 Enterprise Edition>

CD Keys for Windows 2000 Professional are:
  V8YCV-T66J9-YDHT3-D8X7W-QV89J Dell Blue and Green (business), SP4 OEM
  TXY8C-9X778-9BJ3T-6F2DC-332YF U.S. Upgrade
  K3Y7V-XXWHC-8XT9Q-HH6TC-WMFYV U.S. Upgrade from MS
  RBDC9-VTRC8-D7972-J97JY-PRVMG Also worked with Windows Whistler, build 2428 as
  well as Upgrade
  RM233-2PRQQ-FR4RH-JP89H-46QYB Retail, Optiplex GX110, Small Business Server,
  Israeli Compaq and Dell Latitude
  DY26P-7W66J-MQQQ7-QGRTQ-X8PHJ Corporate CD
  RBDC9-VTRC8-D7972-J97JY-PRVMG evaluation key, 120 days

CD Keys Windows 2000 Server are:
  VTWQ6-GQ4DB-RF2BW-RRMRR-WDMDT also SQL Server 2000 Personal Edition
CD Keys that have worked for Windows 2000 Advanced Server are:
  H6TWQ-TQQM8-HXJYG-D69F7-R84VM also Business Server
  RBDC9-VTRC8-D7972-J97JY-PRVMG also Windows 2000 Pro, may be 120 day evaluation

CD Keys that worked for Outlook 2000 are:
  WK4BC-8C9GD-WRCKV-DV39P-T8JKG also FrontPage 2000, Work Suite 2001, Gateway
  Work Suite 2003

Some keys that came with Windows ME (Millenium) are:
  RBDC9-VTRC8-D7972-J97JY-PRVMG Also worked with Windows Whistler build 2428
  C2C8Q-2P36X-JHXPJ-9KQJT-BBGPT Del OEM 00029-056-952-050
  R4J6Q-TT3GQ-FWVP9-K3XH8-2R2GB Austrian Version
  FF8PG-YQQX4-7VHW8-MC4K9-T8VPQ Full Version (Retail)

Some CD Keys that worked for Windows Millenium Upgrade are:

Some CD Keys that worked with Office XP are:
  XFX2Y-28DHH-8XHX3-RXRC8-28TCD worked with Premium edition, also Word and UK
  edition with FrontPage
  FM9FY-TMF7Q-KCKCT-V9T29-TBBBG worked with corporate Pro Enterprise and
  Professional editions, does not check in with MS
  Q4F49-MQ4YG-JCWHM-KF4QR-GRXWY Volume/Corporate CD Applications
  HWB6C-8R8YY-M4M86-PXB88-3C78G Volume/Corporate CD Suites
  RYXMW-P6PFM-YC2GP-YWX2R-9VY9G Retail Applications
  VBVRC-TKK6Y-37HD7-FVGGB-JF36J Retail Suites
  QHV8Q-JYYYQ-WDBWP-9GCPY-P77JB Professional
  QX97T-8R9FY-M3HGX-KGXYD-R3C8T Seems to be 49 trial version

CD Keys for Windows XP Professional are:
  FCKGW-RHQQ2-YXRKT-8TG6W-2B7Q8 Corporate version and upgrade, no mandatory
  registration if you have corporate version! However, SP1 will reject this and
  others as described in the labmice article below. Now black flagged.
  PQGR8-86HKG-2X3P7-H2DH2-HRM96 Corporate generated, WGA OK for now.
  J7282-VM7Y4-MXMJD-83DJM-BM6JY Corporate generated
  RG6Q6-JRJQR-JMY3X-DPR7T-48K86 Corporate generated
  W7VY8-R3HK7-J68PB-TQ4DF-B87M2 Corporate generated
  FRQF8-RW2FT-MHFWB-GRQKP-T9GV2 Corporate generated
  TKFFC-RMY9G-DD3HQ-JKPG9-AX6HD Volume License (may be post SP1)
  BQ92H-YPC9T-3MCMY-7PPH8-8J3JF Retail version
  KBGVG-DK767-BQPTM-3DC9F-HYV83 Retail version
  BBK3H-PPH6P-G8YV7-FMBHM-2RV2P OEM SP1 compatible
  BVFKG-7MXPW-Y6RVF-CMD22-FYRR7 OEM SP1 compatible
  RBR8H-YBHRY-XVD8C-Q47YW-Y62CC OEM SP1 compatible

CD Keys for Windows XP Home Edition are:
  C6QQT-DYQ7H-HG39T-H47FX-Q3JD2 upgrade

A CD Key for Windows XP Tablet PC Edition is:

CD Keys for Microsoft Windows XP Professional Corporate:
  BR89Q-4B9GB-9DPFD-M2PY3-R3F83 SP2
  F4297-RCWJP-P482C-YY23Y-XH8W3 SP3
  QC986-27D34-6M3TY-JJXP9-TBGMD SP3
  R349V-86B3K-JC3KG-D9W6J-9VQHT SP3
  W4P6K-G7WJX-PB4MF-WWF69-938V3 SP3
  WX6R3-K4KJ8-K697K-J3MKP-7HF86 SP3
  M3Y4R-CK87K-R9PPJ-24Q2W-22XCM SP3
  QC986-27D34-6M3TY-JJXP9-TBGMD SP3

A CD Key for Publisher 2000 is:

CD Keys for Publisher XP are:
  dy6wq-d3fyg-v89by-8kpg9-8yw9m also worked with Visio and Publisher 2002 Pro

A CD Key for Visio Enterprise Network Tools is:
  HJ964-7DQ6D-7K7RK-DD7RM-TQGRB Volume/Corporate CD

CD Keys for Works Suite 2001 are:

CD Keys for Publisher 2002 are:

A CD Key for Project Pro 2002 is:

A CD Key for Visual Pro 2002 is:

A CD Key for Visual Studio .NET is:

A CD Key for Visual FoxPro 7.0 is:

A CD Key for Visual FoxPro 8.0 is:
  DTCDY-QTCH8-CHFM8-6D7QD-PDKRW Professional, Retail, full version

A CD Key for Office XP Pro 2002 is:

A CD Key for Project 2002 Pro is:
  dy6wq-d3fyg-v89by-8kpg9-8yw9m (and regular)

A CD Key for Works Suite 2002 is:
  K64YY-JRMKM-7DJJF-F2D96-8K736 also Word 2002 and Outlook 2002, may be 50 use
  trial key.

A CD Key for Word 2002 is:
  HM6W4-KPQ88-CRPFM-VXXJB-26XJJ (may be trial version with 50 uses)

CD Keys for Microsoft Office 2003 are:
  GWH28-DGCMP-P6RC4-6J4MT-3HFDY (appears to be VLK, no activation with MS, now
  blocked from updates)

A CD Key for Microsoft Frontpage 2003 is:
  WFWDY-XQXJF-RHRYG-BG7RQ-BBDHM (appears to be VLK, no actrivation with MS)

A CD Key for Works Suite 2003 is:
  KDQK3-QR72W-TBR3F-DJJHM-TGKF6 (Word 2002)

CD Keys for Publisher 2003 are:
  GWH28-DGCMP-P6RC4-6J4MT-3HFDY Professional V2003
  2003 PRO, ONENOTE 2003

CD Keys for Windows Advanced Server 2003 are:

These keys will probably stop working once Microsoft black lists them so they
won't activate (will install). However, here is a link to a thread which talks
about how to convert an evaluation copy of Advanced Server 2003 into a regular

A CD Key for Office Mac 2004 (for Mac's) is:
A CD Key for Works Suite 2004 (including Word 2002) is:

A CD Key for Microsoft Office S & T Edition 2003 Trial with Microsoft Works 7.0
2004 Standard and Microsoft MSN Encarta Standard is:

CD Keys for Windows Longhorn 4015 beta is:

CD Keys for Microsoft Office 2003 Professional:
  Main Program: CKY4Q-9FXX6-CQVKV-HPF2B-8BPMB Rest of the Programs:
  Main Program: C98BM-B79CD-VD9JC-QPJP8-QK8YB Rest of the Programs:
  Main Program: JMCKC-7QJCW-Y47KM-969Q7-BTH3Y Rest of the Programs:
  Main Program: D7XYV-3J3TY-XTBYY-TR74V-8XTBB Rest of the Programs:
  Main Program: CXB7M-T7R9V-Q9HVW-4X2BP-WF8YB Rest of the Programs:

CD Keys for Microsoft Windows XP Professional X64 Edition Corporate Keys:

CD Keys for Microsoft Windows Server 2003 X64 Edition:

CD Keys for Microsoft Visual FoxPro 9.0:

CD Keys for Microsoft Operations Manager 2005:

CD Keys for Microsoft Office Communicator 2005:

CD Keys for Microsoft ISA Server 2004:

CD Keys for Microsoft Business Network Professional Server v1.0:

CD Key for Microsoft Office Enterprise 2007

CD Key for Microsoft Office Visio\Project Professional 2007

CD Key for Microsoft Office Home and Student 2007

As these codes have been published on the web, they still allow activation, but
do not get past Genuine Advantage so you won't get non-security updates (no
enhancements, just security fixes). What to do?

CD Key for Microsoft Expression Web

CD Key for Microsoft Windows Vista
  6F2D7-2PCG6-YQQTB-FWK9V-932CC Asus Ultimate
  72PFD-BCBK8-R7X4H-6F2XJ-VVMP9 Asus Business
  BH626-XT3FK-MJKJH-6GQT2-QXQMF Asus Home Premium
  8XPM9-7F9HD-4JJQP-TP64Y-RPFFV Asus Home Premium
  2WP98-KHTH2-KC7KG-4YR37-H8PHC Asus Home Basic
  762HW-QD98X-TQVXJ-8RKRQ-RJC9V Asus Home Basic
  2TYBW-XKCQM-XY9X3-JDXYP-6CJ97 Acer Home Premium
  6F2D7-2PCG6-YQQTB-FWK9V-932CC HP Ultimate
  2R6WF-KYF88-27HYQ-XTKW2-WQD8Q HP Home Premium
  GP3FQ-JB647-7CW8F-H646B-7PMGF HP Home Premium
  34BKK-QK76Y-WWR7C-QF2M7-2TB37 Lenovo Home Premium

CD Keys for Microsoft Media Center 2004 or 2005

A most kind person sent me a load of other Windows OS keys. I will present them
all in a separate page for you to look through if none of the above worked.
Hope your reinstallation goes well.

Источник: []

What’s New in the You Find Words 2001 v1.0 serial key or number?

Screen Shot

System Requirements for You Find Words 2001 v1.0 serial key or number

Add a Comment

Your email address will not be published. Required fields are marked *