Tempest Posted April 26, 2015 Share Posted April 26, 2015 I'm trying to run AspeQT under Ubuntu and it seems to work (I get the main screen) but when I try and use it with my SIO2PC device nothing seems to happen. I've tried all the various handshaking methods and I know the serial port is correct, but no matter what the Atari doesn't seem to receive any data from the PC. Any idea what could be wrong or what else I can test? I'm not sure what kind of SIO2PC device I have, it's just a SIO cable with a little serial device on the end that someone made for me years ago. It always worked with my PC though. 1 Quote Link to comment Share on other sites More sharing options...
Tempest Posted April 26, 2015 Author Share Posted April 26, 2015 I think my issue is a bad serial cable. 1 Quote Link to comment Share on other sites More sharing options...
airsoftmodels Posted June 28, 2015 Share Posted June 28, 2015 i am having the same exact problem as you did. Did you figure anything out, and did you get it working since April? Quote Link to comment Share on other sites More sharing options...
Joey Z Posted June 29, 2015 Share Posted June 29, 2015 i am having the same exact problem as you did. Did you figure anything out, and did you get it working since April? airsoftmodels, check your own thread, I already replied there. your SIO2PC is NOT /dev/ttyS3 1 Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted June 29, 2015 Share Posted June 29, 2015 Which serial port line is mapped to /Command ? That makes a difference. 1 Quote Link to comment Share on other sites More sharing options...
morelenmir Posted June 29, 2015 Share Posted June 29, 2015 I encountered much the same problem just last night. Everything compiled and built perfectly. The app is nice to look at and seems to work. However if i connect my "SIO2PC" to the USB port on the Debian end and the SIO socket on the A8, mount say an 'ATARI DOS 2.5' image on the "D1:" simulator of "AspeQT" and then switch on it does not work. What happens is a constant 'handshaking buzz' from my A8 interspersed with random single beeps of normal data transfer. If I look at the log output on "AspeQT" it is producing constant changes in transfer speed and very occasional single reads from the *.ATR image. Nothing else happens until I switch off. However if I try the same thing with the "SIO2PC" connected to a Win2K3 machine and the 0.6v of "Aspeqt" it works perfectly. I assumed it was some issue with the USB hub on my Debian machine, but now I suspect it is a problem with the latest release of "AspeQT" itself since others are having trouble as well. For the record I have "AspeQT" set up to use 'ttyUSB0' through 'RI' handshaking. 1 Quote Link to comment Share on other sites More sharing options...
Joey Z Posted June 29, 2015 Share Posted June 29, 2015 I encountered much the same problem just last night. Everything compiled and built perfectly. The app is nice to look at and seems to work. However if i connect my "SIO2PC" to the USB port on the Debian end and the SIO socket on the A8, mount say an 'ATARI DOS 2.5' image on the "D1:" simulator of "AspeQT" and then switch on it does not work. What happens is a constant 'handshaking buzz' from my A8 interspersed with random single beeps of normal data transfer. If I look at the log output on "AspeQT" it is producing constant changes in transfer speed and very occasional single reads from the *.ATR image. Nothing else happens until I switch off. However if I try the same thing with the "SIO2PC" connected to a Win2K3 machine and the 0.6v of "Aspeqt" it works perfectly. I assumed it was some issue with the USB hub on my Debian machine, but now I suspect it is a problem with the latest release of "AspeQT" itself since others are having trouble as well. For the record I have "AspeQT" set up to use 'ttyUSB0' through 'RI' handshaking. which version of AspeQT are you using on Debian? 1 Quote Link to comment Share on other sites More sharing options...
morelenmir Posted June 29, 2015 Share Posted June 29, 2015 which version of AspeQT are you using on Debian? I built it from the source made available by Hiassof: http://www.horus.com/~hias/tmp/aspeqt-source-svn-r77.tgz This was originally posted in the 'AspeQT under Linux fails to compile' thread. 1 Quote Link to comment Share on other sites More sharing options...
Joey Z Posted June 29, 2015 Share Posted June 29, 2015 I built it from the source made available by Hiassof: http://www.horus.com/~hias/tmp/aspeqt-source-svn-r77.tgz This was originally posted in the 'AspeQT under Linux fails to compile' thread. yes I know the one. Nobody else has been having (as far as I know) the problems you are having with that version. It probably *is* a hardware anomaly with your debian machine. Sometimes disconnecting all other USB devices from that particular USB host can help the issue. Also, I have just posted the r79 source here: http://atariage.com/forums/topic/239909-aspeqt-release-79-100-preview-7-source-code/ You can give that a try, but I don't think anything changed in the serial code, so I doubt it will help you. 1 Quote Link to comment Share on other sites More sharing options...
morelenmir Posted June 29, 2015 Share Posted June 29, 2015 yes I know the one. Nobody else has been having (as far as I know) the problems you are having with that version. It probably *is* a hardware anomaly with your debian machine. Sometimes disconnecting all other USB devices from that particular USB host can help the issue. Also, I have just posted the r79 source here: http://atariage.com/forums/topic/239909-aspeqt-release-79-100-preview-7-source-code/ You can give that a try, but I don't think anything changed in the serial code, so I doubt it will help you. I think you may well be right. I will try setting up another machine and see if the problem recurs. Many thanks for the new version also! I have really enjoyed the Linux experience of building and installing applications from their raw source code. It is so different from the Windows process! 1 Quote Link to comment Share on other sites More sharing options...
airsoftmodels Posted July 1, 2015 Share Posted July 1, 2015 aspeqt on the osx version (which i can't find a link to anymore by the way) loading of atr and xex images was very smooth, no pauses. perhaps due to the ftdi driver? under linux mint, i have compiled aspeqt-code-79-trunk.tar.gz as well as AspeQt_0.8.8_debian, and although it does work, it pauses, and sometimes i have to try again to load the games. Quote Link to comment Share on other sites More sharing options...
+DrVenkman Posted July 1, 2015 Share Posted July 1, 2015 (edited) aspeqt on the osx version (which i can't find a link to anymore by the way) loading of atr and xex images was very smooth, no pauses. perhaps due to the ftdi driver?On the contrary, my experience with the OS X version was terrible, with spiking CPU load, stuttering and halting file transfers, etc. Using the Windows version under WINE worked perfectly. Go figure. I compiled the r79 version JoeyZ posted the other night and it appears to load and run without the spiking processor usage I was seeing with prior versions. I haven't pulled out a real Atari to test it yet, however. Edited July 1, 2015 by DrVenkman 1 Quote Link to comment Share on other sites More sharing options...
airsoftmodels Posted July 2, 2015 Share Posted July 2, 2015 can anyone please give me a link to the osx version that would work with osx 10.6.8 intel? my 2006 imac died and i lost the data, but i think i am gonna get another one. thanks much. Quote Link to comment Share on other sites More sharing options...
+DrVenkman Posted July 2, 2015 Share Posted July 2, 2015 (edited) For what it's worth, the version I compiled last night shows the same kind of processor spiking I was seeing before as soon as I enable SIO emulation. I can post it tonight if you'd like to try it, though. It would be interesting to see if the problem is in my system or the code created by the OS X version of Qt. Sent from my iPhone using Tapatalk Edited July 2, 2015 by DrVenkman 1 Quote Link to comment Share on other sites More sharing options...
airsoftmodels Posted July 2, 2015 Share Posted July 2, 2015 thanks DrVenkman, please do. i know i had downloded a compliled version somewhere not too long ago. Q: "what exactly are you a doctor of?" A: "i hold p.h.d's in psychology and parapsychology" -Ghostbusters 1 Quote Link to comment Share on other sites More sharing options...
+DrVenkman Posted July 2, 2015 Share Posted July 2, 2015 thanks DrVenkman, please do. i know i had downloded a compliled version somewhere not too long ago. Q: "what exactly are you a doctor of?" A: "i hold p.h.d's in psychology and parapsychology" -Ghostbusters "I love this plan! I'm excited to be a part of it! Let's do it!" https://www.dropbox.com/sh/g9f26osftro9m9w/AACYL5iVBI0M7ba6fm4fMmD5a?dl=0 And here's a link to the entire r79 build folder with sources: https://www.dropbox.com/sh/l7satfg0bk5iyvx/AADYD68oQnOqDahdz_TrqU_ta?dl=0 Hope these work - I've had mixed results sharing Dropbox links. 1 Quote Link to comment Share on other sites More sharing options...
airsoftmodels Posted July 3, 2015 Share Posted July 3, 2015 venkman: "remember the time you tried to drill a hole in your head?" Igon: "that would have worked if you hadn't stopped me" Quote Link to comment Share on other sites More sharing options...
+DrVenkman Posted July 4, 2015 Share Posted July 4, 2015 So did you give my build a try? I just did this morning, with my 800XL. In fact, I tried my native OS X builds of both AspeQt r79 and RespeQt r1 and both of them are plagued with crazy-high CPU usage, stuttering and halting data transfers and general unpleasantness. Ironically, the Windows build of AspeQt 1.0 preview 6 from last summer running under CrossOver performed pretty well, all things conserved. Low CPU usage, stable data transfer without hesitations and pauses ... crazy that the native builds just don't work right. I blame Qt. If I get a week or two between projects at work, I might try importing the C++ code into Xcode and trying to rebuild the thing without Qt. THAT will be a learning experience, I'm sure! The best OS X solution, sadly, still appears to be the now-four years old SIO2OSX. It's not free, which I don't mind in principle, but at $25 to register it's definitely on the expensive side for non-updated software. If he made the source available at least I'd be able to try to update it for a more recent release of OS X but it's closed source. If the registration was $10 or less, I'd have a lot less heartburn about it. Quote Link to comment Share on other sites More sharing options...
Joey Z Posted July 4, 2015 Share Posted July 4, 2015 So did you give my build a try? I just did this morning, with my 800XL. In fact, I tried my native OS X builds of both AspeQt r79 and RespeQt r1 and both of them are plagued with crazy-high CPU usage, stuttering and halting data transfers and general unpleasantness. Ironically, the Windows build of AspeQt 1.0 preview 6 from last summer running under CrossOver performed pretty well, all things conserved. Low CPU usage, stable data transfer without hesitations and pauses ... crazy that the native builds just don't work right. I blame Qt. If I get a week or two between projects at work, I might try importing the C++ code into Xcode and trying to rebuild the thing without Qt. THAT will be a learning experience, I'm sure! I blame Qt also porting it away from Qt might not be even really conceivably possible. At that point, writing an entirely new SIO2PC software might end up being easier. I have had someone request backporting to Qt4 for support on linux versions which don't have a Qt5 build (there are plenty, I think, that lack Qt5). I believe you said a *really* old version worked alright? it could be related to Qt5 being terrible on OSX, so if/when I have a Qt4 backport, I'd like to see how it does on OSX. Quote Link to comment Share on other sites More sharing options...
fujidude Posted July 4, 2015 Share Posted July 4, 2015 Qt4 has always seemed pretty solid at least on any of the apps I've used built with it. I don't know what more Qt5 offers but I've not been left wanting from 4. Quote Link to comment Share on other sites More sharing options...
airsoftmodels Posted July 4, 2015 Share Posted July 4, 2015 I am going to keep working with the Linux versions. The trouble is loading an atr image takes too long due to stalls and errors. I want to tweak it using the Tools Menu, anybody know if DSR is the only handshake method that works with the SIO2-PC-USB from Lotherek? Should the Baud Rate be 19200, 38400, or 57600? I am using USB 3.0 on my i5 Dell. I am intrigued by the non-standard speeds POKEY divisor (0 - 40), but I have no idea what number works there and if its needed at all. Quote Link to comment Share on other sites More sharing options...
airsoftmodels Posted July 8, 2015 Share Posted July 8, 2015 I went ahead and re-installed windows 7 on a 120gb SSD, for the sole purpose of trying out AspeQt for windows. It works. I tried COM1, then COM2 then COM3 and found the sio2pc-usb. 1 Quote Link to comment Share on other sites More sharing options...
+DrVenkman Posted July 8, 2015 Share Posted July 8, 2015 I went ahead and re-installed windows 7 on a 120gb SSD, for the sole purpose of trying out AspeQt for windows. It works. I tried COM1, then COM2 then COM3 and found the sio2pc-usb. Yep. AspeQt for Windows works great, even on my Mac running OS X under CrossOver! It's nuts. There's something very screwy in the OS X implementation of the SIO stuff, but I'm hacking away at stuff in the new RespeQt fork, using the advice and suggestions of some very talented folks. Me, I'm just a klutz with access to dev tools. Quote Link to comment Share on other sites More sharing options...
airsoftmodels Posted July 11, 2015 Share Posted July 11, 2015 I was given an early 2008 13" macbook yesterday after setting up a 4TB RAID for a friend. I am formatting the HD and installing OSX 10.6.8. Then I will install AspeQt for OSX, and let you know how it runs. I had it going fine on a 2006 iMac running the same OS, didn't notice any problems at all. I believe all the magic is in the FTDI driver, which I downloaded from here: http://www.ftdichip.com/Drivers/VCP.htm Quote Link to comment Share on other sites More sharing options...
+DrVenkman Posted July 11, 2015 Share Posted July 11, 2015 (edited) I was given an early 2008 13" macbook yesterday after setting up a 4TB RAID for a friend. I am formatting the HD and installing OSX 10.6.8. Then I will install AspeQt for OSX, and let you know how it runs. I had it going fine on a 2006 iMac running the same OS, didn't notice any problems at all. I believe all the magic is in the FTDI driver, which I downloaded from here: http://www.ftdichip.com/Drivers/VCP.h I have been fooling around with AspeQt for over a year on my Mac (OS X 10.9, 10.10 and now a beta of 10.11) ... I have always used the latest FTDI drivers. AspeQt simply doesn't work well with Macs, at least if they're running updated versions of OS X. And it's clearly an AspeQt/Qt problem not a driver problem and I'll tell you why: 1. SIO2OSX (a paid program I finally bought today, for $25) works great, though it does not support booting .XEX files. However, for .ATR files, on the same Mac and using the same version of OS X and the same device drivers, it's perfect; 2. AspeQt for Windows, running under CrossOver on the same Mac and using the same versions of OS X, also works great - absolutely zero problems; 3. SIOServer, a little program written by an AA user named Mellis, also works great, though it hasn't been updated in a long time and doesn't run under 10.10 or 10.11. But it works under 10.9 perfectly, with the same FTDI driver. I've been beating my head against the wall for a week trying to optimize the recent fork (RespeQt) to fix the crazy CPU usage issue in 10.9, 10.10 and 10.11. Thanks to a suggestion from AA user HiassofT, I fixed that issue. I still have a problem with random stutters and halting in the I/O routines. It's hard to narrow down because it's a timing issue and those are always a problem. AA user phaeron, author of Altirra, suggests that perhaps the I/O code is perhaps using the wrong control structures and I'm inclined to agree; however, I have managed to improve performance quite a bit by adding some small (50 - 150 microsecond) delays in several of the I/O routines; it seems the software is trying to cycle between SIO modes faster than Atari hardware is expecting. These delays are an ugly hack but I don't know enough about either the SIO timing specs or BSD/OS X I/O data structures to totally rewrite the code to fix the problem at its source. But in the absence of a real expert stepping up to fix the problem, I'm working on it. Edited July 11, 2015 by DrVenkman Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.