Stas Sergeev wrote: > Hello. > > Boszormenyi Zoltan wrote: > >> and I compiled dosemu-1.1.3.7 with the attached compile-time settings. > > Don't use setup-dosemu script for > now as it removes some important > options from compiletime-settings. > The "compiletime-settings" provided > by default would do in most cases > (or edit it manually).
So just "./default-configure ; make"? Btw, with a newer binutils spit this in the final link phase: lib/libarch_linux_mapping.a(mapself.o)(.text+0x671): In function `realloc_mapping_self': : `sys_errlist' is deprecated; use `strerror' or `strerror_r' instead > >> so it uses the image as a virtual disk instead of the "freedos" >> directory as a network drive. > > You can use also an msdos directory > as a network drive. I know. My intent was to install dos 6.22 but it refused to install into a network drive since the installation sequence recognizes that C: is not "in an acceptable format" and then "format c:" does not format a network drive so the install exits. I then created the disk image, which is over 6 MB after installing the 3 floppies. This refused to boot up. "strings dosdisk.bin | more" shows the correct directory contents and the readable file contents. (Like "Incorrect DOS version", "Non-System disk or disk error Replace and press any key when ready", etc.) I wanted to use the beforementioned $_hdimage "freedos dosdisk.bin" to copy the dos-6.22 files to C: but this does not work either. > For some reasons > I think it is better than the hdimage. > All you need is just to delete the > freedos files and copy the MS-DOS > ones (io.sys, msdos.sys and command.com). > In fact there is probably no need to > even erase the freedos files, as dosemu > recognizes the system files by their names, > and MS-DOS's files have a higher priority > when both DOSes are present. As you instructed, I copied io.sys, msdos.sys, command.com to ~/dosemu/freedos. It boots up happily, but DIR D: shows no D:\DOS directory and the io.sys and msdos.sys are also 0 bytes there. This seems to be a problem with dosemu-1.1.3.7's virtual disk handling. But wait, I created a new diskimage, booted up with dos-6.22 from network drive, d: is the image, copying and listing shows the correct files and sizes. Now where's the problem? When I have time, I will try to reproduce this. >> xdosemu now refuses to work. The boot.log attached. I copied the >> vga.pcf font to the >> proper place but did not bother to restart the font server yet. > I know the method I just did not bother to do it. There was the bigger problem with dos-6.22 not booting from virtual disk. Now I tried some games, some worked, some didn't. E.g. doom2 didn't, supaplex (a boulder dash clone) did. Now back to work. ;-) > Try this: > 1. in the directory you copied the vga.pcf > in, type "mkfontdir". > 2. in xterm type "xset fp rehash" to make > your X server to search for the new fonts. But I did neither this not "/etc/rc.d/init.d/xfs reload". Today morning I switched on the machine, the font is working, as I expected. Best regards, Zoltán Böszörményi - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
