Hello all, for the curious who was wondering.....the original AspeQt development isn't dead by any means. I just released v1.01 and the major new feature is writable folder images with many other smaller enhancements and changes. The development will continue.....enjoy...

AspeQt v1.01

Great!

It's a very convenient and productive operation with AspeQt
Is SIO2BT know implemented as a standard?

Best regards and many thanks for your efforts!

Tigerduck

You're welcome and Yes, bluetooth wireless is supported, however I am currently optimizing the code and will shortly upload a revised version along with rom images and instructions necessary to run bluetooth successfully. This optimization will make a small performance gain and better reliability for Bluetooth. Stay tuned.....

a8w hat geschrieben:bluetooth wireless is supported, however I am currently optimizing the code and will shortly upload a revised version along with rom images and instructions necessary to run bluetooth successfully. This optimization will make a small performance gain and better reliability for Bluetooth. Stay tuned.....

For your information:

a8w for some reasons has rolled back the source code in the AspeQt project repository to the version 0.6.
Luckily nothing can be deleted from "the internet" and some Atari community members were able to restore the latest version. Under these circumstances they decided to continue the development of the tool under the new name "RespeQt". The project is open, everyone can contribute and the source code can be downloaded at github.
I merged the SIO2BT code to this project and you can download the tool with the official SIO2BT support:
http://atariage.com/forums/topic/242422 ... try3449150

It is sad that some people act as children, get offended, take their toys away and do not want to play with others.
The "AspeQt v1.01 - A8W Edition" does not come with the source code and this way a8w violates the license from the original developer Fatih Aygün. Whatever a8w offers here as a "bluetooth support" is his own (closed) code, which is unfortunately not working smoothly with Bluetooth receivers and I do not recommend to use it with SIO2BT.

@a8w
I do not really like the way you go. You decided first to delete your source code (which didn't work).
You didn't integrate my changes to the AspeQt project, which I made freely available with the SIO2BT project.
By the way, you reported once: "I personally found it not worth the trouble and sold my adafruit ez-link bluetooth module" (http://atariage.com/forums/topic/219992 ... try2958859).
On the other hand, you are actively following the RespeQt development (reporting issues, etc.).
Why don't you simply forget it and start contributing to the RespeQt project?

Montezuma, I will chose not to get into the details of what happened or not.

I will only say that the Bluetooth support in AspeQt-A8W Edition works just as smoothly or better than any other fork of AspeQt and it is my own code, just like the Writable folder images are 100% my own code (and tested for many many hours before it is released) and does not use a single line of code from any other development.

In any case users can have their own opinion on what to choose for their SIO2PC software depending on the merits of the software and not just claims.

To whomever is interested in my version: More changes are on the way, and it will only continue in the coming weeks, months and years....

Thank you all who are supporting my efforts by using AspeQt, by buying one of my SIO2PC devices or by contributing to the project in some other tangible way.

a8w hat geschrieben:Hello all, for the curious who was wondering.....the original AspeQt development isn't dead by any means. I just released v1.01 and the major new feature is writable folder images with many other smaller enhancements and changes. The development will continue.....enjoy...

AspeQt v1.01

Is it available as portable app or will it install in Win as the preview version?

The last version caused some trouble because of the forced installation with my Win7Pro-64, so I rolled back to V. 0.8.8 and besides this use RespeQt.

a8w hat geschrieben:I will only say that the Bluetooth support in AspeQt-A8W Edition works just as smoothly or better than any other fork of AspeQt

I have different opinion on that, but if you know everything better...

a8w hat geschrieben:and it is my own code, just like the Writable folder images are 100% my own code (and tested for many many hours before it is released) and does not use a single line of code from any other development.

I have never stated anything else, however no one can tell as long as you do not publish the code (which you should do anyway, because your code is based on the Fatih Aygün's project).

a8w hat geschrieben:In any case users can have their own opinion on what to choose for their SIO2PC software

Sure.

GoodByteXL hat geschrieben:Is it available as portable app or will it install in Win as the preview version?

The last version caused some trouble because of the forced installation with my Win7Pro-64, so I rolled back to V. 0.8.8 and besides this use RespeQt.

AspeQt never had a forced installation (or a installer), you could simply extract the files from the zip archive into a folder on your PC, and run the application.

Montezuma hat geschrieben:

a8w hat geschrieben:I will only say that the Bluetooth support in AspeQt-A8W Edition works just as smoothly or better than any other fork of AspeQt

I have different opinion on that, but if you know everything better...

I only know what i see in my side-by-side tests.

a8w hat geschrieben:

GoodByteXL hat geschrieben:Is it available as portable app or will it install in Win as the preview version?

The last version caused some trouble because of the forced installation with my Win7Pro-64, so I rolled back to V. 0.8.8 and besides this use RespeQt.

AspeQt never had a forced installation (or a installer), you could simply extract the files from the zip archive into a folder on your PC, and run the application.

Oh yes, it changed the paths and wrote it to the registry.

GoodByteXL hat geschrieben:

a8w hat geschrieben:

GoodByteXL hat geschrieben:Oh yes, it changed the paths and wrote it to the registry.

Well, it is portable in a sense that it does not have an installer and can be deleted from the system without leaving any garbage behind, but yes it writes to Windows registry to save it's various settings. That's not something new though, it writes to registry since the very first release (v0.6). And that's the normal way apps behave in the Windows environment, and that's the purpose of the registry (i.e. for apps to save their various settings). It could have been designed to save the settings the old way, using .ini files and there are apps like that, unfortunately AspeQt didn't start that way.

I noticed that you are having some speed problems on Linux, I also personally noticed some hesitation and stuttering when I was testing the latest version on Ubuntu, and the problem seems to be more prominent when a handshake line (like DSR, CTS, RI) is used. Mind you though I have a weak netbook with an ATOM processor and that's my Ubuntu test platform. I do the development on an Ubuntu installation running in VIRTUALBOX on Windows and have no means to attach hardware to that box (well I can, but not that easy, nor convenient)
I have no speed issues with Windows version and AspeQt v1.01 still runs at 0 divisor with no problems on that AMD Athlon 2 X2 240Ghz dual-core machine. It also runs full speed on a rig with PENTIUM 4 240Ghz single core rig with Windows XP. Granted a relatively powerful CPU is a big help in solving SIO speed issues.

I will however look into this problem with linux and see if i can improve it a bit more, no promises but will do my best.

Cheers
Ray

GoodByteXL hat geschrieben:Oh yes, it changed the paths and wrote it to the registry.

Well, it is portable in a sense that it does not have an installer, and can be deleted from the system without leaving any garbage behind. But yes, it writes to Windows registry to save it's various settings. That's not something new though, it writes to registry since the very first release (v0.6). And that's the normal way apps behave in the Windows environment, also that's the purpose of the registry (i.e. for apps to save their various settings). It could have been designed to save the settings the old way, using .ini files and there are apps like that, unfortunately AspeQt didn't start that way.

I noticed that you are having some speed problems on Linux, I also personally noticed some hesitation and stuttering when I was testing the latest version on Ubuntu, and the problem seems to be more prominent when a handshake line (like DSR, CTS, RI) is used. Mind you though I have a weak netbook with an ATOM processor and that's my Ubuntu test platform. I do the development on an Ubuntu installation running in VIRTUALBOX on Windows and have no means to attach hardware to that box (well I can, but not that easy, nor convenient)
I have no speed issues with Windows version and AspeQt v1.01 still runs at 0 divisor with no problems on that AMD Athlon 2 X2 240Ghz dual-core machine. It also runs full speed on a rig with PENTIUM 4 240Ghz single core rig with Windows XP. Granted a relatively powerful CPU is a big help in solving SIO speed issues.

I will however look into this problem with linux and see if i can improve it a bit more, no promises but will do my best.

Cheers
Ray[/quote]

Hi,

a8w hat geschrieben:… and the problem seems to be more prominent when a handshake line (like DSR, CTS, RI) is used. …

Geht es denn auch ohne (Hardware-) Handshake? Nur mit Software- Handshake ?

dl7ukk hat geschrieben:Geht es denn auch ohne (Hardware-) Handshake? Nur mit Software- Handshake ?

When hardware handshaking is used (DSR/RI or CTS) performance is much worse compared to "NO handshake". AspeQt does not have a "Software Handshake". "NO handshake" simply monitors the data line (SIO5 from Atari) and acts upon bytes arriving to the port. For Bluetooth devices the speed is limited to 19,200 bps, for wired SIO2PC devices that provide no hardware hanshaking, the speed can go up to 125,000 bps.

So the problem is worse when a device with hardware handshake is used. I've done a test tonight and the results surprised me:

MY PC SETUP: HP Netbook with 1.6Ghz ATOM CPU, with Ubuntu 15.04, and 1GB of RAM
SIO2PC SETUP: My own SIO2PC/10502PC Dual-USB v3.1

I ran RWTEST.COM with AspeQt set for 125,000 bps (divisor 0) SIO Speed:

WITH "DSR" handshaking, I had lots of speed adjustments (stutters) and some I/O errors. RWTEST result is 1,682 KBs and CPU load was 25%.

WITH NO Handshaking, I had some speed adjustments (stutters) and 1 I/O error. RWTEST result is 4,179 KBs and CPU load was 40%.

So, as you see, even with almost twice as much CPU load "NO handshake" performed better. The reason for higher CPU load was due to constant polling of the DATA IN line by AspeQt. So my conclusion is, the speed problem in Linux is not due to CPU load, but perhaps related to driver issues or some other factor, which needs more detailed investigation.