12 Jun 16 07:42, you wrote to me:   
      
    ml>> i've gone back to your original post where i asked you if you were stil   
      
    JL> Ok. I figured it out. You were right in creating that custom printf   
    JL> function.   
      
   he, i really didn't have much choice... it was either write some simple   
   routine or include common2.pas and whatever else it wanted ;)   
      
    JL> The problem was with the Impulse version of the printf function.   
      
   the original printf actually uses showscr which does a bunch of translation   
   stuff of the files' contents... looks like it does some sort of MCI code   
   stuff... but there's a number of other routines being called from showscr,   
   too... prompt(), sprompt(), setc(), cstr(), cstrl(), lpromptc(), wkey() and a   
   few others... any one of those may have an errant read in them... that's one   
   of the reasons why i was saying to simplify everything and make it a stand   
   alone program... generally the bugs and logic flow problems will be easily   
   seen...   
      
    JL> I replaced all instances of printf('filename'); to shell('/usr/bin/cat   
    JL> filename'); And it appears to be working.   
      
   it will locally but likely not remotely as well as losing the MCI decoding and   
   such...   
      
    JL> I can't believe I didn't think of this sooner. So, thanks, man, with   
    JL> your help. It's grately appreciated.   
      
   sometimes it takes a little bit for the gears to get switched and a new or   
   different way of looking at things takes place... you're welcome and i'm glad   
   that i was finally able to find the time to offer some assistance :)   
      
   )\/(ark   
      
   Always Mount a Scratch Monkey   
      
   ... I'm so poor I can't even pay attention.   
   ---   
    * Origin:  (1:3634/12.73)