> 10 A = 9200
> 20 B = 13136 + 32
> 30 C = 100
> 40 TEXT : HOME
> 50
> DATA173,87,192,173,83,192,173,84,192,173,80,192,208,251,173,86,192,160,22,1 36,208,253,234,173,87,192,76,9,3
> 60 FOR I = 768 TO 796
> 70 READ N: POKE I,N
> 80 NEXT
> 100 HGR : POKE - 16302,0
> 110 HCOLOR= 4
> 120 HPLOT 0,0: CALL 62454
> 130 HCOLOR= 2
> 140 HPLOT 0,63 TO 279,63
> 150 HPLOT 0,62 TO 279,62
> 160 HCOLOR= 6
> 170 HPLOT 0,61 TO 279,61
> 180 HPLOT 0,60 TO 279,60
> 190 HCOLOR= 1
> 200 HPLOT 0,59 TO 279,59
> 210 HPLOT 0,58 TO 279,58
> 220 HCOLOR= 5
> 230 HPLOT 0,55 TO 279,55
> 240 HPLOT 0,54 TO 279,54
> 250 HCOLOR= 0
> 260 HPLOT 0,123 TO C,123
> 261 HPLOT 0,122 TO C,122
> 262 HPLOT 0,119 TO C,119
> 263 HPLOT 0,118 TO C,118
> 270 COLOR= 0
> 280 FOR I = 0 TO 39
> 290 VLIN 0,39 AT I
> 300 NEXT
> 310 COLOR= 13
> 320 HLIN 0,39 AT 14
> 330 FOR I = 0 TO 7
> 340 POKE A + I,0
> 345 POKE B + I,0
> 350 NEXT
> 360 COLOR= 1
> 370 HLIN 0,39 AT 13
> 380 VTAB 21
> 390 PRINT TAB( 16)"RAINBOW"
> 400 PRINT : PRINT "MIXED GRAPHICS (HI-RES/COLOR)"
> 500 CALL 768
I tried running this in Virtual II on my MacBook Air and got an error
"OUT OF DATA ERROR IN 70". I copied it from your post and pasted it
into Virtual II, so I know I couldn't have typed anything wrong. Any
ideas?
> I tried running this in Virtual II on my MacBook Air and got an error
> "OUT OF DATA ERROR IN 70". I copied it from your post and pasted it
> into Virtual II, so I know I couldn't have typed anything wrong. Any
> ideas?
When I copied/(shift inserted) the text into Applewin the line 50 didn't paste properly so the program had no DATA to work with.
>> I tried running this in Virtual II on my MacBook Air and got an error
>> "OUT OF DATA ERROR IN 70". I copied it from your post and pasted it
>> into Virtual II, so I know I couldn't have typed anything wrong. Any
>> ideas?
> When I copied/(shift inserted) the text into Applewin the line 50 didn't
> paste properly so the program had no DATA to work with.
> Cheers,
> Mike T
Before copying the text you need to move the DATA line so that it is following the number 50 then it copies correctly into Applewin.
In Applewin I see horizontal stripes of the normal hires colors and they occasionally blink.
> > In Applewin I see horizontal stripes of the normal hires colors and they
> > occasionally blink.
> Yes, this is the behavior in AppleWin.
> On a real Apple II+, a rainbow is displayed.
After fixing line 50 I get the same thing in Virtual II that you got
in AppleWin. I guess I'll need to try it in a real II to see what it
really looks like.
>>> Before copying the text you need to move the DATA line so that it is
>>> following the number 50 then it copies correctly into Applewin.
>> Yes, the line number 50 and the DATA need to all be on the same line.
>> Unfortunately, Google groups wants to word wrap code.
>> 50 DATA 173,87,192,173,83,192,173,84,192,173,80,192,208,251,
>> 173,86,192,160,22,136,208,253,234,173,87,192,76,9,3
>>> In Applewin I see horizontal stripes of the normal hires colors >>> and they occasionally blink.
>> Yes, this is the behavior in AppleWin.
>> On a real Apple II+, a rainbow is displayed.
> After fixing line 50 I get the same thing in Virtual II that > you got in AppleWin. I guess I'll need to try it in a real II > to see what it really looks like.
The correct syntax is: 50 DATA 173,87,...,76,9,3
I don't have Virtual II, or is that the online emulator?
> On Dec 24, 11:17 am, mmphosis <mmpho...@yahoo.com> wrote:
> >>> Before copying the text you need to move the DATA line so that it is
> >>> following the number 50 then it copies correctly into Applewin.
> >> Yes, the line number 50 and the DATA need to all be on the same line.
> >> Unfortunately, Google groups wants to word wrap code.
> >> 50 DATA 173,87,192,173,83,192,173,84,192,173,80,192,208,251,
> >> 173,86,192,160,22,136,208,253,234,173,87,192,76,9,3
> >>> In Applewin I see horizontal stripes of the normal hires colors
> >>> and they occasionally blink.
> >> Yes, this is the behavior in AppleWin.
> >> On a real Apple II+, a rainbow is displayed.
> > After fixing line 50 I get the same thing in Virtual II that
> > you got in AppleWin. I guess I'll need to try it in a real II
> > to see what it really looks like.
> The correct syntax is: 50 DATA 173,87,...,76,9,3
> I don't have Virtual II, or is that the online emulator?
> It works in AppleWIN.
> Bill
Virtual II is an excellent Apple II emulator for the Macintosh, the
only thing it doesn't emulate is the GS. For that I use Sweet 16. The
web site you're thinking of is Virtual Apple 2.
> On Dec 24, 11:17 am, mmphosis <mmpho...@yahoo.com> wrote:
> >>> Before copying the text you need to move the DATA line so that it is
> >>> following the number 50 then it copies correctly into Applewin.
> >> Yes, the line number 50 and the DATA need to all be on the same line.
> >> Unfortunately, Google groups wants to word wrap code.
> >> 50 DATA 173,87,192,173,83,192,173,84,192,173,80,192,208,251,
> >> 173,86,192,160,22,136,208,253,234,173,87,192,76,9,3
> >>> In Applewin I see horizontal stripes of the normal hires colors
> >>> and they occasionally blink.
> >> Yes, this is the behavior in AppleWin.
> >> On a real Apple II+, a rainbow is displayed.
> > After fixing line 50 I get the same thing in Virtual II that
> > you got in AppleWin. I guess I'll need to try it in a real II
> > to see what it really looks like.
> The correct syntax is: 50 DATA 173,87,...,76,9,3
> I don't have Virtual II, or is that the online emulator?
> It works in AppleWIN.
> Bill
It looks mostly OK in my locally compiled version of kegs (xkegs) --
though I might have mistyped a couple of lines, I see a few black
stripes. But the effect isn't lost at all. Neat!
I typed it in this morning. I found it interesting that when the Reset key
is held down, two of the color bars disappear. Presumably this is because it
causes the machine code program to stop.
I also disassembled the machine code to take a look at how it works. It
looks like it is waiting on a memory address to change ($C050, IIRC) before
taking further action.
-- ]DF$
Mac GUI Vault - A source for retro Apple II and
Macintosh computing.
http://macgui.com/vault/
D Finnigan <dog_...@macgui.com> wrote:
> I typed it in this morning. I found it interesting that when the Reset key
> is held down, two of the color bars disappear. Presumably this is because it
> causes the machine code program to stop.
> I also disassembled the machine code to take a look at how it works. It
> looks like it is waiting on a memory address to change ($C050, IIRC) before
> taking further action.
That reads the "floating bus" value--the byte last read by the video
refresh controlled by the video scanner.
Prior to the introduction of the VBL signal, this was the only way for the
processor to sense the state of the video scanner, and therefore to
synchronize with it.
On Dec 28, 11:56 am, dog_...@macgui.com (D Finnigan) wrote:
> I typed it in this morning. I found it interesting that when the Reset key
> is held down, two of the color bars disappear. Presumably this is because it
> causes the machine code program to stop.
> I also disassembled the machine code to take a look at how it works. It
> looks like it is waiting on a memory address to change ($C050, IIRC) before
> taking further action.
> --
> ]DF$
> Mac GUI Vault - A source for retro Apple II and
> Macintosh computing.http://macgui.com/vault/
You got it!
Are you actually running it on "real" hardware?
I am pretty sure that anyone running this on an emulator, won't see
the same thing as on a real Apple II plus. Although, I believe that
OpenEmulator is very close to making this work.
0300- AD 57 C0 LDA $C057
0303- AD 53 C0 LDA $C053
0306- AD 54 C0 LDA $C054
0309- AD 50 C0 LDA $C050 ; 4 cycles -- reads the "floating bus"
value--the byte last read by the video refresh controlled by the video
scanner.
030C- D0 FB BNE $0309 ; 3 cycles if not $00, keep reading
the "floating bus" -- zeroes are strategically placed within the hi-
res screen
030E- AD 56 C0 LDA $C056 ; 4 cycles -- switch to lo-res
0311- A0 16 LDY #$16 ; 2 cycles -- Y = 22
0313- 88 DEY ; 2 cycles times 22 = 44 cycles
0314- D0 FD BNE $0313 ; 3 cycles times 22 + 2 cycles = 68
cycles
0316- EA NOP ; 2 cycles -- 4 + 2 + 44 + 68 + 2 = 120
cycles, long enough to display horizontal lines of lo-res two pixels
high
0317- AD 57 C0 LDA $C057 ; switch to hi-res
031A- 4C 09 03 JMP $0309 ; do it all over again
forgive me for the word wrap messing with the code
mmphosis wrote:
> On Dec 28, 11:56 am, dog_...@macgui.com (D Finnigan) wrote:
>> I typed it in this morning. I found it interesting that when the Reset
>> key
>> is held down, two of the color bars disappear. Presumably this is because
>> it
>> causes the machine code program to stop.
>> I also disassembled the machine code to take a look at how it works. It
>> looks like it is waiting on a memory address to change ($C050, IIRC)
>> before
>> taking further action.
>> --
>> ]DF$
>> Mac GUI Vault - A source for retro Apple II and
>> Macintosh computing.http://macgui.com/vault/
> I am pretty sure that anyone running this on an emulator, won't see
> the same thing as on a real Apple II plus. Although, I believe that
> OpenEmulator is very close to making this work.
-- ]DF$
Mac GUI Vault - A source for retro Apple II and
Macintosh computing.
http://macgui.com/vault/
> mmphosis wrote:
> > On Dec 28, 11:56 am, dog_...@macgui.com (D Finnigan) wrote:
> >> I typed it in this morning. I found it interesting that when the Reset
> >> key
> >> is held down, two of the color bars disappear. Presumably this is because
> >> it
> >> causes the machine code program to stop.
> >> I also disassembled the machine code to take a look at how it works. It
> >> looks like it is waiting on a memory address to change ($C050, IIRC)
> >> before
> >> taking further action.
> >> --
> >> ]DF$
> >> Mac GUI Vault - A source for retro Apple II and
> >> Macintosh computing.http://macgui.com/vault/
> > You got it!
> > Are you actually running it on "real" hardware?
> > I am pretty sure that anyone running this on an emulator, won't see
> > the same thing as on a real Apple II plus. Although, I believe that
> > OpenEmulator is very close to making this work.
> --
> ]DF$
> Mac GUI Vault - A source for retro Apple II and
> Macintosh computing.http://macgui.com/vault/
Just right now, DF$:
"Bandwidth Limit Exceeded
The server is temporarily unable to service your request due to the
site owner reaching his/her bandwidth limit. Please try again later."
> mmphosis wrote:
> > On Dec 28, 11:56 am, dog_...@macgui.com (D Finnigan) wrote:
> >> I typed it in this morning. I found it interesting that when the Reset
> >> key
> >> is held down, two of the color bars disappear. Presumably this is because
> >> it
> >> causes the machine code program to stop.
> >> I also disassembled the machine code to take a look at how it works. It
> >> looks like it is waiting on a memory address to change ($C050, IIRC)
> >> before
> >> taking further action.
> >> --
> >> ]DF$
> >> Mac GUI Vault - A source for retro Apple II and
> >> Macintosh computing.http://macgui.com/vault/
> > You got it!
> > Are you actually running it on "real" hardware?
> > I am pretty sure that anyone running this on an emulator, won't see
> > the same thing as on a real Apple II plus. Although, I believe that
> > OpenEmulator is very close to making this work.
> --
> ]DF$
> Mac GUI Vault - A source for retro Apple II and
> Macintosh computing.http://macgui.com/vault/
Is it supposed to look like this? (sorry for the horrible-looking URL)
On Jan 19, 2:50 pm, dog_...@macgui.com (D Finnigan) wrote:
> BLuRry wrote:
> > Is it supposed to look like this? (sorry for the horrible-looking URL)
> Nay.
> The machine code adds 2 extra bars in that middle black space.
> If one holds the reset key (or Control-Reset, if you've got your switch that
> way), the machine code halts, and the two bars disappear from the screen.
> --
> ]DF$
> Mac GUI Vault - A source for retro Apple II and
> Macintosh computing.http://macgui.com/vault/
Hmmmm.... If I adjust my timing up or down it no longer holds still
and flickers a lot. I know that my floating bus code is doing
*something* otherwise I wouldn't see it at all. :-D Anyway, looks
like what I implemented is similar to what KEGS does.
BLuRry wrote:
> On Jan 19, 2:50 pm, dog_...@macgui.com (D Finnigan) wrote:
>> BLuRry wrote:
>> > Is it supposed to look like this? (sorry for the horrible-looking URL)
>> Nay.
>> The machine code adds 2 extra bars in that middle black space.
>> If one holds the reset key (or Control-Reset, if you've got your switch
>> that
>> way), the machine code halts, and the two bars disappear from the screen.
> Hmmmm.... If I adjust my timing up or down it no longer holds still
> and flickers a lot. I know that my floating bus code is doing
> *something* otherwise I wouldn't see it at all. :-D Anyway, looks
> like what I implemented is similar to what KEGS does.
KEGS? Even a real IIgs doesn't do the same thing as a real II Plus.
I saved the RAINBOW program on a 5.25" disk so I wouldn't have to type it
again. I loaded it on the IIgs. The results were... we shall say...
interesting.
On Fast speed (that's 2.8 MHz for me) there was quite a bit of screen
flickering. On normal speed, the flickering was less so, and was isolated
the right side of the screen.
-- ]DF$
Mac GUI Vault - A source for retro Apple II and
Macintosh computing.
http://macgui.com/vault/
>>On Jan 19, 2:50 pm, dog_...@macgui.com (D Finnigan) wrote:
>>>BLuRry wrote:
>>>>Is it supposed to look like this? (sorry for the horrible-looking URL)
>>>Nay.
>>>The machine code adds 2 extra bars in that middle black space.
>>>If one holds the reset key (or Control-Reset, if you've got your switch
>>>that
>>>way), the machine code halts, and the two bars disappear from the screen.
>>Hmmmm.... If I adjust my timing up or down it no longer holds still
>>and flickers a lot. I know that my floating bus code is doing
>>*something* otherwise I wouldn't see it at all. :-D Anyway, looks
>>like what I implemented is similar to what KEGS does.
> KEGS? Even a real IIgs doesn't do the same thing as a real II Plus.
> I saved the RAINBOW program on a 5.25" disk so I wouldn't have to type it
> again. I loaded it on the IIgs. The results were... we shall say...
> interesting.
> On Fast speed (that's 2.8 MHz for me) there was quite a bit of screen
> flickering. On normal speed, the flickering was less so, and was isolated
> the right side of the screen.
Of course, being a cycle-counting program, it would have to run at
1MHz.
But does this mean that the vus structure of the IIgs does not allow
"bus sniffing" and "vapor lock" at all?
The red and yellow lines of the rainbow were flickering off and on in
Virtual ][. The screenshot captured the rainbow when the red and
yellow lines were black.
> The red and yellow lines of the rainbow were flickering off and on in
> Virtual ][. The screenshot captured the rainbow when the red and
> yellow lines were black.
Close, but no cigar. Every line of the rainbow should be solid with no
flicker.
> > There is still a problem with two bars that flicker at the beginning
> > (I posted the worst case)... does that happen on an Apple II as well?
> That is almost correct, but not quite.
> Every bar of the rainbow should be of uniform length. There should not be
> any flickering at all.
> --
> ]DF$
> Mac GUI Vault - A source for retro Apple II and
> Macintosh computing.http://macgui.com/vault/
Hello D Finnigan:
thanks a lot for your help! By "uniform length", do you mean that the
LORES lines do not have the same length as the HIRES lines, or
something else? Would it be a lot of trouble to post a picture of the
output on a real Apple II?
I emphasize this, because I feel this is an excellent test of the
timing emulation. It not only tests horizontal but also vertical
timing.
I must also confess that I still have to go into the code further to
fully understand what is going on :-).
