I am not sure that i understand whole hype around plugins you want
i made 64bit .dll in o2 for one java based language called Dragon lang and work well.

Hi Joe,

you can produce both 32 and 64bit DLLS with the 32bit o2 compiler. But we don't have a stable 64bit self-compiling o2 yet. You would only need this if you were using Oxygen as a sub-system at run-time in your application. Do you really need this?

I've been reviewing Oxygen Basic the last couple of days,
on the hope that I can create a plugin for JPSoftware's TCC.EXE

Ref: https://jpsoft.com/

When TCC.EXE was a 32-bit application,
I wrote my plugins using PowerBasic 8 for Windows.

As TCC.EXE is now a 64-bit application,
and PowerBasic is still 32-bit,
I purchased PureBasic to develop 64-bit plugins for TCC.EXE

The first plugin that I converted from 32-bit PowerBasic
to 64-bit PureBasic
was my plugin that allowed the reading of .DBF files.

Ref: https://www.jpsoft.com/forums/threads/64-bit-plugin-development-using-purebasic.10988/

The second 64-bit plugin I developed for TCC.EXE
allowed me to run VBScript files and functions,
fixing the problems that the TCC Script Command had.

Ref: https://jpsoft.com/forums/threads/script-and-getobject.10696/post-60212
Ref: https://jpsoft.com/forums/threads/activescript-for-vbscript.11353/
Ref: https://jpsoft.com/help/script.htm

I would like to develop a plugin that will include Oxygen Basic.

My first step involves getting 64-bit PureBasic to work with the oxygen.dll file.

I note that oxygen.dll is a 32-bit dll,

Quoteoxygen.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows, UPX compressed

which contains the following exports;

QuoteMicrosoft (R) COFF/PE Dumper Version 14.34.31937.0
Copyright (C) Microsoft Corporation.  All rights reserved.


Dump of file oxygen.dll

File Type: DLL

  Section contains the following exports for oxygen.dll

    00000000 characteristics
           0 time date stamp
        0.00 version
           1 ordinal base
          16 number of functions
          16 number of names

    ordinal hint RVA      name

          1    0 00076910 o2_abst
          2    1 00076780 o2_basic
          3    2 000753B0 o2_buf
          4    3 00076980 o2_errno
          5    4 000769D0 o2_error
          6    5 00075600 o2_exec
          7    6 00075360 o2_len
          8    7 000754B0 o2_lib
          9    8 000756B0 o2_link
         10    9 00075330 o2_mode
         11    A 00075300 o2_pathcall
         12    B 000768C0 o2_prep
         13    C 000761B0 o2_stats
         14    D 000752D0 o2_varcall
         15    E 00076A40 o2_version
         16    F 00076870 o2_view

  Summary

      29E000 UPX0
       1F000 UPX1
        1000 UPX2

I need a 64-bit version of oxygen.dll in order to work with 64-bit PureBasic.

Is there a 64-bit version of oxygen.dll?
How can I create a 64-bit version of oxygen.dll?

I am nowhere near an expert programmer as others on the forum,
so constructive suggestions and corrections would be appreciated.

Regards,

Joe

We welcome a new Member: Joe Caverly

About Joe:

Quote
I have been a member of the PowerBasic Forum since 19 Sept 2004.
I have posted 263 times on the PowerBasic Forum.

I have known Kevin Diggins the longest,
as I have been a member of his BASM forum,
and BCX forum,
on Yahoo! Groups,
and on his current BCX Basic Coders Forum.

I know Gary Beene, as I did testing for his gbThreads application.
I have become interested in Oxygen Basic,
and would like to join the forum for that reason.

Welcome Joe.

You are asking the wrong questions, and so is your friend.

Bluetooth devices of Class 2 range up to 100 meter, Bluetooth devices of Class 1 range up to 1 Kilometer.

If you just perform the tests using your phone and in an open space, regardless of open field, cemetery etc., your are more than likely picking up stray signals. Given that Bluetooth 4.0 and up (virtually all devices in the past 13 years) transmit random mac addresses of variable duration (chosen by manufacturer) that explains the unidentified mac addresses.

Now an other important point is that Bluetooth is an active RF signal, as opposed to RF Id's, which means it needs a power source.

Like I said the only way to test the premises that Vaccinated people transmit a BLUETOOTH Signal (not an RF signal, since this is what is been Claimed here using a phone to detect nearby Bluetooth mac addresses) Is to use a Faraday Cage. Anything else is just anecdotal and wishful thinking.

The test is so simple and relatively easy to do, it would have been allover the news (fake news or not) if it had merit.

QuoteThe random Bluetooth mac addresses are more than likely other Bluetooth devices (computers, mice, keyboards, Watches, earbubs, smart home devices, tv's, sound systems, home appliances, old phones, cars, dog collars tracers, etc.)

He checked that of course. He says that these adreses are there even on an open field without any nearby devices, please test it yourself.
I did not have the chance to test it. But i know he is a technician, he is not stupid.

Also its like that. If you see that adress on your phone before a person enters your office - and its always the same adress - and you ask the person "do you have your handphone with you?"
and the person does not have it. And it always happens with many people, then you should really think about it. I guess this is what happened to him.
He told me that he now ask these people "Can i now order over you?" :-)

But in O2 you still need to handcode it yourself :-)

Quoteif you like speed, make these commands in ASM

Oh ..you don't know ?
o2 basic and o2 asm run at same speed ..i TESTED

You can enable "Show Bluetooth devices without names" on many Samsung phones by enabling Developer mode.

The random Bluetooth mac addresses are more than likely other Bluetooth devices (computers, mice, keyboards, Watches, earbubs, smart home devices, tv's, sound systems, home appliances, old phones, cars, dog collars tracers, etc.)

In order to protect us from being tracked via Bluetooth broadcast of our devices Bluetooth LE Privacy was created.

When Bluetooth LE Privacy is in use, advertising packets contain randomly generated MAC addresses disguising your device's identity, the real MAC address remains hidden away.

But what use is this if the outside world sees your device as having a different address?

The answer lies in the Bluetooth pairing process—Bluetooth® users are familiar with this process. Pairing indicates you trust the other device and want to interact with it. For example, if you pair your activity tracker with your phone, from that point on, the phone will have a special, trusted relationship with the tracker. What happens is much more involved but after pairing, the two devices will possess various encryption keys, one of which is concerned with privacy. This key is called the Identity Resolution Key (IRK). IRK allows the first device to translate those special, random MAC addresses which appear in the advertising packets from the second device, to the real MAC address in the second device. This capability is only in devices you have explicitly trusted.

Most electronic devices with Bluetooth support are Class 2 or Class 3 Bluetooth devices. Consumer products such as Apple and Android smartphones, tablets, and peripherals like wireless earbuds and Bluetooth headsets fall into this category.

Class 2 Bluetooth 4.0 radios officially support data transfer up to 33 feet (10 meters). Meanwhile, Class 3 devices typically have a range of less than 3 feet (1 meter). It's not uncommon for Class 2 devices to reach 100 feet, but they don't officially support that range.

The only real way to test for mRNA vaccine Bluetooth transmission is inside a Faraday cage, with some vaccinated people in it. I have not seen any credible evidence, in a controlled environment of such mac addresses.