Forum comments in chronological order
Disclaimer: I am not responsible for what people (other than myself) write in the forums. Please report any abuse, such as insults, slander, spam and illegal material, and I will take appropriate actions. Don't feed the trolls.
Jag tar inget ansvar för det som skrivs i forumet, förutom mina egna inlägg. Vänligen rapportera alla inlägg som bryter mot reglerna, så ska jag se vad jag kan göra. Som regelbrott räknas till exempel förolämpningar, förtal, spam och olagligt material. Mata inte trålarna.
- Jun 2007
- Aug 2007
- Oct 2007
- Nov 2007
- Dec 2007
- Jan 2008
- Feb 2008
- Mar 2008
- Apr 2008
- May 2008
- Jun 2008
- Jul 2008
- Aug 2008
- Sep 2008
- Oct 2008
- Nov 2008
- Dec 2008
- Jan 2009
- Feb 2009
- Mar 2009
- Apr 2009
- May 2009
- Jun 2009
- Jul 2009
- Aug 2009
- Sep 2009
- Oct 2009
- Nov 2009
- Dec 2009
- Jan 2010
- Feb 2010
- Mar 2010
- Apr 2010
- May 2010
- Jun 2010
- Jul 2010
- Aug 2010
- Sep 2010
- Oct 2010
- Nov 2010
- Dec 2010
- Jan 2011
- Feb 2011
- Mar 2011
- Apr 2011
- May 2011
- Jun 2011
- Jul 2011
- Aug 2011
- Sep 2011
- Oct 2011
- Nov 2011
- Dec 2011
- Jan 2012
- Feb 2012
- Mar 2012
- Apr 2012
- May 2012
- Jun 2012
- Jul 2012
- Aug 2012
- Sep 2012
- Oct 2012
- Nov 2012
- Dec 2012
- Jan 2013
- Feb 2013
- Mar 2013
- Apr 2013
- May 2013
- Jun 2013
- Jul 2013
- Aug 2013
- Sep 2013
- Oct 2013
- Nov 2013
- Dec 2013
- Jan 2014
- Feb 2014
- Mar 2014
- Apr 2014
- May 2014
- Jun 2014
- Jul 2014
- Aug 2014
- Sep 2014
- Oct 2014
- Nov 2014
- Dec 2014
- Jan 2015
- Feb 2015
- Mar 2015
- Apr 2015
- May 2015
- Jun 2015
- Jul 2015
- Aug 2015
- Sep 2015
- Oct 2015
- Nov 2015
- Dec 2015
- Jan 2016
- Feb 2016
- Mar 2016
- Apr 2016
- May 2016
- Jun 2016
- Jul 2016
- Aug 2016
- Sep 2016
- Oct 2016
- Nov 2016
- Dec 2016
- Jan 2017
- Feb 2017
- Mar 2017
- Apr 2017
- May 2017
- Jun 2017
- Jul 2017
- Aug 2017
- Sep 2017
- Oct 2017
- Nov 2017
- Dec 2017
- Jan 2018
- Feb 2018
- Mar 2018
- Apr 2018
- May 2018
- Jun 2018
- Jul 2018
- Aug 2018
- Sep 2018
- Oct 2018
- Nov 2018
- Dec 2018
- Jan 2019
- Feb 2019
- Mar 2019
- Apr 2019
- May 2019
- Jun 2019
- Jul 2019
- Aug 2019
- Sep 2019
- Oct 2019
- Nov 2019
- Dec 2019
- Jan 2020
- Feb 2020
- Mar 2020
- Apr 2020
- May 2020
- Jun 2020
- Jul 2020
- Aug 2020
- Sep 2020
- Oct 2020
- Nov 2020
- Dec 2020
- Jan 2021
- Feb 2021
- Mar 2021
- Apr 2021
- May 2021
- Jun 2021
- Jul 2021
- Aug 2021
- Sep 2021
- Oct 2021
- Nov 2021
- Dec 2021
- Jan 2022
- Feb 2022
- Mar 2022
- Apr 2022
- May 2022
- Jun 2022
- Jul 2022
- Aug 2022
- Sep 2022
- Oct 2022
- Nov 2022
- Dec 2022
- Jan 2023
- Feb 2023
- Mar 2023
- Apr 2023
- May 2023
- Jun 2023
- Jul 2023
- Aug 2023
- Sep 2023
- Oct 2023
- Nov 2023
- Dec 2023
- Jan 2024
- Feb 2024
- Mar 2024
- Apr 2024
- May 2024
- Jun 2024
- Jul 2024
- Aug 2024
- Sep 2024
- Oct 2024
- Nov 2024
Feb 2017
Anonymous
Sat 11-Feb-2017 14:13
Sat 11-Feb-2017 14:13
https://youtu.be/Tr30Qubu_V4
Whose version is this?
Whose version is this?
Anonymous
Sun 12-Feb-2017 05:50
Sun 12-Feb-2017 05:50
ZZZZZZZZZZZZZZZZZZZZZZZZZZ to long, jesus christ write up a summery for us lazy people
That was the "summery"; you are an insult to lazy people everywhere.
But you have redeemed yourself with a great toast: To long, jesus christ! >clink!<
Anonymous
Wed 15-Feb-2017 01:26
Wed 15-Feb-2017 01:26
you are genius !!!!!
Anonymous
Wed 15-Feb-2017 12:04
Wed 15-Feb-2017 12:04
I've just compiled this and got it working unmodified on MacOS 10.12.3. It also works on Raspbian, which is where I usually play.
Thanks for the post!
Thanks for the post!
Anonymous
Wed 15-Feb-2017 16:46
Wed 15-Feb-2017 16:46
Hi
Do you know if they will work with z8 files?. It would be cool to play current IF games on the C64. Thanks.
--KMBR
Do you know if they will work with z8 files?. It would be cool to play current IF games on the C64. Thanks.
--KMBR
Varicella (shown in the screenshot at the top of the page) is a z8 game. That doesn't automatically mean that all z8 games work.
-- Fredrik
Anonymous
Wed 15-Feb-2017 16:56
Wed 15-Feb-2017 16:56
thanius wrote:
Drog in Stugan, men fonten verkar sakna ÅÄÖ. Något för framtida versioner?Det är troligen betydligt mer än fonten som skapar problem. Inmatning och utmatning av svenska tecken, användandet av en alternativ alfabetstabell, och tidsstyrd inmatning är exempel på områden som måste funka för att köra Stugan, och som krånglar även i många ganska mogna speltolkar.
/Fredrik (som skapade Z-kodsversionen av Stugan)
Anonymous
Sat 18-Feb-2017 18:18
Sat 18-Feb-2017 18:18
Hi,
Please could you explain why you can say this:
"the phase of the colour carrier with respect to the dotclock. The latter is assigned randomly at power-on".
I believe the MOS-8701 works with fixed delays to generate the dot clock, so it should come up with always the same phase with respect to the color clock.
On the boards with no MOS-8701, there's a classic PLL circuit that should come up with always the same phase relationship too.
What am I missing? Thanks (iz8dwf at amsat dot org)
Please could you explain why you can say this:
"the phase of the colour carrier with respect to the dotclock. The latter is assigned randomly at power-on".
I believe the MOS-8701 works with fixed delays to generate the dot clock, so it should come up with always the same phase with respect to the color clock.
On the boards with no MOS-8701, there's a classic PLL circuit that should come up with always the same phase relationship too.
What am I missing? Thanks (iz8dwf at amsat dot org)
Anonymous
Sat 18-Feb-2017 19:46
Sat 18-Feb-2017 19:46
Thank you Linus. Really helped me understand this stuff.
lft
Linus Åkesson
Thu 23-Feb-2017 17:16
Linus Åkesson
Thu 23-Feb-2017 17:16
Please could you explain why you can say this:
"the phase of the colour carrier with respect to the dotclock. The latter is assigned randomly at power-on".
I believe the MOS-8701 works with fixed delays to generate the dot clock, so it should come up with always the same phase with respect to the color clock.
"the phase of the colour carrier with respect to the dotclock. The latter is assigned randomly at power-on".
I believe the MOS-8701 works with fixed delays to generate the dot clock, so it should come up with always the same phase with respect to the color clock.
Hi!
The MOS-8701 produces a 7.88 MHz dotclock and a 4.43 MHz colour carrier from the same internal signal. Their ratio is exactly 16:9, which means that 16 hi-res pixels on the screen correspond to nine complete cycles of the colour signal.
It follows that for each hi-res pixel, the phase of the colour carrier is advanced by 9/16 revolutions, which is 202.5 degrees. If it starts at 0 degrees, then after 8 hi-res pixels it will be at 180 degrees. Hence the familiar red/green vertical banding that repeats after 16 pixels; red and green are 180 degrees apart in YUV.
Now, at which pixel is the colour carrier at 0 degrees?
This depends on the timing relationship between the 8701 and the VIC chip. The 8701 has a reset pin, but it doesn't seem to be connected in the C64. The VIC doesn't even have a reset pin.
So, during power-on, there will be a brief period before the 8701 is outputting a stable signal, and during this period the VIC state machine may or may not respond properly. Meanwhile, the internal clock-divide counters of the 8701 might not even start from zero.
That is where the random assignment happens.
lft
Linus Åkesson
Thu 23-Feb-2017 17:18
Linus Åkesson
Thu 23-Feb-2017 17:18
Can any byte in ram matching the $0007 pattern be changed?
I guess what is banked out would not suffer?
I guess what is banked out would not suffer?
Yes, and often several bytes at the same time.
Banking doesn't affect anything, I'm afraid, because the Row Select procedure (LSB) is carried out regardless of what the MSB will be. The corruption happens inside the RAM chips themselves.
A case against syntax highlighting
Anonymous
Fri 24-Feb-2017 09:43
Fri 24-Feb-2017 09:43
I'm unsure whether to laugh at this article, or cringe from sheer fremdschämen on its author's behalf. Currently sitting halfway in abject disbelief.
Rather than attempt a sane response, I'll simply recommend you poke through nested Groff macros or the magic-data tables of the venerable file(1) program (ftp://ftp.astron.com/pub/file/file-5.30.tar.gz, under magic/Magdir). If you can dig through those without admitting highlighting plays a critical role in legibility, you're kidding yourself; but you're not kidding every reader shaking their head over this tripe.
Rather than attempt a sane response, I'll simply recommend you poke through nested Groff macros or the magic-data tables of the venerable file(1) program (ftp://ftp.astron.com/pub/file/file-5.30.tar.gz, under magic/Magdir). If you can dig through those without admitting highlighting plays a critical role in legibility, you're kidding yourself; but you're not kidding every reader shaking their head over this tripe.
Anonymous
Sat 25-Feb-2017 03:19
Sat 25-Feb-2017 03:19
Hej, just noticed that the page is broken if you get here via HTTPS; not all browsers allow you to embed HTTP frames in an HTTPS page these days. Should be easy to fix.
Anonymous
Sun 26-Feb-2017 20:25
Sun 26-Feb-2017 20:25
lft wrote:
Hi!The MOS-8701 produces a 7.88 MHz dotclock and a 4.43 MHz colour carrier from the same internal signal. Their ratio is exactly 16:9, which means that 16 hi-res pixels on the screen correspond to nine complete cycles of the colour signal.
Actually, from the C64 schematics (and from what I can see from a scope) the colour clock output is 4 x 4.433619 MHz which is the crystal frequency, and this signal goes to the VIC-II.
The colour carrier is obtained internally on the VIC-II, but what you say of course doesn't depend from where the 4.433 MHz signal is
generated.
lft wrote:
Meanwhile, the internal clock-divide counters of the 8701 might not even start from zero.That is where the random assignment happens.
this could be true.
The discussion is very interesting to me since eliminating a precise phase offset between the two clocks (as long as it's constant after each power up) could allow to make a very cheap 8701 replacement.