X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Sat, 14 Jan 2006 12:47:15 -0500 Message-ID: X-Original-Return-Path: Received: from centrmmtao05.cox.net ([70.168.83.79] verified) by logan.com (CommuniGate Pro SMTP 5.0.6) with ESMTP id 926441 for lml@lancaironline.net; Sat, 14 Jan 2006 09:42:25 -0500 Received-SPF: none receiver=logan.com; client-ip=70.168.83.79; envelope-from=jfuller@cox.net Received: from Notebook ([68.226.50.3]) by centrmmtao05.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060114144130.DVSR5868.centrmmtao05.cox.net@Notebook> for ; Sat, 14 Jan 2006 09:41:30 -0500 From: "Jonathan Fuller" X-Original-To: Subject: JPI software conversion X-Original-Date: Sat, 14 Jan 2006 08:41:05 -0600 X-Original-Message-ID: <003001c61918$8d089fe0$0202a8c0@Notebook> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0031_01C618E6.426E2FE0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 This is a multi-part message in MIME format. ------=_NextPart_000_0031_01C618E6.426E2FE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable There have been a few comments on the list in the last few days on JPI = data files. JPI encodes their data files in a *.dat format that can be = graphed and plotted only with their EZTrend or EZPlot software. In the past = they used *.csv format, but they began encoding the data, I speculate, in = order to limit the utility of the third party software, EGView marketed by EGTrends. I rather doubt that JPI's customers were clamoring to have = their data encoded, and JPI's policy does not, to say the least, enhance the = value of their product for their customers, but I guess certain dog in the = manger personalities don't mind annoying their own customers as long as they = can thwart someone else's success. =20 Anyway, a few contributors have mentioned that JPI is now offering a = utility to convert the *.dat files back to *.csv format. I have not been able = to find that utility on their website. Does anyone know any more details = about this? =20 Jonathan Fuller ------=_NextPart_000_0031_01C618E6.426E2FE0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
There = have been a=20 few comments on the list in the last few days on JPI data files.  = JPI=20 encodes their data files in a *.dat format that can be graphed and = plotted only=20 with their EZTrend or EZPlot software.  In the past they used *.csv = format,=20 but they began encoding the data, I speculate, in order to limit the = utility=20 of the third party software, EGView marketed by EGTrends.  I = rather=20 doubt that JPI's customers were clamoring to have their data encoded,=20 and JPI's policy does not, to say the least, enhance the value = of=20 their product for their customers, but I guess certain dog in the manger = personalities don't mind annoying their own customers as = long=20 as they can thwart someone else's success.
 
Anyway, a few=20 contributors have mentioned that JPI is now offering a utility to = convert the=20 *.dat files back to *.csv format.  I have not been able to find = that=20 utility on their website.  Does anyone know any more details about=20 this?
 
Jonathan=20 Fuller
------=_NextPart_000_0031_01C618E6.426E2FE0--