From: justliketomsthumbsblues@gmail.com   
      
   On Friday, December 9, 2022 at 8:39:55 PM UTC-5, stephen...@gmail.com wrote:   
   > On Friday, December 9, 2022 at 7:01:21 PM UTC-6, justliketom...@gmail.com   
   wrote:    
   > > I have my original diskettes and copies of ORCA/M and ORCA/C and figured   
   I'd probably reinstall on my IIgs first or maybe make disk images and create a   
   new install with Bernie or KEGS. Finding time to fit that in is a bit   
   problematic but thank you    
   and I'll post what becomes of it when I do.   
      
   > ... you can also get a "clean" installation of ORCA/C 2.2.0 B6 by installing   
   ORCA/C 2.1.0 from the original floppy disks, and then applying the ORCA/C   
   2.2.0 B6 update.    
   >    
   > --    
   > Stephen Heumann   
      
   While likely not here nor there, but… after some foibles; the power jack has   
   gone flaky on my PB 3400c running Bernie ][ the Rescue, cracked solder joint   
   most likely; I have a VST Zip drive in the expansion bay and a Zip drive   
   hooked up to my IIgs and    
   transfer files between the two that way then FTP them between the PB and my   
   MacBook Pro to use with KEGS; the installer on the disk image didn’t like a   
   disk image in the set to be mounted until it asked for it; gave an I/O error,   
   I forget exactly its    
   lament.   
      
   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.   
      
   -- Mark Wade   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)