PureBasic Forums - English

When it works in your VM, then you have a problem on the machine where it crashes.

I was also not able to reproduce your fault.

Have you already completely disabled all virus scanners? (for testing)


Apologies for the late reply, I had no time to look at this until just now. FYI it is not an ...

Thank you for testing everyone. I compiled a 32bit version (see link to it below) and let it run in x64dbg.

https://www.mediafire.com/file/so6gu6lut3iwjjb/Test2.zip/file

This is the location and exception that it occurs (screenshot in the link)...

https://www.mediafire.com/view/co0ru4rcwytc4wf ...

Using the data.b in the DataSection of this topic has the same results...

https://www.purebasic.fr/english/viewtopic.php?p=609915&sid=61d5bd8ab778f10041205193e6c8472e#p609915

Here is a compiled binary of that code, it works in a VM and, not on the host.

https://www.mediafire.com/file ...

I downloaded the demo version of 6.20 and installed it on a VM. I was able to get all working, no problems.

Compiled the PB demo version in the VM to an executable. Executed it on the machine where it crashes and, after a short time the executable crashed...

Ted.

Apologies, I should have mentioned I had already tried the latest 6.21 beta 6 release, same issue.

PureBasic 6.20 (x86 & x64), when running the code posted in the link below it crashes after a minute or so running. There is an invalid memory access (read error) in x86 and, in x64 the program simply crashes out with no error. Same problem exists with either ASM or C compilers.

https://www ...

Since 6.10 Purebasic has started static linking the MS runtime, as previously it linked with the MSVCRT.dll that ships with windows.
This blog post has details about this https://www.purebasic.fr/blog/?p=538


I read the blog entry back in November, obviously forgot all about 6.10 being affected ...

I have not tried any other betas than 6.10 beta 8 so I can't tell if this problem is specific to beta 8.

I have a program compiled using 6.04 LTS to 153KB in size. In 6.10 beta 8 this now compiles to 359KB.

Using both C and ASM backend compilers produce similar filesize results.

Is this normal ...

I note in PureBasic 6.04 LTS there is a new DLL protection feature in compiler options.

The English translation in the documentation is not well worded. From the wording in the documentation, my understanding, is the default search directory of system DLL's is restricted to the System32 folder ...

PureBasic guides and manuals can be found here...

PureBasic - Reference Manual v5.20
PureBasic - A Beginners Guide
PureBasic - Survival Guide

Other reference/ API guides can be found here...

https://forum.tuts4you.com/files/catego ... ng-coding/

Ted.

Thank you for the info and links. Good to read this change is coming! I see it being an advantage in the long term as it may help to speed up development of PureBasic and have a quicker turn around introducing and supporting new hardware and OS features...

Ted.

Keya wrote: Thu Apr 15, 2021 4:59 am PB moving to a C compiler

Is this is a fact or a wish list comment? If fact where is this information to be found on PB's roadmap!

Ted.

Anyone else noticed a change in the font/scaling size for the tab and panel contents in the latest beta (not tried b1)? The font appears too small compared to 5.70 which, seemed fine to me.

Ted.

Thanks for the DPI Aware feature.
Any thoughts about PerMonitor Awareness? It can be set in the manifest, too.

<dpiAware>True/PM</dpiAware>
<dpiAwareness>PerMonitorV2, PerMonitor</dpiAwareness>

High-DPI Scaling Improvements for Desktop Applications in the Windows 10 Creators Update (1703)

I ...

Apologies for not being clear. If I have a preference file that can be edited by the user with a new custom key value the result from ReadPreferenceString is of an unknown string length. Where I will be using some of the strings they need to be, at some point limited to a maximum string length. I ...