Proton BASIC Community

Hello,
After the update I have an error message.

Access violation at address 004029D1 in module "ProtonIDE.exe". Read of address 05797E31.

Any idea how I can deal with it? How do I remove the last update?

It's probably windows related issue. Uninstall Positron, then install it back and apply the update again. The both files should be run as Administrator.

Before I updated I had no problem. Immediately after I installed the update I had an error.
Reinstallation takes a long time. I will reinstall, but I will not install the new update, there is clearly an error.

Quote from: Georgi on Aug 25, 2025, 04:02 PMReinstallation takes a long time. I will reinstall, but I will not install the new update, there is clearly an error.

Well, I wonder why it would take such a long time to re-install Positron?

If more users report this type of error, which seems to be a memory related violation, then we could conclude that there's a problem with the update, thus far this is not the case.

The Positron update process has working seamlessly and I never had the slightest issue. 

Hi,
I have installed and tested the latest version of the Positron compiler and I have no problems. The compilation works very well with no errors found so far.

The update does not re-install the IDE. So the IDE now is the IDE it was before the update.

If the update was taking a long time to install, it is a third party program in the windows OS that has interfered with things.

I always test the update and upgrade installers on fresh windows operating systems, to make sure they are OK before uploading them to the cloud drive. And the operating systems I use do not have third party bulk on them, they are virgin Windows 10.

Why does the assembler give this good code with version 1.1.2.8

; start of the user's program
.global __reset
.global _pos16_main_start_
_pos16_main_start_:
__reset:
; setup the stack
    mov.w #0x0800,W15
    mov.w #0x08c8,W0
    mov.w W0,SPLIM
    nop
; Clear the WREG SFRs
    clr.w W0
    mov.w W0,W14
    repeat #12
    mov.w W0,[++W14]
    clr.w W14
    clr.w TBLPAG
    bset.w CORCON,#pp_psv
.def .bf
.val .
.scl 101
.Line 1
.endef
    clr.w PMCON
    clr.w CMCON
    setm.w AD1PCFGL
    bset.b PADCFG1,#0
; rd_i000005_f001_000014_p000016,0 mkr$ in [test.bas] CLKDIV =  2 - 2
    clr.w CLKDIV
    mov.w #38,W0
    mov.w W0,PLLFBD
    disi #14
    mov.w #3,W0
    mov.w #1859,W1
    mov.w #120,W2
    mov.w #154,W3
    mov.b W2,[W1]
    mov.b W3,[W1]
    mov.b W0,[W1]
    mov.w #0,W0
    mov.w #1858,W1
    mov.w #70,W2
    mov.w #87,W3
    mov.b W2,[W1]
    mov.b W3,[W1]
    mov.b W0,[W1]
_lbl__2:
    btss.b OSCCON,#5
    goto _lbl__2
_lbl__3:
; rd_i000025_f001_000016_p000016,0 mkr$ in [test.bas] Do
_lbl__4:
_lbl__6:
; rd_i000026_f001_000017_p000016,0 mkr$ in [test.bas] Loop
    goto _lbl__4

and this other one bad with version 1.1.3.0?

;------------------------------------------
; start of the user's program
.global __reset
.global _pos16_main_start_
_pos16_main_start_:
__reset:
; setup the stack
    mov.w #0x0800,W15
    mov.w #0x08c8,W0
    mov.w W0,SPLIM
    nop
; Clear the WREG SFRs
    clr.w W0
    mov.w W0,W14
    repeat #12
    mov.w W0,[++W14]
    clr.w W14
    clr.w TBLPAG
    bset.w CORCON,#pp_psv
.def .bf
.val .
.scl 101
.Line 1
.endef
    clr.w PMCON
    clr.w CMCON
    setm.w AD1PCFGL
    bset.b PADCFG1,#0
; rd_i000005_f001_000014_p000016,0 mkr$ in [test.bas] CLKDIV =  2 - 2
    clr.w CLKDIV
    mov.w #38,W0
    mov.w W0,PLLFBD
    disi #14
    mov.w #3,W0
    mov.w #1859,W1
    mov.w #120,W2
    mov.w #154,W3
    mov.b W2,[W1]
    mov.b W3,[W1]
    mov.b W0,[W1]
    mov.w #0,W0
    mov.w #1858,W1
    mov.w #70,W2
    mov.w #87,W3
    mov.b W2,[W1]
    mov.b W3,[W1]
    mov.b W0,[W1]
_lbl__2:
    btsc.b OSCCON.5,#0
    bra
    goto _lbl__2
_lbl__3:
; rd_i000025_f001_000016_p000016,0 mkr$ in [test.bas] Do
_lbl__4:
_lbl__6:
; rd_i000026_f001_000017_p000016,0 mkr$ in [test.bas] Loop
    goto _lbl__4


1.1.2.8 gives btss.b OSCCON,#5
1.1.3.0 gives btsc.b OSCCON,#5

I've noticed a couple of anomalies with Positron16 version 1.1.3.0 and some of its internal labels, and I am now investigating. I have a sneaky feeling it is the C++ compiler playing up, with some pointers of pointers etc... That carry label names.

I have removed the update thread from the forum, so if you have not installed it yet... Don't.

The problem is now corrected. It was the embarcadero C++ compiler, not following on with some "char *" pointers that held a label name, for some unknown reason. It has always done so previously, and no changes were made to their mechanism in the compiler's source code. These have now been changed to "AnsiString", so no pointers.

A 1.1.3.1 update has been posted on the forum.

hi LES, 
my karspersky plus reported have virius (not a virus but ) for  Positron Corrections and Additions Update 4.0.6.0-1.1.3.1 and deleted the file.

i made disable kaspersky firstly then i installed  Positron Corrections and Additions Update 4.0.6.0-1.1.3.1.exe
i am sending report screenshot  to LES to learn the detail of problem what is is?

This is a common problem with virus checkers, and some use a "best guess" method to scare people, and some actually report anomalies that are not actually there, when using a free version, to try to 'con' people into buying it. I know this as fact, after quite a few years of using some of them on a "very clean, virgin" virtual machine. Yet it still comes up with nonsense about things that are not there!

The compilers and the installer are all scanned for virus' and trojans using two checkers, before an upload is performed. I have also just scanned the compiler files, and the installer files, with them and they are OK.