wwitt@adara.intel.com (06/13/91)
Greetings! Here are some miscellaneous questions regarding Windows 3, QEMM and DOS 5... 1) What is WINHIRAM.VXD? I'm running Windows 3 in 386 Enhanced Mode under QEMM and everything is fine. However, I discovered a file called WINHIRAM.VXD that came with QEMM. What is this thing? I have not been able to find any reference to this file in QEMM'a manual or README file. I looked at a hex dump of WINHIRAM.VXD and found a string that said something like "Win386 LoadHi Device". Is WINHIRAM.VXD the Windows equivalent of loadhi.sys and/or loadhi.com for DOS? If it is, I guess using WINHIRAM.VXD would only make sense when Windows is run in real mode? 2) DOS 5 in HMA Of course I ran out yesterday and picked up my copy of DOS 5 which I'm now running in HMA. Everything works so far. I'm curious though about how Windows handles DOS apps that use the HMA. Does Windows create virtual high memory areas for these programs, such that there is no conflict with DOS? I would guess that it doesn't and that programs that try to access the HMA are just out of luck. Does anybody know? 3) DOS 5's SmartDrive DOS 5 came with a new version of SmartDrive which is at least bigger, if not better, than the one that came with Windows. Does anybody know what's new and/or different in DOS 5's SmartDrive? Thanks for any info you can provide. Wolf => Wolf Witt, Design Engineer <=> You say there is a bug in this chip? <= => i860 Focus Group, Intel Corp. <=> No, no, you don't understand... <= => wwitt@smdvx1.intel.com <=> This is a feature! <= => Intel knows nothing about what I say or do, but they pay me anyway. <=
marcelo@deadzone.uucp (Marcelo Gallardo) (06/14/91)
wwitt@adara.intel.com writes: >1) What is WINHIRAM.VXD? >What is this thing? I have not been able to find any reference to this file >in QEMM'a manual or README file. I looked at a hex dump of WINHIRAM.VXD You didn't look hard enough. There is a Windows ReadMe file which will explain what this file does. >2) DOS 5 in HMA >Of course I ran out yesterday and picked up my copy of DOS 5 which I'm now >running in HMA. Everything works so far. I'm curious though about how Windows >handles DOS apps that use the HMA. Does Windows create virtual high memory >areas for these programs, such that there is no conflict with DOS? I would >guess that it doesn't and that programs that try to access the HMA are just >out of luck. Does anybody know? You got me. >3) DOS 5's SmartDrive >DOS 5 came with a new version of SmartDrive which is at least bigger, if not >better, than the one that came with Windows. Does anybody know what's new >and/or different in DOS 5's SmartDrive? Use the SmartDrive that came with DOS 5.0. It fixes a few problems the previous version had. It still has some problems with drives that have more than 1024 cyl, but they're working on it. -- Marcelo Gallardo marcelo%deadzone@princeton.edu Test and Evaluation Specialist ...!princeton!deadzone!marcelo Princeton University marcelo@sparcwood.princeton.edu Advanced Technologies and Applications (609) 258-5661
ed@odi.com (Ed Schwalenberg) (06/15/91)
In article <4686@inews.intel.com> wwitt@adara.intel.com writes:
Here are some miscellaneous questions regarding Windows 3, QEMM and DOS 5...
1) What is WINHIRAM.VXD?
When you run in 386Enhanced mode, Windows takes over the memory management
functions of QEMM. WINHIRAM.VXD is the "glue" that QEMM uses to tell Windows
what's mapped where, so Windows and QEMM can gracefully pass control of the
memory management hardware back and forth.