geekmungus

mgetty is already installed, so only needs to be configured. This will allow a windows box for example to be able to console straight to a linux box via the com port, useful if you have a windows network and a linux network that you don’t want connecting.

# vi /etc/inittab
Added this line:
7:2345:respawn:/sbin/mgetty ttys0

This should make sure it autostarts on boot.
# vi /etc/securetty

Added this line to very bottom:
ttys0
This allows terminal access to the console from the serial port.

Now the mgetty configuration:

# vi /etc/mgetty+sendfax/mgetty.config
Added the following lines to the configuration file:

port ttys0
direct y
speed 19200
toggle-dtr n

This sets serial port 1 to listen for connections on the com 1 port. Supposed to make it VT100 Terminal Emulation.

Now on the Windows box (or anything else) you can use hyperterminal to make a connection as the following:

- COM 1 (or whatever port you are using)
- 19200 baud
- 8 bits, no parity, 1 stop bit
- No flow control

As for the terminal emulation it should be VT100 but in my case using auto detect or using ANSIW appeared to work correctly.

What To Do If Outlook Web Access Starts the Office Installer

[This discussion is based on Microsoft Knowledge Base Article - 298110
XCCC: Outlook Web Access Starts Office Installer When You Click the New Message Icon]

Sometimes when a user logs on to an Exchange 2000 server by using OWA on a computer that is running Microsoft Windows 2000 and that has Outlook 2000 installed, some strange behavior results. When the user clicks the New Message icon to create a new message, or clicks reply, OWA may start Microsoft Office Installer. The user is then repeatedly prompted for the Office Installation CD. This annoyance can be prevented by either providing the requested installation disk or modifying a Registry entry.

This problem occurs because Office 2000 creates the following entry in the registry when it is installed on Windows 2000:

HKEY_CLASSES_ROOT\CLSID\{438DA5E0-F171-11D0-984E-0000F80270F8}
\InprocServer32\InprocServer32 ——>TriEditDocument Class

HKEY_CLASSES_ROOT\CLSID\{010E6CBE-FE2B-11D0-B079-006008058A0E}
\InprocServer32\InprocServer32 ——>TriEditParse Class

These registry keys point to the Office Installer, so every time the DHTML Edit control (which is already installed by Microsoft Internet Explorer) is accessed on the client computer, the Office Installer comes up.

To work around this problem by editing the Registry, remove the string in the Inprocserver32 value so that the value is blank.

1. Start Regedt32.

2. Locate the following registry key:

HKEY_CLASSES_ROOT\CLSID\{010E6CBE-FE2B-11D0-B079-006008058A0E} \InprocServer32 key

3. Locate the following value on the key:

InprocServer32, a REG_MULTI_SZ value

4. Expand the value, and then remove the entry in the value so that the value is blank. NOTE: The string typically is similar to “26!!gxsf[Ng]gF……….”

5. Repeat steps 1 through 4 for the following path:

HKEY_CLASSES_ROOT\CLSID\{438DA5E0-F171-11D0-984E-0000F80270F8}
\InprocServer32\InprocServer32

6. Restart the client computer.

After you have taken the steps described in this article, you can start and edit a new e-mail form in the OWA client without starting the Office Installer.

For additional information check out the KB article (298110): http://support.microsoft.com/default.aspx?scid=kb;en-us;298110

You can of course just put in the Office CD to install whatever it is harping on about.