The direct download link is http://www.godevtool.com/Gorc.zip and in theory should give you the same issue, unless the file was compromised by its brief visit to my build system. Thanks for the link, this worked without problems (no message from Avira). It seems, it's related to the build process, ...

Does Avira remove it during a scan? Or just when it gets executed? No, the removal is instant, when extracting the .7z (with 7zip File Manager). It says, it's been put into "quarantine" ... Last time IIRC, I've sent it to manufacturer, who confirmed "false positive" and, adjuste...

Avira (anti virus) removes GoRC.exe, in both WIN32/WIN64, due to (probably) false positive.

Had that IIRC, with FBC's 1.04.0 too ...
(Probably works also, with the GoRC version from 1.05.0, as workaround.)

Leave it, as is ... (aka: no need for change)

Reason: the only person here, that has mastered the Art of complexifying everything,
instead of keeping simple things the way they are, should not be the "yardstick" ...

To get back OT (... when using input), by leaving it to input, to deal with it: Function main_menu() As String Dim As String choice, room = "" While room = "" ' run until we have a useful answer Cls choice = "" ' assure a empty string Print "welcome to this thing&q...

UEZ wrote:Please do not reply such comments in my topic anymore.

No problem, provided that you in future, keep your "Libraries code" out of all threads,
that are not your own ... because that's become very, very annoying!

Well then, that seems to confirm the issue being related to: high DPI settings ...

UEZ wrote:Why?

You may want to become a "Programmer" and, not just stay put as "Library Linker".

Try 100% (M$'s recommendations are quite useless sometimes) because:
you can, at any later stage change back, if you don't like what you see ...

<edit/>

Seems to me, to be a "high DPI" issue, rather than a bug.
Check Windows settings ... (if NOT set to: 100%)

Never had it in 1920 x 1080 (100%), but with 3200 x 1800 display.
(setting here, is 150%)

However, I've found whatever it does can be unreliable on some machines, and fail to return anything. Well, the first thing I'd investigate, whould be: "are my assuptions" regarding the way, the agent is "expected" to react, correct? (may not be the case) Before that, I'd not ev...

@gothon, your criticism below, in point 3) has the facts 'the wrong way around' , because: C's 'int' = FB's 'Long' (both 32 bit, fixed size) and, C's 'long' = FB's 'Integer' (both dynamic sizing, aka: Ptr size), exception is: WIN64 (API) See also: (data-type) comparison table, in the FB-Manual

You'll just have to realize, that it in fact does, nothing to be fixed, therefore.

Btw. the max. value of ULongInt = 2 ^ 64 - 1 or,
ULongInt = &hFFFFFFFFFFFFFFFF

if a do 512 loops of Int( RND * 256 ) it should chose each of 256 values , at least once.. No, this now relates to the randomizers randomness, meaning, you cannot know when a certain number appears. The only guaranteed fact is, that it eventually will appear ... provided, you run the randomizer for...