XCOPY update helped :-) / DPMI16BI problem
Eric Auer <[email protected]> Mon, 11 Nov 2002 05:43:58 +0100 (MET)
| Newsgroups | gmane.os.freedos.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, thanks for the hint! > completely rewritten by Rene Ableidinger > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/xcopy/rene/ The help screen is too long, but it works even better than the MS one. The problem is that the zip is not called xcopy* but rxcopy* - this is why I missed the update from beta 7 :-((. But works fine :-). On http://www.coli.uni-sb.de/~eric/stuff/soft/by-others/ xcopy.zip you can find a version which I have re-zipped to reflect the FreeDOS directory structure as expected by the installer program that we wanted. On the issue that all DPMI16BI programs crash when a BITDISK ramdisk exists (does not need to do anything more than existing): > Interesting. That might get us somewhere, and maybe the Turbo C++ 3.0 IDE > problems are related (also a DPMI16 program). How about XMSDSK instead of > BitDisk? I know that TDSK is worse (not "LCD.exe compatible"), but where can I get XMSDSK? What are the pros/cons compared to BITDISK / TDSK ? TDSK allows > 32 MB size. BITDISK requires you to format the disk in autoexec.bat, but allows resizing (data will be lost on resize). BITDISK uses almost no DOS RAM and allows small sector sizes (which I do not use, as 512 byte is kind of standard). The BITDISK root directory seems to auto-resize, but this should not harm DPMI16BI as long as the size is correctly reflected in the boot sector. And after all, DPMI16BI is not supposed to open all drives just because you run a program on one drive anyway! Eric