Jump to content

Search the Community

Showing results for tags 'SourceBoost Assembler'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • PIC Embedded Programming
    • BoostC and Chameleon compilers programming
    • BoostC porting source code
    • BoostC++ compiler programming
    • BoostBasic compiler programming
    • Assembler programming PIC
    • Novo RTOS Programming
    • Hardware PIC
    • Enhancement Requests
    • Bug Reports

Found 1 result

  1. Greetings Sourceboost Forum and Happy New Year 2015. The type of problem stated below may not be new, but I need guidance from a few SourceBoost forum members familiar with this type of problem. First, Happy New Year. Second, well something is wrong and I will try to brief in explaining: I recently upgraded the Sourceboost running in my HP Pavilion Elite workstation to Ver. 7.22; the OS in the HP is Windows 7 64-bit and the MPLAB is Ver. 8.90. Each Souceboost Toolsuite is running flawlessly, including the assembler. In 2013, I purchased a full second version of Sourceboost for my HP workstation notebook (the OS is Windows 7 64-bit and MPLAB is also 8.90). This week I upgraded the Sourceboost in the notebook to Ver. 7.22. Everything post upgrading works great, except the assembler. The message prompted in the output windows is as illustrated below. - ATTACHED PICTURE GOES HERE I tried to solved this problem by upgrading to MPLABX, reading all posts in the Sourceboost forum, disabling the anti-virus utility, removing MPLABX and installing MPLAB Ver. 8.90 and copying the content in the MPASM Suite folder from the workstation into the MPASM Suite folder in the notebook, making sure MPASMWIN.EXE Is the default assembler chosen in the Assembler options menu, uninstalling Sourceboost Ver. 7.22; removing all Sourceboost folders; removing all regedit references to Souceboost; and re-installing Sourceboost Ver. 7.22 again. I also made sure the Read-only attributes in all Sourceboost working forlders are off. Please, you are my last hope in solving this problem. Thank you so much for reading the above request and your constant support. Cordially, PICforLIFE