View Single Post
  #13   Spotlight this post!  
Unread 27-02-2004, 17:07
gnormhurst's Avatar
gnormhurst gnormhurst is offline
Norm Hurst
AKA: gnorm
#0381 (The Tornadoes)
Team Role: Programmer
 
Join Date: Jan 2004
Location: Trenton, NJ
Posts: 138
gnormhurst will become famous soon enoughgnormhurst will become famous soon enough
Re: How do we convert a modified user routines file into a valid .HEX file

Quote:
Originally Posted by Astronouth7303
The only way that could happen is that FrcDefault_code.hex got corrupted. It's just the default code. What you described would be characterized by the fact that changes seem to have no effect. I did that Wed. night.
Yeah, I've done that sort of thing: spend hours making changes and wondering why it still wouldn't work, only to find out I wasn't actually changing the output file that I thought I was changing.

Try this: rename or delete the .hex file you think you are creating, then build it again. If the file doesn't reappear (i.e. the new file), then you are not creating the file you thought you were. Use Windows Explorer and "sort by date" (click the date heading), and see which .hex file is newest -- that's the file you just created (check the date/time of the file.)

I hope that helps -- I could just be misunderstanding something.