> > Am Samstag, 10. Januar 2004 21:32 schrieb [EMAIL PROTECTED]: > > > > For the sole purpose of being able to use a DOS application which > > > > drives my par-port from linux, I installed > > > > dosemu-1.0.2-bin.tgz and dosemu-freedos.bin.tgz > > > > to my red-hat6.2 to dir: > > > > /home/crg/DOSEMU/dosemu > > > > which gave me 4 sub-dirs: conf, freedos, bin, Xfonts. > > > > Claudia wrote: > > > Try newest version dosemu-1.1.99.1, where you don't have to run > > > dosemu as root for parport usage. > > > Runing programs as root is always a bad advice. > Please don't punish me as a beta tester for your Ver 1.1.99.1 ! Just tell me how to use the stable version 1.0.2 to drive par-port(s). Other users have done this.
> > OK ! I have to ask: how is it possible that with an application which is > > a decade old, I could have down loaded and installed a very out of date > > version, just 2 weeks ago ? > > > > My log shows:- > > http://dosemu.sourceforge.net/mirrors.txt > > it means that the mirrors still haven't picked up the newest versions, > sorry I haven't checked them recently. > > Have a look at www.dosemu.org > That's were I started which led to the 'mirrors' which are not updated. > -- there are more ways to find something. There are MANY ways to failure. Lets try to reduce them. Here's what I find: 1. when I try to download Ver 1.1.99.1 as advised, I get spam in my face: ->>> Browse SourceForge - Shop Thinkgeek - ... ... ->>> [_] Send me photos of my matches. Plus uncover the secrets of ->>> * Buy cool stuff from our network ->>> Lowest Price: $96.99 2. AFTER you have unpacked the tarball its contents: README.bindist tells you how the unpack the tar ball ! ? 3. Similarly the script 'dosemu' which is only available after unpacking its parent-tarball, has code to (possibly) unpack the tarball ! ? tar -xzf $SYSTEM_INSTALL_PATH/dosemu-bin.tgz .... tar -xzf $SYSTEM_INSTALL_PATH/dosemu-freedos-bin.tgz 4. Following the apparently out of date (invalid) documentation with Ver. 1.1.99.1: == select a new, clean directory; try as root: # tar -zxf dosemu-freedos-bin.tgz [EMAIL PROTECTED] mydos]# ls dosemu dosemu-1.1.99.1-bin.tgz dosemu-freedos-bin.tgz # tar -zxf dosemu-1.1.99.1-bin.tgz cd dosemu [EMAIL PROTECTED] dosemu]# ls FDchange.log README.bindist Xfonts bin conf dosemu freedos xdosemu [EMAIL PROTECTED] dosemu]# ./xdosemu Creating symbolic link for bootdirectory as /root/.dosemu/drives/c <-- OK ./dosemu: readlink: command not found <--? no such 'executable' ? ./dosemu: /../bin/dosemu.bin: No such file or directory exec: /../bin/dosemu.bin: cannot execute: No such file or directory --------------------------------- Indeed the command 'readlink' called from within script dosemu is unknown to my RH 6.2 installation. Perhaps this cause the problem of the existing bin/dosemu.bin not being accessible ? == Chris Glur. - 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
