Jon,
> > Well... What I do is clear hooks and fill the area D000h-F000h
> > with zeros...
> hmmm... seems dangerous to me: some hardware drivers can be installed in
> this area at startup. (example: workspace of diskroms). MSX system area
> is from #F380...#FFFF. Below that area, the DOS kernel area;
Remember that UZIX doesn' uses DOS. It acesses peripherals
directly (using their ROM, if available).
> Another remark: most (all?) diskroms (DISKIO #4010) use routine at #F36E
> when loading/saving data in page 0 or 1. (#0000...#7FFF) This is only
> possible in MSX-DOS environment. (at #F36E there is a JP to a routine in
> the MSX-DOS area. This area is located below the driverarea and is
> certainly deleted by your program.) Therefore UZIX shouldn't try to
> load/save data via #4010 to page 0 or 1.
Yes, I know that. That's why data to be read/written via 4010h is
put at upper 16k. And, also, because diskROM is switched directly to page
1.
Adriano Camargo Rodrigues da Cunha ([EMAIL PROTECTED])
Engenharia de Computacao - UNICAMP
http://www.adrpage.cjb.net MSX-TR:I have one.And you?
* Real good programmers program assembly with COPY CON. *
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
****
