From owner-freebsd-embedded@FreeBSD.ORG Mon Jun 30 07:53:58 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49BB6106567A for ; Mon, 30 Jun 2008 07:53:58 +0000 (UTC) (envelope-from rgrover1@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227]) by mx1.freebsd.org (Postfix) with ESMTP id 1E45E8FC1F for ; Mon, 30 Jun 2008 07:53:57 +0000 (UTC) (envelope-from rgrover1@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1428198rvf.43 for ; Mon, 30 Jun 2008 00:53:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=43r1pTIU5zgbQp8Pu3B+CU1Msy5YdhjF1aW0rMaXE00=; b=RW0JnOEuNaxynq+KE9hdgTs15cG4f/KfNoh0mrxsw1ncnxJ1No8di3e+nw2QiVGB+e 2NvmFszSdupSp/yHJsIHwIpMFWIj7fF6VQ6gQu6gcQQUK6JjXjjv1fmwLkrVLgC36Lz+ PWwtbqQgGqfGi02G8vNGCzWushwI9nbKr0nmE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=KIda7awPak7tT1YAhj3z17msICJpya27S9p5DH1dyIbzx/wW0ZG0Xtywk9MJyf4ez5 NRxJcITWgG6RAYN6rrgESwTmCu7sl2eO+1rW64D81qWs/BDdMBHQTYBVxnL/tk8HYk11 nRm9IMmRlRhsPBTh8kqhLZaQl4b7LH2wSigwg= Received: by 10.141.76.21 with SMTP id d21mr2414542rvl.270.1214810723998; Mon, 30 Jun 2008 00:25:23 -0700 (PDT) Received: by 10.141.66.20 with HTTP; Mon, 30 Jun 2008 00:25:23 -0700 (PDT) Message-ID: <426bed110806300025j5a92080bx59cdb2248c77b8c0@mail.gmail.com> Date: Mon, 30 Jun 2008 19:25:23 +1200 From: "Rohit Grover" To: freebsd-embedded@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: having trouble receiving serial data using my USB->serial adaptor X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 07:53:58 -0000 Hi, I am having trouble getting my BAFO 810 USB->serial adaptor to work. I have built the uplcom and ucom drivers into the kernel, and my USB->serial adaptor is recognized at boot, as can be inferred from the following lines from /var/run/dmesg.boot: ucom0: on uhub3 I am using minicom to drive /dev/cuaU0 at 115200 8N1. If I connect the Tx and Rx lines (pins 2 and 3) of the DB9 connector, I can get echoes of my keystrokes on the minicom terminal. Unfortunately, I am unable to connect to an embedded device which supports serial connections at 115200 8N1. When I plug the serial output connector of my adaptor to a NULL modem and then to the target embedded system, I don't see any serial output from the device on my minicom terminal. This same device communicates correctly with the serial port of my linux desktop with minicom and 115200 8N1. As a further experiment, I manually connected pins 2,3, and 5 of the serial end of my adaptor to pins 3,2, and 5 respectively of the embedded device, but still no luck. What am I missing? regards, From owner-freebsd-embedded@FreeBSD.ORG Mon Jun 30 11:06:55 2008 Return-Path: Delivered-To: freebsd-embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1429F10656C2 for ; Mon, 30 Jun 2008 11:06:55 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DCABA8FC1F for ; Mon, 30 Jun 2008 11:06:54 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m5UB6seB095701 for ; Mon, 30 Jun 2008 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m5UB6ssf095697 for freebsd-embedded@FreeBSD.org; Mon, 30 Jun 2008 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 Jun 2008 11:06:54 GMT Message-Id: <200806301106.m5UB6ssf095697@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-embedded@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 11:06:55 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o misc/15876 embedded [picobsd] PicoBSD message of the day problems o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub 4 problems total. From owner-freebsd-embedded@FreeBSD.ORG Mon Jun 30 19:45:41 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E0461065676 for ; Mon, 30 Jun 2008 19:45:41 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id 8FDD18FC1C for ; Mon, 30 Jun 2008 19:45:40 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (Q7ce4.q.ppp-pool.de [89.53.124.228]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id CF72612883F; Mon, 30 Jun 2008 21:27:02 +0200 (CEST) Received: from cesar.sz.vwsoft.com (cesar.sz.vwsoft.com [192.168.16.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 88C372E823; Mon, 30 Jun 2008 21:26:28 +0200 (CEST) Message-ID: <4869337C.6050105@vwsoft.com> Date: Mon, 30 Jun 2008 21:26:52 +0200 From: Volker User-Agent: Thunderbird 2.0.0.14 (X11/20080615) MIME-Version: 1.0 To: Rohit Grover References: <426bed110806300025j5a92080bx59cdb2248c77b8c0@mail.gmail.com> In-Reply-To: <426bed110806300025j5a92080bx59cdb2248c77b8c0@mail.gmail.com> X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit MailScanner-NULL-Check: 1215458792.4556@LLJoIZPeGef6F+HuUWArBw X-MailScanner-ID: 88C372E823.59A46 X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: freebsd-embedded@freebsd.org Subject: Re: having trouble receiving serial data using my USB->serial adaptor X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 19:45:41 -0000 On 12/23/-58 20:59, Rohit Grover wrote: > Hi, > > I am having trouble getting my BAFO 810 USB->serial adaptor to > work. I have built the uplcom and ucom drivers into the kernel, > and my USB->serial adaptor is recognized at boot, as can be > inferred from the following lines from /var/run/dmesg.boot: > > ucom0: 0/0, rev 1.10/3.\ 00, addr 2> on uhub3 > > I am using minicom to drive /dev/cuaU0 at 115200 8N1. > > If I connect the Tx and Rx lines (pins 2 and 3) of the DB9 > connector, I can get echoes of my keystrokes on the minicom > terminal. > > Unfortunately, I am unable to connect to an embedded device which > supports serial connections at 115200 8N1. When I plug the serial > output connector of my adaptor to a NULL modem and then to the > target embedded system, I don't see any serial output from the > device on my minicom terminal. This same device communicates > correctly with the serial port of my linux desktop with minicom > and 115200 8N1. > > As a further experiment, I manually connected pins 2,3, and 5 of > the serial end of my adaptor to pins 3,2, and 5 respectively of > the embedded device, but still no luck. > > What am I missing? > > regards, > Rohit, hard to tell on the distance but if you're able to receive (using a loopback adapter), it sounds like either side is most likely requiring hardware handshake (DSR/DTR, RTS/CTS). Sometimes it helps to short cut the DCD line (to RTS/DSR), as some device refuse to send if DCD is not set. If you're owning a break out box, it should be snap to figure that out. At least you should check using a serial line tester (those little tools signaling line status using LEDs or use a Voltmeter to check for correct line status). Volker From owner-freebsd-embedded@FreeBSD.ORG Tue Jul 1 10:01:45 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C568106566C for ; Tue, 1 Jul 2008 10:01:45 +0000 (UTC) (envelope-from rgrover1@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id E2AF28FC13 for ; Tue, 1 Jul 2008 10:01:44 +0000 (UTC) (envelope-from rgrover1@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2078755rvf.43 for ; Tue, 01 Jul 2008 03:01:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=67eG1jTEYbiBhWGJ02zbyBVlXIs58ttGJS7YCLbJe2E=; b=GKEup5WRt/6AYu2qSnUJq2q4DYWiWt7vV77/WTqHWpvCgx0/j37FtSrrhfhyRqaXO4 YgK0whN+kLQq+0vMkCTKbkqyiNKqNhDaVaBaaqiE8RYIRdw9P/xWfCSetKfMovHVmrSe GFo1zlJriCrWNdrN1iCrKk0Z87M5auprsuZF4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=Szf89gl7PQctNH2MgfROtXkCkGYAQNM6icxjcNLZlrUlQum4ZEcKdhsFBDTzfZSifn C+qrgHMgg0XJzolPxFn69YL+7JFF1KUFklTjAXFtZ0/z9x9kq8JCVCygJdxDS/Tlt5Pi kuVvtRzn7Bg+0nB4CyC7OUrmBWOjhGe4gacPc= Received: by 10.141.71.8 with SMTP id y8mr3363972rvk.63.1214906504646; Tue, 01 Jul 2008 03:01:44 -0700 (PDT) Received: by 10.141.66.20 with HTTP; Tue, 1 Jul 2008 03:01:44 -0700 (PDT) Message-ID: <426bed110807010301j132a75f4q1c85fce62ca85188@mail.gmail.com> Date: Tue, 1 Jul 2008 22:01:44 +1200 From: "Rohit Grover" To: Volker In-Reply-To: <4869337C.6050105@vwsoft.com> MIME-Version: 1.0 References: <426bed110806300025j5a92080bx59cdb2248c77b8c0@mail.gmail.com> <4869337C.6050105@vwsoft.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-embedded@freebsd.org Subject: Re: having trouble receiving serial data using my USB->serial adaptor X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 10:01:45 -0000 Hi, Thanks for the response. I stumbled upon the solution quite by chance. My USB->serial adaptor has a NULL modem built into it, so attaching an external NULL modem was un-necessary and incorrect. It is a wonder that the devices survived this treatment. thanks again. regards, > > > I am having trouble getting my BAFO 810 USB->serial adaptor to > > work. I have built the uplcom and ucom drivers into the kernel, > > and my USB->serial adaptor is recognized at boot, as can be > > inferred from the following lines from /var/run/dmesg.boot: > > > > ucom0: > 0/0, rev 1.10/3.\ 00, addr 2> on uhub3 > > > > I am using minicom to drive /dev/cuaU0 at 115200 8N1. > > > > If I connect the Tx and Rx lines (pins 2 and 3) of the DB9 > > connector, I can get echoes of my keystrokes on the minicom > > terminal. > > > > Unfortunately, I am unable to connect to an embedded device which > > supports serial connections at 115200 8N1. When I plug the serial > > output connector of my adaptor to a NULL modem and then to the > > target embedded system, I don't see any serial output from the > > device on my minicom terminal. This same device communicates > > correctly with the serial port of my linux desktop with minicom > > and 115200 8N1. > > > > As a further experiment, I manually connected pins 2,3, and 5 of > > the serial end of my adaptor to pins 3,2, and 5 respectively of > > the embedded device, but still no luck. > > > > What am I missing? > > > > regards, > > > > > Rohit, > > hard to tell on the distance but if you're able to receive (using a > loopback adapter), it sounds like either side is most likely requiring > hardware handshake (DSR/DTR, RTS/CTS). > > Sometimes it helps to short cut the DCD line (to RTS/DSR), as some > device refuse to send if DCD is not set. If you're owning a break out > box, it should be snap to figure that out. At least you should check > using a serial line tester (those little tools signaling line status > using LEDs or use a Voltmeter to check for correct line status). > > Volker > From owner-freebsd-embedded@FreeBSD.ORG Tue Jul 1 10:39:31 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 546C41065688 for ; Tue, 1 Jul 2008 10:39:31 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from gidgate.gid.co.uk (host-83-146-60-88.dslgb.com [83.146.60.88]) by mx1.freebsd.org (Postfix) with ESMTP id B16888FC29 for ; Tue, 1 Jul 2008 10:39:30 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from [192.168.255.1] (seagoon.gid.co.uk [194.32.164.1]) by gidgate.gid.co.uk (8.13.8/8.13.8) with ESMTP id m61AL4nr054849; Tue, 1 Jul 2008 11:21:04 +0100 (BST) (envelope-from rb@gid.co.uk) Message-Id: From: Bob Bishop To: Rohit Grover In-Reply-To: <426bed110807010301j132a75f4q1c85fce62ca85188@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v926) Date: Tue, 1 Jul 2008 11:21:04 +0100 References: <426bed110806300025j5a92080bx59cdb2248c77b8c0@mail.gmail.com> <4869337C.6050105@vwsoft.com> <426bed110807010301j132a75f4q1c85fce62ca85188@mail.gmail.com> X-Mailer: Apple Mail (2.926) Cc: Volker , freebsd-embedded@freebsd.org Subject: Re: having trouble receiving serial data using my USB->serial adaptor X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 10:39:31 -0000 Hi, On 1 Jul 2008, at 11:01, Rohit Grover wrote: > My USB->serial adaptor has a NULL modem built into it, so attaching an > external NULL modem was un-necessary and incorrect. It is a wonder > that the > devices survived this treatment. FTR, standards-compliant serial ports are pretty robust; it would be much more surprising if the devices hadn't survived. -- Bob Bishop +44 (0)118 940 1243 rb@gid.co.uk fax +44 (0)118 940 1295 From owner-freebsd-embedded@FreeBSD.ORG Tue Jul 1 11:40:34 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 050401065684 for ; Tue, 1 Jul 2008 11:40:34 +0000 (UTC) (envelope-from v.werth@bally-wulff.de) Received: from mail2.bally-wulff-berlin.de (mail2.bally-wulff-berlin.de [212.144.118.9]) by mx1.freebsd.org (Postfix) with ESMTP id 848E58FC13 for ; Tue, 1 Jul 2008 11:40:33 +0000 (UTC) (envelope-from v.werth@bally-wulff.de) Received: from ex1.bally-wulff.de (ex1.bally.de [192.9.204.18]) by mail2.bally-wulff-berlin.de (Postfix) with ESMTP id 999319906E; Tue, 1 Jul 2008 13:16:49 +0200 (CEST) Thread-Index: Acjba/VmSNXb6XkbTPqGTmZJiQYW5Q== Thread-Topic: having trouble receiving serial data using my USB->serial adaptor Received: from pc88.bally.de ([192.9.205.88]) by ex1.bally-wulff.de with Microsoft SMTPSVC(6.0.3790.1830); Tue, 1 Jul 2008 13:16:50 +0200 From: "Werth, Volker" To: "Rohit Grover" Date: Tue, 1 Jul 2008 13:16:50 +0200 User-Agent: KMail/1.9.4 References: <426bed110806300025j5a92080bx59cdb2248c77b8c0@mail.gmail.com> <4869337C.6050105@vwsoft.com> <426bed110807010301j132a75f4q1c85fce62ca85188@mail.gmail.com> In-Reply-To: <426bed110807010301j132a75f4q1c85fce62ca85188@mail.gmail.com> MIME-Version: 1.0 Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826 Importance: normal Priority: normal Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-ID: <200807011316.50422.v.werth@bally-wulff.de> X-OriginalArrivalTime: 01 Jul 2008 11:16:50.0474 (UTC) FILETIME=[F55FD0A0:01C8DB6B] Cc: Volker , freebsd-embedded@freebsd.org Subject: Re: having trouble receiving serial data using my USB->serial adaptor X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2008 11:40:34 -0000 Volker Werth schrieb am 01.07.2008 13:16 _____________________________________________________________________ Am Dienstag, 1. Juli 2008 12:01 schrieb Rohit Grover: > Hi, > > Thanks for the response. I stumbled upon the solution quite by chance. > > My USB->serial adaptor has a NULL modem built into it, so attaching an > external NULL modem was un-necessary and incorrect. It is a wonder = that the > devices survived this treatment. > > thanks again. > > regards, > > > > I am having trouble getting my BAFO 810 USB->serial adaptor to > > > work. I have built the uplcom and ucom drivers into the kernel, > > > and my USB->serial adaptor is recognized at boot, as can be > > > inferred from the following lines from /var/run/dmesg.boot: > > > > > > ucom0: > > 0/0, rev 1.10/3.\ 00, addr 2> on uhub3 > > > > > > I am using minicom to drive /dev/cuaU0 at 115200 8N1. > > > > > > If I connect the Tx and Rx lines (pins 2 and 3) of the DB9 > > > connector, I can get echoes of my keystrokes on the minicom > > > terminal. > > > > > > Unfortunately, I am unable to connect to an embedded device which > > > supports serial connections at 115200 8N1. When I plug the serial > > > output connector of my adaptor to a NULL modem and then to the > > > target embedded system, I don't see any serial output from the > > > device on my minicom terminal. This same device communicates > > > correctly with the serial port of my linux desktop with minicom > > > and 115200 8N1. > > > > > > As a further experiment, I manually connected pins 2,3, and 5 of > > > the serial end of my adaptor to pins 3,2, and 5 respectively of > > > the embedded device, but still no luck. > > > > > > What am I missing? > > > > > > regards, > > > > Rohit, > > > > hard to tell on the distance but if you're able to receive (using a > > loopback adapter), it sounds like either side is most likely = requiring > > hardware handshake (DSR/DTR, RTS/CTS). > > > > Sometimes it helps to short cut the DCD line (to RTS/DSR), as some > > device refuse to send if DCD is not set. If you're owning a break = out > > box, it should be snap to figure that out. At least you should check > > using a serial line tester (those little tools signaling line status > > using LEDs or use a Voltmeter to check for correct line status). > > > > Volker Rohit, correct terminology is: Instead of the usual DTE (provided by built-in = PC=20 serial ports), your adapter is a DCE. Connecting that to a DTE (modem, = serial=20 terminal) does not require a null-modem (crossed Rx/Tx, handshake) = cabling. Connecting DCE to DCE or DTE to DTE always requires a (crossed) null = modem=20 connection. DTE to DCE requires a straight 1:1 cabling. Against everybody's assumption, a PC's serial port is mostly always a = DTE. I=20 think this may go back to the time (some 20 or 30 years) while PCs were = seen=20 just as smart (dumb?) terminals connected to a mainframe. HTH Volker --=20 Volker Werth system engineering Bally Wulff Entertainment GmbH Maybachufer 48-51 12045 Berlin, Germany ph: +49(30)62002-109 Bally Wulff Entertainment GmbH, Maybachufer 48-51, 12045 Berlin, = Postanschrift: Postfach 44 01 57, 12001 Berlin Tel.: 030-620 02-0 FAX: = 030-620 02-200, Gesch=E4ftsf=FChrer: Sascha Blodau, Wolfram J. Seiffert, = Tim Wittenbecher, Amtsgericht Berlin-Charlottenburg, HRB 91532 B, UST-ID = DE 234 517 998 _____________________________________________________________________ Dieses E-Mail ist nur f=FCr den Empf=E4nger bestimmt, an den es = gerichtet ist und kann vertrauliches bzw. unter das Berufsgeheimnis fallendes Material enthalten. Jegliche darin enthaltene Ansicht oder Meinungs- =E4u=DFerung ist die des Autors und stellt nicht notwendigerweise die Ansicht oder Meinung von Bally Wulff Entertainment GmbH dar. Sind Sie nicht der Empf=E4nger, so haben Sie diese E-Mail irrt=FCmlich erhalten und jegliche Verwendung, Ver=F6ffentlichung, Weiterleitung, Abschrift oder jeglicher Druck dieser E-Mail ist strengstens untersagt. Weder Bally Wulff Entertainment GmbH noch der Absender (Volker Werth) =FCbernehmen die Haftung f=FCr Viren; es obliegt Ihrer Verantwortung, die E-Mail und deren 0 Anh=E4nge auf Viren zu pr=FCfen. 0 Anh=E4nge: _____________________________________________________________________ Versand am 01.07.2008 13:16 von Werth Volker