atari800-users Mailing List for Atari800 (Page 9)
Brought to you by:
joy
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(97) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(28) |
Feb
(14) |
Mar
(26) |
Apr
(77) |
May
(5) |
Jun
(20) |
Jul
(51) |
Aug
(48) |
Sep
(23) |
Oct
(10) |
Nov
(21) |
Dec
(116) |
2003 |
Jan
(94) |
Feb
(105) |
Mar
(31) |
Apr
(31) |
May
(13) |
Jun
(14) |
Jul
(12) |
Aug
(26) |
Sep
(43) |
Oct
(21) |
Nov
(5) |
Dec
(17) |
2004 |
Jan
(12) |
Feb
(16) |
Mar
|
Apr
(3) |
May
(13) |
Jun
(9) |
Jul
(9) |
Aug
(10) |
Sep
(6) |
Oct
|
Nov
(13) |
Dec
(9) |
2005 |
Jan
(9) |
Feb
(3) |
Mar
(12) |
Apr
(3) |
May
(11) |
Jun
(5) |
Jul
(15) |
Aug
(25) |
Sep
(68) |
Oct
(44) |
Nov
(114) |
Dec
(83) |
2006 |
Jan
(165) |
Feb
(94) |
Mar
(58) |
Apr
(41) |
May
(28) |
Jun
(25) |
Jul
(1) |
Aug
|
Sep
|
Oct
(15) |
Nov
(17) |
Dec
(21) |
2007 |
Jan
(1) |
Feb
(3) |
Mar
|
Apr
(10) |
May
(26) |
Jun
(2) |
Jul
(14) |
Aug
|
Sep
(8) |
Oct
(1) |
Nov
(7) |
Dec
(1) |
2008 |
Jan
(3) |
Feb
(7) |
Mar
(18) |
Apr
(45) |
May
(44) |
Jun
(14) |
Jul
(3) |
Aug
(49) |
Sep
(14) |
Oct
(2) |
Nov
(9) |
Dec
(2) |
2009 |
Jan
(9) |
Feb
(12) |
Mar
(69) |
Apr
(4) |
May
(2) |
Jun
(20) |
Jul
|
Aug
(4) |
Sep
(18) |
Oct
(7) |
Nov
(4) |
Dec
(5) |
2010 |
Jan
(98) |
Feb
(12) |
Mar
(6) |
Apr
(40) |
May
(22) |
Jun
(3) |
Jul
(22) |
Aug
(2) |
Sep
(3) |
Oct
(16) |
Nov
(14) |
Dec
(5) |
2011 |
Jan
(6) |
Feb
(2) |
Mar
(7) |
Apr
(52) |
May
(6) |
Jun
(11) |
Jul
(15) |
Aug
(17) |
Sep
(15) |
Oct
|
Nov
(1) |
Dec
(2) |
2012 |
Jan
|
Feb
|
Mar
(17) |
Apr
(2) |
May
(3) |
Jun
|
Jul
(4) |
Aug
|
Sep
(2) |
Oct
(19) |
Nov
|
Dec
|
2013 |
Jan
(7) |
Feb
(7) |
Mar
(39) |
Apr
(11) |
May
(5) |
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
(6) |
Oct
(9) |
Nov
(2) |
Dec
(2) |
2014 |
Jan
(19) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(8) |
Jun
(1) |
Jul
|
Aug
(3) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(4) |
2015 |
Jan
|
Feb
(4) |
Mar
(20) |
Apr
(15) |
May
(5) |
Jun
(29) |
Jul
(2) |
Aug
|
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(5) |
2016 |
Jan
(1) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
2017 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(9) |
Aug
(23) |
Sep
(21) |
Oct
(10) |
Nov
(2) |
Dec
|
2018 |
Jan
(1) |
Feb
|
Mar
(11) |
Apr
(28) |
May
(74) |
Jun
(30) |
Jul
(8) |
Aug
(1) |
Sep
|
Oct
(32) |
Nov
(4) |
Dec
(3) |
2019 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
(5) |
May
(1) |
Jun
(10) |
Jul
(5) |
Aug
|
Sep
(8) |
Oct
(7) |
Nov
(6) |
Dec
(3) |
2020 |
Jan
|
Feb
(7) |
Mar
|
Apr
(9) |
May
(5) |
Jun
|
Jul
|
Aug
(14) |
Sep
(9) |
Oct
(6) |
Nov
(3) |
Dec
(3) |
2021 |
Jan
|
Feb
(18) |
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(11) |
Aug
(17) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
(3) |
Jun
(4) |
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
2023 |
Jan
(5) |
Feb
(1) |
Mar
(17) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2024 |
Jan
|
Feb
|
Mar
|
Apr
(24) |
May
(18) |
Jun
(3) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(4) |
2025 |
Jan
(2) |
Feb
|
Mar
(3) |
Apr
(2) |
May
|
Jun
(5) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Edward S. B. Jr. <edb...@co...> - 2020-08-02 14:42:11
|
Just wondering if there was an upgrade for the Atari800 emulator (Firebee version) that has the actual joystick usage fixed? Sent from Mail for Windows 10 |
From: Hemil R. <hem...@gm...> - 2020-08-02 14:28:26
|
I installed successfully. Thanks On Sun 2 Aug, 2020, 6:31 PM Petr Stehlík, <pst...@so...> wrote: > On Ne, 2020-08-02 at 15:01 +0530, Hemil Ruparel wrote: > > Hey guys! I am Hemil Ruparel. I am a CS student. I didnt quite get > > how to install the emulator. Can someone guide me on how to install > > emulator on my ubuntu? > > Have you tried this: > > sudo apt install atari800 > > Or perhaps starting the Software Center and searching for Atari800 ? > > Petr > > > > > > > _______________________________________________ > Atari800-users mailing list > Ata...@li... > https://lists.sourceforge.net/lists/listinfo/atari800-users > |
From: Petr S. <pst...@so...> - 2020-08-02 13:00:53
|
On Ne, 2020-08-02 at 15:01 +0530, Hemil Ruparel wrote: > Hey guys! I am Hemil Ruparel. I am a CS student. I didnt quite get > how to install the emulator. Can someone guide me on how to install > emulator on my ubuntu? Have you tried this: sudo apt install atari800 Or perhaps starting the Software Center and searching for Atari800 ? Petr |
From: Hemil R. <hem...@gm...> - 2020-08-02 09:31:33
|
Hey guys! I am Hemil Ruparel. I am a CS student. I didnt quite get how to install the emulator. Can someone guide me on how to install emulator on my ubuntu? Thanks a lot |
From: Edward S. B. Jr. <edb...@co...> - 2020-05-18 09:52:48
|
Well that is good. At least I know now. Will keep trying though. Thanks for the reply. Sent from Mail for Windows 10 From: Miro Kropáček Sent: Sunday, May 17, 2020 1:42 PM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation I have given it a try - and yes, it doesn't work. :) I tried both XBIOS (default for gem) and IKBD drivers in SDL, nope. Good news is that at least direct joystick usage (in native Falcon binary) works fine. It can be a bug in Atari SDL or in Atari800. Definitely needs more investigation. On Sat, 16 May 2020 at 13:47, Edward S. Baiz Jr. <edb...@co...> wrote: Oops. In my message I meant that I could NOT get the joystick to work. Will keep trying though. Sent from Mail for Windows 10 From: Edward S. Baiz Jr. Sent: Saturday, May 16, 2020 12:02 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation Hello Miro. Sorry it took me so long to answer. I found out my Mint Ext2 Partition was corrupted so I had to re-installed it again by using a TAR backup file. I had a lot of trouble getting the TAR program to work on the Firebee. I would start the restore and the TAR program would just stop after a while and would sometimes write to the partition and make it unusable. I would then have to re-format the partition using Mini Tool Wizard on the PC. After many failed attempts try to get the Firebee restore to work, I restored the backup on the Pandora which is a mini Linux pocket computer. I then installed the newest version of SDL and used the SDL environmental variables you listed. I still could get the joystick to work, but I did not try all the variables. Or do I need to configure SDL? Sent from Mail for Windows 10 From: Edward S. Baiz Jr. Sent: Tuesday, April 28, 2020 6:24 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation No I did not, but I will try it tomorrow and let you know. Have to go to work now. Thanks for the reply. Ed Sent from Mail for Windows 10 From: Miro Kropáček Sent: Tuesday, April 28, 2020 5:52 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation Did you try to change some of the SDL environment variables as I have recommended here: http://atari-forum.com/viewtopic.php?f=92&t=38737&p=400130#p400155 ? On Tue, 28 Apr 2020 at 11:50, Edward S. Baiz Jr. <edb...@co...> wrote: Yes they do. I downloaded Xenon2 that was re-done for the Friebee and they joystick worked fine. Ed Sent from Mail for Windows 10 From: Petr Stehlík Sent: Tuesday, April 28, 2020 4:18 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation Edward S. Baiz Jr. píše v Po 27. 04. 2020 v 14:43 -0400: > fine. The Firebee has a port that the TT and MegaSTe keyboards > attach to. I have a TT keyboard that I purchased from Best > Electronics. It has two Joystick ports do the joystick ports work in other ST games and/or in say GFA Basic's simple code for reading Atari joysticks? 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 -- http://mikro.atari.org _______________________________________________ Atari800-users mailing list Ata...@li... https://lists.sourceforge.net/lists/listinfo/atari800-users -- http://mikro.atari.org |
From: Miro K. <mir...@gm...> - 2020-05-17 17:42:42
|
I have given it a try - and yes, it doesn't work. :) I tried both XBIOS (default for gem) and IKBD drivers in SDL, nope. Good news is that at least direct joystick usage (in native Falcon binary) works fine. It can be a bug in Atari SDL or in Atari800. Definitely needs more investigation. On Sat, 16 May 2020 at 13:47, Edward S. Baiz Jr. <edb...@co...> wrote: > Oops. In my message I meant that I could NOT get the joystick to work. > Will keep trying though. > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows 10 > > > > *From: *Edward S. Baiz Jr. <edb...@co...> > *Sent: *Saturday, May 16, 2020 12:02 AM > *To: *ata...@li... > *Subject: *Re: [Atari800-users] Joystick emulation > > > > Hello Miro. > > Sorry it took me so long to answer. I found out my Mint Ext2 Partition was > corrupted so I had to re-installed it again by using a TAR backup file. > I had a lot of trouble getting the TAR program to work on the Firebee. I > would start the restore and the TAR program would just stop after a while > and would sometimes write to the partition and make it unusable. I would > then have to re-format the partition using Mini Tool Wizard on the PC. > After many failed attempts try to get the Firebee restore to work, I > restored the backup on the Pandora which is a mini Linux pocket computer. > > > > I then installed the newest version of SDL and used the SDL environmental > variables you listed. I still could get the joystick to work, but I did not > try all the variables. Or do I need to configure SDL? > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows 10 > > > > *From: *Edward S. Baiz Jr. <edb...@co...> > *Sent: *Tuesday, April 28, 2020 6:24 AM > *To: *ata...@li... > *Subject: *Re: [Atari800-users] Joystick emulation > > > > No I did not, but I will try it tomorrow and let you know. Have to go to > work now. Thanks for the reply. > > > > Ed > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows 10 > > > > *From: *Miro Kropáček <mir...@gm...> > *Sent: *Tuesday, April 28, 2020 5:52 AM > *To: *ata...@li... > *Subject: *Re: [Atari800-users] Joystick emulation > > > > Did you try to change some of the SDL environment variables as I have > recommended here: > http://atari-forum.com/viewtopic.php?f=92&t=38737&p=400130#p400155 ? > > > > On Tue, 28 Apr 2020 at 11:50, Edward S. Baiz Jr. <edb...@co...> > wrote: > > Yes they do. I downloaded Xenon2 that was re-done for the Friebee and they > joystick worked fine. > > > > Ed > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows 10 > > > > *From: *Petr Stehlík <pst...@so...> > *Sent: *Tuesday, April 28, 2020 4:18 AM > *To: *ata...@li... > *Subject: *Re: [Atari800-users] Joystick emulation > > > > Edward S. Baiz Jr. píše v Po 27. 04. 2020 v 14:43 -0400: > > > fine. The Firebee has a port that the TT and MegaSTe keyboards > > > attach to. I have a TT keyboard that I purchased from Best > > > Electronics. It has two Joystick ports > > > > do the joystick ports work in other ST games and/or in say GFA Basic's > > simple code for reading Atari joysticks? > > > > 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 > > > > > -- > > http://mikro.atari.org > > > > > > > > > _______________________________________________ > Atari800-users mailing list > Ata...@li... > https://lists.sourceforge.net/lists/listinfo/atari800-users > -- http://mikro.atari.org |
From: Edward S. B. Jr. <edb...@co...> - 2020-05-16 11:47:16
|
Oops. In my message I meant that I could NOT get the joystick to work. Will keep trying though. Sent from Mail for Windows 10 From: Edward S. Baiz Jr. Sent: Saturday, May 16, 2020 12:02 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation Hello Miro. Sorry it took me so long to answer. I found out my Mint Ext2 Partition was corrupted so I had to re-installed it again by using a TAR backup file. I had a lot of trouble getting the TAR program to work on the Firebee. I would start the restore and the TAR program would just stop after a while and would sometimes write to the partition and make it unusable. I would then have to re-format the partition using Mini Tool Wizard on the PC. After many failed attempts try to get the Firebee restore to work, I restored the backup on the Pandora which is a mini Linux pocket computer. I then installed the newest version of SDL and used the SDL environmental variables you listed. I still could get the joystick to work, but I did not try all the variables. Or do I need to configure SDL? Sent from Mail for Windows 10 From: Edward S. Baiz Jr. Sent: Tuesday, April 28, 2020 6:24 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation No I did not, but I will try it tomorrow and let you know. Have to go to work now. Thanks for the reply. Ed Sent from Mail for Windows 10 From: Miro Kropáček Sent: Tuesday, April 28, 2020 5:52 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation Did you try to change some of the SDL environment variables as I have recommended here: http://atari-forum.com/viewtopic.php?f=92&t=38737&p=400130#p400155 ? On Tue, 28 Apr 2020 at 11:50, Edward S. Baiz Jr. <edb...@co...> wrote: Yes they do. I downloaded Xenon2 that was re-done for the Friebee and they joystick worked fine. Ed Sent from Mail for Windows 10 From: Petr Stehlík Sent: Tuesday, April 28, 2020 4:18 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation Edward S. Baiz Jr. píše v Po 27. 04. 2020 v 14:43 -0400: > fine. The Firebee has a port that the TT and MegaSTe keyboards > attach to. I have a TT keyboard that I purchased from Best > Electronics. It has two Joystick ports do the joystick ports work in other ST games and/or in say GFA Basic's simple code for reading Atari joysticks? 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 -- http://mikro.atari.org |
From: Edward S. B. Jr. <edb...@co...> - 2020-05-16 04:02:07
|
Hello Miro. Sorry it took me so long to answer. I found out my Mint Ext2 Partition was corrupted so I had to re-installed it again by using a TAR backup file. I had a lot of trouble getting the TAR program to work on the Firebee. I would start the restore and the TAR program would just stop after a while and would sometimes write to the partition and make it unusable. I would then have to re-format the partition using Mini Tool Wizard on the PC. After many failed attempts try to get the Firebee restore to work, I restored the backup on the Pandora which is a mini Linux pocket computer. I then installed the newest version of SDL and used the SDL environmental variables you listed. I still could get the joystick to work, but I did not try all the variables. Or do I need to configure SDL? Sent from Mail for Windows 10 From: Edward S. Baiz Jr. Sent: Tuesday, April 28, 2020 6:24 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation No I did not, but I will try it tomorrow and let you know. Have to go to work now. Thanks for the reply. Ed Sent from Mail for Windows 10 From: Miro Kropáček Sent: Tuesday, April 28, 2020 5:52 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation Did you try to change some of the SDL environment variables as I have recommended here: http://atari-forum.com/viewtopic.php?f=92&t=38737&p=400130#p400155 ? On Tue, 28 Apr 2020 at 11:50, Edward S. Baiz Jr. <edb...@co...> wrote: Yes they do. I downloaded Xenon2 that was re-done for the Friebee and they joystick worked fine. Ed Sent from Mail for Windows 10 From: Petr Stehlík Sent: Tuesday, April 28, 2020 4:18 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation Edward S. Baiz Jr. píše v Po 27. 04. 2020 v 14:43 -0400: > fine. The Firebee has a port that the TT and MegaSTe keyboards > attach to. I have a TT keyboard that I purchased from Best > Electronics. It has two Joystick ports do the joystick ports work in other ST games and/or in say GFA Basic's simple code for reading Atari joysticks? 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 -- http://mikro.atari.org |
From: Petr S. <pst...@so...> - 2020-05-05 08:35:52
|
Let me just post it here, maybe it'll be useful to someone in the future: https://github.com/cnlohr/rawdrawandroid https://www.youtube.com/watch?v=Cz_LvaN36Ag |
From: Edward B. <edb...@co...> - 2020-04-29 20:22:08
|
> Hello > I thought I installed SDL, but it looks like I did not so I will have to download it and install it. > On April 28, 2020 at 5:51 AM Miro Kropáček <mir...@gm...> wrote: > Did you try to change some of the SDL environment variables as I have recommended here: http://atari-forum.com/viewtopic.php?f=92&t=38737&p=400130#p400155 ? > > On Tue, 28 Apr 2020 at 11:50, Edward S. Baiz Jr. < edb...@co... mailto:edb...@co... > wrote: > > > > > > Yes they do. I downloaded Xenon2 that was re-done for the Friebee and they joystick worked fine. > > > > > > > > Ed > > > > > > > > Sent from Mail https://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10 > > > > > > > > From: Petr Stehlík mailto:pst...@so... > > Sent: Tuesday, April 28, 2020 4:18 AM > > To: ata...@li... mailto:ata...@li... > > Subject: Re: [Atari800-users] Joystick emulation > > > > > > > > Edward S. Baiz Jr. píše v Po 27. 04. 2020 v 14:43 -0400: > > > > > fine. The Firebee has a port that the TT and MegaSTe keyboards > > > > > attach to. I have a TT keyboard that I purchased from Best > > > > > Electronics. It has two Joystick ports > > > > > > > > do the joystick ports work in other ST games and/or in say GFA Basic's > > > > simple code for reading Atari joysticks? > > > > > > > > Petr > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Atari800-users mailing list > > > > Ata...@li... mailto:Ata...@li... > > > > https://lists.sourceforge.net/lists/listinfo/atari800-users > > > > > > > > > > > > _______________________________________________ > > Atari800-users mailing list > > Ata...@li... mailto:Ata...@li... > > https://lists.sourceforge.net/lists/listinfo/atari800-users > > > > > > > -- > http://mikro.atari.org > > > _______________________________________________ > Atari800-users mailing list > Ata...@li... > https://lists.sourceforge.net/lists/listinfo/atari800-users > |
From: Edward S. B. Jr. <edb...@co...> - 2020-04-28 10:23:59
|
No I did not, but I will try it tomorrow and let you know. Have to go to work now. Thanks for the reply. Ed Sent from Mail for Windows 10 From: Miro Kropáček Sent: Tuesday, April 28, 2020 5:52 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation Did you try to change some of the SDL environment variables as I have recommended here: http://atari-forum.com/viewtopic.php?f=92&t=38737&p=400130#p400155 ? On Tue, 28 Apr 2020 at 11:50, Edward S. Baiz Jr. <edb...@co...> wrote: Yes they do. I downloaded Xenon2 that was re-done for the Friebee and they joystick worked fine. Ed Sent from Mail for Windows 10 From: Petr Stehlík Sent: Tuesday, April 28, 2020 4:18 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation Edward S. Baiz Jr. píše v Po 27. 04. 2020 v 14:43 -0400: > fine. The Firebee has a port that the TT and MegaSTe keyboards > attach to. I have a TT keyboard that I purchased from Best > Electronics. It has two Joystick ports do the joystick ports work in other ST games and/or in say GFA Basic's simple code for reading Atari joysticks? 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 -- http://mikro.atari.org |
From: Miro K. <mir...@gm...> - 2020-04-28 09:51:53
|
Did you try to change some of the SDL environment variables as I have recommended here: http://atari-forum.com/viewtopic.php?f=92&t=38737&p=400130#p400155 ? On Tue, 28 Apr 2020 at 11:50, Edward S. Baiz Jr. <edb...@co...> wrote: > Yes they do. I downloaded Xenon2 that was re-done for the Friebee and they > joystick worked fine. > > > > Ed > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows 10 > > > > *From: *Petr Stehlík <pst...@so...> > *Sent: *Tuesday, April 28, 2020 4:18 AM > *To: *ata...@li... > *Subject: *Re: [Atari800-users] Joystick emulation > > > > Edward S. Baiz Jr. píše v Po 27. 04. 2020 v 14:43 -0400: > > > fine. The Firebee has a port that the TT and MegaSTe keyboards > > > attach to. I have a TT keyboard that I purchased from Best > > > Electronics. It has two Joystick ports > > > > do the joystick ports work in other ST games and/or in say GFA Basic's > > simple code for reading Atari joysticks? > > > > 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 > -- http://mikro.atari.org |
From: Edward S. B. Jr. <edb...@co...> - 2020-04-28 09:49:20
|
Yes they do. I downloaded Xenon2 that was re-done for the Friebee and they joystick worked fine. Ed Sent from Mail for Windows 10 From: Petr Stehlík Sent: Tuesday, April 28, 2020 4:18 AM To: ata...@li... Subject: Re: [Atari800-users] Joystick emulation Edward S. Baiz Jr. píše v Po 27. 04. 2020 v 14:43 -0400: > fine. The Firebee has a port that the TT and MegaSTe keyboards > attach to. I have a TT keyboard that I purchased from Best > Electronics. It has two Joystick ports do the joystick ports work in other ST games and/or in say GFA Basic's simple code for reading Atari joysticks? Petr _______________________________________________ Atari800-users mailing list Ata...@li... https://lists.sourceforge.net/lists/listinfo/atari800-users |
From: Petr S. <pst...@so...> - 2020-04-28 08:18:01
|
Edward S. Baiz Jr. píše v Po 27. 04. 2020 v 14:43 -0400: > fine. The Firebee has a port that the TT and MegaSTe keyboards > attach to. I have a TT keyboard that I purchased from Best > Electronics. It has two Joystick ports do the joystick ports work in other ST games and/or in say GFA Basic's simple code for reading Atari joysticks? Petr |
From: Edward S. B. Jr. <edb...@co...> - 2020-04-27 18:43:24
|
Hello , My name is Ed Baiz Jr. I go by the n9ickname Gamer. I own a lot of Atari computer and now I use the Falcon and Firebee. Am using the Atari800 for the Firebee and I am surprised just how good it is. I am having a good time with it. Right now, the only thing I cannot get to work is the real joystick emulation. The keyboard Joystick works just fine. The Firebee has a port that the TT and MegaSTe keyboards attach to. I have a TT keyboard that I purchased from Best Electronics. It has two Joystick ports, one which can accommodate an Atari mouse. I get nothing when I set the real Joystick emulation, but I do get some movement with the Joystick when I set the mouse option and set it to use a joystick. My question is, does the Firebee version of this program not as yet have the real joystick option activated. If it does, just how do I go about activating it? Thanks… Ed Baiz Jr. (Gamer) Sent from Mail for Windows 10 |
From: Petr S. <pst...@so...> - 2020-04-20 08:34:50
|
Jerzy Kut píše v So 18. 04. 2020 v 14:51 +0200: > > > Patch is available to download from > > http://mono.i-demo.pl/atari800/atari800-4.2.0-ramcart.patch and > > ready to > > apply e.g. by: > > > > $ git patch atari800-4.2.0-ramcart.patch > it should be: > > $ git apply atari800-4.2.0-ramcart.patch Ideally you'd create a pull request in GitHub. Petr |
From: Jerzy K. <jer...@po...> - 2020-04-18 12:54:50
|
Hello. Last days I prepared Ram-Cart (Polish ones released by Unerring Masters company and Zenon/Dial scene group) support for Atari800. In short words - Ram-Cart is a RAM cartridge using static RAM chips and battery power supply to persist the data written in cartridge. Whole memory is partitioned to 16KB banks. Control register located at $D5xx page is responsible to current bank selection and enabling visibility of it's lower and higher part in $8000-$9FFF and $A000-$BFFF windows (similar to many standard ROM banking cartridges). Ram-Cart was released in many variants: - 64K and 128K - original cart released by Unerring Masters company and available on market back in the days of '90 (L.K. Avalon company was distributor), - Double Ram-Cart 2x128/256K and 1M - released by Zenon/Dial back in the days too, - 1M, 2M and 4M - designed by Zenon/Dial, based on the original 1M cartridge and released now in the days by Unerring Masters company and is available to buy on AtariOnline forum. Beside of amount of RAM, all cartridges differ with number and functions of switches placed on the top of cart case and bank switching ideas. My implementation of emulation supports: - all sizes of memory, - all variants of bank switching, - all switches and buttons present on the top of cartridge case functions, - writing to the RAM in runtime, - writing content of cartridge to the file on remove or on exit emulator, - monitor CARTRIDGE command to show detailed state of Ram-Cart cartridge (just DWORD state is showing for all the rest of carts), - cartridge management options in GUI, - creation of blank cartridge item in menu for specified Ram-Cart. I created patch in reference to current HEAD of git repository by: $ git format-patch master --stdout > atari800-4.2.0-ramcart.patch Patch is available to download from http://mono.i-demo.pl/atari800/atari800-4.2.0-ramcart.patch and ready to apply e.g. by: $ git patch atari800-4.2.0-ramcart.patch if you'd like to test it. Changes made in the code of Atari800: - new CopyToCart macro was created to copy data to the cartridge memory, - CopyROM macro's name has changed to CopyFromCart, - cartridge creation routines (based on ROM image) and ROM extraction routine was externalised to separate function and moved from ui.c to cartridge.c - cartridge and image loading routine was externalized to separate function in cartridge.c You can read about Ram-Cart (in Polish only, but I don't know if there are English version anywhere) at: - http://atariki.krap.pl/index.php/Ram-Cart - http://atarionline.pl/forum/comments.php?DiscussionID=5337 (2/4M) - http://atarionline.pl/forum/comments.php?DiscussionID=5301 (1/2M) - http://atarionline.pl/v01/index.php?subaction=showfull&id=1211326622&archive=&start_from=&ucat=6&ct=wynalazki (DRC) - http://atarionline.pl/1215254384 (64/128/DRC/1M) - http://atarionline.pl/1576034129 (UM is back in busiiness) and there are few Serious #8,#9,#10,#11 disk magazines (in Polish too) where design details and programming techniques are described: http://web.archive.org/web/20100804024148/http://www.serious-dial.atari.pl/zzone/pserious.html Back in the days Dial Group released modified version of DOS II+/D supporting RAMCART as D7 and D8 ramdisks: http://web.archive.org/web/20091210152852/http://www.serious-dial.atari.pl/pliki/softdial/DblRC.zip Description in Polish is here: http://web.archive.org/web/20090209232906/http://serious-dial.atari.pl/artykuly/dblrc.html My future plans: 1. SiDiCAR support: - http://atariki.krap.pl/index.php/SiDiCar - http://tajemnice.atari8.info/8_92/8_92_dyskkrzemowy.html - http://tajemnice.atari8.info/11-12_92/11-12_92_sidicar.html (more about fixes) 2. Raster/C.P.U. S/XEGS 128K RAM-CART support http://raster.atariportal.cz/hw/ramcart/ramcart.htm Best regards Jerzy Kut |
From: Jerzy K. <jer...@po...> - 2020-04-18 12:51:51
|
My fault: > Patch is available to download from > http://mono.i-demo.pl/atari800/atari800-4.2.0-ramcart.patch and ready to > apply e.g. by: > > $ git patch atari800-4.2.0-ramcart.patch it should be: $ git apply atari800-4.2.0-ramcart.patch Best regards Jerzy Kut |
From: Bruce B. <bru...@gm...> - 2020-02-27 15:50:26
|
Hi, I would like to respond to the suggestion given in regards to Atari800 emulation on Android: c) I may have mentioned here, a few years ago, that controller-and-keyboard issues were preventing me from reaching my lifelong goal of enjoying an Atari emulator on a handheld device, namely my Android tablet and/or phone. Again, try the latest (Android) version first. Oh, and this is a Nexus 7 tablet I'm talking about. Vintage late 2013 / early 2014. ;-) Since it seems that you enjoy using old hardware/software I fear that answer to most of your bug reports would be "try latest version first". First, I would like to point out that Colleen, the Atari 800 emulator for > Android is still using Atari800 version 3.0 and even though I have seen > Atari800 version 4.0, it has never been compiled for Android. Second, I have tried to use Bluetooth controllers with Colleen, but no success and the onscreen joystick doesn't worh well. Colleen does work with a Wiimote, but only on Android 4.1 or earlier. Android 4.4 and later won't connect to the Wiimote after Google changed the Bluetooth stack. So, how about compiling Atari800 4.0 for Android? Bruce Baier > |
From: Miro K. <mir...@gm...> - 2020-02-26 13:03:32
|
Hi Chris, thank you for you nice email! Not that I do not appreciate a good Atari story but I think best place to place most of your intriguing Atari events is a place like https://atariage.com/forums, if everybody wrote email like yours, nobody would ever read the mailing list. ;-) Here in the list we tend to discuss user issues or ideas, generally questions, which may interest others. For reporting bugs, we use https://github.com/atari800/atari800/issues. I'll try to briefly answer your questions (those I know answer to). On Wed, 26 Feb 2020 at 04:38, Chris Chiesa <chr...@gm...> wrote: > In the meantime (and for a good period even before then) I've made heavy > use of Atari800, the emulator, to satisfy the Atari cravings that are never > very far away. (I tried Altirra, but found it unable to load-and-run the > very first thing I picked at random, which immediately discouraged me; I > went right back to Atari800.) Indeed, I'm the very Chris Chiesa whose name > appears in the Atari800 Credits, having "added code to let the emulator run > under DEC Windows" (sic) back in the 1990s -- but I haven't kept up with > progress. I still use mainly Atari800 v2.2.1 (!), sometimes v3.0.0. At > one time I was very fond of Atari800*Win* 3.1, but I checked in here > once, long ago, heard that it wasn't part of the main line of Atari800 > development, and basically gave it up. > Situation is a bit different these days. Atari800Win <https://github.com/Jaskier/Atari800Win-PLus/downloads> ended up at version 4.1+, Altirra has become the most cycle exact and feature rich emulator around (also the slowest ;)) and Atari800's development pace is not great, mainly with the departure of Piotr Fusik. However it is still the fastest and most portable emulator. 1) Apparently I at least *tried* to "upgrade" to a "more recent" version of > Atari800, at some point. I see a Zip, folder, and DLL, named *atari800.4.1.0-win32-sdl > *-- but when I try to run the program, all that comes up is an error > message, that procedure *GetTickCount64 *is not found in KERNEL32.dll. > It almost sounds like maybe I've grabbed a 64-bit version instead of the > 32-bit version I need -- but that ought to generate an even more > fundamental "cant run" error. Anybody know what's going on in this > scenario? Please advise. > You mention Windows XP, that function is available since Vista it seems. My guess is that it is the SDL which requires it, i.e. SDL support is from Vista onwards... 2) I'd like to unpack and resurrect that Atari hardware that's been in > storage, but am leery of having something burn out or blow up when I apply > power to possibly-deteriorated equipment. Can anyone advise me as to a > procedure for reviving these things *safely?* Thanks in advance. > That is definitely a question for AtariAge forum. 3) Also please advise as to how I can best "keep up" and have an > at-least-roughly-"current" version of Atari800. > I would recommend to stick with Windows 10 then. Both XP & 7 aren't supported anymore, by both its creator and 3rd party software. a) A way to get the intended output from Atari programs that were designed > to *print on paper. * Such things currently produce multiple single-line > Windows text files at best, and gibberish at worst, at least here on my > system(s) as already described. I'd like to be able to get whole-page text > printouts from text editors, word processors, and BASIC programs that > perform multiple LPRINT statements. I'd like to be able to get the > originally-intended dot-matrix "bit graphics" imagery from screendump > utilities, the Daisy-Dot "fancy font" tools, the sheet-music-printing > function of the Music Construction Set, and a great many other of my own > and others' programs. > > It's a nice idea and surely would be a nice addition to Atari800. Adding peripherals is easy but naturally, you have to be a C developer. b) I would love to see emulation of the Black Box, if only because it is > simply so damn cool. That's the one piece of hardware I will miss the most, > if either mine no longer works when I try it, or I eventually get rid of it > and don't have an emulation to take its place. > > If you know its internals, then again it is just a question of coding support for it. c) I would like to be able to "image," and use in the emulator, types of > floppy disks beyond the built-in emulation of standard single- and > enhanced-density Atari floppy drives. > > I think Atari800 supports all possible ATR images already. Then there's *track*-level reading-and-writing as performed by the > "Archiver" drive modification -- and goodness-only-knows what the BitWriter > modification did... I love, Love, LOVE the Archiver and, along with the > Black Box, it's the physical Atari device I miss the most. And it's > obvious that the Europeans have continued to turn out brilliant and > ingenious peripherals, nonstop and unabated over the past 20+ years. > > That's a different story, copy protections (and the "protected" disk image formats) are not supported, AFAIK. > 5) As a software engineer, it seems to me that a good way to support > emulation of the never-ending stream of new peripheral devices might be to > rearchitect Atari800's I/O underpinnings to hand off peripheral-device > emulation to modular plugins or companion programs that Atari800 proper > merely calls, or communicates with. > Since the SIO protocol in Atari800's OS is basically just that, adding peripherals is not that complicated. And most importantly: nobody is willing to implement new features/hardware, so ... But as I said, Altirra is better in this way, it supports many "new" peripherals. a) I wanted to bring up Atari800 (v2.2.1) on my brother-in-law's > Windows-based MAME arcade cabinet. There was no physical keyboard, so I > used the Windows Virtual Keyboard "accessibility tool" to "type" > when-and-where necessary during the installation. Basic execution and > program-loading were easy to achieve -- it's just Windows, after all. Most > things worked fine, and I thought we were "all set" -- and then I > discovered that clicking F2/F3/F4 in the Virtual Keyboard "did nothing" in > Atari800 -- there was no response on the part of the emulator, whether > trying to to start a game or just continuously PEEKing-and-printed the > contents of the joystick PIA register in a one-line BASIC program. The two > things -- Virtual Keyboard and Atari800 -- simply don't communicate on the > sole subject of the Function keys. I don't know quite enough Windows to > say why/how that can be -- but it is. Typing Alt-F4 in the Virtual > Keyboard was just as capable of "killnig off the currently-in-focus > program," just like a physical Alt-F4 keystroke, which shows that the > Virtual Keyboard was generating *something* -- so, apparently, it just > "wasn't what Atari800 was looking for" to *recognize* an F4 keystroke. I'm > mystified. If anyone reading this is involved in Windows-platform Atari800 > development, I'd like to hear your thoughts on this weirdness, in the hope > that you/we :-) can fix it. I, and my brother-in-law, would be much > obliged. > > I'd try latest version first. Android build uses something similar. b) Back in the day, I wrote at least one Atari program which (for no good > reason ;-) ) was exited by pressing Shift-Ctrl-Esc. Running Atari800 on > Windows, though, that key combination is intercepted and acted upon by > Windows itself, so is not delivered to Atari800, and thus those programs of > mine become impossible to exit cleanly, in the emulator. As noted above, I > don't know enough about Windows programming to know whether that behavior > of Windows can be overridden in application code such as Atari800. If it > can be, please allow me to request that it be done, at least as an option > one can toggle, with the goal of having *all possible *keypress-combinations > come through to Atari programs. > > Feel free to post such tool, then we can investigate and decide what to do. c) I may have mentioned here, a few years ago, that controller-and-keyboard > issues were preventing me from reaching my lifelong goal of enjoying an > Atari emulator on a handheld device, namely my Android tablet and/or phone. > > Again, try the latest (Android) version first. > Oh, and this is a Nexus 7 tablet I'm talking about. Vintage late 2013 / > early 2014. ;-) > > Since it seems that you enjoy using old hardware/software I fear that answer to most of your bug reports would be "try latest version first". "2017 me" also held out the possibility that he (I) "might be able to > supply the disk image in question, for you guys to look at" -- but, at this > point, I would have no idea what disk-image file that was, or where I might > have stored it. So, here in 2020, I can only offer this episode as a "data > point" for you guys to be aware that "this is a thing that happened." > If/when you find it, please post it. > -- http://mikro.atari.org |
From: Petr S. <pst...@so...> - 2020-02-26 08:50:08
|
Chris Chiesa píše v Út 25. 02. 2020 v 19:33 -0500: > > > care to handhold me and (attempt to) give me the absolute basic > education and assistance in this area, I would be delighted to hear > from you at chr...@gm.... Either buy a new hardware with an up-to-date OS (some kind of a Linux distro like Ubuntu, or maybe some Mac or even Windows 10), or if you want to stick with an ancient laptop then install 32-bit Ubuntu 16.04 on that and you'll be almost OK (not with Chrome, that one is 64-bit only, but Firefox will do). Petr |
From: Chris C. <chr...@gm...> - 2020-02-26 03:37:49
|
Well, I promised you a post of about 1500 words, but I thought I'd edit it down to make it shorter. It has ended up *2846* words. Oops. Sorry about that. Please forgive me; I just can't bear to spend any more hours editing it! By way of introduction, I've been "into" the Atari 8-bit computers since 1981, got my own first Atari 800 in 1982, and acquired several more, better-and-better, models as time went on. I was a software engineer on other, larger, platforms from 1988 to 2016, but never lost my love for the Atari. I've written lots of "little" programs for various purposes: games, graphics demos, tools for myself and others... I still have all my machines and all my floppies, plus a thousand or so floppies that, technically, were *other* people's until they sold, or gave, their systems to me back in the late 90s when the Atari "became obsolete" and had not yet "become retro and cool again." I never really wrote any full-blown Atari software, unless you count a couple of very simple games, some of which have been lost. I've also accumulated a whole lot of Atari books, manuals, language tools, etc. Unfortunately, it's all been in storage for the past 13 years (!), and I don't know whether it will still work, or explode spectacularly, if I unbox it all, hook it up, and "throw the switch." In the meantime (and for a good period even before then) I've made heavy use of Atari800, the emulator, to satisfy the Atari cravings that are never very far away. (I tried Altirra, but found it unable to load-and-run the very first thing I picked at random, which immediately discouraged me; I went right back to Atari800.) Indeed, I'm the very Chris Chiesa whose name appears in the Atari800 Credits, having "added code to let the emulator run under DEC Windows" (sic) back in the 1990s -- but I haven't kept up with progress. I still use mainly Atari800 v2.2.1 (!), sometimes v3.0.0. At one time I was very fond of Atari800*Win* 3.1, but I checked in here once, long ago, heard that it wasn't part of the main line of Atari800 development, and basically gave it up. I still have it, but I almost never use it. I "have a million stories" about the role Atari 8-bit computers have played in my life: meeting my first college girlfriend in 1981, being able to trace from that moment straight through to meeting my current (second) wife in 1994, Usenet conversations and shenanigans from the mid-80s to the late 90s, cool (if I do say so myself) programs I've written, or hacks I've pulled off, or *ideas* for hacks that I *wish I'd gotten around to* pulling off. But I won't tell those here-and-now because I'm trying to keep this *short!* Let me know if you want to read them, though, and I'll start writing them up and put them online somewhere for you to grab. Okay. That said, on with the questions-and-thoughts that inspired this post. 1) Apparently I at least *tried* to "upgrade" to a "more recent" version of Atari800, at some point. I see a Zip, folder, and DLL, named *atari800.4.1.0-win32-sdl *-- but when I try to run the program, all that comes up is an error message, that procedure *GetTickCount64 *is not found in KERNEL32.dll. It almost sounds like maybe I've grabbed a 64-bit version instead of the 32-bit version I need -- but that ought to generate an even more fundamental "cant run" error. Anybody know what's going on in this scenario? Please advise. 2) I'd like to unpack and resurrect that Atari hardware that's been in storage, but am leery of having something burn out or blow up when I apply power to possibly-deteriorated equipment. Can anyone advise me as to a procedure for reviving these things *safely?* Thanks in advance. 3) Also please advise as to how I can best "keep up" and have an at-least-roughly-"current" version of Atari800. I have this 32-bit XP laptop (preferred), a Win10 machine I *assume* is *probably* 64-bit but don't really know (bought it very recently, used, and haven't used it much, yet; it is also dog slow); and a 64-bit Win 7 desktop machine that has been down since 2014 and is *also* waiting to be powered back up. Note that I know *nothing* about using SourceForge, Github, any IDEs, etc. -- and, using the last version of Chrome that will even install on XP, I can't even *connect to* SourceForge, for reasons having something to do with the site requiring an outdated HTTPS security protocol -- ??? I don't know enough about such things to have the first clue how to overcome the problem (other than moving on from XP, but I'm not ready to do that, and I may *never* be!). Now, regarding Atari800 more specifically: 4) What is the state of emulation of peripheral devices beyond those that are part of Atari800 itself? I would like to see a few things. It's possible these have already been done, while I've been "out of the loop," so please forgive me if I'm reinventing the wheel... a) A way to get the intended output from Atari programs that were designed to *print on paper. * Such things currently produce multiple single-line Windows text files at best, and gibberish at worst, at least here on my system(s) as already described. I'd like to be able to get whole-page text printouts from text editors, word processors, and BASIC programs that perform multiple LPRINT statements. I'd like to be able to get the originally-intended dot-matrix "bit graphics" imagery from screendump utilities, the Daisy-Dot "fancy font" tools, the sheet-music-printing function of the Music Construction Set, and a great many other of my own and others' programs. In v2.2.1, at least, as I have it here, the P: device emulation looks like little more than a quick add-on to "at least get *something *out to a file," but in my opinion this needs to become a first-class, flexible, print facility, worthy of the level of polish of so much of the rest of Atari800. I may still have the manual for at least one of the dot-matrix printers I owned over the years (one of the few categories of peripheral I ever actually got rid of), which might suffice as a source of specifications... (Oh, and while we're at it, how about emulating the Atari 1020 printer/plotter? That device had capabilities I've never heard of being equalled in any other Atari peripheral: text *and plotting*, in *color!* We've *got* to get that back! :-) ) b) I would love to see emulation of the Black Box, if only because it is simply so damn cool. That's the one piece of hardware I will miss the most, if either mine no longer works when I try it, or I eventually get rid of it and don't have an emulation to take its place. c) I would like to be able to "image," and use in the emulator, types of floppy disks beyond the built-in emulation of standard single- and enhanced-density Atari floppy drives. For instance, I have John Dunning's original disks from his development of the CC65 C compiler (the only Atari language I'm aware of that produces *relocatable* machine code), but I've never been able to read them because they're true-double-sided, true-double-density. So I can't even *image* them -- but if someone *could*, I'd want them to be accessible, in emulation, "in their original forms," so to speak, i.e. to appear and function as true-double-sided-true-double-density disks -- and for that you need an emulation of a true DSDD *drive*, and of course whatever special software, modified DOS, or whatever, is necessary to work with it. Then there's *track*-level reading-and-writing as performed by the "Archiver" drive modification -- and goodness-only-knows what the BitWriter modification did... I love, Love, LOVE the Archiver and, along with the Black Box, it's the physical Atari device I miss the most. And it's obvious that the Europeans have continued to turn out brilliant and ingenious peripherals, nonstop and unabated over the past 20+ years. 5) As a software engineer, it seems to me that a good way to support emulation of the never-ending stream of new peripheral devices might be to rearchitect Atari800's I/O underpinnings to hand off peripheral-device emulation to modular plugins or companion programs that Atari800 proper merely calls, or communicates with. Separating peripheral emulation from Atari800 emulation would allow each to proceed at its own pace without impacting the other(s), and to simply be combined, as desired, when-and-as various pieces became available. This would also keep Atari800 from having to become ever more bloated by having to constantly incorporate emulation of more and more devices into itself, that *aren't really part of* "the computer" per se. I expect this suggestion will strike most folks as "infeasible" or "impractical," given "the amount of work that's already been done to emulate devices just as they are" -- but, if there's ever going to be any interest, by anyone at all, ever, in implementing more peripherals than are emulated *right now*, allow me to point out that the sooner a change like this -- the separation of computer and peripheral emulations -- is made, the easier it will be. It will only get harder, the more stuff is incorporated into Atari800 by the time someone bites the bullet and makes the change. Even if it's never going to happen, I'd at least like to see somebody assess the possibility, in as realistic and unbiased a fashion as possible. 6) I may have missed recent developments, or fixes, for a few other things: a) I wanted to bring up Atari800 (v2.2.1) on my brother-in-law's Windows-based MAME arcade cabinet. There was no physical keyboard, so I used the Windows Virtual Keyboard "accessibility tool" to "type" when-and-where necessary during the installation. Basic execution and program-loading were easy to achieve -- it's just Windows, after all. Most things worked fine, and I thought we were "all set" -- and then I discovered that clicking F2/F3/F4 in the Virtual Keyboard "did nothing" in Atari800 -- there was no response on the part of the emulator, whether trying to to start a game or just continuously PEEKing-and-printed the contents of the joystick PIA register in a one-line BASIC program. The two things -- Virtual Keyboard and Atari800 -- simply don't communicate on the sole subject of the Function keys. I don't know quite enough Windows to say why/how that can be -- but it is. Typing Alt-F4 in the Virtual Keyboard was just as capable of "killnig off the currently-in-focus program," just like a physical Alt-F4 keystroke, which shows that the Virtual Keyboard was generating *something* -- so, apparently, it just "wasn't what Atari800 was looking for" to *recognize* an F4 keystroke. I'm mystified. If anyone reading this is involved in Windows-platform Atari800 development, I'd like to hear your thoughts on this weirdness, in the hope that you/we :-) can fix it. I, and my brother-in-law, would be much obliged. b) Back in the day, I wrote at least one Atari program which (for no good reason ;-) ) was exited by pressing Shift-Ctrl-Esc. Running Atari800 on Windows, though, that key combination is intercepted and acted upon by Windows itself, so is not delivered to Atari800, and thus those programs of mine become impossible to exit cleanly, in the emulator. As noted above, I don't know enough about Windows programming to know whether that behavior of Windows can be overridden in application code such as Atari800. If it can be, please allow me to request that it be done, at least as an option one can toggle, with the goal of having *all possible *keypress-combinations come through to Atari programs. c) I may have mentioned here, a few years ago, that controller-and-keyboard issues were preventing me from reaching my lifelong goal of enjoying an Atari emulator on a handheld device, namely my Android tablet and/or phone. I don't remember offhand the name of the Atari 8-bit computer emulator for Android (I got it wrong, repeatedly, when I posted here about it, last time), but surely *you* guys know what I'm talking about. That said -- First, having the pop-up, on-screen keyboard obscure, or replace, part of the emulated Atari screen, means that I cant' see what I'm typing, a lot of the time. That's no big deal if one is just going to play games -- but this isn't just a game console, it's a *computer*, and I, for one, still write Atari BASIC programs, type letters or journal entries or other documents, etc. in Atari800, once in a while, on *other* devices, and I'd like to be able to do so on my tablet. I realize that "screen real estate" is at a premium on small screens, but perhaps there could at least be a *mode* where the Atari screen is shrunken to make room for a screen keyboard when so desired by a weirdo such as myself. :-) Second, the virtual joystick "pad" *moves around the tablet screen*, rather than *emulating the Atari joystick it's supposed to.* I'd love to see that fixed, too. Oh, and this is a Nexus 7 tablet I'm talking about. Vintage late 2013 / early 2014. ;-) 7) This post has been sitting in my "Drafts" folder since sometime in 2017. When I rediscovered and reread it the other night, the final piece talked about "an odd experience" I had had "recently" as of that time. I no longer remember this "firsthand" but, apparently, a friend had presented me with a floppy-disk image that was supposed to boot into the game "Gumball," but it wouldn't boot on either of the two versions of Atari800 I had at the time, which undoubtedly meant v2.2.1, and probably either v3.0.0 or Atari800Win 3.1. My friend then launched "some other emulator that I'd never heard of and which was not visibly part of the Atari800 family tree" -- maybe it was Altirra, before I realized what that was? I don't know -- and *that* one successfully booted the disk. "2017 me" went on to say that "I was shocked to see such a difference in behavior between Atari800 and another emulator, especially with the other one doing better. I have always considered Atari800 the gold standard of Atari 8-bit computer emulators, so this was almost physically painful. Anybody else ever seen something like this?" :-) "2017 me" also held out the possibility that he (I) "might be able to supply the disk image in question, for you guys to look at" -- but, at this point, I would have no idea what disk-image file that was, or where I might have stored it. So, here in 2020, I can only offer this episode as a "data point" for you guys to be aware that "this is a thing that happened." 8) A couple of braggy-cool things just to leave off on a light note: a) In addition to my Atari computers, other hardware, floppies, etc. etc., I also still have all the records, cassette tapes, reel-to-reel tapes, etc. that I've ever owned. After 20+ years of procrastination ;-) I have recently begun to make progress in the area of digitizing the cassettes. One of them was labeled as containing some Commodore 64 (*hack*, *spit*) (LOL) SID music, *and Mac/65 source code!* Sure enough, when played back, there was the horrible noise made by saving Atari data to cassette! So I captured that audio track, processed it into a mono (single-channel) Windows WAV file, Googled, found, downloaded, and ran, the *wav2cas *program, ended up with a .CAS file, loaded up Atari800 and pointed the C: device at that file, and wrote a little BASIC program to "read the tape and print out whatever I get" -- and, sure enough, there was a whole ASCII-text file of Mac/65 source code! Holy mackerel! Judging from what I remember about *when* I acquired those C64 tunes, this tape had to have been recorded in the summer of 1987 at the absolute latest. So -- I am tickled immensely to report that I have successfully recovered Atari source code from a tape *at least 33 years old!* WOOHOO!!! :-) b) One of my favorite Atari programming accomplishments is a graphics demo that is simultaneously really cool (if I do say so myself) and really primitive. I really, really, like the graphics effect I obtained, plus the fact that it's *interactive* -- but it's not a "demo" in the "scene" sense: there's no scrolltext, no music, etc. etc. I put a short screen-capture video up on YouTube in <goes off to look at YouTube> <*shock*> *2009* -- https://www.youtube.com/watch?v=bYGxXgwGlFQ -- and would be happy to put the bootable .ATR image up someplace if anybody would like to see it, play with it, etc. themselves. Oh, and the source code I got off that cassette tape last night? It's the joystick-reader/image-page-flipper code that makes up the executable part of this demo! Chris Chiesa |
From: Chris C. <chr...@gm...> - 2020-02-26 00:32:05
|
> > > Date: Mon, 24 Feb 2020 08:19:01 +0100 > From: Petr Stehl?k <pst...@so...> > Subject: Re: [Atari800-users] Long message ready to post - advice > please > > Chris Chiesa [...] > > > I have a roughly-1500-word message I'd like to post here, presenting > > a number of? wishlist items and asking a few questions.? [...] > > [Is] it acceptable to post the whole thing all at once? > > It is perfectly OK to post a long-ish email. > Great! I have a little more editing to do, and then I can post. Thanks! > > Also, I would like to change my delivery preferences for this > > mailinglist, from Digest mode to individual-message mode, but thte > > last time I tried to log into the main host to do that, I was (if I > > recall correctly; admittedly, it's been a while) unable to log in. > > Try again. > *GROAN* It's even WORSE now, than it was before. My ancient version of Chrome (which refuses to upgrade further because I'm on an ancient laptop running XP) refuses to connect to the site, alleging that the server can't accept the browser's SSL (or something) connection. Same error in Opera. Don't want to even *launch* Firefox because it instantly sucks up all my RAM and grinds the whole machine to a halt. I did find a webpage that suggested checking my Internet security software, but I'm not sure I'm even *running* any or, if I am, what program it is or how I bring it up or what settings I'd need to fiddle with, in what ways. Yeah, I was hot stuff on the Atari, and a couple other machines/OSes, thirty-five years ago -- but on Windows, the Web, and now in the age of Internet security concerns, SSL, certificates, etc. -- well, very much NOT SO. If someone would care to handhold me and (attempt to) give me the absolute basic education and assistance in this area, I would be delighted to hear from you at *chr...@gm... <chr...@gm...>*. Chris > > |
From: Petr S. <pst...@so...> - 2020-02-24 07:56:00
|
Chris Chiesa píše v So 22. 02. 2020 v 12:54 -0500: > Hi gang! > > I have a roughly-1500-word message I'd like to post here, presenting > a number of wishlist items and asking a few questions. There are > five "major" bullet points, of which two of them have three or four > subparts. What is the best way to post such a thing? Five or ten > separate messages? > Or is it acceptable to post the whole thing all at once? It is perfectly OK to post a long-ish email. > Also, I would like to change my delivery preferences for this > mailinglist, from Digest mode to individual-message mode, but thte > last time I tried to log into the main host to do that, I was (if I > recall correctly; admittedly, it's been a while) unable to log in. Try again. Petr |
From: Chris C. <chr...@gm...> - 2020-02-22 17:54:40
|
Hi gang! I have a roughly-1500-word message I'd like to post here, presenting a number of wishlist items and asking a few questions. There are five "major" bullet points, of which two of them have three or four subparts. What is the best way to post such a thing? Five or ten separate messages? Or is it acceptable to post the whole thing all at once? Also, I would like to change my delivery preferences for this mailinglist, from Digest mode to individual-message mode, but thte last time I tried to log into the main host to do that, I was (if I recall correctly; admittedly, it's been a while) unable to log in. I assume I have an account, since I receive the Digests and am able to post to the list... Please advise. Thanks in advance. Chris |