Another one... Is this already too complex?

http://msx.fi/temp/newlogo4.bin

On my real turboR I see a lot of flickering. The fade does not function properly. Did anyone else also tested the files on a real turboR? Because with blueMSX, turboR emulation, everything seems to work just fine.

I like 3 more than 4.
Looks like your 512byte TurboR demo btw =p

Latok:
Grrr...

What version you are talking about?

I think that last version (newlogo4.bin) should be done now so that it syncs correctly also on real hardware. (Actually I even tested this on OCM) Check also that you are running on Z80.

Quote:

I like 3 more than 4.

3 was a bug

Quote:

Looks like your 512byte TurboR demo btw =p

Yeah This time it is otherway around and without RAM variables.

Hmm... Maybe something like this one could be used...
http://www.youtube.com/watch?v=e7Sp8ltiBHI

It would require just little customized "Dragon's Lair"-player. As the OCM can have FAT16 boot partition the space how much boot-logo takes is not really an issue as long as BIOS is loaded from SD/MMC... (Needed FAT I/O routines are already available in IPL-ROM)

well, you could also use less ram and have a vdpenc player in the logo..

Nyyrikki: indeed, no more flickering when booting newlogo4.bin. Fading works just fine. But the MSX-logo itself is really shaking oddly.....Doesn't look too nice.

Quote:

Let's use something similar in C-BIOS?

That was a joined effort between AuroraMSX (making the logo) / Bifi (coding the logo) and me (converting it into MSX2 format and doing the initial color animation)

I'll take a look at these 3 entries.

I have tested version 4 on OCM and on turboR. It looks the same on both.

I found version 1 nicer though. The effect of version 4 is over the top IMHO. With the way that the logo moves to the left while scrolling in gives the effect of a TV with a bad high-voltage regulator on which the screen distorts due to the logo appearing. This makes me feel a little bit bad about it.

I also think that version 1 and 2 are the best ones... BTW I fixed the version 2 to work also on real machines.

Version 2 looks indeed very good on OCM and on MSX turbo R. Can you put it in the ROM-image of the OCM to replace the standard MSX2 logo?

Too bad I realized, that the version of source that I have for MSX2 SUB-ROM is not ready to compile. ( http://sourceforge.net/projects/msxsyssrc ) I didn't realize this because most of the ROMs in that site can be recompiled. This means that putting the code in means pretty hard binary patching job.

I think that better option is to make additional ROM for the optional boot logo and just link that to the original SUB-ROM. I was thinking something like this:

SET TITLE "XYZ",0 = original logo
SET TITLE "XYZ",1 = original logo, MSX1 colors
SET TITLE "XYZ",2 = new logo
SET TITLE "XYZ",3 = new logo, MSX1 colors

I know that the RTC memory is not supported at the moment by OCM, but I have already fixed that on my version and I will soon release first version of my modifyed ROM. I think that no one is going to miss those original awfull color options.

To add this additional ROM means ofcourse downloading latest hardware configuration from HRA... Another possibility is to make it to load before the actual ROM's that makes it run also in not modifyed OCM, but I just don't see the future in the original hardware configuration...

Interesting development, especially the additional ROM idea, which could be used for more enhancements on top of this cool boot logo.

I have a few questions though:

Did you add RTC memory support by updating the RTC related functions in the ROM or by updating the VHDL? It is not clear to me.

I have not yet looked into the details of the modifications that HRA did; does that version bring the possibility too add such an extra ROM?

Quote:

Did you add RTC memory support by updating the RTC related functions in the ROM or by updating the VHDL? It is not clear to me.

I don't know VHDL, so the original routine where RTC is reseted if check fails is just patched to load a bit more completed dump from MMC instead. I still need to fix the SAVERTC.COM (that saves the settings) a bit...

I did also some other little improvements like "hold 'H' down untill beep to use 50Hz"

Best thing would be if someone could fix the RTC VHDL code to use permanent memory of the chip.

Quote:

I have not yet looked into the details of the modifications that HRA did; does that version bring the possibility too add such an extra ROM?

Yes, the latest version should add possibility to use 2 additional 64KB ROMs in slots 0-1 and 0-3. To make them automaticly load at startup needs just 1 byte patch to IPL-ROM.

I just did not dare to update yet as I don't have the ByteBlaster cable to restore if something goes wrong.