From: stephen...@gmail.com   
      
   On Tuesday, December 13, 2022 at 8:57:55 PM UTC-6, justliketom...@gmail.com   
   wrote:   
   > After working around that and making the installer happy I have a new   
   installation of ORCA/C and ORCA/M updated to version 2.2.0 B6. Then trying to   
   set a breakpoint, same problem, bummer. But, it was the file that didn’t   
   work before. I created a new    
   file and set a breakpoint and, yeah, it works but it looks identical to the   
   one that doesn’t. So i’m going through it with a few files, some old ,   
   some new, some work, some don’t and thought I was onto some sequence of   
   saving a file and setting a    
   breakpoint, but…    
   >    
   > It all works as it should now with the new install. The old files created   
   with the old installation had some errant entry in the resource fork when a   
   breakpoint was set. I used removerez on an old file that didn’t work and set   
   a breakpoint and    
   recompiled it and it works as expected.    
   >    
   > I had looked at both the older and newer files with a different editor and   
   the character displayed for the breakpoint was different betwen the two; ^D   
   for the former I think and an N under a ~ in the latter.    
   >    
   > i guess I could have just said I reinstalled and it’s all good now. Thanks   
   for the help and bearing with me.    
      
   I'm glad you got things working now.   
      
   In case you're interested, I think I figured out what was going on. ORCA/C   
   2.1.0 added support for extended characters such as Ñ. The characters used to   
   indicate breakpoints and auto-go points in older versions of ORCA/C conflicted   
   with those, so they    
   were changed at that time, with corresponding changes to Prizm. If ORCA/C   
   2.1.0 or later encounters the old debugging characters, it will treat them as   
   accented letters beginning an identifier, leading to the error you saw.   
      
   This was a change in ORCA/C 2.1.0 back in 1996, but I think at least parts of   
   your old setup must have been older than that, leading to this problem.   
      
   Anyhow, you will have to remove any old breakpoints set using the old   
   characters. With some combinations of versions, it might also be possible for   
   the "use old debugging characters" flag to get stored in the resource forks of   
   source files, so you may    
   have to remove the resource forks too.   
      
   --    
   Stephen Heumann   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)