Skip to contentSkip to conversation

1.2.0 binary install

DISCUSSION Bart Oldeman 2 participants 3 messages Jan 24, 2004 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 3 lines · Jan Willem Stumpel

No, I am not worried about the bandwidth, it's probably more my feeling that the dosemu C drive should be set up in a user's home directory with its own DOS in it.

that's what the "dosemu" script does (optionally) -- it sets up a bunch of symbolic links and a private copy of config.sys/autoexec.bat.

Quoted 6 lines
Quoted 1 line

1.2.0 is in sid now.

Thanks for the tip! This must have happened in the last few days. Pity that the Debian version does not have this handy ~/.dosemu/drives directory. In the RPM, apparently, there is a drives directory, but it is in /etc. I think it should be in the user´s home directory.

the /etc/dosemu/drives/c symlink in the RPM acts as a systemwide and backup symlink.

it's what is used if the user answers "none" to this question:

Going to install your private DOSEMU-freedos files into the directory $HOME/dosemu
Enter an empty string to confirm, a new path (the files will then be installed in a subdirectory named "dosemu" under that new path), or "none" (without the quotes) if you don't want a writable C-drive.

Essentially DOSEMU looks for boot directories and hdimages under ~/.dosemu/, then in /etc/dosemu, and then in /var/lib/dosemu.

The Debian config is just the same as it was in Debian's dosemu 1.0.2.1 -- I suppose Herbert Xu couldn't be bothered to change a lot again. It's always been a little different from what "make install" (or "./install_systemwide" when "make install" didn't work) did. Whatever is better is so much a question of taste that I don't want to go into that debate now :)

Quoted 11 lines
Quoted 6 lines

About the font problem. I honestly don't know what is going on. Between rc1 and rc2 I added some attempts to desperate get xset +fp ... working but apparently there's still something broken, but only for some people; for me it can find the font just fine. Seems to depend on the X server configuration. But I honestly don't know... I just can't reproduce.

I also messed about a lot with xset, xfontsel, xlsfonts but nothing helped. But I could finally make it work by changing Xfonts/fonts.dir in the binary distribution (it is generated the first time that xdosemu runs). Replaced the line

Quoted 5 lines

vga.pcf vga

with

vga.pcf -dosemu-vga-medium-r-normal--17-160-75-75-p-80-ibm-cp437

hmm, yes that could be it! And now I see why: the vga.pcf in the source install and in the rpm in generated dynamically (using bdftopcf from vga.bdf) but the one in the bindist is still simply copied from the old vga.pcf in etc/ in the source (which should be deleted really).

-- if you copy the installed vga.pcf.gz to your Xfonts dir and then run mkfontdir it will just go fine. Time to correct this bug. Thanks for nailing it down.

Bart

-
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

#2 lore raw
Quoted 3 lines · Bart Oldeman

that's what the "dosemu" script does (optionally) -- it sets up a bunch of symbolic links and a private copy of config.sys/ autoexec.bat.

So you set some kind of option on running the script? [at this point I thought of trying man dosemu]. I tried xdosemu -install ~/mytestdos but that does not work. Got some kind of help screen which did not mention the -install option talked about by man dosemu.

Quoted 2 lines

the /etc/dosemu/drives/c symlink [..] is used if the user answers "none" to this question:

I´m sorry, I did not actually install and run the rpm, just looked inside it. If questions are asked during the install, offering a writable C drive, that is of course just fine. The Debian package does not do it. OK.. I´m now going to try to actually install the rpm (using "alien").

Quoted 3 lines

Essentially DOSEMU looks for boot directories and hdimages under ~/.dosemu/, then in /etc/dosemu, and then in /var/lib/dosemu.

OK.. that clears it up.

Regards, Jan

-
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

#3 lore raw
Quoted 10 lines · Jan Willem Stumpel
Quoted 3 lines · Bart Oldeman

that's what the "dosemu" script does (optionally) -- it sets up a bunch of symbolic links and a private copy of config.sys/ autoexec.bat.

So you set some kind of option on running the script? [at this point I thought of trying man dosemu]. I tried xdosemu -install ~/mytestdos but that does not work. Got some kind of help screen which did not mention the -install option talked about by man dosemu.

What did the "some kind of help screen" say exactly?

The -install option works differently for the dosemu script that is part of the binary tarball than for the one in the RPM or created by make install.

The binary-tarball-dosemu works on the assumption that dosemu.bin lives ~/.dosemu/drives/c/../bin -- that's why its "install" isn't as flexible and it doesn't need to ask questions.

The RPM/"make install" dosemu has the position of dosemu.bin hardcoded in the script (e.g. /usr/bin/dosemu.bin or /usr/local/bin/dosemu.bin).

Bart