View Single Post
  #10   Spotlight this post!  
Unread 22-09-2004, 12:35
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,754
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: IFI Loader problem - "Invalid HEX file"

Quote:
Originally Posted by Alan Anderson
Doing the ftp in binary mode is guaranteed not to modify the end-of-line characters. You'd have to do it in text mode.
I was attempting to recreate David's problem and so tested windows and unix style files.

I chose binary on purpose to test the various CR/LF mixes in IFI_Loader on a windows machine. I used ftp in ASCII mode transferring to UNIX and binary coming back to maintain the UNIX style. I verified the file difference on windows. I didn't want ftp changing the UNIX style I'd created back to Windows style.

P.S. I was able to get identical symptoms to the ones David described, where the file path doesn't even appear, when I used non-ASCII characters at the beginning of the file. A pure ASCII corrupted file still displays the filename path while showing the error message.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 22-09-2004 at 13:16.