Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.sys.apple2.programmer > #4287 > unrolled thread

Emulator Detection

Started by"Frank M." <frank_o_rama@hotmail.com>
First post2018-03-06 14:46 -0800
Last post2018-03-14 21:23 -0700
Articles 20 on this page of 56 — 14 participants

Back to article view | Back to comp.sys.apple2.programmer


Contents

  Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-06 14:46 -0800
    Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-06 19:03 -0800
      Re: Emulator Detection gids.rs@sasktel.net - 2018-03-07 01:07 -0800
        Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-07 07:18 -0800
          Re: Emulator Detection TomCh <tomcharlesworth26@gmail.com> - 2018-03-07 12:53 -0800
            Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-07 13:24 -0800
              Re: Emulator Detection Antoine Vignau <antoine.vignau@laposte.net> - 2018-03-08 04:42 -0800
                Re: Emulator Detection Tom Porter <laseractiveguy@gmail.com> - 2018-03-08 07:41 -0800
                  Re: Emulator Detection Tom Porter <laseractiveguy@gmail.com> - 2018-03-08 07:46 -0800
                    Re: Emulator Detection Tom Porter <laseractiveguy@gmail.com> - 2018-03-08 08:55 -0800
    Re: Emulator Detection Steve Nickolas <usotsuki@buric.co> - 2018-03-07 05:49 -0500
    Re: Emulator Detection Mark Pilgrim <markpilgrimfastmail@gmail.com> - 2018-03-08 10:21 -0800
      Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-08 22:41 -0800
        Re: Emulator Detection MG <michael@apps.guidero.us> - 2018-03-10 13:24 -0800
          Re: Emulator Detection Zellyn <zellyn@gmail.com> - 2018-03-11 14:21 -0700
      Re: Emulator Detection qkumba <peter.ferrie@gmail.com> - 2018-03-11 14:50 -0700
        Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-11 22:02 -0700
        Re: Emulator Detection TomCh <tomcharlesworth26@gmail.com> - 2018-03-12 13:25 -0700
    Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-11 22:19 -0700
      Re: Emulator Detection gids.rs@sasktel.net - 2018-03-12 10:17 -0700
        Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-12 11:11 -0700
          Re: Emulator Detection mmphosis <mmphosis@macgui.com> - 2018-03-12 22:37 +0000
          Re: Emulator Detection gids.rs@sasktel.net - 2018-03-12 17:03 -0700
            Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-12 17:27 -0700
              Re: Emulator Detection gids.rs@sasktel.net - 2018-03-12 17:39 -0700
                Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-12 20:02 -0700
                  Re: Emulator Detection gids.rs@sasktel.net - 2018-03-12 20:39 -0700
                    Re: Emulator Detection gids.rs@sasktel.net - 2018-03-12 20:40 -0700
                    Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-12 20:58 -0700
                      Re: Emulator Detection qkumba <peter.ferrie@gmail.com> - 2018-03-12 21:51 -0700
                        Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-13 18:45 -0700
                          Re: Emulator Detection gids.rs@sasktel.net - 2018-03-13 22:22 -0700
                            Re: Emulator Detection Antoine Vignau <antoine.vignau@laposte.net> - 2018-03-13 22:43 -0700
                              Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-14 00:08 -0700
                                Re: Emulator Detection Antoine Vignau <antoine.vignau@laposte.net> - 2018-03-14 00:30 -0700
                                  Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-14 08:38 -0700
                          Re: Emulator Detection Zellyn <zellyn@gmail.com> - 2018-03-14 09:03 -0700
                            Re: Emulator Detection Antoine Vignau <antoine.vignau@laposte.net> - 2018-03-14 13:58 -0700
                              Re: Emulator Detection Zellyn <zellyn@gmail.com> - 2018-03-15 06:11 -0700
          Re: Emulator Detection Michael Pohoreski <michael.pohoreski@gmail.com> - 2018-03-12 21:55 -0700
            Re: Emulator Detection Antoine Vignau <antoine.vignau@laposte.net> - 2018-03-12 22:50 -0700
        Re: Emulator Detection Zellyn <zellyn@gmail.com> - 2018-03-12 13:40 -0700
    Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-14 08:42 -0700
      Re: Emulator Detection Antoine Vignau <antoine.vignau@laposte.net> - 2018-03-14 13:57 -0700
        Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-14 21:07 -0700
          Re: Emulator Detection Antoine Vignau <antoine.vignau@laposte.net> - 2018-03-15 14:56 -0700
            Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-16 20:49 -0700
              Re: Emulator Detection Antoine Vignau <antoine.vignau@laposte.net> - 2018-03-16 22:20 -0700
                Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-16 22:24 -0700
                  Re: Emulator Detection Antoine Vignau <antoine.vignau@laposte.net> - 2018-03-17 02:32 -0700
                    Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-17 08:09 -0700
                      Re: Emulator Detection Michael J. Mahon <mjmahon@aol.com> - 2018-03-17 17:01 -0500
                        Re: Emulator Detection Antoine Vignau <antoine.vignau@laposte.net> - 2018-04-28 02:44 -0700
                          Re: Emulator Detection John Brooks <jbrooks@blueshiftinc.com> - 2018-04-28 22:01 -0700
                            Re: Emulator Detection Antoine Vignau <antoine.vignau@laposte.net> - 2018-04-29 08:16 -0700
    Re: Emulator Detection "Frank M." <frank_o_rama@hotmail.com> - 2018-03-14 21:23 -0700

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →


#4321

From"Frank M." <frank_o_rama@hotmail.com>
Date2018-03-12 11:11 -0700
Message-ID<5406a272-781f-42a6-811b-b939a9230fef@googlegroups.com>
In reply to#4320
Try running my latest video playback drive under Virtual II or Sweet16. It just blazes through the frames. While I do think Virtual II is very well designed, there are many things that it just gets wrong (drive access speed, how lores video is presented as solid blocks rather than 'dithered' like actual hardware, etc).

AppleWin is my favorite because it seems the most faithful to real hardware, and has great debugging facilities. It's just not on my main machine, which is a mac air.

F


On Monday, March 12, 2018 at 10:17:46 AM UTC-7, gid...@sasktel.net wrote:
> 
> I would like to see a list of issues that break the code under each emulator.

[toc] | [prev] | [next] | [standalone]


#4324

Frommmphosis <mmphosis@macgui.com>
Date2018-03-12 22:37 +0000
Message-ID<mmphosis-1520894245@macgui.com>
In reply to#4321
Frank M. wrote:
> AppleWin is my favorite because it seems the most faithful to real
> hardware, and has great debugging facilities. It's just not on my main
> machine, which is a mac air.
> 
> F

AppleWin is my favorite too, so sometimes I run Wine on Linux to run
AppleWin.  In the past, I've run Wine on Mac OS X in order to run AppleWin. 
Wine runs well on both OSes, and it should run on the newer macos...

https://www.winehq.org/
https://wiki.winehq.org/MacOS
https://dl.winehq.org/wine-builds/macosx/download.html



[toc] | [prev] | [next] | [standalone]


#4325

Fromgids.rs@sasktel.net
Date2018-03-12 17:03 -0700
Message-ID<45b8eb96-d3bf-41e0-a07e-589539e1e8db@googlegroups.com>
In reply to#4321
On Monday, March 12, 2018 at 12:11:46 PM UTC-6, Frank M. wrote:
> Try running my latest video playback drive under Virtual II or Sweet16. It just blazes through the frames. While I do think Virtual II is very well designed, there are many things that it just gets wrong (drive access speed, how lores video is presented as solid blocks rather than 'dithered' like actual hardware, etc).
> 
> AppleWin is my favorite because it seems the most faithful to real hardware, and has great debugging facilities. It's just not on my main machine, which is a mac air.
> 


Sweet16 does have a couple of preferences for drive access.  Under STORAGE, 5.25 drives in slot #6 can be set to 1 Mhz.  Under CPU, Speed Control sets how fast the instruction code is accelerated.

With both set, you shouldn't have a run-away animation.

[toc] | [prev] | [next] | [standalone]


#4326

From"Frank M." <frank_o_rama@hotmail.com>
Date2018-03-12 17:27 -0700
Message-ID<5b4ab2a1-3e46-4cd6-870a-41f1690408b5@googlegroups.com>
In reply to#4325
No dice, Rob. My vids runs from a hard drive. That seems to be where VII and Sweet16 both run into problems. They assume the drive access time is essentially instantaneous. Might partly be qkumba's fault for writing a read driver which doesn't use very many CPU cycles. :)

mmphosis--I'll check it out. I found a build someone did of CiderPress for MacOS with wine bundled which is great. Still has tons of bugs with copy/paste and also can't read/write to a CompactFlash card (Waiting for my CFFA3000--currently stuck with the older Rev B card), but works okay for everything else.


Also, I'm getting fluctuating numbers of FFs when using this newer code to poll the disk II address field. Is this expected behavior? Or am I counting in the wrong area?

f

[toc] | [prev] | [next] | [standalone]


#4327

Fromgids.rs@sasktel.net
Date2018-03-12 17:39 -0700
Message-ID<552e2236-f359-4f71-96b6-d114950b39dc@googlegroups.com>
In reply to#4326
On Monday, March 12, 2018 at 6:27:03 PM UTC-6, Frank M. wrote:
> No dice, Rob. My vids runs from a hard drive. That seems to be where VII and Sweet16 both run into problems. They assume the drive access time is essentially instantaneous. Might partly be qkumba's fault for writing a read driver which doesn't use very many CPU cycles. :)
> 
> mmphosis--I'll check it out. I found a build someone did of CiderPress for MacOS with wine bundled which is great. Still has tons of bugs with copy/paste and also can't read/write to a CompactFlash card (Waiting for my CFFA3000--currently stuck with the older Rev B card), but works okay for everything else.
> 
> 
> Also, I'm getting fluctuating numbers of FFs when using this newer code to poll the disk II address field. Is this expected behavior? Or am I counting in the wrong area?
> 
> f


In this case, instead of implementing emulator identification, I would identify if it is a II+, and if not, then use the VBL to slow down the video.

[toc] | [prev] | [next] | [standalone]


#4328

From"Frank M." <frank_o_rama@hotmail.com>
Date2018-03-12 20:02 -0700
Message-ID<bb0a2b1b-bbb4-4155-9f96-323dac18bae8@googlegroups.com>
In reply to#4327
Problem 1: ][+ doesn't have double-lores graphics.

Problem 2: individual frames load slightly slower than 2 VBLs (30 fps) in double-lores mode. They might on a faster CFFA3000, I don't know. Would be a good way to handle it in GR mode, which could run maybe 40 frames per second. DGR is more like 20 currently. I do have updated ][plus-friendly GR playback code though.

f


On Monday, March 12, 2018 at 5:39:27 PM UTC-7, gid...@sasktel.net wrote: 
> In this case, instead of implementing emulator identification, I would identify if it is a II+, and if not, then use the VBL to slow down the video.

[toc] | [prev] | [next] | [standalone]


#4329

Fromgids.rs@sasktel.net
Date2018-03-12 20:39 -0700
Message-ID<6d874b40-3c16-451f-8960-0a91ab3d5cc0@googlegroups.com>
In reply to#4328
On Monday, March 12, 2018 at 9:02:09 PM UTC-6, Frank M. wrote:
> Problem 1: ][+ doesn't have double-lores graphics.
> 
> Problem 2: individual frames load slightly slower than 2 VBLs (30 fps) in double-lores mode. They might on a faster CFFA3000, I don't know. Would be a good way to handle it in GR mode, which could run maybe 40 frames per second. DGR is more like 20 currently. I do have updated ][plus-friendly GR playback code though.
> 
> f
> 
> 
> On Monday, March 12, 2018 at 5:39:27 PM UTC-7, gid...@sasktel.net wrote: 
> > In this case, instead of implementing emulator identification, I would identify if it is a II+, and if not, then use the VBL to slow down the video.



It can't be both.  Your previous post mentions that Sweet16 blazes through the frames which means it is playing and/or loading faster than 60 FPS which is what the VBL would slow it down to.

Without the VBL you will still get flicker even if using Qkumba's code and it is only getting 40 FPS.

The advantage for playing the video animation then lies with using Sweet16 or Virtual II which can load a DLR frame in under 1/60 of a second.

[toc] | [prev] | [next] | [standalone]


#4330

Fromgids.rs@sasktel.net
Date2018-03-12 20:40 -0700
Message-ID<9212e4a3-5ac6-418c-b21e-2d7be4f881b8@googlegroups.com>
In reply to#4329
On Monday, March 12, 2018 at 9:39:42 PM UTC-6, gid...@sasktel.net wrote:
> On Monday, March 12, 2018 at 9:02:09 PM UTC-6, Frank M. wrote:
> > Problem 1: ][+ doesn't have double-lores graphics.
> > 
> > Problem 2: individual frames load slightly slower than 2 VBLs (30 fps) in double-lores mode. They might on a faster CFFA3000, I don't know. Would be a good way to handle it in GR mode, which could run maybe 40 frames per second. DGR is more like 20 currently. I do have updated ][plus-friendly GR playback code though.
> > 
> > f
> > 
> > 
> > On Monday, March 12, 2018 at 5:39:27 PM UTC-7, gid...@sasktel.net wrote: 
> > > In this case, instead of implementing emulator identification, I would identify if it is a II+, and if not, then use the VBL to slow down the video.
> 
> 
> 
> It can't be both.  Your previous post mentions that Sweet16 blazes through the frames which means it is playing and/or loading faster than 60 FPS which is what the VBL would slow it down to.
> 
> Without the VBL you will still get flicker even if using Qkumba's code and it is only getting 40 FPS.
> 
> The advantage for playing the video animation then lies with using Sweet16 or Virtual II which can load a DLR frame in under 1/60 of a second.


In this instance I can see how an emulator identification can be used.

[toc] | [prev] | [next] | [standalone]


#4331

From"Frank M." <frank_o_rama@hotmail.com>
Date2018-03-12 20:58 -0700
Message-ID<cd37c153-33f3-4029-8a55-b4146d6914e7@googlegroups.com>
In reply to#4329
If I add the VBL code it's too slow on actual hardware (15fps), if I don't add it the OSX emulators run all out and don't work. That's why I wanted to test for Virtual II. Then I can add a BIT $V2SLOWDOWN and have it change to JSR $V2SLOWDOWN if Virtual ][ is detected. Still losing 4 cycles per frame on actual hardware to add it though (I didn't think anyone would actually notice).

f

[toc] | [prev] | [next] | [standalone]


#4332

Fromqkumba <peter.ferrie@gmail.com>
Date2018-03-12 21:51 -0700
Message-ID<4b2f1d5c-c0dd-497e-87ca-45cba5ce4f3e@googlegroups.com>
In reply to#4331
The soft-switch to switch pages could be replaced in the emulator case with a JSR, perhaps.  No penalty on hardware in that case.

[toc] | [prev] | [next] | [standalone]


#4338

From"Frank M." <frank_o_rama@hotmail.com>
Date2018-03-13 18:45 -0700
Message-ID<b3d03e2e-6315-4505-bc61-14e6393c0694@googlegroups.com>
In reply to#4332
qkumba- I added a JMP $EMU instead of BIT $SOFTSW when detecting an emulator which is working great. Thanks for the tip. Skips page flipping which doesn't seem to be a problem under emulation.

mmphosis/Michael- Tried Wine out, which mostly works, but seems to stutter every 2 seconds or so. Didn't try scrolling, but those bugs/oversights seem consistent with the "open source" code I've tried over the years (saying this as someone who really wants to like open source).

Zellyn- Add the inability to display page 2 in either lores or double-lores mode to your list of problems with Sweet16.

F

[toc] | [prev] | [next] | [standalone]


#4339

Fromgids.rs@sasktel.net
Date2018-03-13 22:22 -0700
Message-ID<3abb9512-2f26-47f3-8dc8-348def277a0e@googlegroups.com>
In reply to#4338
> Zellyn- Add the inability to display page 2 in either lores or double-lores mode to your list of problems with Sweet16.
>


I don't see it as a problem.  I see it as a feature.  :)

[toc] | [prev] | [next] | [standalone]


#4340

FromAntoine Vignau <antoine.vignau@laposte.net>
Date2018-03-13 22:43 -0700
Message-ID<cb9ae5dc-3055-4269-b8f3-4bbc958552c8@googlegroups.com>
In reply to#4339
It is a ROM 01 bug (unless activated in the control panel). It should work with an emulated ROM 3 (no need to activate anything in the control panel)
av

[toc] | [prev] | [next] | [standalone]


#4341

From"Frank M." <frank_o_rama@hotmail.com>
Date2018-03-14 00:08 -0700
Message-ID<d1780e23-2ce5-47b0-94d8-cd49f1225b5f@googlegroups.com>
In reply to#4340
Any way to hit that Alternate Display Mode setting with a softswitch? I have a ROM 3 so I've never noticed. Sounds like playback wouldn't work on an actual ROM 1 either. Is that why other games (Rastan) tend to crash?

Neither emulator seems to mind just loading to page 1 though. Loads seem to happen instantaneously anyway.

f


On Tuesday, March 13, 2018 at 10:43:53 PM UTC-7, Antoine Vignau wrote:
> It is a ROM 01 bug (unless activated in the control panel). It should work with an emulated ROM 3 (no need to activate anything in the control panel)
> av

[toc] | [prev] | [next] | [standalone]


#4342

FromAntoine Vignau <antoine.vignau@laposte.net>
Date2018-03-14 00:30 -0700
Message-ID<0271312b-666f-4450-951d-71c7bfa1c796@googlegroups.com>
In reply to#4341
I don't have my notes handy but if you call FE1F and have ROM 01 returned then you can call a routine to turn on the alternate display mode. Pretty easy to write :-)

[toc] | [prev] | [next] | [standalone]


#4344

From"Frank M." <frank_o_rama@hotmail.com>
Date2018-03-14 08:38 -0700
Message-ID<a9f2e133-d516-4358-81fb-f726187583ae@googlegroups.com>
In reply to#4342
I have code to detect a gs (below), but it doesn't test which ROM version, or turn on alt display mode. I don't know if TOTEXTPG2DA can be called from my program. Also can't seem to find the PEEK to return the gs ROM version.
f


$E1/00A4-00A7 : TOTEXTPG2DA
Point to Alternate Display Mode desk accessory.

This vector points to the Alternate Display Mode program. It
assumes it was called from the Desk Manager. It RTLs back to
the Desk Manager when a key is pressed. The form of the call
in memory is as follows:
JMP abslong ($5C/low byte/high byte/bank byte)





TESTGS SEC
 JSR $FE1F ; Does RTS on //e, clears carry on //gs
 BCC SETGS ; If we have a //gs, fix settings
 CLC
 RTS ; Not a //gs, just exit
SETGS LDA #$00
 STA $C034 ; If we're on a //gs, turn border color black
 LDA $C036 ; Read Speed register (bit 7 is speed control)
 ORA #%10000000 ; Force bit 7 on (fast speed)
 EOR #%10000000 ; now turn it off (normal speed)
 STA $C036 ; Set processor speed to normal
 RTS



On Wednesday, March 14, 2018 at 12:30:33 AM UTC-7, Antoine Vignau wrote:
> I don't have my notes handy but if you call FE1F and have ROM 01 returned then you can call a routine to turn on the alternate display mode. Pretty easy to write :-)

[toc] | [prev] | [next] | [standalone]


#4348

FromZellyn <zellyn@gmail.com>
Date2018-03-14 09:03 -0700
Message-ID<05a1d877-65cf-4850-a463-8582544f3847@googlegroups.com>
In reply to#4338
On Tuesday, March 13, 2018 at 9:45:45 PM UTC-4, Frank M. wrote:
> Zellyn- Add the inability to display page 2 in either lores or double-lores mode to your list of problems with Sweet16.

Does 4am's OpenEmulator build work correctly? If not, I should add a test case to a2audit, and fix OpenEmulator :-)

Zellyn

[toc] | [prev] | [next] | [standalone]


#4351

FromAntoine Vignau <antoine.vignau@laposte.net>
Date2018-03-14 13:58 -0700
Message-ID<5322d571-0b32-4f6f-9e3e-2a47690fc46b@googlegroups.com>
In reply to#4348
On Wednesday, March 14, 2018 at 5:03:06 PM UTC+1, Zellyn wrote:
> On Tuesday, March 13, 2018 at 9:45:45 PM UTC-4, Frank M. wrote:
> > Zellyn- Add the inability to display page 2 in either lores or double-lores mode to your list of problems with Sweet16.
> 
> Does 4am's OpenEmulator build work correctly? If not, I should add a test case to a2audit, and fix OpenEmulator :-)
> 
> Zellyn

Does that mean that OpenEmulator now emulates the 16-bit IIgs?
av

[toc] | [prev] | [next] | [standalone]


#4355

FromZellyn <zellyn@gmail.com>
Date2018-03-15 06:11 -0700
Message-ID<7273d098-449b-44a3-b365-3103a556a36d@googlegroups.com>
In reply to#4351
On Wednesday, March 14, 2018 at 4:58:15 PM UTC-4, Antoine Vignau wrote:
> On Wednesday, March 14, 2018 at 5:03:06 PM UTC+1, Zellyn wrote:
> > On Tuesday, March 13, 2018 at 9:45:45 PM UTC-4, Frank M. wrote:
> > > Zellyn- Add the inability to display page 2 in either lores or double-lores mode to your list of problems with Sweet16.
> > 
> > Does 4am's OpenEmulator build work correctly? If not, I should add a test case to a2audit, and fix OpenEmulator :-)
> > 
> > Zellyn
> 
> Does that mean that OpenEmulator now emulates the 16-bit IIgs?
> av

Oops no. I didn't read that carefully.

It could though, if someone who knows how to emulate a IIgs wanted to work on it… it's a pretty general framework.  :-)

Zellyn

[toc] | [prev] | [next] | [standalone]


#4333

FromMichael Pohoreski <michael.pohoreski@gmail.com>
Date2018-03-12 21:55 -0700
Message-ID<8c1ff1ce-08de-4eae-9950-e8a00994f822@googlegroups.com>
In reply to#4321
> AppleWin is my favorite because it seems the most faithful to real hardware, and has great debugging facilities. 

Mine too. :-)  99% of my time is now on my MBP. Here are what I've found works and what doesn't when running AppleWin under OSX:

* Wine -- don't bother. The up/down arrows or scroll wheel after about ~8 scroll events locks up the debugger. It is a bug in either WM_MOUSEWHEEL / WM_VSCROLL in Wine which in ridiculous it hasn't been fixed in 2018.
* VM Ware -- this works great. This is my preferred way to run AppleWin when I'm not on my i7 dev box.

I haven't tried VirtualBox (yet).

[toc] | [prev] | [next] | [standalone]


Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

Back to top | Article view | comp.sys.apple2.programmer


csiph-web