mirror of
https://github.com/reactos/reactos.git
synced 2024-12-27 09:34:43 +00:00
2693a26e3e
This fixes the age-long annoyance that wherever you ran a DOS program with NTVDM, its cmos.ram file would be created in the same current directory the DOS program was being started. This created at least two problems: - useless pollution of directories with cmos.ram files; - for installers, e.g. of Turbo C 1.x that enumerate the install files from their directories to be copied/extracted somewhere, the cmos.ram file could then be enumerated along and cause the installation to interrupt and/or fail. Now the cmos.ram file is created in the same directory NTVDM resides (usually in System32...). Also, debug-print out only loading errors instead of successes as well. |
||
---|---|---|
.. | ||
config | ||
dos | ||
ntvdm | ||
pifmgr | ||
samples | ||
vdmdbg | ||
wow16 | ||
asm16.cmake | ||
CMakeLists.txt | ||
README.txt |
Multiple Virtual DOS Machines - Directory description ===================================================== - config : Miscellaneous configuration files. - dos : 16-bit DOS components (kernel, drivers, apps...). - ntvdm : NT Virtual DOS Machine. - pifedit: ReactOS Program Information File Editor. - pifmgr : PIF Manager Icon Resource Library. - samples: Sample programs for NTVDM. - vdmdbg : Virtual DOS Machine debug helper DLL (from Wine). - wow16 : Win16 thunk files and components.