atari800-users — Atari800 users

Re: [Atari800-users] Cannot get my USB joystick to work

[Greg H. <gre...@ba...>]

I tried that, it didn't recognize all my buttons, neither did
joystick-mapper.
I found a program called joymap (https://github.com/wizlab-it/joymap.git),
it's the simplest joystick key mapper, it is one c file of 210 lines of
code.

When I run joymap -x, it dumps out the current state of all buttons and
axes, then as buttons/axes are pushed/released/moved, it shows the changes.

You can run joymap with a set of args indicating which mappings you want.
If I run joymap with mappings, then run xev, xev shows the expected keysym
as I press the buttons. xev only shows output when buttons are pressed.

Yet when I run atari800, my guy keeps running and/or jumping when I'm not
even touching the joystick.

The only emulator that works perfectly for me is mednafen - it reads the
joystick directly, noy key mappings required. I can only guess I have some
very weird problem, that can only be solved by having emulators directly
read the joystick.

On Fri, Aug 6, 2021 at 8:11 PM <be...@op...> wrote:

> I've just discovered AntiMicroX, and that seems to work well. Uses qt5 so
> not lightweight though.
>
>
> On Fri, 6 Aug 2021 19:52:00 -0300
> Greg Hall <gre...@ba...> wrote:
>
> > I noticed some issues spending more time using the coolcv Coleco emulator
> > to play HERO. The game would work for maybe 5 or 6 levels, then get stuck
> > moving left and/or up all the time. I'm thinking you're probably right
> > Miro, that qjoypad has some issues.
> >
> > I found another solution called joystick-mapper, which appears to be a
> > Linux only solution. I'll see how well that works :)
> >
> > On Fri, Aug 6, 2021 at 2:59 PM Petr Stehlík <pst...@so...> wrote:
> >
> > > On Čt, 2021-08-05 at 21:20 -0300, Greg Hall wrote:
> > > > I map my USB joystick to keys using qjoypad
> > >
> > > why?
> > >
> > > Petr
> > >
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Atari800-users mailing list
> > > Ata...@li...
> > > https://lists.sourceforge.net/lists/listinfo/atari800-users
> > >
>
>
>
>
> _______________________________________________
> Atari800-users mailing list
> Ata...@li...
> https://lists.sourceforge.net/lists/listinfo/atari800-users
>

Re: [Atari800-users] Cannot get my USB joystick to work

[<be...@op...>]

I've just discovered AntiMicroX, and that seems to work well. Uses qt5 so not lightweight though.


On Fri, 6 Aug 2021 19:52:00 -0300
Greg Hall <gre...@ba...> wrote:

> I noticed some issues spending more time using the coolcv Coleco emulator
> to play HERO. The game would work for maybe 5 or 6 levels, then get stuck
> moving left and/or up all the time. I'm thinking you're probably right
> Miro, that qjoypad has some issues.
> 
> I found another solution called joystick-mapper, which appears to be a
> Linux only solution. I'll see how well that works :)
> 
> On Fri, Aug 6, 2021 at 2:59 PM Petr Stehlík <pst...@so...> wrote:
> 
> > On Čt, 2021-08-05 at 21:20 -0300, Greg Hall wrote:
> > > I map my USB joystick to keys using qjoypad
> >
> > why?
> >
> > Petr
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Atari800-users mailing list
> > Ata...@li...
> > https://lists.sourceforge.net/lists/listinfo/atari800-users
> >

Re: [Atari800-users] Cannot get my USB joystick to work

[Greg H. <gre...@ba...>]

I noticed some issues spending more time using the coolcv Coleco emulator
to play HERO. The game would work for maybe 5 or 6 levels, then get stuck
moving left and/or up all the time. I'm thinking you're probably right
Miro, that qjoypad has some issues.

I found another solution called joystick-mapper, which appears to be a
Linux only solution. I'll see how well that works :)

On Fri, Aug 6, 2021 at 2:59 PM Petr Stehlík <pst...@so...> wrote:

> On Čt, 2021-08-05 at 21:20 -0300, Greg Hall wrote:
> > I map my USB joystick to keys using qjoypad
>
> why?
>
> Petr
>
>
>
>
>
>
> _______________________________________________
> Atari800-users mailing list
> Ata...@li...
> https://lists.sourceforge.net/lists/listinfo/atari800-users
>

Re: [Atari800-users] Cannot get my USB joystick to work

[Petr S. <pst...@so...>]

On Čt, 2021-08-05 at 21:20 -0300, Greg Hall wrote:
> I map my USB joystick to keys using qjoypad

why?

Petr

Re: [Atari800-users] Cannot get my USB joystick to work

[Miro K. <mir...@gm...>]

Well, you can map the joypad to A, B, C, D, E and run a text editor to see
whether you get clean A/B/C/D/E keystrokes and not A+E or B+E.

Then go to Atari800 and set A, B, C, D, E as the keyboard joystick. If you
still see trigger events, then it becomes interesting.

Otherwise it would seem that qjoypad has troubles with some specific keys
(like left control).

On Fri, 6 Aug 2021 at 16:17, Greg Hall <gre...@ba...> wrote:

> Is there some kind of test app I can use that just checks the input and
> prints what key(s) it thinks are pressed?
>
> On Fri, Aug 6, 2021 at 11:15 AM Greg Hall <gre...@ba...> wrote:
>
>> The thing I can't quite get my head around is that qjoypad works with
>> every other emulator I've tried. As far as not being updated for 2 years,
>> when was the last time x11 changed how input works :)
>>
>> I find it strange that even though I have no mapping of any joystick
>> button to the space key (the key I use for fire), the joystick keeps
>> jumping anyway. If I use the keyboard, I don't have that problem. And auto
>> fire is off.
>>
>> On Fri, Aug 6, 2021 at 3:19 AM Miro Kropáček <mir...@gm...>
>> wrote:
>>
>>> On Fri, 6 Aug 2021 at 02:44, Greg Hall <gre...@ba...> wrote:
>>>
>>>> Hello. I find the emulator works great on Arch Linux with XFCE except
>>>> for one detail: if I map my USB joystick to keys using qjoypad, the
>>>> emulator thinks the fire button is always pressed. So when running Jumpman,
>>>> my guy constantly jumps.
>>>>
>>> To me it looks like a bug in qjoypad (looks quite outdated judging from
>>> its website), I would try another application which takes roughly the same
>>> keyboard input to see what qjoypad really sends. By default the trigger is
>>> mapped to the left control key.
>>>
>>> Oh and of course check whether you don't have 'auto fire' enabled in the
>>> options.
>>>
>>> --
>>> http://mikro.atari.org
>>>
>>>
>>> _______________________________________________
>>> Atari800-users mailing list
>>> Ata...@li...
>>> https://lists.sourceforge.net/lists/listinfo/atari800-users
>>>
>>
>
> _______________________________________________
> Atari800-users mailing list
> Ata...@li...
> https://lists.sourceforge.net/lists/listinfo/atari800-users
>


-- 
http://mikro.atari.org

Re: [Atari800-users] Cannot get my USB joystick to work

[Greg H. <gre...@ba...>]

Is there some kind of test app I can use that just checks the input and
prints what key(s) it thinks are pressed?

On Fri, Aug 6, 2021 at 11:15 AM Greg Hall <gre...@ba...> wrote:

> The thing I can't quite get my head around is that qjoypad works with
> every other emulator I've tried. As far as not being updated for 2 years,
> when was the last time x11 changed how input works :)
>
> I find it strange that even though I have no mapping of any joystick
> button to the space key (the key I use for fire), the joystick keeps
> jumping anyway. If I use the keyboard, I don't have that problem. And auto
> fire is off.
>
> On Fri, Aug 6, 2021 at 3:19 AM Miro Kropáček <mir...@gm...>
> wrote:
>
>> On Fri, 6 Aug 2021 at 02:44, Greg Hall <gre...@ba...> wrote:
>>
>>> Hello. I find the emulator works great on Arch Linux with XFCE except
>>> for one detail: if I map my USB joystick to keys using qjoypad, the
>>> emulator thinks the fire button is always pressed. So when running Jumpman,
>>> my guy constantly jumps.
>>>
>> To me it looks like a bug in qjoypad (looks quite outdated judging from
>> its website), I would try another application which takes roughly the same
>> keyboard input to see what qjoypad really sends. By default the trigger is
>> mapped to the left control key.
>>
>> Oh and of course check whether you don't have 'auto fire' enabled in the
>> options.
>>
>> --
>> http://mikro.atari.org
>>
>>
>> _______________________________________________
>> Atari800-users mailing list
>> Ata...@li...
>> https://lists.sourceforge.net/lists/listinfo/atari800-users
>>
>

Re: [Atari800-users] Cannot get my USB joystick to work

[Greg H. <gre...@ba...>]

The thing I can't quite get my head around is that qjoypad works with every
other emulator I've tried. As far as not being updated for 2 years, when
was the last time x11 changed how input works :)

I find it strange that even though I have no mapping of any joystick button
to the space key (the key I use for fire), the joystick keeps jumping
anyway. If I use the keyboard, I don't have that problem. And auto fire is
off.

On Fri, Aug 6, 2021 at 3:19 AM Miro Kropáček <mir...@gm...>
wrote:

> On Fri, 6 Aug 2021 at 02:44, Greg Hall <gre...@ba...> wrote:
>
>> Hello. I find the emulator works great on Arch Linux with XFCE except for
>> one detail: if I map my USB joystick to keys using qjoypad, the emulator
>> thinks the fire button is always pressed. So when running Jumpman, my guy
>> constantly jumps.
>>
> To me it looks like a bug in qjoypad (looks quite outdated judging from
> its website), I would try another application which takes roughly the same
> keyboard input to see what qjoypad really sends. By default the trigger is
> mapped to the left control key.
>
> Oh and of course check whether you don't have 'auto fire' enabled in the
> options.
>
> --
> http://mikro.atari.org
>
>
> _______________________________________________
> Atari800-users mailing list
> Ata...@li...
> https://lists.sourceforge.net/lists/listinfo/atari800-users
>

Re: [Atari800-users] Cannot get my USB joystick to work

[Miro K. <mir...@gm...>]

On Fri, 6 Aug 2021 at 02:44, Greg Hall <gre...@ba...> wrote:

> Hello. I find the emulator works great on Arch Linux with XFCE except for
> one detail: if I map my USB joystick to keys using qjoypad, the emulator
> thinks the fire button is always pressed. So when running Jumpman, my guy
> constantly jumps.
>
To me it looks like a bug in qjoypad (looks quite outdated judging from its
website), I would try another application which takes roughly the same
keyboard input to see what qjoypad really sends. By default the trigger is
mapped to the left control key.

Oh and of course check whether you don't have 'auto fire' enabled in the
options.

-- 
http://mikro.atari.org

[Atari800-users] Cannot get my USB joystick to work

[Greg H. <gre...@ba...>]

Hello. I find the emulator works great on Arch Linux with XFCE except for
one detail: if I map my USB joystick to keys using qjoypad, the emulator
thinks the fire button is always pressed. So when running Jumpman, my guy
constantly jumps.

I have had no issue using qjoypad this way with any other emulators (eg
mednafen, stella, coolcv, vice64).

My goal is to configure a series of emulators this way, and use my own menu
system with zenity to choose a game, such that I only need a joystick (the
menu system itself has a qjoypad configuration). I can then get a system
running on something like an RPI 4 hooked up to a TV.

I tried some retro distros, and found they were a pain to configure,
couldn't get newer versions to boot on my older rpi, and don't work very
well for systems like an atari 800 or c64 that have a keyboard.

Since I really only need my one joystick to work, I'm happy to
pre-configure all the emulators ahead of time, and a very simple shell
script can select the qjoypad config I need for a given system (and
possibly the individual game) and then run the game.

If I can just solve this one problem, then this emulator will be perfect!

[Atari800-users] Adding a -quiet or -nowarn option

[Rob M. <pla...@gm...>]

Anyone object to me adding a command line argument to suppress all warning
messages? I was thinking of '-quiet' or '-nowarn'; any other ideas for the
argument name?

The purpose of this is that I'm updating the libatari800 target and it
would be nice to limit stdout messages when running as a library. I can
make it a libatari800 option only, hidden behind #defines if you'd rather,
but thought maybe it could be useful in general.

I've got sound support working in libatari800; will submit a pull request
shortly. I finally have a user other than me developing with libatari800,
which is what is prompting the work. The developer of 8bitworkshop.com is
compiling libatari800 to WASM to add native a8 support to his list of
emulators on his web-based emulator/debugger. (Amazing site if you haven't
checked it out before, but the previous a8 support was only through MAME.)

Rob
-- 
Rob McMullen, host of the Player/Missile Podcast at http://playermissile.com
Follow me on Twitter: @atari8bitgames

Re: [Atari800-users] Joystick Compatibility

[Edward S. B. Jr. <edb...@co...>]

I am using the Atari Firebee version, so I am using an original Atari 2600 joystick. I get no response when I use it. If I plug in an Atari TT keyboard and use the mouse port, I do some response, but nothing when I use the joystick port.

Ed

Sent from Mail for Windows 10

From: Petr Stehlík
Sent: Tuesday, July 20, 2021 8:47 AM
To: ata...@li...
Subject: Re: [Atari800-users] Joystick Compatibility

Edward S. Baiz Jr. píše v So 03. 07. 2021 v 09:24 -0400:
> Hello all. Just wondering if the Atari 800 emulator is anywhere near
> to having joystick compatibility yet?

??????

I use the emulator with original Quick Shot II (arguably the best
joystick ever). What do you mean with your question?

Petr






_______________________________________________
Atari800-users mailing list
Ata...@li...
https://lists.sourceforge.net/lists/listinfo/atari800-users

Re: [Atari800-users] Joystick Compatibility

[Petr S. <pst...@so...>]

Edward S. Baiz Jr. píše v So 03. 07. 2021 v 09:24 -0400:
> Hello all. Just wondering if the Atari 800 emulator is anywhere near
> to having joystick compatibility yet?

??????

I use the emulator with original Quick Shot II (arguably the best
joystick ever). What do you mean with your question?

Petr

Re: [Atari800-users] Atari800-users Digest, Vol 111, Issue 3

[Petr S. <pst...@so...>]

Chris Chiesa píše v Čt 08. 07. 2021 v 20:18 -0400:
> > Two obvious choices: either a virtual HW register or an
> > illegal/unused CPU opcode. The virtual register approach is more
> > error prone, I feel, so I'd go for a special CPU opcode.

> I'm not sure I agree that the register approach is "more error-
> prone."  May I ask you to clarify the line of thought that leads you 

that was just a first gut feeling and it was probably wrong. Feel free
to go for the virtual HW register. It'll be easier to use it on Atari
than using a special CPU instruction would be (say calling it from
BASIC, C, Action! or so where using an invalid CPU instruction would be
rather complicated).

Petr

Re: [Atari800-users] Atari800-users Digest, Vol 112, Issue 1

[Chris C. <chr...@gm...>]

On Sat, Jul 3, 2021 at 11:59 AM <
ata...@li...> wrote:

> Send Atari800-users mailing list submissions to
>         ata...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/atari800-users
> or, via email, send a message with subject or body 'help' to
>         ata...@li...
>
> You can reach the person managing the list at
>         ata...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Atari800-users digest..."
>
>
> Today's Topics:
>
>    1. Joystick Compatibility (Edward S. Baiz Jr.)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 3 Jul 2021 09:24:09 -0400
> From: "Edward S. Baiz Jr." <edb...@co...>
> To: "ata...@li..."
>         <ata...@li...>
> Subject: [Atari800-users] Joystick Compatibility
> Message-ID:
>         <mai...@li...
> >
> Content-Type: text/plain; charset="utf-8"
>
> Hello all. Just wondering if the Atari 800 emulator is anywhere near to
> having joystick compatibility yet?
> Using the keyboard is fine, but using a joystick would be better.  Thanks..
>

Ooo, yeah, I'd like to see that, too!  I've puzzled for years over how one
would do this; it seems to require host drivers that recognize a real
joystick, and an API for accessing that information.  Why the heck didn't
atari800 add that functionality *25 years ago?*

As a last resort -- and *also *25 years late! -- I realized that, at any
time in the past few decades, I could have wired a joystick to a few keys
in a spare keyboard, so that manipulating the stick became
hardware-identical to pressing those keys.  (In my brother-in-law's MAME
cabinet I discovered hardware that takes exactly this idea to its logical
extreme: somebody markets a custom device that, under software
configuration, dynamically maps external switch-closures to fake
keypresses!)

Anyway -- I second the request for "real" joystick support, if it can be
done.

Chris

Re: [Atari800-users] Atari800-users Digest, Vol 111, Issue 3

[Chris C. <chr...@gm...>]

On Sat, Jun 26, 2021 at 11:34 AM <
ata...@li...> wrote:

> Date: Sat, 26 Jun 2021 15:38:12 +0200
> From: Petr Stehl?k <pst...@so...>
> Subject: Re: [Atari800-users] "basic" tatget
>
> On Ne, 2021-06-20 at 15:20 +0200, Christian Groessler wrote:
> > For this to work I would need a way to terminate atari800 from within
> > an Atari program. (Maybe also an emulator detection would be nice.)
> >
> > Is something like this already implemented? If not, I would try to
> > implement it. Do you have ideas how the "Atari program" <-->
> > "atari800 emulator" communication should look like?
>
> Two obvious choices: either a virtual HW register or an illegal/unused
> CPU opcode. The virtual register approach is more error prone, I feel,
> so I'd go for a special CPU opcode. I think it would be smart to
> implement something compatible with another emulator as I guess other
> Atari800 emulators implemented similar thing already.
>
> Petr
>

Whoops.  I guess I should read all the *other *responses before offering my
own.  My apologies for wasting bandwidth.

On the other hand, it's good to see that "great minds think alike!" ;-)

I'm not sure I agree that the register approach is "more error-prone."  May
I ask you to clarify the line of thought that leads you to that conclusion?

Oh, and I apologize *again,* if you've *already *given that clarification;
I'm not yet actually following my own advice, above.

Chris

>
>
>
>
>
> ------------------------------
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Atari800-users mailing list
> Ata...@li...
> https://lists.sourceforge.net/lists/listinfo/atari800-users
>
>
> ------------------------------
>
> End of Atari800-users Digest, Vol 111, Issue 3
> **********************************************
>

Re: [Atari800-users] Atari800-users Digest, Vol 111, Issue 2

[Chris C. <chr...@gm...>]

On Sun, Jun 20, 2021 at 12:52 PM <
ata...@li...> wrote:

> Send Atari800-users mailing list submissions to
>         ata...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/atari800-users
> or, via email, send a message with subject or body 'help' to
>         ata...@li...
>
> You can reach the person managing the list at
>         ata...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Atari800-users digest..."
>
>
> Today's Topics:
>
>    1. "basic" tatget (Christian Groessler)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 20 Jun 2021 15:20:43 +0200
> From: Christian Groessler <ch...@gr...>
> To: ata...@li...
> Subject: [Atari800-users] "basic" tatget
> Message-ID: <9b6...@gr...>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi,
>
> the "basic" target, which doesn't use GUI nor termcap/terminfo, just
> stdin and stdout, would be a good candidate to create automated tests
> for CC65.
>
> For this to work I would need a way to terminate atari800 from within an
> Atari program. (Maybe also an emulator detection would be nice.)
>
> Is something like this already implemented? If not, I would try to
> implement it. Do you have ideas how the "Atari program" <--> "atari800
> emulator" communication should look like?
>
> regards,
> chris
>

Interesting ideas.  I can certainly see these being useful.

However, my immediate reaction is that we'd want to be careful not to
implement something that encouraged the writing of software, for the
emulator, that would misbehave too greatly on a physical Atari.  (I
consider backward-compatibility at least as important as forward-...)  Too,
the very idea of an emulator is that software running on it *should not *be
able to detect that it is running on an emulator rather than a physical
machine, so we would need to be very careful, right from the start in the
design/specification phase, to make it work in a way that wouldn't disrupt
existing software.

That said, I do have a couple of ideas.

First, I seem to remember that on the Atari 800 there were / are a number
of high-memory addresses that didn't dereference to anything -- memory or
hardware -- or which, at the very least, simply accessed the *same hardware
*as a "legitimate" register, but at an unofficial/unsupported address.   I
don't remember whether these "went away" in later models (XL, XE, XEGS,
etc.), e.g. perhaps as a consequence of the added ability to switch out the
OS ROM for RAM -- but if any of them remain, to me it would seem an ideal
solution to simply define a pseudo-register at one of those addresses
which, when accessed, performed one or both of the functions you desire.
"Detect Emulator" would depend upon whether, on a real machine, you could
count on the address to return a known value -- or, at least, *one *of a *small
set *of known values -- when read; if so, we would simply arrange for that
address to return a *completely different *value in atari800.
Unfortunately, this probably eliminates "unofficial addresses that access
the same hardware," because *those wouldn't *deliver a predictable value on
a physical machine.  I think the concept bears consideration, though, if a
suitable do-nothing address can be identified.  "Terminate Emulation" would
then also be quite simple: instead of *reading *the new pseudo-register,
*write *it.  Boom, done.  This register would need to be at an address that
didn't get bank-switched out of the address space, or superseded by
plugging in a device such as e.g. the Black Box.

Second, if no suitable address can be found, perhaps a currently unused
byte value or two could be defined as emulator-specific CPU instructions
which performed these operations.  One of them would be defined as "loads
accumulator with <value> if running under emulation," and another to "exit
emulation."  The problem, though, is that you have to consider what those
"instructions" do when running on a *real *machine -- and arrange for *that
*to happen, even under emulation, in case some software, somewhere, relies
on it.  The obvious solution here is to make the behavior of these
instructions configurable in the emulator.

If no suitable *unused *byte values can be found, or we want to avoid the
slippery slope of being too cavalier about hijacking bytes, perhaps *existing
*instructions can be pressed into service.  Theory suggests that there
"surely must" be a Halt instruction in the 6502; if so, and if it truly
stops the processor from executing any further instructions (including
servicing interrupts), it is the perfect candidate for (when configured)
"Exit Emulator."  "Detect Emulator" is trickier.  The only way I can think
of would be to add a new side effect to some existing instruction.  As long
as we make the behavior configurable, though, we might be able to pull it
off.  Let's say we pick the NOP instruction, and have it (when the behavior
is enabled) set a couple of bits, in the Status register, that can *never
both *be set at the same time on a physical machine, and which of course
the NOP instruction would ordinarily *not affect.*  You could push the
Status register onto the stack, execute a NOP, then compare the pushed
value of the Status register with its previous value.  (Restoring the
original value of the Status register, if needed / desired, is left as an
exercise for the reader!)

Just some thoughts.

Chris

Re: [Atari800-users] Atari800-users Digest, Vol 111, Issue 1

[Chris C. <chr...@gm...>]

On Sat, Jun 19, 2021 at 1:50 PM <
ata...@li...> wrote:

> Send Atari800-users mailing list submissions to
>         ata...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/atari800-users
>
> Today's Topics:
>
>    1. this is interesting (Petr Stehl?k)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 18 Jun 2021 20:17:59 +0200
> From: Petr Stehl?k <pst...@so...>
> To: ata...@li...
> Subject: [Atari800-users] this is interesting
> Message-ID:
>         <b2c...@so...>
> Content-Type: text/plain; charset="UTF-8"
>
> Check the github issue and if you're a developer and/or Atari800 port
> maintainer then feel free to comment there.
>
> https://github.com/atari800/atari800/issues/134
>
> Petr
>

I'm a software developer "from way back" -- by which I mean, in part, that
I'm *waaaaaay behind *on today's tools, e.g. github, whatever compiler(s)
you folks are using to build Atari800 from scratch, etc. -- but late last
fall I expressed interest in getting involved "if I got the Windows 10 PC
I'm expecting, for Christmas."  Well, I got the PC, but I haven't yet
gotten around to looking at the source code I somehow managed to download
last fall, let alone figuring out how to get anything "current" from github
(or anywhere else).

So I also don't know how to *comment *on github, hence I'll have to do it
*here.*

If I correctly understand the discussion at the link above, it seems that a
plug-in-based architecture is being proposed, though it's not entirely
clear to me.

In general I support this idea.  I have a medium-long personal list of
things I'd like to see supported in/by atari800, but which it strikes me as
inefficient or clumsy to include in the body of atari800 itself.  A
modular architecture, using plug-ins or the equivalent, seems to be the
right way to go.  This would also allow separation of *development *of
peripheral-device emulation from atari800 mainline development, so that
each could proceed at its own pace without unduly affecting, e.g. requiring
a rebuild, of any other.

The prerequisites for this would be to a) design the modular architecture,
b) define a standard API (and/or ABI) (or two -- perhaps one at SIO level
and another more abstract; certainly I can imagine it being useful for each
plug-in to supply its own configuration menu) for communication between
atari800 and a peripheral emulator, and c) extract the *currently *embedded
device emulations (disk drives, modem, printer) from atari800 and make them
plug-ins.  (The currently embedded devices could be set as *default *plug-ins,
to preserve existing configuration menus and hotkeys -- or could be left in
place in atari800 but with the ability for plugins to *override *them at
various levels (e.g. either in the Disk Management menu or in another,
auxiliary, menu)...)

I suppose there could be arguments in the other direction, in favor of
preserving the current "monolithic" architecture, so feel free to disagree
with me.

Also feel free to inform me of how to respond properly *on github.*  Thanks
in advance for that.


Chris

Re: [Atari800-users] Joystick Compatibility

[Edward B. <edb...@co...>]

Hello,

I am using the Atari Firebee version. Joystick results in action, but the keyboard works fine. I tried it with a USB keyboard and TT keyboard that I bought from best Electronics.  If I hook the Joystick to the Mouse port on the TT keyboard, I do get some movement.

Ed Baiz jr.

> On 07/06/2021 4:21 AM Bill Kendrick <nb...@so...> wrote:
> 
>  
> On Sat, Jul 03, 2021 at 09:24:09AM -0400, Edward S. Baiz Jr. wrote:
> > Hello all. Just wondering if the Atari 800 emulator is anywhere near to having joystick compatibility yet?
> > Using the keyboard is fine, but using a joystick would be better.  Thanks..
> 
> Erm... it does?! :) I've certainly used it in the past with a real
> Atari joystick via Stelladapter, as well as a PlayStation controller
> via some PSX->USB adapter.  Admittedly, that was a while ago now.
> 
> 
> -- 
> -bill!
> Sent from my computer
> 
> 
> 
> 
> _______________________________________________
> Atari800-users mailing list
> Ata...@li...
> https://lists.sourceforge.net/lists/listinfo/atari800-users

Re: [Atari800-users] Joystick Compatibility

[Bill K. <nb...@so...>]

On Sat, Jul 03, 2021 at 09:24:09AM -0400, Edward S. Baiz Jr. wrote:
> Hello all. Just wondering if the Atari 800 emulator is anywhere near to having joystick compatibility yet?
> Using the keyboard is fine, but using a joystick would be better.  Thanks..

Erm... it does?! :) I've certainly used it in the past with a real
Atari joystick via Stelladapter, as well as a PlayStation controller
via some PSX->USB adapter.  Admittedly, that was a while ago now.


-- 
-bill!
Sent from my computer

[Atari800-users] Joystick Compatibility

[Edward S. B. Jr. <edb...@co...>]

Hello all. Just wondering if the Atari 800 emulator is anywhere near to having joystick compatibility yet?
Using the keyboard is fine, but using a joystick would be better.  Thanks..

Ed Baiz Jr.

Sent from Mail for Windows 10

Re: [Atari800-users] "basic" tatget

[Peter D. <Pet...@we...>]

Hi,
 
how about intercept the jump to the ROM coldstart vector (e477), like we're intercepting SIO.
And maybe also a virtual CIO device to control the Emulator.
The latter would be the best option I think.
 
Regards, Peter.
 
 

Gesendet: Samstag, 26. Juni 2021 um 17:34 Uhr
Von: ata...@li...
An: ata...@li...
Betreff: Atari800-users Digest, Vol 111, Issue 3
Send Atari800-users mailing list submissions to
ata...@li...

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/atari800-users
or, via email, send a message with subject or body 'help' to
ata...@li...

You can reach the person managing the list at
ata...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Atari800-users digest..."


Today's Topics:

1. Re: "basic" tatget (Petr Stehl?k)


----------------------------------------------------------------------

Message: 1
Date: Sat, 26 Jun 2021 15:38:12 +0200
From: Petr Stehl?k <pst...@so...>
To: ata...@li...
Subject: Re: [Atari800-users] "basic" tatget
Message-ID:
<1d9...@so...>
Content-Type: text/plain; charset="UTF-8"

On Ne, 2021-06-20 at 15:20 +0200, Christian Groessler wrote:
> For this to work I would need a way to terminate atari800 from within
> an Atari program. (Maybe also an emulator detection would be nice.)
>
> Is something like this already implemented? If not, I would try to
> implement it. Do you have ideas how the "Atari program" <-->
> "atari800 emulator" communication should look like?

Two obvious choices: either a virtual HW register or an illegal/unused
CPU opcode. The virtual register approach is more error prone, I feel,
so I'd go for a special CPU opcode. I think it would be smart to
implement something compatible with another emulator as I guess other
Atari800 emulators implemented similar thing already.

Petr





------------------------------



------------------------------

Subject: Digest Footer

_______________________________________________
Atari800-users mailing list
Ata...@li...
https://lists.sourceforge.net/lists/listinfo/atari800-users[https://lists.sourceforge.net/lists/listinfo/atari800-users]


------------------------------

End of Atari800-users Digest, Vol 111, Issue 3
**********************************************

Re: [Atari800-users] "basic" tatget

[Peter D. <Pet...@we...>]

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi,</div>

<div>&nbsp;</div>

<div>how about intercept the jump to the ROM coldstart vector (e477), like we&#39;re intercepting SIO.</div>

<div>Or maybe also a virtual CIO device to control the Emulator.</div>

<div>&nbsp;</div>

<div>Regards, Peter.</div>

<div>&nbsp;
<div>&nbsp;
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b>&nbsp;Samstag, 26. Juni 2021 um 17:34 Uhr<br/>
<b>Von:</b>&nbsp;ata...@li...<br/>
<b>An:</b>&nbsp;ata...@li...<br/>
<b>Betreff:</b>&nbsp;Atari800-users Digest, Vol 111, Issue 3</div>

<div name="quoted-content">Send Atari800-users mailing list submissions to<br/>
ata...@li...<br/>
<br/>
To subscribe or unsubscribe via the World Wide Web, visit<br/>
<a href="https://lists.sourceforge.net/lists/listinfo/atari800-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/atari800-users</a><br/>
or, via email, send a message with subject or body &#39;help&#39; to<br/>
ata...@li...<br/>
<br/>
You can reach the person managing the list at<br/>
ata...@li...<br/>
<br/>
When replying, please edit your Subject line so it is more specific<br/>
than &quot;Re: Contents of Atari800-users digest...&quot;<br/>
<br/>
<br/>
Today&#39;s Topics:<br/>
<br/>
1. Re: &quot;basic&quot; tatget (Petr Stehl?k)<br/>
<br/>
<br/>
----------------------------------------------------------------------<br/>
<br/>
Message: 1<br/>
Date: Sat, 26 Jun 2021 15:38:12 +0200<br/>
From: Petr Stehl?k &lt;pst...@so...&gt;<br/>
To: ata...@li...<br/>
Subject: Re: [Atari800-users] &quot;basic&quot; tatget<br/>
Message-ID:<br/>
&lt;1d9...@so...&gt;<br/>
Content-Type: text/plain; charset=&quot;UTF-8&quot;<br/>
<br/>
On Ne, 2021-06-20 at 15:20 +0200, Christian Groessler wrote:<br/>
&gt; For this to work I would need a way to terminate atari800 from within<br/>
&gt; an Atari program. (Maybe also an emulator detection would be nice.)<br/>
&gt;<br/>
&gt; Is something like this already implemented? If not, I would try to<br/>
&gt; implement it. Do you have ideas how the &quot;Atari program&quot; &lt;--&gt;<br/>
&gt; &quot;atari800 emulator&quot; communication should look like?<br/>
<br/>
Two obvious choices: either a virtual HW register or an illegal/unused<br/>
CPU opcode. The virtual register approach is more error prone, I feel,<br/>
so I&#39;d go for a special CPU opcode. I think it would be smart to<br/>
implement something compatible with another emulator as I guess other<br/>
Atari800 emulators implemented similar thing already.<br/>
<br/>
Petr<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
------------------------------<br/>
<br/>
<br/>
<br/>
------------------------------<br/>
<br/>
Subject: Digest Footer<br/>
<br/>
_______________________________________________<br/>
Atari800-users mailing list<br/>
Ata...@li...<br/>
<a href="https://lists.sourceforge.net/lists/listinfo/atari800-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/atari800-users</a><br/>
<br/>
<br/>
------------------------------<br/>
<br/>
End of Atari800-users Digest, Vol 111, Issue 3<br/>
**********************************************</div>
</div>
</div>
</div></div></body></html>

Re: [Atari800-users] "basic" tatget

[Petr S. <pst...@so...>]

On Ne, 2021-06-20 at 15:20 +0200, Christian Groessler wrote:
> For this to work I would need a way to terminate atari800 from within
> an Atari program. (Maybe also an emulator detection would be nice.)
> 
> Is something like this already implemented? If not, I would try to 
> implement it. Do you have ideas how the "Atari program" <-->
> "atari800 emulator" communication should look like?

Two obvious choices: either a virtual HW register or an illegal/unused
CPU opcode. The virtual register approach is more error prone, I feel,
so I'd go for a special CPU opcode. I think it would be smart to
implement something compatible with another emulator as I guess other
Atari800 emulators implemented similar thing already.

Petr

[Atari800-users] "basic" tatget

[Christian G. <ch...@gr...>]

Hi,

the "basic" target, which doesn't use GUI nor termcap/terminfo, just 
stdin and stdout, would be a good candidate to create automated tests 
for CC65.

For this to work I would need a way to terminate atari800 from within an 
Atari program. (Maybe also an emulator detection would be nice.)

Is something like this already implemented? If not, I would try to 
implement it. Do you have ideas how the "Atari program" <--> "atari800 
emulator" communication should look like?

regards,
chris

[Atari800-users] this is interesting

[Petr S. <pst...@so...>]

Check the github issue and if you're a developer and/or Atari800 port
maintainer then feel free to comment there.

https://github.com/atari800/atari800/issues/134

Petr