I think rolins in on the way, you have to insert the msx-dos 2 ROM in a slot (emulated), and declare it like a dos 2 rom not a game (usually this is automatic, except for obsonet rom)

Quote:

I created a dsk and everything works (very impractical for development!) What I find incredible is that it seems there is no way to force dirasdisk to boot from msxdos2!

My idea is to create a disk with just an autoexec.bat containing something like:

b:
autoexec

and b: being the drive with the dirasdisk functionality applied to it.

Sd-Snatcher, I have no problems with that, I'm emulating a TR.
The issue is the boot sector of dirasdirsk in BLUEMSX, that cannot be slected to be msxdos2

Good one Vincent !!
your workaround is ok!

Dont emulate the TR.
Emulate a MSX2 or 2+ (on 7Mhz if needed) with DOS2 ROM on slot A, and it shouldnt need a DOS2 boot sector, just msxdos2.sys and command2.com.
Only TR requires a disk with DOS2 boot sector to run DOS2.

Quote:

Dont emulate the TR. Emulate a MSX2 or 2+ (on 7Mhz if needed)

Ummm, i usually emulate a MSX2 and i boost it to 200%-500%

ARTRAG: FYI: on openMSX you can set the dir-as-disk boot sector to DOS2 and DOS1 at will, using the 'bootsector' setting. Default is DOS2.

Thanks manuel, the fact is that I love the debugger in blue
Developing in open isn't the same

New feature request for Blue....

Or for open: add a decent debugger

ARTRAG: did you try the openMSX debugger? (The GUI version...)

See http://openmsx.sourceforge.net/ in the download box at the bottom for a snapshot. (Which will be updated soon.)

ARTRAG: updated... check it out!

Question about msxdos
Is there a way to avoid the echo on the screen of the typed chars?
I know this comes from CPM, but I remember there was a way to avoid it.
I'm under msxdos1
Any help ?