A very special driver I would have thoughtA graphics driver would naturally assume that it should address all available video RAM, so the 'special driver' would have to cut in before the graphics driver and somehow convince the graphics driver that there's less video RAM to address.
When playing around with RAM disks, I used to use boot.ini to set the maximum amount of physical system memory that the system could see/use, then a RAM disk driver (I used RAMDiskNT) would grab the remaining RAM and set that up with its own drive letter.
I wonder what sort of latency the 'video RAM masquerading as system RAM' would have.
