A#8.15: This is usually caused by serial port configuration problems. Common symptoms may be: % copycat .ttyco .ttya Error opening tty .ttya, aborting. or % /usr/sbin/getty 8bit.38400 .ttya getty: .ttya: I/O error The first thing to check is that the following GNO serial port drivers exist: /dev/modem /dev/printer Next, ensure the following two lines are in your /etc/tty.config file, and that they are uncommented: modem 2 .ttya printer 1 .

A#8.6: Currently the GNO serial drivers only support the two built-in serial ports. This does not imply that you cannot use a serial card in a remote machine (such as a IIe) that is connecting to your IIgs running GNO. A#8.7: These settings will usually work. See the Notes, below.

A#8.9: This answer describes hooking up a terminal to the printer port. Hooking one up to the modem port will be similar except that .ttya should be used instead of .ttyb. On the hardware side, you will need a mini DIN 8 to DB25 printer cable. This should be connected from the IIgs' printer port to the port on the terminal that would normally be hooked to a modem. Next, you have to run a getty(8) over the printer port. Add this line to your /etc/inittab file: pp:23478:rest::/usr/sbin/getty 8bit.

For Unix, see a Usenet post by Mitch Chapman: http://groups.google.com/groups?selm=34A04430.CF9@ohioee.com

If I am in a loop processing Tcl code, even though I call "update idletasks" I cannot change the cursor, and the pointer position is not updated

There are various reasons that the modem may get into this state, but the more common ones are power supplies dipping below spec, flow control set incorrectly, and commands being sent to the modem at a greater rate than that at which they can be processed.

Yes, because the SignaLink doesn't require a connection to the computer's serial port! Unlike other interfaces, the SignaLink never requires a serial port connection. This is particularly handy if your computer doesn't happen to have one! In addition to simplifying your installation, this feature also reduces the likelihood of the computer's RF noise getting into your radio. It also eliminates serial port related transmit problems that plague other interfaces.

The serial port should be located on the back of your computer. An example of a serial port image is provided here.

If you've checked all of these things, then the problem may be that your system is lacking Client for Microsoft Networks in your network control panel. If this client is not installed in the Network Control Panel, you will not be able to authenticate in Microsoft SharePoint. If you are not experienced in working with the Network Control Panel, check Microsoft's documentation before making any changes.

Q. I've tried to connect my 2100 with 8210 cable and nothing happens. Your program doesn't detect my phone.

Our EZ serial switch all have auto uplink function and all ports support it. So that means any port could be the uplink port to the other switch

For versions prior to 1.5.2: Ensure that you are using Visual Studio 6 and have the latest service pack (at least sp5 - if you get error C2440 you need this), also ensure that you have the latest Microsoft Platform SDK (the one that comes with Visual Studio is dated and does not work with AxCrypt - you may receive errors about undefined symbols and also errors in templates used for safe Handle-handling in AxCrypt). For versions 1.5.

A - You can add a Serial Board or a Multi-Port Board (with serial ports) to add more serial ports to your PC which cost as very little . Or you could use a (Serial) Switch box to connect two devices to one serial port.

If no, please review "communications port conflicts" to ensure that the com port you are using is enabled and properly configured. Once you have ascertained that the port is working properly, retry communications. If the problem persists, then proceed to the next question. If yes, then there could be a communication port conflict between the portable and another device assigned to that port.

Probably because you haven't got your kernel sources configured correctly. Ensure that you have the sources in the expected locations (/usr/src/linux-2.x.x) and that you have a symlink from /lib/modules/2.x.x/build to that source folder)

Remember that when you apply a patch to the kernel, you must use the -p0 or -p1 option: otherwise, the patch may be misapplied. See the patch manual page for details. ld: unrecognized option -qmagic means that you should get a newer linker, from ftp://tsx-11.mit.edu/pub/linux/packages/GCC/, in the file binutils-2.8.1.0.1.bin.tar.gz.

I've connected the USB to Serial adapter but it's on Com Port 5 (or higher) and your software only has Ports 1-4. This issue applies to the c\temp software only. This has been resolved with the new version of the MDAS-Pro software. If you do not have a copy of this software, please contact us.

Some unnamed clone cards have also been known to work, especially those that claim to be AST compatible. USB device support was added to FreeBSD 3.1. However, it is still in preliminary state and may not always work as of version 3.2. If you want to experiment with the USB keyboard support, follow the procedure described below. Add the following lines to your kernel configuration file, and rebuild the kernel.