The first dosemu-1.2.0 release candidate is available!

The first dosemu-1.2.0 release candidate is available!

[Bart Oldeman]

Hi,

please have a look at
http://www.dosemu.org/stable
the version number is set to 1.1.99.1 (close to 1.2.0).

Some notes:
The -bin tarball and dosemu-freedos tarball (now updated to Beta9) work
like they did for 1.0.2.1
Alternatively, all-in-one RPMs (including FreeDOS) are available.
All the binaries are now dynamically linked and require glibc 2.2 (for
instance RH 7.0 or newer, SuSE 7.2 or newer, and Debian 3.0 or newer
should work) and X libraries.

The built-in command shell (comcom) is no longer used by default; FreeCOM
is used instead.

For those of you who have followed development, the 1.2 branch was forked
off version 1.1.5.3 and incorporates everything in 1.1.5.7 + some more,
but without the more experimental LFN support, filename NLS translations,
and bitmap fonts in text mode in xdosemu.

Some of the changes that happened since 1.1.5.7 are:
* mouse support in xterms and putty
* better support for keys in terminals
* new (hopefully clearer) layout of dosemu.conf
* the xterm and xdosemu title bars now show the DOS command that is
  executed
* fixes to work with NPTL (as present in Red Hat 9)
* various DPMI fixes
* fix copy/paste to xdosemu
* updated various parts of the documentation (HOWTO, EMUfailure)
  -- yes, I'm aware they aren't high quality but at least they are no
     longer wrong and reflect the current DOSEMU.
* fix Turkish keyboard

I'll get a full list of user-visable changes (wrt DOSEMU 1.0) and an
announcement ready for 1.2.0 proper.

Please let us know if there are any release critical bugs present --
regressions vs. 1.0.2.1, doesn't run at all, the RPM is braindead, or
similar.

Bart

Re: The first dosemu-1.2.0 release candidate is available!

[A. Alper ATICI]

On Sun, Sep 28, 2003 at 11:21:04PM +0100, Bart Oldeman wrote:
[...]
> 
> Please let us know if there are any release critical bugs present --
> regressions vs. 1.0.2.1, doesn't run at all, the RPM is braindead, or
> similar.
> 

Here's the first glitch from RPM, a path problem:

Please enter the name of a directory which contains a bootable
  DOS [ENTER = the default /usr/share/dosemu/freedos]

[....]

' to confirm/continue: yes
CONF aborted with:
*** error: /usr/local/share/dosemu does not exist
    ... giving up.

Re: The first dosemu-1.2.0 release candidate is available!

[Bart Oldeman]

On Tue, 30 Sep 2003, A. Alper ATICI wrote:

> On Sun, Sep 28, 2003 at 11:21:04PM +0100, Bart Oldeman wrote:
> [...]
> >
> > Please let us know if there are any release critical bugs present --
> > regressions vs. 1.0.2.1, doesn't run at all, the RPM is braindead, or
> > similar.
> >
>
> Here's the first glitch from RPM, a path problem:
>
> Please enter the name of a directory which contains a bootable
>   DOS [ENTER = the default /usr/share/dosemu/freedos]
>
> [....]
>
> ' to confirm/continue: yes
> CONF aborted with:
> *** error: /usr/local/share/dosemu does not exist
>     ... giving up.

I think your RPM installation clashes with the one from "make install".
The first is in /usr, the second in /usr/local.

can you check
`which dosemu.bin`
and remove it if it's /usr/local/bin/dosemu.bin?

Bart

Re: The first dosemu-1.2.0 release candidate is available!

[Ralph Alvy]

Bart Oldeman wrote:

> Hi,
> 
> please have a look at
> http://www.dosemu.org/stable
> the version number is set to 1.1.99.1 (close to 1.2.0).
> 
> Some notes:
> The -bin tarball and dosemu-freedos tarball (now updated to Beta9) work
> like they did for 1.0.2.1
> Alternatively, all-in-one RPMs (including FreeDOS) are available.
> All the binaries are now dynamically linked and require glibc 2.2 (for
> instance RH 7.0 or newer, SuSE 7.2 or newer, and Debian 3.0 or newer
> should work) and X libraries.
> 
> The built-in command shell (comcom) is no longer used by default; FreeCOM
> is used instead.
> 
> For those of you who have followed development, the 1.2 branch was forked
> off version 1.1.5.3 and incorporates everything in 1.1.5.7 + some more,
> but without the more experimental LFN support, filename NLS translations,
> and bitmap fonts in text mode in xdosemu.
> 
> Some of the changes that happened since 1.1.5.7 are:
> * mouse support in xterms and putty
> * better support for keys in terminals
> * new (hopefully clearer) layout of dosemu.conf
> * the xterm and xdosemu title bars now show the DOS command that is
>   executed
> * fixes to work with NPTL (as present in Red Hat 9)
> * various DPMI fixes
> * fix copy/paste to xdosemu
> * updated various parts of the documentation (HOWTO, EMUfailure)
>   -- yes, I'm aware they aren't high quality but at least they are no
>      longer wrong and reflect the current DOSEMU.
> * fix Turkish keyboard
> 
> I'll get a full list of user-visable changes (wrt DOSEMU 1.0) and an
> announcement ready for 1.2.0 proper.
> 
> Please let us know if there are any release critical bugs present --
> regressions vs. 1.0.2.1, doesn't run at all, the RPM is braindead, or
> similar.
Here's what I get after unpacking and running the 1.1.99.1 binary:

---

[ralvy@localhost dosemu]$ ./xdosemu
./xdosemu: line 1: readlink: command not found
./xdosemu: line 285: cd: /../Xfonts: No such file or directory

   You do not have the DOSEMU vga font installed and are running
   remote X. You need to install the vga font on your _local_ Xserver.
   Look at the readme for details. For now we start with an fixed font,
   which does not display all national characters correctly.
   ... be warned

./xdosemu: line 375: /../bin/dosemu.bin: No such file or directory
./xdosemu: line 375: exec: /../bin/dosemu.bin: cannot execute: No such file
or directory

---

But there is definitely a ../bin/dosemu.bin there.

Re: The first dosemu-1.2.0 release candidate is available!

[Ralph Alvy]

Ralph Alvy wrote:
> Here's what I get after unpacking and running the 1.1.99.1 binary:
> 
> ---
> 
> [ralvy@localhost dosemu]$ ./xdosemu
> ./xdosemu: line 1: readlink: command not found
> ./xdosemu: line 285: cd: /../Xfonts: No such file or directory
> 
>    You do not have the DOSEMU vga font installed and are running
>    remote X. You need to install the vga font on your _local_ Xserver.
>    Look at the readme for details. For now we start with an fixed font,
>    which does not display all national characters correctly.
>    ... be warned
> 
> ./xdosemu: line 375: /../bin/dosemu.bin: No such file or directory
> ./xdosemu: line 375: exec: /../bin/dosemu.bin: cannot execute: No such
> file or directory

Shouldn't the script execute

        cd ./Xfonts

instead of 

        cd /../Xfonts

And the same for 

        cd /../bin

Re: The first dosemu-1.2.0 release candidate is available!

[Bart Oldeman]

On Tue, 30 Sep 2003, Ralph Alvy wrote:

> Here's what I get after unpacking and running the 1.1.99.1 binary:
>
> ---
>
> [ralvy@localhost dosemu]$ ./xdosemu
> ./xdosemu: line 1: readlink: command not found
> ./xdosemu: line 285: cd: /../Xfonts: No such file or directory
>
>    You do not have the DOSEMU vga font installed and are running
>    remote X. You need to install the vga font on your _local_ Xserver.
>    Look at the readme for details. For now we start with an fixed font,
>    which does not display all national characters correctly.
>    ... be warned
>
> ./xdosemu: line 375: /../bin/dosemu.bin: No such file or directory
> ./xdosemu: line 375: exec: /../bin/dosemu.bin: cannot execute: No such file
> or directory
>
> ---
>
> But there is definitely a ../bin/dosemu.bin there.

Looks like the readlink utility isn't as standard as I assumed it to be --
newer distributions have it in coreutils (standard), Debain has had it for
a long time ind debianutils, but other distributions would only have it as
part of teTeX.

What distribution are you using?

try to replace the line
BOOT_DIR_PATH=`readlink $HOME/.dosemu/drives/c`/..
in the shell script named "dosemu" with the line
BOOT_DIR_PATH=`dirname $0`

I'll think about a better workaround.

Bart

Re: The first dosemu-1.2.0 release candidate is available!

[Bart Oldeman]

On Tue, 30 Sep 2003, Ralph Alvy wrote:

> Ralph Alvy wrote:
> > Here's what I get after unpacking and running the 1.1.99.1 binary:
> >
> > ---
> >
> > [ralvy@localhost dosemu]$ ./xdosemu
> > ./xdosemu: line 1: readlink: command not found
> > ./xdosemu: line 285: cd: /../Xfonts: No such file or directory
> >
> >    You do not have the DOSEMU vga font installed and are running
> >    remote X. You need to install the vga font on your _local_ Xserver.
> >    Look at the readme for details. For now we start with an fixed font,
> >    which does not display all national characters correctly.
> >    ... be warned
> >
> > ./xdosemu: line 375: /../bin/dosemu.bin: No such file or directory
> > ./xdosemu: line 375: exec: /../bin/dosemu.bin: cannot execute: No such
> > file or directory
>
> Shouldn't the script execute
>
>         cd ./Xfonts
>
> instead of
>
>         cd /../Xfonts
>
> And the same for
>
>         cd /../bin

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

Re: The first dosemu-1.2.0 release candidate is available!

[Robert Komar]

On Tue, 30 Sep 2003, Bart Oldeman wrote:

> On Tue, 30 Sep 2003, Ralph Alvy wrote:
>
> > Ralph Alvy wrote:
> > > Here's what I get after unpacking and running the 1.1.99.1 binary:
> > >
> > > ---
> > >
> > > [ralvy@localhost dosemu]$ ./xdosemu
> > > ./xdosemu: line 1: readlink: command not found
> > > ./xdosemu: line 285: cd: /../Xfonts: No such file or directory
> > >
> > >    You do not have the DOSEMU vga font installed and are running
> > >    remote X. You need to install the vga font on your _local_ Xserver.
> > >    Look at the readme for details. For now we start with an fixed font,
> > >    which does not display all national characters correctly.
> > >    ... be warned
> > >
> > > ./xdosemu: line 375: /../bin/dosemu.bin: No such file or directory
> > > ./xdosemu: line 375: exec: /../bin/dosemu.bin: cannot execute: No such
> > > file or directory
> >
> > Shouldn't the script execute
> >
> >         cd ./Xfonts
> >
> > instead of
> >
> >         cd /../Xfonts
> >
> > And the same for
> >
> >         cd /../bin
>
> 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.

Hi,
this doesn't look like it will work if there is a space somewhere in
the path.  If awk is available on every system, then how about this:

BOOT_DIR_PATH=`ls -l $HOME/.dosemu/drives/c | awk -F"-> " '{ print $2 }'`/..

It uses "-> " as the field separator instead of the space.  On my system,
the last '/' isn't required (the contents of the link already have a
trailing slash), but I guess it doesn't hurt to leave it there.

Another option would be for dosemu to roll its own version of readlink
based on readlink(2).  Something like:

#include <unistd.h>
#include <stdio.h>

int main(int argc, char** argv)
{
  char buf[BUFSIZ];

  if ((argc == 2) && (readlink(argv[1], buf, BUFSIZ) != -1))
    printf("%s\n", buf);

  return 0;
}

Cheers,
Rob Komar

Re: The first dosemu-1.2.0 release candidate is available!

[Bart Oldeman]

On Tue, 30 Sep 2003, Robert Komar wrote:

> this doesn't look like it will work if there is a space somewhere in
> the path.  If awk is available on every system, then how about this:
>
> BOOT_DIR_PATH=`ls -l $HOME/.dosemu/drives/c | awk -F"-> " '{ print $2 }'`/..
>
> It uses "-> " as the field separator instead of the space.  On my system,
> the last '/' isn't required (the contents of the link already have a
> trailing slash), but I guess it doesn't hurt to leave it there.

but this won't work if there is " -> " somewhere in $HOME ;)

How about
BOOT_DIR_PATH=`cd "$HOME/.dosemu/drives" && ls -l c | sed 's/.* -> //'`/..
in this case the source filename in "ls" won't have spaces.

That'll work as long as no user name or group name or month (in some
language) has " -> " in it.

An extra readline binary would be another headache -- where to find it?

perl is another option, but IIRC not completely standard, at least I
received patches a while ago to remove perl dependencies.

Bart

Re: The first dosemu-1.2.0 release candidate is available!

[Robert Komar]

On Tue, 30 Sep 2003, Bart Oldeman wrote:

> On Tue, 30 Sep 2003, Robert Komar wrote:
>
> > this doesn't look like it will work if there is a space somewhere in
> > the path.  If awk is available on every system, then how about this:
> >
> > BOOT_DIR_PATH=`ls -l $HOME/.dosemu/drives/c | awk -F"-> " '{ print $2 }'`/..
> >
> > It uses "-> " as the field separator instead of the space.  On my system,
> > the last '/' isn't required (the contents of the link already have a
> > trailing slash), but I guess it doesn't hurt to leave it there.
>
> but this won't work if there is " -> " somewhere in $HOME ;)
>
> How about
> BOOT_DIR_PATH=`cd "$HOME/.dosemu/drives" && ls -l c | sed 's/.* -> //'`/..
> in this case the source filename in "ls" won't have spaces.
>
> That'll work as long as no user name or group name or month (in some
> language) has " -> " in it.

Yes, I think this will work.  Replacing '{ print $2 }' with '{ print $NF }'
in the awk script would also work as well, but it's six of one and half a
dozen of the other.  Whichever you're happier to maintain.

Cheers,
Rob Komar

Re: The first dosemu-1.2.0 release candidate is available!

[A. Alper ATICI]

On Tue, Sep 30, 2003 at 01:50:04PM +0100, Bart Oldeman wrote:
> 
> I think your RPM installation clashes with the one from "make install".
> The first is in /usr, the second in /usr/local.
> 
> can you check
> `which dosemu.bin`
> and remove it if it's /usr/local/bin/dosemu.bin?
> 

Seems I missed that one remnant from "make install" :-I

Anyway, glitch is bogus.

Re: The first dosemu-1.2.0 release candidate is available!

[Bart Oldeman]

On Tue, 30 Sep 2003, A. Alper ATICI wrote:

> On Tue, Sep 30, 2003 at 01:50:04PM +0100, Bart Oldeman wrote:
> >
> > I think your RPM installation clashes with the one from "make install".
> > The first is in /usr, the second in /usr/local.
> >
> > can you check
> > `which dosemu.bin`
> > and remove it if it's /usr/local/bin/dosemu.bin?
> >
>
> Seems I missed that one remnant from "make install" :-I

Well it should be possible to run the two side-by-side. I'm changing the
dosemu script now to specifically execute /usr/bin/dosemu.bin
($(bindir)/dosemu.bin in general).

> Anyway, glitch is bogus.

Yes, you're right; I already noticed that before you and the glitch was
removed in 1.2.0rc1 (but your dosemu.bin was probably an older one).

Bart

Re: The first dosemu-1.2.0 release candidate is available!

[Ralph Alvy]

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 !"

 

Re: The first dosemu-1.2.0 release candidate is available!

[Sylvain Petreolle]

Be sure I see and understand the ';)'. Everyone that creates a file
containing '>' in its name is calling for trouble and should know what
to do with it.

> > It uses "-> " as the field separator instead of the space.  On my
system,
> > the last '/' isn't required (the contents of the link already have
a
> > trailing slash), but I guess it doesn't hurt to leave it there.
 
> but this won't work if there is " -> " somewhere in $HOME ;)

> That'll work as long as no user name or group name or month (in some
> language) has " -> " in it.


=====
Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net)
 ICQ #170597259
Say NO to software patents
Dites NON aux brevets logiciels

"What if tomorrow the War could be over ?" Morpheus, in "Reloaded".

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: The first dosemu-1.2.0 release candidate is available!

[Bart Oldeman]

On Tue, 30 Sep 2003, Ralph Alvy wrote:

> 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

you should upgrade your helper utitilities. By plugging into
/usr/local/share/dosemu it is easy to forget something; in that case it
would be easier to install the RPM instead of the binary tarball, since
the tarball is meant for pure local installation under $HOME.

in the bin tarball you should find generic.com and some symbolic links
(lredir, xmode and so on) in the dosemu/freedos/dosemu directory.
In your case these (probably) need to be copied to
/usr/local/share/dosemu/freedos/dosemu

Bart

Re: The first dosemu-1.2.0 release candidate is available!

[A. Alper ATICI]

Hi,

> Please let us know if there are any release critical bugs present --
> regressions vs. 1.0.2.1, doesn't run at all, the RPM is braindead, or
> similar.
> 

I have this machine running 2.6.0-test6 kernel with 
sleep-inside-spinlock checking enabled.
Some time after starting dosemu, the kernel begins to display debug 
messages and continues sporadically, sometimes loops per second or so.

Now that it's a test kernel, I'm not sure if this is a problem of dosemu 
or not, but one thing for sure is that it stops once dosemu exits.

Here is a snapshot of the messages:

Debug: sleeping function called from invalid context at 
include/asm/uaccess.h:473
in_atomic():0, irqs_disabled():1
Call Trace:
 [<c011b15e>] __might_sleep+0x9e/0xc0
 [<c010bdd0>] save_v86_state+0x70/0x200
 [<c01095ce>] work_notifysig_v86+0x6/0x14
 [<c010957b>] syscall_call+0x7/0xb

Debug: sleeping function called from invalid context at 
include/asm/uaccess.h:473
in_atomic():0, irqs_disabled():1
Call Trace:
 [<c011b15e>] __might_sleep+0x9e/0xc0
 [<c010bdd0>] save_v86_state+0x70/0x200
 [<c010b3e7>] do_IRQ+0x107/0x140
 [<c01095ce>] work_notifysig_v86+0x6/0x14
 [<c010957b>] syscall_call+0x7/0xb

Debug: sleeping function called from invalid context at 
include/asm/uaccess.h:473
in_atomic():0, irqs_disabled():1
Call Trace:
 [<c011b15e>] __might_sleep+0x9e/0xc0
 [<c010bdd0>] save_v86_state+0x70/0x200
 [<c010a5b0>] do_general_protection+0x0/0xb0
 [<c01095ce>] work_notifysig_v86+0x6/0x14
 [<c010957b>] syscall_call+0x7/0xb

Re: The first dosemu-1.2.0 release candidate is available!

[Bart Oldeman]

On Wed, 1 Oct 2003, A. Alper ATICI wrote:

> Now that it's a test kernel, I'm not sure if this is a problem of dosemu
> or not, but one thing for sure is that it stops once dosemu exits.

yes, I've seen this myself too. It's most likely not a DOSEMU problem but
an in-kernel vm86 problem (xfree86 suffers too).

> Debug: sleeping function called from invalid context at
> include/asm/uaccess.h:473
> in_atomic():0, irqs_disabled():1
> Call Trace:
>  [<c011b15e>] __might_sleep+0x9e/0xc0
>  [<c010bdd0>] save_v86_state+0x70/0x200
>  [<c01095ce>] work_notifysig_v86+0x6/0x14
>  [<c010957b>] syscall_call+0x7/0xb

Some kernel developers are looking at this -- see
http://lkml.org/lkml/2003/8/18/209

Another thing that is broken on 2.6.0test is DPMI. That's a DOSEMU problem
and fixed in the CVS now (will be fixed in 1.2.0 proper).

Bart

Re: The first dosemu-1.2.0 release candidate is available!

[Ged Haywood]

Hi there,

On Wed, 1 Oct 2003, Bart Oldeman wrote:

> Another thing that is broken on 2.6.0test is DPMI. That's a DOSEMU problem
> and fixed in the CVS now (will be fixed in 1.2.0 proper).

No rush about this, but any idea when 1.2.0 will be out?
I need DPMI to work but I can wait until the stable release.

73,
Ged.

Re: The first dosemu-1.2.0 release candidate is available!

[Bart Oldeman]

On Wed, 1 Oct 2003, Ged Haywood wrote:

> On Wed, 1 Oct 2003, Bart Oldeman wrote:
>
> > Another thing that is broken on 2.6.0test is DPMI. That's a DOSEMU problem
> > and fixed in the CVS now (will be fixed in 1.2.0 proper).
>
> No rush about this, but any idea when 1.2.0 will be out?
> I need DPMI to work but I can wait until the stable release.

hopefully next weekend, there are some problems relating to the binaries
(RPM/tarballs) to flush out but nothing fundamental -- well except for
that kernel 2.6.0test problem but only a small and safe fix is required to fix
that.

Bart

Re: The first dosemu-1.2.0 release candidate is available!

[Ralph Alvy]

Bart Oldeman wrote:

> On Tue, 30 Sep 2003, Ralph Alvy wrote:
> 
>> 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
> 
> you should upgrade your helper utitilities. By plugging into
> /usr/local/share/dosemu it is easy to forget something; in that case it
> would be easier to install the RPM instead of the binary tarball, since
> the tarball is meant for pure local installation under $HOME.
> 
> in the bin tarball you should find generic.com and some symbolic links
> (lredir, xmode and so on) in the dosemu/freedos/dosemu directory.
> In your case these (probably) need to be copied to
> /usr/local/share/dosemu/freedos/dosemu

Ah, yes. Forgot about those. Copied them into
/usr/local/share/dosemu/msdos/dosemu and all is well now.

Regarding the RPM installation, I was afraid of doing that, not knowing
where the RPM would place various stuff. I may do that next after making
sure I have a backup. I'd much rather have RPM installs for everything on
this system. Just never did that with dosemu, though.

Re: The first dosemu-1.2.0 release candidate is available!

[Ralph Alvy]

Bart Oldeman wrote:

> Hi,
> 
> please have a look at
> http://www.dosemu.org/stable
> the version number is set to 1.1.99.1 (close to 1.2.0).
> 
> Some notes:
> The -bin tarball and dosemu-freedos tarball (now updated to Beta9) work
> like they did for 1.0.2.1
> Alternatively, all-in-one RPMs (including FreeDOS) are available.
> All the binaries are now dynamically linked and require glibc 2.2 (for
> instance RH 7.0 or newer, SuSE 7.2 or newer, and Debian 3.0 or newer
> should work) and X libraries.
> 
> The built-in command shell (comcom) is no longer used by default; FreeCOM
> is used instead.
> 
> For those of you who have followed development, the 1.2 branch was forked
> off version 1.1.5.3 and incorporates everything in 1.1.5.7 + some more,
> but without the more experimental LFN support, filename NLS translations,
> and bitmap fonts in text mode in xdosemu.
> 
> Some of the changes that happened since 1.1.5.7 are:
> * mouse support in xterms and putty
> * better support for keys in terminals
> * new (hopefully clearer) layout of dosemu.conf
> * the xterm and xdosemu title bars now show the DOS command that is
>   executed
> * fixes to work with NPTL (as present in Red Hat 9)
> * various DPMI fixes
> * fix copy/paste to xdosemu
> * updated various parts of the documentation (HOWTO, EMUfailure)
>   -- yes, I'm aware they aren't high quality but at least they are no
>      longer wrong and reflect the current DOSEMU.
> * fix Turkish keyboard
> 
> I'll get a full list of user-visable changes (wrt DOSEMU 1.0) and an
> announcement ready for 1.2.0 proper.
> 
> Please let us know if there are any release critical bugs present --
> regressions vs. 1.0.2.1, doesn't run at all, the RPM is braindead, or
> similar.
> 
> Bart

I decided to rename all directories that contain dosemu and freedos (from my
old 1.1.5 installation, and install the new RPM. I notice the following
error when attempting the new xdosemu:

ERROR: X: Unable to open font "vga"ERROR: , trying "vga"...
ERROR: X: Unable to open font "vga"ERROR: , trying "9x15"...

Everything else seems to be working. Just can't get VGA working over here.
I'm booting dosemu from an MSDOS directory that's installed in 

        /usr/share/dosemu

like this

        /usr/share/dosemu/msdos

Re: The first dosemu-1.2.0 release candidate is available!

[Bart Oldeman]

On Thu, 2 Oct 2003, Ralph Alvy wrote:

> ERROR: X: Unable to open font "vga"ERROR: , trying "vga"...
> ERROR: X: Unable to open font "vga"ERROR: , trying "9x15"...
>
> Everything else seems to be working. Just can't get VGA working over here.
> I'm booting dosemu from an MSDOS directory that's installed in
>
>         /usr/share/dosemu
>
> like this
>
>         /usr/share/dosemu/msdos

I can't reproduce your font problem. Please try the following:
/usr/bin/xdosemu
(explicitly use /usr/bin)

if that doesn't give you the right font then try, *after* running xdosemu,
some commands, like this

/usr/bin/xdosemu
xlsfonts -fn vga
xset q

and please let me know what the output is.

Bart

Re: The first dosemu-1.2.0 release candidate is available!

[Ralph Alvy]

Bart Oldeman wrote:
> I can't reproduce your font problem. Please try the following:
> /usr/bin/xdosemu
> (explicitly use /usr/bin)

Same errors.

> if that doesn't give you the right font then try, *after* running xdosemu,
> some commands, like this
> 
> /usr/bin/xdosemu
> xlsfonts -fn vga
> xset q
> 
> and please let me know what the output is.
> 
> Bart

Okay, here's the output, which seems to show my Fonts are being looked for
in my old 1.1.5 fonts directory. Is there a way for me to undo that old
reference you see below?

[ralvy@localhost ralvy]$ xlsfonts -fn vga
vga
[ralvy@localhost ralvy]$ xset q
Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000000
  auto repeat delay:  660    repeat rate:  25
  auto repeating keys:  00ffffffdffffbbf
                        fa9fffffffdfe5ff
                        ffffffffffffffff
                        ffffffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  2/1    threshold:  4
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  0    cycle:  600
Colors:
  default colormap:  0x20    BlackPixel:  0    WhitePixel:  16777215
Font Path:
  /usr/local/share/dosemu/msdos/../Xfonts,unix/:7100
Bug Mode: compatibility mode is disabled
DPMS (Energy Star):
  Standby: 1200    Suspend: 1800    Off: 2400
  DPMS is Disabled
Font cache:
  hi-mark (KB): 1024  low-mark (KB): 768  balance (%): 70

Re: The first dosemu-1.2.0 release candidate is available!

[Ralph Alvy]

Bart Oldeman wrote:

> On Thu, 2 Oct 2003, Ralph Alvy wrote:
> 
>> ERROR: X: Unable to open font "vga"ERROR: , trying "vga"...
>> ERROR: X: Unable to open font "vga"ERROR: , trying "9x15"...
>>
>> Everything else seems to be working. Just can't get VGA working over
>> here. I'm booting dosemu from an MSDOS directory that's installed in
>>
>>         /usr/share/dosemu
>>
>> like this
>>
>>         /usr/share/dosemu/msdos
> 
> I can't reproduce your font problem. Please try the following:
> /usr/bin/xdosemu
> (explicitly use /usr/bin)
> 
> if that doesn't give you the right font then try, *after* running xdosemu,
> some commands, like this
> 
> /usr/bin/xdosemu
> xlsfonts -fn vga
> xset q
> 
> and please let me know what the output is.
> 
> Bart

Okay, I read the help screen on xset and did

        xset fp default

Now all is well with my xdosemu fonts.