EH> Melanie Baillot (1:163/215) schreef aan Eef Hartman op 03-Mar-99 om 17:17:

 MB> No. If you're using virtual screen like in Windows, it actually 
 MB> uses your Video Ram to store each pixels

 EH> It always uses your video RAM to store the pixels. But 

I didn't mean it that way, if you have a game, but you want to be able to
scroll right left up and down, Like Warcraft 2, Red Alert, etc.. It fills each
screen at one time from buffers, etc.. But they don't use the V-Ram to store
it.  When I saud virtual screen, I meant actually storing example 1024x768 in
320x240...


 EH> To see all of it you have to map the video RAM into 
 EH> addresses OUT of range of the normal RAM, and THAT is 
That,s why I said advanced win'95 drivers or Win'98 drivers...

But for VESA 5.0, well Univbe 5.0, you're able to use the virtual screen
feature, not that I know how...

 MB> If you use Turbo Pascal, then MOVE is the fastest, if you're 
 MB> using Borland Pascal then using the XMS DMA Transfer assembly 
 MB> code is the fastest.

 EH> MOVE cannot move more then 64 KB at a time (16 bit 
 EH> counter) and unless you fiddle in assembler with the 
 EH> segments you cannot address memory above the 16 MB 
 EH> limit, I believe (16 bits protected mode, not 32-bits 
 EH> mode is what BP runs in).
I know, that's why I bolded TURBO Pascal, not Borland.. Move is good for
Variable to screen and I never said to use it for more than 64KB / PAGE...

 MB> Old games uses the 15M-16M space but with the new computers with 
 MB> 128MB ram, setting the BIOS to 15-16M state will cause it to 
 MB> report 64MB ram left..

 EH> I said ABOVE 16 MB (the old 15-16 was for those 
 EH> programs/modes that couldn't address any higher).
Ok...

 MB> In 16bit mode in BP, you can use the HEAP to also be able to 
 MB> write to the video memory all at once without the 64K thing. But 
 MB> programming to fo that is a little bit more complex..

 EH> And you cannot use the standard MOVE anymore, so you do 
 EH> have to do the MOVE in assembler too (with a 32-bits 
 EH> counter register, not CX that can contain at most 
 EH> 65535).

I know, that's why I said it gets a little bit more complex doing it that way. 
I myself still use the 64K pages with 640x480x16bit modes exactly because in
Boralnd Pascal, I'm able to create lets say a 100KB variable in the heap, and
access it byte per byte or transfer not more than 64kb at a time..
Out of curiosity, would you have a copy of the special MOVE function to be able
to transfer more than 64KB at a time?

/======================================================================
| Orange County Usenet  Fidonet gateway                              
|                                                                      
| User email address:   Melanie.Baillot.noemail@webworldinc.com                                             
| FTN email: Melanie Baillot[RemoveThis]@f215.n163.z1.fidonet.org
| User FidoNet address: 1:163/215                                             
| Report abuse of this service to joejared@webworldinc.com