From: Ralph Alvy <ralvy@warpmail.net>
To: linux-msdos@vger.kernel.org
Subject: Re: The first dosemu-1.2.0 release candidate is available!
Date: Tue, 30 Sep 2003 20:17:26 -0700 [thread overview]
Message-ID: <bldh07$98g$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.44.0309301558110.4180-100000@enm-bo-lt.localdomain
Bart Oldeman wrote:
>
> no, the problem is that you don't have "readlink". But fortunately we can
> read a link using "ls" and, that combined with "sed" gives us a the poor
> man's readlink:
>
> BOOT_DIR_PATH=`ls -l $HOME/.dosemu/drives/c | sed 's/.* \([^
> ]*\)$/\1/'`/.. (line 245 of the script).
> Please try this instead of my previous workaround.
>
> Bart
I'm using RedHat 8 here. I went ahead and installed tetex to see what
happens. I then made a copy of the dosemu/bin directory, placing the copy
in usr/local/share/dosemu, which is where my msdos directory is. Otherwise
I found the script couldn't find ../dosemu.bin.
Okay, now I get this when I run ./xdosemu:
OR: Unable to allocate memory pool
ERROR: lowmem_alloc failed for 10240
ERROR: Unable to allocate memory pool
ERROR: lowmem_alloc failed for 10240
ERROR: Unable to allocate memory pool
ERROR: lowmem_alloc failed for 10240
ERROR: Unable to allocate memory pool
ERROR: lowmem_alloc failed for 10240
ERROR: Unable to allocate memory pool
ERROR: lowmem_alloc failed for 10240
ERROR: Unable to allocate memory pool
ERROR: lowmem_alloc failed for 10240
ERROR: Unable to allocate memory pool
ERROR: lowmem_alloc failed for 10240
ERROR: Unable to allocate memory pool
Then xdosemu finally loads, with this as the final line before the C prompt:
"Welcome to dosemu !"
next prev parent reply other threads:[~2003-10-01 3:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 22:21 The first dosemu-1.2.0 release candidate is available! Bart Oldeman
2003-09-30 12:21 ` A. Alper ATICI
2003-09-30 12:50 ` Bart Oldeman
2003-09-30 19:20 ` A. Alper ATICI
2003-09-30 19:35 ` Bart Oldeman
2003-09-30 13:50 ` Ralph Alvy
2003-09-30 14:35 ` Ralph Alvy
2003-09-30 15:02 ` Bart Oldeman
2003-09-30 16:15 ` Robert Komar
2003-09-30 17:13 ` Bart Oldeman
2003-09-30 17:57 ` Robert Komar
2003-10-01 7:21 ` Sylvain Petreolle
2003-10-01 3:17 ` Ralph Alvy [this message]
2003-10-01 10:50 ` Bart Oldeman
2003-10-01 21:30 ` Ralph Alvy
2003-09-30 14:37 ` Bart Oldeman
2003-10-01 14:12 ` A. Alper ATICI
2003-10-01 14:42 ` Bart Oldeman
2003-10-01 15:27 ` Ged Haywood
2003-10-01 19:56 ` Bart Oldeman
2003-10-02 22:10 ` Ralph Alvy
2003-10-02 23:33 ` Bart Oldeman
2003-10-03 0:06 ` Ralph Alvy
2003-10-03 1:38 ` Ralph Alvy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='bldh07$98g$1@sea.gmane.org' \
--to=ralvy@warpmail.net \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox