Not sure if its the faq's but we've certainly found a repository of indepth info. Prodatrons also has had the odd offer of help with the VDP which is the only main difference between the machines (and the only subject he isn't a genius at, but give him aweek or two with it and I'm sure he would be). From the tool point of view its even easier, so I think we're set to start the port in the new year.

It's not as though as I have something useful to contribute, but now seemed the right time to me to wish you guys all the luck porting this promising OS to MSX! So good luck!

Quote:

so, Prodatron, do you already have an MSX2 to work with? Or are you using an emulator? In case of the latter, please use an accurate one, like blueMSX or openMSX. Better use the real thing, of course

Yes, I own a Phillips VG-8235 MSX2 machine, and I also installed BlueMSX.
Btw, what is the best MSX2 emulator for developing? (Assembler/Disassembler/Monitor integrated?)

Quote:

Humm, invitation hasn't arrive. See if domain is right

Ops, sorry, now I sent it again, hope, this time it works...

Ok, now waiting (remember xenon_soft AT yahoo DOT es)

Humm... problems with yahoo! ?

Quote:

Btw, what is the best MSX2 emulator for developing? (Assembler/Disassembler/Monitor integrated?)

There is no emulator with an assembler integrated. But AFAIK BLueMSX has a monitor and disassembler integrated. So has the (yet unreleased) openMSX debugger.
And there are some other emulators with an extensive debug interface as well: NO$MSX and BrMSX, IIRC. I never use those, because I'm a Linuxer (and a developer of openMSX)

Quote:

Humm... problems with yahoo! ?

Strange, I get a message with something like "this email is not accepted".
Maybe Yahoo doesn't accept your email, or you told Yahoo, that you don't want to receive emails from Yahoo?

Quote:

There is no emulator with an assembler integrated. But AFAIK BLueMSX has a monitor and disassembler integrated. So has the (yet unreleased) openMSX debugger. And there are some other emulators with an extensive debug interface as well: NO$MSX and BrMSX, IIRC. I never use those, because I'm a Linuxer (and a developer of openMSX)

Well, a monitor and debugger will be fine, as it should be possible to use a cross assembler.
But I am surprised: Is nobody developing new MSX software with the help of an emulator? (on the CPC there are 3 or 4 emulators with integrated assembler... well, it doesn't make fun anymore to wait half an hour for the final binary like in the past ).

Quote:

because I'm a Linuxer (and a developer of openMSX)

Well, would be a good reason for me to use Linux more often, if your emulator includes a nice development environment, too!
What are your plans for the future?

As an MSX developer I'm using an assembler/emulator on a daily basis. But I haven't really ever wished for the both to be integrated. Basically I use a cross assembler to generate *all* target files from one base asm file in a separate folder. Then I use the openmsx dir-as-disk feature to run it. I even use a multi pass assemble on my current project that compresses data and integrates it into the target files with a simple shell script (yes, I'm on linux as well). Anything included in the emulator would never be as versatile.
A debugger on the other hand is extremely helpful. Working on that. But making a final version will have to wait till after the MSXdev05 deadline.

Quote:

Quote: There is no emulator with an assembler integrated. But AFAIK BLueMSX has a monitor and disassembler integrated. So has the (yet unreleased) openMSX debugger. And there are some other emulators with an extensive debug interface as well: NO$MSX and BrMSX, IIRC. I never use those, because I'm a Linuxer (and a developer of openMSX) Well, a monitor and debugger will be fine, as it should be possible to use a cross assembler. But I am surprised: Is nobody developing new MSX software with the help of an emulator? (on the CPC there are 3 or 4 emulators with integrated assembler... well, it doesn't make fun anymore to wait half an hour for the final binary like in the past ).

I think a lot of us use emus to develop, just not to actually assemble the stuff. Like edwin said, with modern-day cross-assemblers it's not only possible to generate the code, but also all the additional files you'll be using. I often use a simple batch-file that assembles the code, does the graphics (including crunching) and dumps the whole thing in a big-old lib file that's ready to be used on the MSX. I generally use NLMSX for trial-and-error stuff, then double check it in openMSX (which is almost like checking on hardware) and debug it in blueMSX. Prolly sounds a bit tedious, but it works for me.

Heck, I've even used TNIASM to generate the disk-images directly. I just double-click a batch-file after modifying the code or the graphics and half a second later my diskimage is updated. It really makes coding so much easier, compared to the times of ye-old-corruptfatwhenyouvejustfinishedcodingsomethingthattookmonthstomake.

Hi,

there is a new website for SymbOS online now, which is open for everyone:

www.symbos.de

It's still under construction, but most parts are already finished. The most interesting part may be the screen shot section, where you can see the current SymbOS version (BETA I) in life.

CU,
Prodatron

Quote:

Quote: because I'm a Linuxer (and a developer of openMSX) Well, would be a good reason for me to use Linux more often, if your emulator includes a nice development environment, too! What are your plans for the future?

See the post of Edwin. I also prefer external assemblers or C cross compilers. Indeed much more versatile.

Switching to Linux is great, but not necessary for this purpose. openMSX runs fine on Windows and so does Edwin's debugger for it. Yes, we take care of cross-platform portability (openMSX runs (or at least compiles) on 12 different CPU architectures and at least 6 operating systems, including most Windows, any Linux, OpenBSD, NetBSD, FreeBSD and Mac OS X))

Quote:

Quote: so, Prodatron, do you already have an MSX2 to work with? Or are you using an emulator? In case of the latter, please use an accurate one, like blueMSX or openMSX. Better use the real thing, of course Yes, I own a Phillips VG-8235 MSX2 machine, and I also installed BlueMSX. Btw, what is the best MSX2 emulator for developing? (Assembler/Disassembler/Monitor integrated?)

http://openmsx.sf.net but then again I'm biased