I love my Ys originals, DragonSlayer (Falcom fan here) and Fray . Oh, and I finally got hold of an original Quarth for an affordable price half a year ago . My other two favorites, Metal Gear 2 and SD-Snatcher however are just too expensive to buy from eBay. Besides, I already have legal copies of those, they are on the MCCM CD's.

But really, I don't play that many games on MSX... And I own a fair stock of Dutch and other productions already, so I have plenty to choose from .


~Grauw

Actually, they showed all their production in a SVI-738 computer, usually called a MSX v.1.5, because it has some details from MSX2 computers (V9938, space for RTC, build-in disk drive) and others from MSX1 (16 KB VRAM, 64 KB RAM, etc). It also has an interesting RS-232 serial port.

I owe one of this machines and I have upgraded it to 128 KB VRAM and V9958, but I do not want to change the BIOS. Perhaps I will add a 6 MHz CPU.

Quote:

Dhau, I highly doubt we will ever cooperate because of our history, and that is what the argument between us is about. Further, as you said, we don't share territory at all. I would never consider creating MSX1 stuff because I don't feel any affection towards it, I kinda grew up during the 'MSX2 era' and that's what I'm used to. The other way around pitpan feels uncomfortable coding for MSX2 because he has little experience with it and prefers the MSX1.

Well, I think I understand. It's like same as there will be no "GuveR800 and dhau" production, no matter how good I will become in MSX programming. Also historical reasons...

Quote:

Btw, I don't have a turboR... (do have 7MHz upgrade tho, and a v9958 VDP). My next project will indeed probably be something high-spec. I was thinking of something with a dual-engine, which either works with v9958 or v9990 (so no v9938, but Gfx9000 support for people who don't want an internal hardware upgrade, and to please Sunrise ;p)

Lol, man, you owe yourself a TurboR ST + 1MB upgrade on SIMM. This baby will rock your world

TurboR GT is too expensive, and somehow I don't have the guts to butcher it for 1MB memory upgrade...

Dhau: actually, AFAIK, your "good old friend" Patriek Lesparre is also a part of the GURU LOGIC TEAM.

I don't care very much for a turboR. I like my MSX just the way it is.

btw, pitpan, didn't somebody else say Bandwagon used the SVI-728 (or er, something, the MSX1 version I mean)???

dhau: yes, Guyver is also a member of the GLC team (tho' that's not our official name, it's more like a co-production). So are Chaos, BiFi and Snout.

~Grauw

Quote:

Dhau: actually, AFAIK, your "good old friend" Patriek Lesparre is also a part of the GURU LOGIC TEAM.

Well, Grauw and Patriek are really good in programming, I hope they will keep their interest in platform for the years to come.

Meanwhile I am totally interested in joining my forces with you, Eduardo, (then I get enough skills anyway, I read MSX Red Book right now) to rock MSX1 world

I like it minimalistic too. I believe majority of MSX users are in Brazil, Spain and Japan, and most of them have only standard MSX equipment (no GFX9000 / MoonSound elite hardware, not even memory mapper).

Of course that they are excellent programmers, I have never doubted that.

Grauw: somebody said that they used a SVI-728, but in their page, IIRC, they said that they were showing the demo in a SVI-738. That makes more sense, because its built-in FDD makes easier to code in MSX-DOS. Even that, I tried some of the demos in my tiny HB-75P with HBD-50, and they worked, but only the first third of the screen was seen.
Of course, this only happens with the high-definition parts. SCREEN 3 demos work perfectly and they are impressive too.

Dhau: thank you for joning the extremely narrow MSX1 developers community. If you need any help, please do not hesitate to mail me. The MSX Red Book is an excellent doc, and you can complete it with Sean Young's Z80 document and some TMS9918 technical reference. Then you will have all that you will need to code for MSX (that's what I use, with my own buggy assembler, rZ80).

I actually use HiSoft GEN80 2.04, because I am a bloody pirate

And I do hope to eventually code my own assembler / debugger / emulator in C# / .NET to accelerate my development skills

I even own domain for this: devkit.org (as in www.devkit.org) and devkit.sf.net SourceForge project, but didn't posted anything yet

Actually I coded my assembler in C, using the fab tools Bison and Flex. Of course, it could be compiled in any GCC port and works fine. At the moment, I use a Win32 console version and I should say that it fits all my needs.

Perhaps we could share some experience: I could code the kernell of the assembler and you a cool IDE for Windoze. It could be interesting. Tell me what do you think about it!

I am interested for sure. But I have a very clear vision as to what I want to acheive in my MSX SDK:

- all source in C# language (for .Net framework on Windows and Mono on Linux/Unix)
- reuse #developer as ide (it's very flexible in extending features, and is working on Mono under Linux already)
- hyperfast compilation time due to no external calls!
- full compatibility with M80/L80 with HiSoft GEN80 extensions
- custom 16 or 32K flashable ROM image to get quick communications with MSX via serial and/or parallel port to test stuff on real hardware

I think you prefer C, and I quit C two years ago and moved to C#. C is great, but too much time is spent on debugging buffer overflows and boundary mis-hits... C# compiller detects those on compile time and not in run time... Very good for overall quality of code.

But who cares what tools we use as long as they are source level compartible? I mean is the same ASM project can be compiled in both devkits, then isn't it great?

pitpan, you say for the second time false things about the Bandwagon demos.

This text :
"The demos were coded and shown at the partys with a Spectravideo SVI-728 MSX 1. PSG, VDP1, 64K RAM, Z80 @ 3.57 MHz, MSX-DOS 1 and so forth - a basic MSX1 with no extensions."

comes from the Bandwagon page : http://gr.ath.cx/bandwagon/news.php3

Besides, these pages, written by a Bandwagon member, explain the tricks used by Bandwagon :

http://www.mccw.aktu.nl/91/msx1demos1/en.html

http://www.mccw.aktu.nl/92/msx1demos2/en.html

Nothing other comment from my part, but your knowledge of MSX1 seems to be uncomplete

Quote:

Nothing other comment from my part, but your knowledge of MSX1 seems to be uncomplete

Lol, Mars! Pitpan never claimed to be MSX1 guru. I was the one who told so, based on my experience with his game Guru Logic from MSXDEV'03. If you feel the rush to bash someone, come and get me

Quote:

If you feel the rush to bash someone, come and get me

It's not my intention, but I'm very surprised to see that pitpan doesn't have checked the Bandwagon site before posting in this thread .... And I had already mentioned this text in another thread ....

I don't have the pretention to be myself a MSX(1) guru, but I try always to check my infos and my sources before posting some messages with technical info .... By this way, I can give good infos and I really don't like repetition of false infos

Bashing, dhau? There's nothing wrong with pointing someone to the right information, and correcting him. Otherwise, people will get misinformed, and that's the way many false rumours came into existence (for example about the v9948 - much is in fact speculation even though sometimes claimed as fact) (I fear I am guilty on that too ). I think no-one claims to know-all.

~Grauw

Well, if the site says so, I cannot say anything else. But anyway, try to run the high-definition parts in an MSX1 computer (without V9938) and FDD. They simply do not work like they should.

Perhaps they have other compatibility issues. I know for sure that they all work in my NMS-8245 MSX2 computer and they do not work in my SONY HB-75P (a very standard machine).