> > You can write uzix software using asm, all you have to do is beware of
the
> > memory location of your software (in order to not erase uzix's code)
> > and you can't use DI.
>
> Yeah, write in ASM, use direct access, make dirty routines, ignore
> the BIOS, put pieces of code on every memory area you think is free, read
> the mapper registers, forget about subslots, etc, etc, etc.
Nah. For file- and memorymanagement I use the Dos2 routines. I do no
slotswitching at all, and if I do I certainly will take subslots in account
since I have a slotexpander myself (and even if I hadn't!). I tend to call
myself a good programmer so I do things this way, and not the 'dirty' way.
You have a very strange perception of direct access. You immediately think
of the worst. For screen i/o I do use direct access. That way, I avoid
problems with unwanted ASCII codes interpreted as control codes, and
extended character sets not fitting in the 256 bytes (for the table
characters I now don't have to use a CHR 1 first).
And have you tried scrolling (a part of) the screen without direct access???
Nah, definately direct access.
And btw, does Uzix support graphical modes??? Don't think so.
> > AFAIK, it's only that, but you'd better ask Adriano about it.
>
> Avoid using ASM in UZIX. It's better for you, it's better for the
> system.
And it's worse for the speed.
Well those things are exactly why I DON'T program for Uzix.
> > > have to get used to Uzix first before I can start working on it. I
know a
> > > lot about Dos, but nothing about Uzix, and I'm afraid it will be a bit
slow
> > > (multitasking, C core, no direct access to the hardware allowed, etc)
>
> It's perfect when using with a HD. I was impressed when I saw UZIX
> running with MegaSCSI. Faster than MSXDOS2.
Yeah, right. Using a diskimage of 720k, therefor only benefitting of the
speed of the HD. That's not what I have my HD for... then I could as well
use a ramdisk.
> And:
> multitasking: UZIX can download a file from funet while you check
> your e-mail or visit www.msx.org. DOS can't.
It is possible to make such a thing yourself. I will in a later stage, but
not now yet because I want to keep it simple.
> C core: it's A LOT easier to find/fix bugs and maintain the code.
> No direct access do the hardware: why the BIOS exists????
Does the word SLOWWW mean anything to you???
> > I heard you can use EP (or another software, i don't use them) and run
uzix as a
> > dsk file in your HD.
With my IDE interface?
However, still doesn't solve the 720k-problem. And how can I write files to
a disk(image) which is not MSX-DOS compatible?
~Grauw
--
>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<
email me: [EMAIL PROTECTED] or ICQ: 10196372
visit the Datax homepage at http://datax.cjb.net/
>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED]
and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in
the body (not the subject) of the message.
Problems? contact [EMAIL PROTECTED]
More information on MSX can be found in the following places:
The MSX faq: http://www.faq.msxnet.org/
The MSX newsgroup: comp.sys.msx
The MSX IRC channel: #MSX on Undernet
****
