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.

Feb 2017

Fratres

Anonymous
Sat 11-Feb-2017 15:13
https://youtu.be/Tr30Qubu_V4

Whose version is this?

The TTY demystified

Anonymous
Sun 12-Feb-2017 06: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!<

About me

Anonymous
Wed 15-Feb-2017 02:26
you are genius !!!!!

Freecell

Anonymous
Wed 15-Feb-2017 13: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!

Zeugma

Anonymous
Wed 15-Feb-2017 17: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

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 17: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)

Safe VSP

Anonymous
Sat 18-Feb-2017 19: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)

The TTY demystified

Anonymous
Sat 18-Feb-2017 20:46
Thank you Linus. Really helped me understand this stuff.

Safe VSP

lft
Linus Åkesson
Thu 23-Feb-2017 18: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.

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 18:18
Can any byte in ram matching the $0007 pattern be changed?
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 10: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.