Hello, I would like to access Memdisk (as a RAM disk) from my application in pure protected mode. "Pure" means that I don't' want to have any switches to real mode even if these switches are automatically handled by Memdisk interrupt stubs. The reason is that my application is running on top of Virtual Machine Monitor (VMM). This virtualization layer is quite simple and doesn't tolerate any transitions to real mode. Thanks. Best regards, Alex
>I would like to access Memdisk (as a RAM disk) from my application in > pure protected mode. "Pure" means that I don't' want to have any > switches to real mode even if these switches are automatically handled > by Memdisk interrupt stubs. The reason is that my application isrunning> on top of Virtual Machine Monitor (VMM). This virtualization layer is > quite simple and doesn't tolerate any transitions to real mode.Sorry, its me again. I forgot to ask the question: Is it possible to access Memdisk in that way? Does Memdisk API provides such capability?
Loginov Alexander wrote:> Hello, > > I would like to access Memdisk (as a RAM disk) from my application in > pure protected mode. "Pure" means that I don't' want to have any > switches to real mode even if these switches are automatically handled > by Memdisk interrupt stubs. The reason is that my application is running > on top of Virtual Machine Monitor (VMM). This virtualization layer is > quite simple and doesn't tolerate any transitions to real mode. >This is quite possible -- after all, MEMDISK is really nothing other than a chunk of memory. What you want to do is stash away the MEMDISK info structure pointer immediately after boot, while still in real mode. That structure contains the location and size of the MEMDISK in high memory. -hpa