PureBasic Forums - English

Now, the question and answer of what causes the Defender to "friendly fire" is getting more and more bizarre. :o :lol: But it is also very interesting, because you can see how you can influence the behavior of the defender without any code change. :shock: https://abload.de/img/defender_21q...

Hi, yes, thank you.
I just wanted to show that Peeks() triggers this and what you can do about it.
With the sample bypass you usually have peace.
It also makes no difference, both variants are equally fast.

I would like to describe a problem to you here once. It does not concern me currently, since I have been bypassing it habitually for a long time. For the sake of simplicity, I am posting a code here, my StringFields_BF, which is detected as a Trojan, and below the code with the workaround I usually ...

The zero termination of the strings has not only disadvantages. As with any other method, there are advantages and disadvantages. In many cases one can also accelerate the access strongly, which presupposes however that one is exactly familiar with the mode of operation. With smaller strings there i...

Well, you should get rid of Win7 and x86.
You shouldn't even use the Internet with Win7 anymore.

Temporary decoder bug removed on all decoders. New codes added. A variant with supporting AES and a fully automatic randomized IV has been added. This means that all encrypted data is encrypted completely differently for each encryption process. The behavior of the crypter is similar to the CBC mode...

New codes added.

A variant with supporting AES and a fully automatic randomized IV has been added.
This means that all encrypted data is encrypted completely differently for each encryption process.
The behavior of the crypter is similar to the CBC mode with randomized IV.

Many thanks @idle New codes added. A variant with supporting AES and a fully automatic randomized IV has been added. This means that all encrypted data is encrypted completely differently for each encryption process. The behavior of the crypter is similar to the CBC mode with randomized IV. Creating...

@Tenaja
As sample.
Imagine you have an image with 100 vertical lines with a thickness of one pixel.
Now you want to enlarge it by 20%.
Then you may only add another line to 20 lines to enlarge the image 20%.
Then you have 80 lines with a width of one pixel and 20 lines with a width of two pixels.

You can set a flag with SetGadgetData()

Try it with the x64 compiler. and there is no way around the test with the purifier. In principle, the test with the purifier should always be performed cyclically ! I myself once had the purifier on all the time for one thing. Surprisingly, it ran with Purifier, but crashed without it. That was bad...

I don't know if he just wants to use that for a QR code.
It's just with a QR code that it should be as clean as possible to be readable even under bad conditions.
It also looks unprofessional, even if it still works.

Well, first I would then test the ram with a diagnostic tool. How many images do you embed, how big are they ? This should not be relevant, but a little insight into what exactly you are doing would not be wrong. I don't think your problem is solvable like this, because everything you can be told is...

Yes, it's not that easy to do.
Otherwise, you always have to increase the size by a factor of 2, otherwise it will never work,
because something always has to be added somewhere to achieve the desired size.

The usual way with the QR code is to completely recreate it in the appropriate size.

Have fun ; Use on Windows DPI aware, this is needed for clear output on high scalings ! EnableExplicit InitNetwork() UsePNGImageDecoder() Define imageURL$ = "https://nsa40.casimages.com/img/2021/06/04/210604103322144271.png" Define *queryresponse = ReceiveHTTPMemory(imageURL$) Define img =...