On Tue, 24 Aug 1999 15:35:01 +0200, Laurens Holst wrote:
>> You said that a routine to display sprites work under BASIC and not on
>>DOS because DOS uses the upper memory for itself. So, I thought this is
>>strange.
>> I DON'T think VDP needs RAM info to display sprites. (-:
>Oh, no. I wan't talking about that. I said that if a program works in Basic
>environment but not in Dos environment that the memorymapper is the most
>common problem Dos2 uses the memorymapper's highest segments for its kernel,
>so if the program corrupts this part then in Basic it will still work but in
>Dos2-environment not anymore.
>I had no idea you were talking about a spriteroutine or so...
The routine is perfect. It just doesn't work under DOS (neither in BDOS1)
and works great under Basic.
>But I think something went wrong with the conversion or so. Changed memory
>adresses (Dos starts at #100, Basic commonly at #9000), different mapped
>pages (ROM/RAM), this kind of stuff.
You do not understand. There is no real problem. It's just something bizarre.
Something that DOS do that Basic do not.
>Owww, yeah, ofcourse.
>How could I know that you meant Ricardo Bittencourt with RicBit (it isn't
>exactly the first thing that pops into my mind...).
Here, on USP (Sao Paulo University) where Ricardo and I study, we call
him "RicBit"... (-:
>Hehe... Well project "i" is a multitasking internet environment with Dos
>emulation... (it can still run PMEXT etc as long as they use BDOS calls for
>screen updates etc).
AFAIK, Adriano is working (and there is a preliminary version on 1.1.3 of UZIX)
BDOSEMU, that do exactly this task, but runs a DOS program under UZIX.
The only limit is that the program cannot use more than the first 32Kb (AFAIK).
>> I agree that is not needed, but it would be useful! (-:
>But it doesn't make memorymanagement harder to program I think...
Maybe yes, Maybe not. The only change would be that you would receive
a Process ID. And you'll have to kill this ID when exiting the program...
>> Oh, THESE are the routines that are taking my RAM away?!?!
>(((((((((((((((-:
>No. In Dos2 environment you have more RAM available in the direct accessible
>RAM because the drive-info blocks are all moved to Dos2's datasegment.
>Ofcourse you have 2 free mapperpages less though.
It's strange. I'm trying to create a utility to change BDOS2->BDOS1 on-the-fly
(without
reset), but there is some strange problem. The first strange fact is that I really
need to copy a LARGE amount of sys vars to DISK so it works, and when it works,
some really strange problems are shown.
On the last version I worked on, the program actualy switched BDOS2->BDOS1,
loading MSXDOS.SYS and COMMAND.COM after setting the proper system vars.
The SysID detects the version of BDOS as 1.0 after the program runs, BUT some
strange things happen. When I exec a DIR on BDOS1 (after change), sometimes
only a few names of the directory are shown. Some times, NO names are shown.
Some times ALL names are shown... And If I exec a TYPE command, the system
hangs... It's weird. But when I was trying this I have not BrMSX2.0... Now I'll try it
again.
>> This is not very good. In this case you should be unhappy to be right.
>Snif... I'm so unhappy... I think I'm gonna commit suicide or so... my life
>has been completely ruined.
Hehehe... (((((-:
>> But maybe Z280 was better. Z280 had a mode like V86 on 386... This means
>> we could open several Z80 sessions on the Z280. But this is a little
>confuse to
>> use.
>Yeah, think so. But isn't the Z380 an enhanced Z280???
No. Z280 was an enhanced Z180. Z380 is an MORE enhanced
Z180. There is a lot of things that were present on Z280 that
are missing on Z380. And, of course, there is a lot of things present
on Z380 that were missing on Z280.
[]'s Daniel Caetano ([EMAIL PROTECTED])
...The biggest Noah's mistake was let the bugs enter in the Ark!
OS/2 Sites: http://www.os2brasil.com.br/novidades/
http://www.os2brasil.com.br/novidades/drivers.shtml
http://www.geocities.com/SiliconValley/8752/os2hp/index.html
MSX Sites: http://www.fudeba.cjb.net/ e http://www.msxnews.cjb.net/
MSX Phoenix: http://www.msxphoenix.cjb.net/
****
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/)
****
