how the heck do you actually use APE with SIO2PC (USB)

[+Larry]

@ Frankie-

 

Thanks. The only differences that I see are that my FTDI adapter uses com 3 with RI. It might be wired to RI. (?) I need to look at that sometime. And my XP ran better with the Master Timing set at +40 to +50.

 

Interestingly, it runs worse on my Win7-64 box @ 3.4 GHz. In fact, it crashed windows to the BSOD. Think I'm done with this exercise...

 

-Larry

 

Edit: Couldn't resist.. I got out another adapter -- the one from Sloopy that is the SIO plug mini type. This one sets itself up as Com 4, but as DSR, and it works much better. I can get 3X on my XP machine, with the Master Schedule set at the default of zero. The SIO even sounds better -- cleaner, if that makes any sense. Also went back and opened up the original FTDI adapter, and it was wired as RI. Rewired it to DSR, and now it sounds and works just as good as the Sloopy adapter.

[_The Doctor__]

funny how data set ready has always worked better as it is indeed a flow control line... where as ring indicate has historically had mixed success being used in that fashion.... but it does make sense if you think about their designed purpose and how virtual serial ports software simulates those lines

[Kyle22]

I made my own SIO2PC USB cable with one of these: http://www.ebay.com/itm/6P-FTDI-FT232RL-USB-to-Serial-adapter-module-USB-TO-TTL-RS232-Cable-F-Arduino-5v-/111241824248?hash=item19e68787f8:g:7ScAAOxycmBSs3lW

 

All I had to do was add the SIO plug. This one uses CTS for the command line. It works perfectly with APE Pro and RespeQt. It runs full speed (divisor zero) in RespeQt, and PCLink works great.