Dar,

It is the same as this I found below ,
If complied on 4.0.0 it works , If complied on later versions if fails to read.

Regards
Camm


On Nov 7, 2010, at 10:07 AM, J. Landman Gay wrote:

> On 11/7/10 9:18 AM, Larry Walker wrote:
>> I am trying to read data from a "serial port" (using a USB-serial adaptor).
> 
> Glad to see this here Larry. Just to fill everyone in, Larry and I have been 
> going around with this issue for about a week in the tech queue without 
> success (and I really appreciate his patience, he's been incredibly 
> reasonable about it.) I asked Mark Waddingham about the problem and he said 
> that basically the serial commands haven't been changed since their initial 
> implementation back in MetaCard, and that any device that represents itself 
> as a serial device should work with "open file" (but not necessarily with the 
> device name returned by the drivernames. Use "modem:" or "printer:" instead.) 
> He also said that they have never been reworked to support OS X; they were 
> originally written for OS 9 and have always continued to work in OS X, so the 
> code hasn't been examined.
> 
> Eric's comment that it works in 4.0 and not in 4.5 is something I don't think 
> the team knows about. Since serial access hasn't changed in the engine, there 
> must be some other change that peripherally affects serial port access. If 
> that's so, then a bug report in the QCC would be in order.
> 
> I hope either Sarah or Phil will see this, since they are the serial/USB 
> experts here. Maybe they have some comments to add or a workaround they've 
> discovered.
> 


----- Original Message -----
From: "Dar Scott" <[email protected]>
To: "How to use LiveCode" <[email protected]>
Sent: Sunday, 13 May, 2012 8:17:45 PM
Subject: Re: Serial Comms in 4.6.4

I'm not sure what you mean.

Are you saying you upgraded to Windows 7 and LiveCode 4.6.4 at the same time?

I have heard that some people have had trouble with Windows 7 and serial ports. 
 Perhaps modems are especially an issue.

Do you see the port in the device manager?  Can you connect with HyperTerminal? 
 What error results do you get?  (You might have to create a version of your 
script that logs those.)

Have the scripts ever worked on this Windows 7 installation?

As you can probably tell, I'm leaning towards eliminating non-LiveCode issues 
and then looking at the script, but the script errors can give clues to both.

Dar



On May 13, 2012, at 4:23 AM, Camm wrote:

> Dar ,
> 
> Windows 7
> 
> All hardware has been checked okay.
> 
> When using read from driver in scripts loaded into 4.6.4 or standalone from
> 4.6.4 nothing is read ?
> 
> The identical script loaded in pre-windows  7 Livecode releases work.
> 
> Thanks
> Camm
> 
> 
> 
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Dar Scott
> Sent: 13 May 2012 05:43
> To: How to use LiveCode
> Subject: Re: Serial Comms in 4.6.4
> 
> Hi, Camm!
> 
> I don't remember any changes.
> 
> Maybe this can be tracked down.  What OS?  How does it fail?
> 
> However, you might want to rule out other things.  I find the most common
> reason that a serial communications program suddenly fails is a cable issue.
> Usually the handshake lines don't make it trough or something else is wrong
> in the wiring.  Sometimes the USB-to-serial adaptor is an issue.  
> 
> Dar
> 
> On May 12, 2012, at 3:30 PM, Camm wrote:
> 
>> Has something changed in the use of open , close , read , write driver 
>> and/or  SerialControlString string in version 4.6.4.
>> 
>> 
>> 
>> I have a stack for serial comms that works fine if run in older 
>> versions of Livecode , but fails to read in version 4.6.4
>> 
>> Same script ??
>> 
>> 
>> 
>> Regards
>> 
>> Camm
> 
> ---------------------------
> Dar Scott
> dba
> Dar Scott Consulting
> 8637 Horacio Place NE
> Albuquerque, NM 87111
> 
> Lab, home, office phone: +1 505 299 9497 For Skype and fax, please contact.
> [email protected]
> 
> Computer Programming and tinkering,
> often making LiveCode libraries and
> externals, sometimes writing associated
> microcontroller firmware.  
> ---------------------------
> 
> 
> 
> _______________________________________________
> use-livecode mailing list
> [email protected]
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.1913 / Virus Database: 2425/4996 - Release Date: 05/13/12
> 
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.1913 / Virus Database: 2425/4996 - Release Date: 05/13/12
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.1913 / Virus Database: 2425/4996 - Release Date: 05/13/12
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.1913 / Virus Database: 2425/4996 - Release Date: 05/13/12
> 
> 
> _______________________________________________
> use-livecode mailing list
> [email protected]
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to