Jump to content



atari8warez's Photo

atari8warez

Member Since 9 Sep 2007
OFFLINE Last Active Yesterday, 11:25 PM

Posts I've Made

In Topic: AspeQt: Yet another SIO2PC/APE clone

Yesterday, 7:36 PM

View Postw1k, on Sat May 26, 2012 1:02 PM, said:

please, czech translation.. or slovak :)

Do you want to do it ;-)

In Topic: AspeQt: Yet another SIO2PC/APE clone

Fri May 25, 2012 3:23 PM

View Posta8isa1, on Fri May 25, 2012 7:46 AM, said:

View Postatari8warez, on Fri May 25, 2012 12:10 AM, said:

View Posta8isa1, on Thu May 24, 2012 8:32 PM, said:

View Postatari8warez, on Thu May 24, 2012 2:14 AM, said:

version 0.8.3 is now available:

+ Added option to keep the Boot Executable dialog open for succesive reboots of the same XEX file


Source and Windows binaries

The dialog box stays open but I cannot load an XEX file on successive tries. The old progress bar stays at 100% from the first loading.

I haven't tried any of the other new features yet.

This is in linux.

Sorry, I didn't test it on linux as I don't have it, but it does work on Windows (and works pretty good) with several xex files i tried. Actually I can't see why it shouldn't work with linux, did you try some other game or games.
Ah! Thanks!

I found my problem. My own compiled Action! programs are what won't load on successive attempts. The mounted ATR in D1: loads instead.

I don't know what could be causing that but it's not a real issue for me. Only one of them is something I might even consider booting directly from aspeqt. Usually I just place it on a bootable ATR.

Sorry for the false alarm. My own programs were at hand so those are what I tried.

No problem....One thing about the exe, xex, or com files is that NOT ALL OF THEM WILL WORK with the AspeQt loader. The majority does however there will always be some which doesn't. I am not sure why, but my guess is it could be the custom SIO code (which I haven't written myself). Some executable files will not work with High Speed loader, in that case try the normal speed (an option in AspeQt). If it still doesn't work then there is no fast and easy answer as to why?

Also some files which load and run the first time will not reboot when you leave the executable loader dialog open. At this time I am not sure why this happens, i will check the code again to try to find an answer.

Ray

In Topic: AspeQt: Yet another SIO2PC/APE clone

Fri May 25, 2012 3:11 PM

View Postatarixle, on Fri May 25, 2012 3:07 PM, said:

I'm just wondering (and be angry to myself) cuz I compiled it already ... and the reason, why 0.8.3 not compiles has always been something else than I thought...

I will have to spend a lot of more time with that :/

I know the ultimate solution: I will ask Carsten on the Fujiama Event. He knows much about OS X as he worked on it years ago (when they still were cool) ;-)

Ok nice to hear that.....

In Topic: AspeQt: Yet another SIO2PC/APE clone

Fri May 25, 2012 3:09 PM

View Postjohn-m, on Fri May 25, 2012 2:54 PM, said:

I can get ASPEQT to work fine with a Prolific to Atari SIO serial to sio cable in Windows 7 and Windows Vista.
But, with linux, I set up the Prolific adapter, and it comes up as a serial back end called ttyUSB0.
When I select that in ASPEQT as the port, I get a message saying it is connected, but no data is transferred at all.
On another laptop with a true serial port, it works fine.
Also, when the connection is supposedly made, my processor usage goes way up.
And how does one tell linux what serial port the adapter is to use?
This is driving me crazy as I know the adapter works from use with Windows and ASPEQT.

View Postjohn-m, on Fri May 25, 2012 2:54 PM, said:

I can get ASPEQT to work fine with a Prolific to Atari SIO serial to sio cable in Windows 7 and Windows Vista.
But, with linux, I set up the Prolific adapter, and it comes up as a serial back end called ttyUSB0.
When I select that in ASPEQT as the port, I get a message saying it is connected, but no data is transferred at all.
On another laptop with a true serial port, it works fine.
Also, when the connection is supposedly made, my processor usage goes way up.
And how does one tell linux what serial port the adapter is to use?
This is driving me crazy as I know the adapter works from use with Windows and ASPEQT.
I am just having major problems getting it to work with linux.
Has anyone been successful in getting ASPEQT working with a Prolific USB2serial adapter connected to an Atari SIO2PC cable in Linux?
If so, I would like to know how you accomplished the feat!
I am just having major problems getting it to work with linux.

Has anyone been successful in getting ASPEQT working with a Prolific USB2serial adapter connected to an Atari SIO2PC cable in Linux?
If so, I would like to know how you accomplished the feat!

I can't really comment on linux issues, however I can suggest using an FTDI based VCP. I too have a Prolific VCP and even though it works fine with AspeQt in Win 7, it only works up to 2 x SIO speed and not as reliably as an FTDI cable. an FTDI cable will work up to 6x SIO on Win7 with no problems because it supports more serial port baud rates than a Prolific cable does. Also FTDI drivers have a miriad of settings that you can customize, not so with the Prolific drivers which will only give you standard serial port options.
Cables with FTDI chipset can also be re-programmed as they include an inline programmable EPROM, you can even change the signal strength on the chip's pins.

AspeQt officially only supports the FTDI based cables.

Ray

In Topic: AspeQt: Yet another SIO2PC/APE clone

Fri May 25, 2012 3:00 PM

View Postatarixle, on Fri May 25, 2012 11:46 AM, said:

Damn, what the f is this???

Even AspeQt 0.8.1 doesn't compile on my Mac anymore, even if I am sure it did already!!!!!!

The My Binary Build on my Homepage proves that!!!

I can certainly understand your frustration but sorry can't do much about that as I am not familiar with Mac OS, but maybe you should check if you need to include some Mac OS specific header files before you compile (doesn't the compiler say what's wrong with the compile?) or ask to some Mac OS guru among Atariage users. Shouting "damn it doesn't work" will most certainly not help with the situation. You need to be more specific about the problem.

I've mentioned that many times but here we go again, I am not a Mac or Linux coder and I don't have a clue about either of these platforms.