One thing I've tried, with no success (unfortunately) is to "include" the disputed memory ranges on the command line for EMM386/QEMM. That's supposed to override it but then the VM doesn't boot.
What is the reason for pre-committing "ROM" space in the VM?
Oh, BTW, if you run "MSD" (Microsoft Diagnostics) from the DOS prompt, you get a slightly different view of upper memory:
  A000-BFFF:  "RAM" {Video of course}
  C000-C7FF:  "ROM" {same as below}
  C800-EFFF:  "RAM"  {different!}
  F000-FFFF:  "ROM"  {same}
  So, I did a little testing. If you use the following, I get 159k of upper memory at c800 (resulting in 726k of free memory):  device=emm386.exe noems i=c800-efff
  Now, if you try to enable EMS by doing something like the following (... 2048 RAM i=c800-efff), it bombs out, complaining that it can't set the page frame address. If you use MEMMAKER, always answer "NO" to the question about programs needing EMS. After running MEMMAKER, I get the following:
  Total under 1mb: 795k/69k used/726k free
  Largest program size: 617k
  Largest free UMB: 109k
  I guess you need the right incantation. Can anyone from Parallels Support comment on the lack of EMS support?
					 
				
			
			
			
		 
		
		
		
			
			
				Last edited: May 23, 2007