FW: Re: Why is my executabel in DOS file format?

[Meg Abyte]

>Can you quote what stty gives you when you say
># stty -F /dev/tts/0 -a
>please?

speed 9600 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon 
-ixoff
-iuclc -ixany -imaxbel
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 
ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke


I tried everything that had to do with CR and LF in the stty config you 
mentioned, and any other commands that looked somehow related.

I even did a serial loop back and that seeme to be ok, (i.e. it had ONLY CR, 
or it had ONLY CR/LF) however, that doesn't prove what is really going OUT, 
as coming in it might chage.
As far as using the system this is all you see on the screen:
Mbug >>dl
/ ERROR : not in S-Record Format
Mbug >>S3153000000071092A01E80660027308B203200301BC0

That tells me it didn't like the first line. As after dl the transfer 
occurs. I can't tell though if it had two CR's or not.  This does work fine 
though if the file has ONLY CR, or ONLY LF. And hardware works fine on same 
machine if windows is use to send ONLY LF, or CR/LF.

I think only a protocol analyser of some sort. Or a program on my laptop 
that would read the raw charaters comming in on the serial port would be 
able to tell me what is going on.  Know of any win terminal apps that are 
free and print the raw input? I'll have to write one when I get the time.

_________________________________________________________________
MSN Premium with Virus Guard and Firewall* from McAfee® Security : 2 months 
FREE*   
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines