DOSEMU 1.1.4.15 for testing.

DOSEMU 1.1.4.15 for testing.

[Bart Oldeman]

Hi,

I've put a new patchset (1.1.4.15) at
http://www.dosemu.org/testing

if you were using 1.1.4.13 before then please check if this one fixes your
compilation fixes, and also please let us know if there are any new
problems -- if everything is fine then I'll make this one 1.1.5.

Bart

Re: DOSEMU 1.1.4.15 for testing.

[Stephen Lee]

On Sat, 2003-03-15 at 18:06, Bart Oldeman wrote:
> Hi,
> 
> I've put a new patchset (1.1.4.15) at
> http://www.dosemu.org/testing
> 
> if you were using 1.1.4.13 before then please check if this one fixes your
> compilation fixes, and also please let us know if there are any new
> problems -- if everything is fine then I'll make this one 1.1.5.
> 

No problems compiling under Redhat 7.2. However, as mentioned in another
thread, numlock within xdosemu only works if numlock is off before
starting xdosemu when displayed remotely via VNC. If the xdosemu session
is displayed remotely to another X workstation without using VNC, the
numlock problem does not occur. Based on brief testing, everything else
seems to work fine with Foxpro2.6.

Stephen

Re: DOSEMU 1.1.4.15 for testing.

[Bart Oldeman]

On 15 Mar 2003, Stephen Lee wrote:

> On Sat, 2003-03-15 at 18:06, Bart Oldeman wrote:
> > Hi,
> >
> > I've put a new patchset (1.1.4.15) at
> > http://www.dosemu.org/testing
> >
> > if you were using 1.1.4.13 before then please check if this one fixes your
> > compilation fixes, and also please let us know if there are any new
> > problems -- if everything is fine then I'll make this one 1.1.5.
> >
>
> No problems compiling under Redhat 7.2. However, as mentioned in another
> thread, numlock within xdosemu only works if numlock is off before
> starting xdosemu when displayed remotely via VNC. If the xdosemu session
> is displayed remotely to another X workstation without using VNC, the
> numlock problem does not occur. Based on brief testing, everything else
> seems to work fine with Foxpro2.6.

I've never used VNC so I really cannot say much about this specific
situation; it might be problematic for DOSEMU to ask for the numlock
state via VNC, it might even be a VNC problem and not a DOSEMU problem.
At least the workaround isn't hard.

what you also could try:
* set $_X_keycode=(0) in your .dosemurc or dosemu.conf
or
* run an X server on the Windows site such as Cygwin xfree86.

Bart

Re: DOSEMU 1.1.4.15 for testing.

[Stephen Lee]

On Sat, 2003-03-15 at 18:49, Bart Oldeman wrote:
> I've never used VNC so I really cannot say much about this specific
> situation; it might be problematic for DOSEMU to ask for the numlock
> state via VNC, it might even be a VNC problem and not a DOSEMU problem.
> At least the workaround isn't hard.
> 
> You also could try:
> * set $_X_keycode=(0) in your .dosemurc or dosemu.conf
> or
> * run an X server on the Windows site such as Cygwin xfree86.

set $_X_keycode=(0) makes no difference and adding Cygwin xfree86 to 20
offsite workstations is too ambitious for me. I guess I'll just have to
train users to turn off numlock before starting xdosemu - a minor
inconvenience considering the coolness of being able to use a DOS
program remotely ;-)

Thanks,
Stephen

Re: [Dosemu-devel]DOSEMU 1.1.4.15 for testing.

[Ant]

I mailed this list some months ago with a way old version. Hopefully Im
up to speed this time ;)

Redhat 8.0, standard redhat 2.4.18 kernel.. 

make[2]: Entering directory `/home/ant/dosemu-1.1.4/src'
gcc -c -I/usr/X11R6/include -MP -MMD
-I/home/ant/dosemu-1.1.4/src/plugin/include
-I/home/ant/dosemu-1.1.4/src/include -I/usr/include/slang -Wall
-Wstrict-prototypes -Wmissing-declarations -Wnested-externs -O2
-fomit-frame-pointer -fno-strict-aliasing -mcpu=i686 -pipe  -o emu.o
emu.c
emu.c: In function `leavedos':
emu.c:501: too many arguments to function `port_exit'
make[2]: *** [emu.o] Error 1
make[2]: Leaving directory `/home/ant/dosemu-1.1.4/src'
make[1]: *** [emu] Error 2
make[1]: Leaving directory `/home/ant/dosemu-1.1.4/src'
make: *** [default] Error 2
[root@ant dosemu-1.1.4]# cat ChangeLog |grep 1.1.4.15
2003/03/15 ver 1.1.4.15 unofficial pre-release

Ant

On Sun, 2003-03-16 at 12:36, Bart Oldeman wrote:
> Hi,
> 
> I've put a new patchset (1.1.4.15) at
> http://www.dosemu.org/testing
> 
> if you were using 1.1.4.13 before then please check if this one fixes your
> compilation fixes, and also please let us know if there are any new
> problems -- if everything is fine then I'll make this one 1.1.5.
> 
> Bart
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:Crypto Challenge is now open! 
> Get cracking and register here for some mind boggling fun and 
> the chance of winning an Apple iPod:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> _______________________________________________
> Dosemu-devel mailing list
> Dosemu-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dosemu-devel

Re: [Dosemu-devel]DOSEMU 1.1.4.15 for testing.

[Ant]

Sorry guys, ive investigated further, and my source tree seems to have
somehow become corrupted. I installed a fresh 1.1.4 and patched up to
.15 and it compiled OK this time around.

Ant

On Sun, 2003-03-16 at 13:44, Ant wrote:
> I mailed this list some months ago with a way old version. Hopefully Im
> up to speed this time ;)
> 
> Redhat 8.0, standard redhat 2.4.18 kernel.. 
> 
> make[2]: Entering directory `/home/ant/dosemu-1.1.4/src'
> gcc -c -I/usr/X11R6/include -MP -MMD
> -I/home/ant/dosemu-1.1.4/src/plugin/include
> -I/home/ant/dosemu-1.1.4/src/include -I/usr/include/slang -Wall
> -Wstrict-prototypes -Wmissing-declarations -Wnested-externs -O2
> -fomit-frame-pointer -fno-strict-aliasing -mcpu=i686 -pipe  -o emu.o
> emu.c
> emu.c: In function `leavedos':
> emu.c:501: too many arguments to function `port_exit'
> make[2]: *** [emu.o] Error 1
> make[2]: Leaving directory `/home/ant/dosemu-1.1.4/src'
> make[1]: *** [emu] Error 2
> make[1]: Leaving directory `/home/ant/dosemu-1.1.4/src'
> make: *** [default] Error 2
> [root@ant dosemu-1.1.4]# cat ChangeLog |grep 1.1.4.15
> 2003/03/15 ver 1.1.4.15 unofficial pre-release
> 
> Ant
> 
> On Sun, 2003-03-16 at 12:36, Bart Oldeman wrote:
> > Hi,
> > 
> > I've put a new patchset (1.1.4.15) at
> > http://www.dosemu.org/testing
> > 
> > if you were using 1.1.4.13 before then please check if this one fixes your
> > compilation fixes, and also please let us know if there are any new
> > problems -- if everything is fine then I'll make this one 1.1.5.
> > 
> > Bart
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by:Crypto Challenge is now open! 
> > Get cracking and register here for some mind boggling fun and 
> > the chance of winning an Apple iPod:
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> > _______________________________________________
> > Dosemu-devel mailing list
> > Dosemu-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/dosemu-devel
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:Crypto Challenge is now open! 
> Get cracking and register here for some mind boggling fun and 
> the chance of winning an Apple iPod:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> _______________________________________________
> Dosemu-devel mailing list
> Dosemu-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dosemu-devel

Re: DOSEMU 1.1.4.15 for testing.

[Sergey Suleymanov]

>>>>> Bart Oldeman writes:

        One more little bug - SLang prompts "[ctrl]", etc. don't
        disappeared when key is released.

--- /usr/src/dosemu-1.1.4.15/src/plugin/term/keyb_slang.c	Mon Mar 17 10:44:06 2003
+++ /usr/src/dosemu-1.1.4.15.my/src/plugin/term/keyb_slang.c	Mon Mar 17 09:58:10 2003
@@ -1316,9 +1316,7 @@
 		if (!(scan&0x80000000)) {
 			slang_send_scancode(keyb_state.Shift_Flags | scan, symbol);
 		}
-		else {
-			do_slang_special_keys(scan);
-		}
+		do_slang_special_keys(scan);
 	}
 }
 

-- 
  Sergey Suleymanov

Re: DOSEMU 1.1.4.15 for testing.

[Grigory Batalov]

[-- Attachment #1: Type: text/plain, Size: 661 bytes --]

On Sat, 15 Mar 2003 21:06:17 -0500 (EST)
Bart Oldeman <oldeman@math.ohio-state.edu> wrote:

> I've put a new patchset (1.1.4.15) at
> http://www.dosemu.org/testing
> 
> if you were using 1.1.4.13 before then please check if this one fixes your
> compilation fixes, and also please let us know if there are any new
> problems -- if everything is fine then I'll make this one 1.1.5.

  I'm sorry, I forgot to inform you that I changed cp866
  font type from "proportional" to "cell", so at least
  letter "p" should be changed to "c" in dosemu.alias.

  Also cp1125 fonts aliases could be added to dosemu.alias.
  (Look into attached patch.)

--
 Grigory Batalov.

[-- Attachment #2: dosemu-1.1.4.15-alt-fonts_alias.patch --]
[-- Type: text/plain, Size: 716 bytes --]

diff -ruN dosemu-1.1.4.orig/etc/dosemu.alias dosemu-1.1.4/etc/dosemu.alias
--- dosemu-1.1.4.orig/etc/dosemu.alias	Wed Dec 18 04:36:44 2002
+++ dosemu-1.1.4/etc/dosemu.alias	Mon Mar 17 02:25:53 2003
@@ -1,4 +1,6 @@
 vga          -dosemu-vga-medium-r-normal--17-160-75-75-p-80-ibm-cp437
 vga11x19     -dosemu-vga-medium-r-normal--19-190-75-75-c-100-ibm-cp437
-vgacyr       -dosemu-vga-medium-r-normal--17-160-75-75-p-80-ibm-cp866
+vgacyr       -dosemu-vga-medium-r-normal--17-160-75-75-c-80-ibm-cp866
 vga10x20     -dosemu-vga-medium-r-normal--20-200-75-75-c-100-ibm-cp866
+vga-ua       -dosemu-vga-medium-r-normal--17-160-75-75-c-80-ibm-cp1125
+vga10x20-ua  -dosemu-vga-medium-r-normal--20-200-75-75-c-100-ibm-cp1125

Re: DOSEMU 1.1.4.15 for testing.

[Ged Haywood]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1812 bytes --]

Hi there,

On Sat, 15 Mar 2003, Bart Oldeman wrote:

> I've put a new patchset (1.1.4.15) at
> http://www.dosemu.org/testing

hurricane:~$ >>> gcc -v
Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
hurricane:~$ >>> uname -a
Linux hurricane 2.4.19 #6 Fri Mar 7 15:31:31 GMT 2003 i586 unknown
hurricane:~$ >>> 

I hope you'll do something about the instructions for building it
before you put it out as 1.1.5.  It's very confusing because there's
so much of it that's out of date and inconsistent.  It doesn't need to
be completely rewritten but if you put some up-to-date instructions in
a file called INSTALL then people who are used to doing

./configure
make
make install

will be more much comfortable.

The build scripts seem to be very fragile, I changed the directories
in the compiletime-options and although everything was supposed to be
in my home directory the make install failed with permission problems
unless I was root.  It asked me if it was OK to use /home/ged/dosemu
and I said no, use /home/ged/src/dosemu and it said OK, then I'll use
/home/ged/src/dosemu/dosemu so I tried to stop that.  The script then
had trouble because it had created ~/.dosemu but hadn't done other
stuff that was needed.  When finally I got it figured out it failed
again because the symlinks in /usr/local/share/dosemu/freedos/dosemu
already existed.  I had to keep doing rm -rf on a few directories to
get a build I was happy with.  It grumbled about not having freedos
even though I'd set 'fdtarball none' in the compiletime-settings.

Having said that once it did compile (2.4.19) it started and ran quite
a few things fine, but the attached pager (LIST.COM) crashes dosemu
very reliably under X on my system.

HTH

73,
Ged.

[-- Attachment #2: pager crashes dosemu --]
[-- Type: APPLICATION/x-gzip, Size: 10240 bytes --]

Re: DOSEMU 1.1.4.15 for testing.

[Bart Oldeman]

On Tue, 18 Mar 2003, Ged Haywood wrote:

> I hope you'll do something about the instructions for building it
> before you put it out as 1.1.5.  It's very confusing because there's
> so much of it that's out of date and inconsistent.  It doesn't need to
> be completely rewritten but if you put some up-to-date instructions in
> a file called INSTALL then people who are used to doing
>
> ./configure
> make
> make install
>
> will be more much comfortable.

This is exactly what the file "QuickStart" is supposed to do -- please
tell me what you want to have changed in QuickStart -- I may be blind but
the instructions are up-to-date as far as I know.

> The build scripts seem to be very fragile, I changed the directories
> in the compiletime-options and although everything was supposed to be
> in my home directory the make install failed with permission problems
> unless I was root.

Shouldn't be and I just tested it. You must clean the tree and recompile
(and reconfigure) DOSEMU if you fiddle with the compiletime-settings
though, but maybe a Makefile rule could be added to do that
automatically.

> It asked me if it was OK to use /home/ged/dosemu
> and I said no, use /home/ged/src/dosemu and it said OK, then I'll use
> /home/ged/src/dosemu/dosemu so I tried to stop that.  The script then
> had trouble because it had created ~/.dosemu but hadn't done other
> stuff that was needed.  When finally I got it figured out it failed
> again because the symlinks in /usr/local/share/dosemu/freedos/dosemu
> already existed.  I had to keep doing rm -rf on a few directories to
> get a build I was happy with.

There are two things here you talk about and I can't quite follow you here
(to be able to correct the problem I must be able to reproduce your
problems and without telling exactly what you did that is very difficult).

a) problems with 'make install'
b) problems running dosemu for the first time.

One problem with a symlink may be solved using:
--- dosemu-1.1.4.15/src/arch/linux/Makefile.main	Mon Mar 17 11:26:13 2003
+++ dosemu-1.1.4.16/src/arch/linux/Makefile.main	Mon Mar 17 11:27:58 2003
@@ -273,8 +273,8 @@
 	    $(INSTALL) -d $(DESTDIR)$(syshdimagedir)/drives; \
 	    ln -s $(DESTDIR)$(dosemudir)/freedos $(DESTDIR)$(syshdimagedir)/drives/c; \
 	  fi; \
-	  rmdir $(DESTDIR)$(syshdimagedir)/freedos/tmp; \
-	  ln -sf /tmp $(DESTDIR)$(syshdimagedir)/freedos/tmp; \
+	  rm -f $(DESTDIR)$(dosemudir)/freedos/tmp; \
+	  ln -sf /tmp $(DESTDIR)$(dosemudir)/freedos/tmp; \
 	fi
 	$(INSTALL) -d $(DESTDIR)$(sysconfdir)
 	if [ ! -f $(DESTDIR)$(sysconfdir)/dosemu.conf ]; then \


to the question:
  Going to install your private DOSEMU files into the directory
  $HOME/dosemu
  Enter an empty string to confirm, a new path, or \"none\" (without
  the quotes) if you don't want this:"

you said you entered
/home/ged/src/dosemu/
and then it uses
/home/ged/src/dosemu/dosemu
well the files are going into "/home/ged/src/dosemu/", just with one more
directory below it. I don't see why that would be a major problem?

The reason why is that a tarfile (by default,
/usr/local/share/dosemu/dosemu-freedos-bin.tgz)
is untarred into this directory and the pathnames just happen to start
with dosemu/

But is what you really mean that the install script could be clearer and
say something like

  Going to install your private DOSEMU files into the directory
  $HOME/dosemu
  Enter an empty string to confirm, a new path, or \"none\" (without
  the quotes) if you don't want this,
  example: /home/ged/src installs your private DOSEMU files into
           /home/ged/src/dosemu.

?

> It grumbled about not having freedos
> even though I'd set 'fdtarball none' in the compiletime-settings.

Same thing here as a few lines above: "fdtarball none" only takes effect
after you run configure again.

> Having said that once it did compile (2.4.19) it started and ran quite
> a few things fine, but the attached pager (LIST.COM) crashes dosemu
> very reliably under X on my system.

I just tried it, it doesn't crash for me. Which DOS are you using in your
DOSEMU?

Bart

Re: DOSEMU 1.1.4.15 for testing.

[Ged Haywood]

Hi Bart,

On Tue, 18 Mar 2003, Bart Oldeman wrote:

> -- I may be blind but the instructions are up-to-date as far as I know.

Maybe not blind, maybe just a bit too close to it.  :)

----------------------------------------------------------------------
On Tue, 18 Mar 2003, Ged Haywood wrote:

> I hope you'll do something about the instructions for building it
> before you put it out as 1.1.5.  It's very confusing because there's
> so much of it that's out of date and inconsistent.  It doesn't need to
> be completely rewritten but if you put some up-to-date instructions in
> a file called INSTALL then people who are used to doing
>
> ./configure
> make
> make install
>
> will be more much comfortable.

This is exactly what the file "QuickStart" is supposed to do -- please
tell me what you want to have changed in QuickStart

1.  The name of the file.  It should be INSTALL.
2.  There should be a file called README as well.  It should tell us (in less
    than 24 lines:) what we've got here and to go read INSTALL.
3.  Remove the reference to ViewDocs.  If we go off and start reading the stuff
    in docs/ then we'll come back not knowing what to believe and what not.
    If people are confused by what it calls "BOLDFACE" formatting then why add
    to the confusion with a crappyy script that doesn't clear the screen, offers
    two different menu options (1 and 2) to view the same file; one (6) which 
    lies; and no way to exit?  Why not just provide plain text files that really
    are plain text files?
4.  Remove the bit where you "strongly recommend" abandoning 1.1.4.15 in favour
    of the 1.0.2.1 binary distribution.
5.  While we're in the middle of compiling DOSEMU, the 'make' step tells us
    to read QuickStart before compiling DOSEMU.  Don't do that.  If you're
    going to do it at all, tell us at the beginning and offer to STOP to allow
    us to do it.
6.  Explain that we should normally use setup-dosemu to modify compiletime-settings
    but
7.  explain that setup-dosemu is broken.
8.  Don't refer to scripts with the syntax "./setup-dosemu" because the document
    will get moved (see 3.(6) above) and the script won't be there any more.  At
    least use a path relative to (for example) the top of the DOSEMU tree, a path
    relative to some other directory involved in the installation such as $HOME,
    or use a full path.
9.  Clarify whether you can use DOSEMU without 'make install'.  The QuickStart
    document talks about make install only for system wide installation, whatever
    that means.
10. After the 'make' step there's a message telling us to run 'make install'.
    If 'make install' isn't necessary then remove it or at least explain under
    what circumstances 'make install' is required, and
11. explain the differences between using DOSEMU *with* 'make install'
    and using it *without* make install.
12. Explain how to run DOSEMU after installation.  It is mentioned for the
    binary distribution installation (it talks about xdosemu) but not for the
    source.  There's no reason to assume that the user is running X.
13. Explain that there is a script called 'default-configure' which should be run
    instead of 'configure' which is what the experienced user will be expecting.
14. Explain that 'make' will run 'default-configure' and not to be concerned
    by the message "You chose not to run default-configure...".  (There was no
    question of choosing not to run it since it wasn't mentioned except in the
    section of 'QuickStart' which talks about non-standard configuration.  Which
    kind of begs the question "what is the standard configuration?".)

> > The build scripts seem to be very fragile, I changed the directories
> > in the compiletime-options and although everything was supposed to be
> > in my home directory the make install failed with permission problems
> > unless I was root.
> 
> Shouldn't be and I just tested it. You must clean the tree and recompile

This was out-of-the-box in a new tree.  Does the compiletime-options file
get modified by any of the scripts?  I had the impression that it was but
I haven't been through it all again to check.

> a) problems with 'make install'

I still don't know if I'm supposed to do 'make install' or not.

> b) problems running dosemu for the first time.

The problem is that the script doesn't check the result of getting the
pathname from the user - it continues regardless even if it didn't get
one, and makes a mess which will cause problems when you next run it.

> One problem with a symlink may be solved using:
> [snip]

I think that ought to do it.

> to the question:
>   Going to install your private DOSEMU files into the directory
>   $HOME/dosemu
>   Enter an empty string to confirm, a new path, or \"none\" (without
>   the quotes) if you don't want this:"
> 
> you said you entered
> /home/ged/src/dosemu/
> and then it uses
> /home/ged/src/dosemu/dosemu
> well the files are going into "/home/ged/src/dosemu/", just with one more
> directory below it. I don't see why that would be a major problem?

It's not a major problem, it's just confusing because it's not what's
asked for.  You can't expect people to know that the extra directory
level won't matter.  My worry was that the installation would fail.

> The reason why is that a tarfile (by default,
> /usr/local/share/dosemu/dosemu-freedos-bin.tgz)
> is untarred into this directory and the pathnames just happen to start
> with dosemu/

I'd told it not to use freedos in the compiletime-settings file but it
complained anyway.

> But is what you really mean that the install script could be clearer and
> say something like

>  Going to install your private DOSEMU files into the directory
>  $HOME/dosemu
>  Enter an empty string to confirm, a new path, or \"none\" (without
>  the quotes) if you don't want this,
>  example: /home/ged/src installs your private DOSEMU files into
>           /home/ged/src/dosemu.
> 
> ?

That would be fine.

> > It grumbled about not having freedos
> > even though I'd set 'fdtarball none' in the compiletime-settings.
> 
> Same thing here as a few lines above: "fdtarball none" only takes effect
> after you run configure again.

You mean default-configure?

> > Having said that once it did compile (2.4.19) it started and ran quite
> > a few things fine, but the attached pager (LIST.COM) crashes dosemu
> > very reliably under X on my system.
> 
> I just tried it, it doesn't crash for me. Which DOS are you using in your
> DOSEMU?

MS-DOS 6.22.  Today I've found that if I set the xterm for 80x25 it
seems to run OK (although I haven't tested it much) but if I start the
xterm full-screen as I usually do
(
*MiniButtons - mini-term.xpm Exec "XTerm" xterm -ls -sb -fn 7x14 -title "Color xterm" -geometry 142x53+0+0 &
)
then I don't see anything on the dosemu screen.  It instantly bombs
out into the shell that started dosemu.

I have two reasons for running DOSEMU.  One is to run WordPerfect 5.0
and that seems to run just fine, which is great.  I'm going to install
it in our offices now, where it will get -er- tested.  They currently
run WP under DOS; I want to get the benefits of Linux without losing
all the years of experience of WP5.0.  I'll keep you posted.

The other reason is to run an old C compiler suite, I sent a message a
while ago about a memory-related problem I'd had with it but it's not
so important to me right now.  When I've got the secretarial stuff
running reliably I'll get on to it and let you know how it goes.

Thanks for all the effort.

73,
Ged.

Re: DOSEMU 1.1.4.15 for testing.

[Claudia Neumann]

Hi all,

I upgraded vom dosemu 1.1.3.7, which run perfectly in my installation. 

My problem is, I need 2 dosemu-consoles oder -windows with a 
clipper-programm, which need both access to /dev/ttyS0 (COM1) with a card 
reading device. In dosemu 1.1.3.7 I managed to divert the COM1-Locking-File 
into 2 different directories. In dosemu-1.1.4.15 I would have to run dosemu as
root to run with different dosemu.conf-Files or is there another way?

Is it possible to switch the locking of COM1 off?

Regards

Claudia