linux-msdos-digest        Wednesday, March 15 2000      Volume 01 : Number 168

In this issue:

----------------------------------------------------------------------

From: Francisco Matias Cuenca-Acuna <[EMAIL PROTECTED]>
Date: Mon, 28 Feb 2000 01:33:55 -0500
Subject: How to capture a video sequence

        I want to extract a video sequence from an old DOS program. Does anybody 
know how can I do this with dosemu? I was thinking about hooking a "frame 
grabber"from the screen update routine........ Does anybody know about an 
already made extension?
        Thanks
                Matias

------------------------------

From: [EMAIL PROTECTED]
Date: Mon, 28 Feb 2000 05:05:32 -0600
Subject: Re: Key combos

On Sat, Feb 19, 2000 at 09:05:37PM +0100, [EMAIL PROTECTED] wrote:
> >Date: Fri, 18 Feb 2000 07:19:20 -0600
> >From: [EMAIL PROTECTED]
> >Who can point me to documentation on faking odd key combinations 
> >through dosemu?  Things like <alt>F1, <ctrl><alt>F5, and things like 
> 
> I wrote a program which sends these combinations from terminal
> (needs DOS PC to be used as terminal, and it converts all keys
>  to combinations DosEmu on Linux machine understands).
> I supose its source contains the documentation you need.
> 
> To get it: go to my page http://www.fuw.edu.pl/~jt,
> click "my plans" then "here" in line containg "DosEmu".
> 
> You can get some help from DosEmu: press Ctrl-^ then ?.
> 
> Jerzy

Thanks for your reply!

I downloaded your program and it seems to be something to use on a true 
DOS machine?  Perhaps I mis-stated my problem.  Whether I use dosemu 
directly through a virtual console or telnet (from another Linux 
machine), certain key combinations are not passed to the DOS program 
that is running under dosemu.  For instance, <alt> F-keys are used by 
Linux to switch virtual consoles and, therefore, such key combinations 
never get seen by a DOS program that is run under dosemu.

- -- 
Onward!  Through the Fog!
Willie
http://austinfarm.org/homegrown

------------------------------

From: Hugh Lawson <[EMAIL PROTECTED]>
Date: Mon, 28 Feb 2000 07:53:49 -0500 (EST)
Subject: Re: Key combos

On Mon, 28 Feb 2000 [EMAIL PROTECTED] wrote:

> Whether I use dosemu 
> directly through a virtual console or telnet (from another Linux 
> machine), certain key combinations are not passed to the DOS program 
> that is running under dosemu.  For instance, <alt> F-keys are used by 
> Linux to switch virtual consoles and, therefore, such key combinations 
> never get seen by a DOS program that is run under dosemu.

Maybe I got into this late, but here is my answer.  The dos program I run
under dosemu is WordPerfect 5.1.  It uses lots of F-keys with the
modifiers for its basic operations.  These seem to work ok (I haven't
tried all of them!) when xdos is running in its own X-window, and when
'dos' is run from the console with the raw keyboard option.

However, I'd like to know how to control the way keys are passed to
applications when 'dos' is running in an xterm: say WordPerfect 5.1 is
running in dosemu, which is running in an xterm.  Just idle curiosity!


- --
Hugh Lawson
Greensboro, North Carolina
[EMAIL PROTECTED]


------------------------------

From: Hans Lermen <[EMAIL PROTECTED]>
Date: Mon, 28 Feb 2000 15:10:43 +0100 (MET)
Subject: Re: Key combos

On Mon, 28 Feb 2000, Hugh Lawson wrote:

> However, I'd like to know how to control the way keys are passed to
> applications when 'dos' is running in an xterm: say WordPerfect 5.1 is
> running in dosemu, which is running in an xterm.  Just idle curiosity!

Try <Ctrl>^h (2 strokes: first  '<Ctrl>^' then 'h'). You'll get help
on what is possible. Example:

  Pressing  <Ctrl>^s followed by  <Ctrl>^3 results in SHIFT-F3.

Well, normally people are used to read ^H as <Ctrl>H and using just
this '^' as 'escchar' realy is confusing. However, on an US keyboard,
the '^' is 'above' number '6', so the above example could be written in a
more usual way such as

  Pressing  ^6s followed by  ^63 results in SHIFT-F3.

or

  Pressing  ^^s followed by  ^^3 results in SHIFT-F3.

(grrh...)

Ok, here is the complete help from ^6h (aka <Ctrl>^h aka ^^h) and
'translated' to use '^6' as the prefix for all those special typings:

Hope this helps and doesn't give more confusion ;-)

Hans
<[EMAIL PROTECTED]>

- ----------------------------------------------------------------------------
NOTE: see dosemu.conf 'terminal {escchar}' to change '^6' .
Function Keys:
    F1: ^61      F2: ^62 ...  F9: ^69    F10: ^60   F11: ^6-   F12: ^6=
Key Modifiers:
    Normal:  ^6s SHIFT KEY, ^6a ALT KEY, ^6c CTRL KEY, ^6g ALTGR KEY
    Sticky:  ^6S SHIFT KEY, ^6A ALT KEY, ^6C CTRL KEY, ^6G ALTGR KEY
Substitute keys:
    ^6K0 Insert, ^6K7 Home, ^6K3 PgDn, ^6Kd Delete, ^6Kp PrtScn, etc.
Notes:
    The numbers are the same as those on the key on the numeric keypad.
    To cancel the sticky key, press it again or use ^6 Space.
Examples:
    Pressing ^6s followed by ^63 results in SHIFT-F3.
    Pressing ^6C Up Up Up ^6C results in Ctrl-Up Ctrl-Up Ctrl-Up.
    Pressing ^6c ^6K1  results in Ctrl-End
Miscellaneous:
    ^6^R : Redraw display      ^6^L : Redraw the display.
    ^6^Z : Suspend dosemu      ^6b  : Select BEST monochrome mode.
    ^6 Up Arrow: Force the top of DOS screen to be displayed.
    ^6 Dn Arrow: Force the bottom of DOS screen to be displayed.
    ^6 Space: Reset Sticky keys and Panning to automatic panning mode.
    ^6? or ^6h:  Show this help screen.
    ^6^6:  Send the ^6 character to dos.
- ----------------------------------------------------------------------------



------------------------------

From: "Jakob Eriksson" <[EMAIL PROTECTED]>
Date: Mon, 28 Feb 2000 17:07:13 +0100
Subject: Hi!

I think you do a wonderful job on DOSEMU! :-)
Thanks!

- -- 
Jakob Eriksson QuickNet AB


------------------------------

From: David Milligan <[EMAIL PROTECTED]>
Date: Tue, 29 Feb 2000 08:49:12 +1300
Subject: Multiple network cards

I am trying to use 2 network cards with an IPX based application running in DOSEMU. 
Both are connected to a Novell server and are working OK using IPX_INTERFACE (I have 
setup the IPX network and frame types etc).

However when I use VLM.EXE in DOSEMU it always uses the primary IPX interface 
(IPX_INTERFACE ADD -P ETH0 1). I would like to be able to specify which interface is 
used for each DOSEMU user in order to provide simple IPX load balancing. 

David Milligan


------------------------------

From: Alistair MacDonald <[EMAIL PROTECTED]>
Date: Tue, 29 Feb 2000 00:37:30 +0000 (GMT)
Subject: Re: ATI Rage 128

Yes - use X-Windows. The problem is that there are too many graphics cards
out there for us to maintain drivers for each them, but we don't have time
to write new ones. However, the XFree86 people do a wonderful job of
trying to keep up with the new cards, so we use their work. It has the
nice side effect that you can run DOS on a different machine over the
network .... 

The original console drivers do a reasonable job for the cards that they
support but they don't support them all. You might notice that most of the
supported cards are now quite old. They were written at a time when
running X was too much of an overhead. I remember my original linux
machine with its massive 4Mb of memory paging madly just trying to run
twm. (The worst thing is that I used to *use* it like that ... ah the old
days ...) In these days when most machines have at least 32Mb of memory X
is a reasonable overhead, and so we can concentrate on the X drivers.

Its unlikely that any new console drivers will be developed. If someone
feels the desperate need to write one then a generic VESA driver *might*
be useful. However, it would be more fun (and more use) to deal with the
limitations of VGAEmu (such as 16-colour modes, Mode-X, etc)

Alistair

On Fri, 25 Feb 2000, Michal Svec wrote:
> It seems that dosemu doesn't recognize the ATI Rage 128 graphics card. Can
> I do something to get it working?


------------------------------

From: "Sean Schroeder" <[EMAIL PROTECTED]>
Date: Mon, 28 Feb 2000 22:05:07 -500
Subject: Dr.Dos C++ compiler

Hello,  I have been running Caldera Open Linux for two years, and now I am in
need of a C/C++ compiler that will run under Dr.Dos.  I have tried an old Quick
C (microsoft) but it appears that I am missing most of the files, but it was
able to make an obj file :) and the environment looked great! Any ideas where
I can find either Quick c/C++ or boralnd c/C++ for dos?

thanks 

Sean Schroeder

------------------------------

From: [EMAIL PROTECTED]
Date: Tue, 29 Feb 2000 16:44:38 MET
Subject: Re: Key combos

> Date: Mon, 28 Feb 2000 05:05:32 -0600
>> On Sat, Feb 19, 2000 at 09:05:37PM +0100, [EMAIL PROTECTED] wrote:
>> >From: [EMAIL PROTECTED]
>> >Who can point me to documentation on faking odd key combinations 
>> >through dosemu?  Things like <alt>F1, <ctrl><alt>F5, and things like 
>> I wrote a program which sends these combinations from terminal
>> (needs DOS PC to be used as terminal, and it converts all keys
>>  to combinations DosEmu on Linux machine understands).
>> I supose its source contains the documentation you need.
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> To get it: go to my page http://www.fuw.edu.pl/~jt,
>> click "my plans" then "here" in line containg "DosEmu".
>> You can get some help from DosEmu: press Ctrl-^ then ?.
>I downloaded your program and it seems to be something to use on a true 
>DOS machine?  Perhaps I mis-stated my problem.  Whether I use dosemu 
>directly through a virtual console or telnet (from another Linux 
>machine), certain key combinations are not passed to the DOS program 
>that is running under dosemu.  For instance, <alt> F-keys are used by 

And you can simulate them. To send Alt-F5 you type Ctrl-6 a Ctrl-6 5.

Here is the doc extracted from my program source:
; DosEmu key sequences (all start from code 1Eh):
; 1234567890-=          F1-F12
; ?hH                   help
; acgsACGS              Alt Ctrl rAlt Shift (uppercase=stick)
; with k:       789456123       Home,Up,PgUp,Left,'5',Right,End,Down,PgDn
;       0/*-+<Enter>    Ins,/,*,-,+,Enter
;       other:          1Eh,'k' is ignored and the code is passed
; with K: dhnpsy.               eDel,Pause,NumLock,PrtSc/SysReq,ScrollLock,
                                SysReq,eDel
;       (case ignored)
;       digits:         same as with k except enhanced unless 5.
; what with '<'? scan code 56h (57h=F11, 58h=F12)

For instance, for DosEmu to see SysReq (Alt-PrtSc) you need send:
Ctrl-6 a Ctrl-6 K p  (enable Alt and send PrtSc/SysReq).

Seems there are some bugs in DosEmu (seems I tested it up to 0.98.8):
it cannot get Del (only Enhanced Del), and it cannot get normal '<'
- - I remember some problems with Norton Commander because of it.

Jerzy

------------------------------

From: "scott little" <[EMAIL PROTECTED]>
Date: Wed, 1 Mar 2000 08:34:47 +1100
Subject: vmodem?

Hi all,

Does DOSEMU have any kind of 'vmodem' capability? Ideally, what I would like
is for a specified COM port to be redirected to stdin/out - which will
generally be the TTY I'm on. This is to support DOS doors for my BBS.

If it doesn't support this, who should I bribe to 'make it so' ?


thanks.




------------------------------

From: Bart Oldeman <[EMAIL PROTECTED]>
Date: Tue, 29 Feb 2000 22:39:08 +0000 (GMT)
Subject: Console video drivers (was Re: ATI Rage 128)

On Tue, 29 Feb 2000, Alistair MacDonald wrote:

> support but they don't support them all. You might notice that most of the
> supported cards are now quite old. They were written at a time when
> running X was too much of an overhead. I remember my original linux
> machine with its massive 4Mb of memory paging madly just trying to run
> twm. (The worst thing is that I used to *use* it like that ... ah the old
> days ...) In these days when most machines have at least 32Mb of memory X

I didn't even install X on my 386SX-20 with 5 MB RAM and 2 40Mb harddisks,
one dedicated to DOS and the other to linux. And gcc was quite slow
compared to the Borland DOS compilers ...
All is different now of course ...

> Its unlikely that any new console drivers will be developed. If someone
> feels the desperate need to write one then a generic VESA driver *might*
> be useful. However, it would be more fun (and more use) to deal with the
> limitations of VGAEmu (such as 16-colour modes, Mode-X, etc)

I was actually looking into this since it is a whole lot easier to
implement a vesa video mode save/restore routine than emulating 16 color
modes, as far as I can see. I can use my graphics card with vesa 2.0 for
just about anything under the console with dosemu, except for vc-
switching. And of course switching from X to the console is always
possible with Ctrl-Alt-F something.

The vesa video save/restore routines are as follows (this is from
svgalib):

/* Read and save chipset-specific registers */
static int vesa_saveregs(unsigned char regs[])
{
  void * buf;
  buf=LRMI_mem1;
  vesa_r.eax=0x4f04;
  vesa_r.ebx=0;
  vesa_r.es=((long)buf)>>4;
  vesa_r.edx=1;
  vesa_r.ecx=__svgalib_VESA_savebitmap;
  __svgalib_LRMI_int(0x10,&vesa_r);
  memcpy(&regs[VGA_TOTAL_REGS],buf,vesa_regs_size);
    return vesa_regs_size;
}

/* Set chipset-specific registers */

static void vesa_setregs(const unsigned char regs[], int mode)
{

  void * buf;
  buf=LRMI_mem1;
  memcpy(buf,&regs[VGA_TOTAL_REGS],vesa_regs_size);
  vesa_r.eax=0x4f04;
  vesa_r.ebx=0;
  vesa_r.es=((long)buf)>>4;
  vesa_r.edx=2;
  vesa_r.ecx=__svgalib_VESA_savebitmap;
  __svgalib_LRMI_int(0x10,&vesa_r);
}

What I need to figure out is what is the dosemu equivalent of
__svgalib_LRMI_int(), which calls the real vesa bios. I looked
through the source to find the example where c000:3 is called, but
one place in src/env/vga.c, where other comments point to, is commented
out with a "#if 0". I would greatly appreciate it if somebody could point
me to the cleanest way of implementing this.

Bart  


------------------------------

From: "M. Ceroni" <[EMAIL PROTECTED]>
Date: Tue, 29 Feb 2000 19:26:41 -0500 (EST)
Subject: Video Problems:

I have downloaded dosemuv0.98 howver when I try to run simple games such
as Space Quest 1 all the graphics are screwed up. It doesn't display
anything close to what it should.

Help would be appreciate..

Thanks in advance


------------------------------

From: Hans Lermen <[EMAIL PROTECTED]>
Date: Wed, 1 Mar 2000 11:43:22 +0100 (MET)
Subject: Re: vmodem?

On Wed, 1 Mar 2000, scott little wrote:

> Does DOSEMU have any kind of 'vmodem' capability? Ideally, what I would like
> is for a specified COM port to be redirected to stdin/out - which will
> generally be the TTY I'm on. This is to support DOS doors for my BBS.
> 
> If it doesn't support this, who should I bribe to 'make it so' ?

There was a patch from "Julia A . Case" <[EMAIL PROTECTED]> to just do
that. She started to adapt this patch for dosemu-0.98, but did not finish.
I just mailed her asking to finish the patch, no response until now.

Hans
<[EMAIL PROTECTED]>


------------------------------

From: [EMAIL PROTECTED]
Date: Wed, 01 Mar 2000 12:49:26 MET
Subject: RE: vmodem?

> Date: Wed, 1 Mar 2000 08:34:47 +1100
>
> Does DOSEMU have any kind of 'vmodem' capability? Ideally, what I would like
> is for a specified COM port to be redirected to stdin/out - which will
> generally be the TTY I'm on. This is to support DOS doors for my BBS.
> If it doesn't support this, who should I bribe to 'make it so' ?

In dosemu.conf you can define COM ports, if I remember correctly
any device from /dev can be used there (I tried /dev/cua2).
Seems you can use /dev/ptyxx and /dev/ttyxx pair - they form
bidirectional pipe, you open pty first, then run DosEmu giving
corresponding tty to it. 
Or maybe you can just specify /dev/tty (or whatever is name of
current terminal on Linux) to pass it to DosEmu.

Jerzy

------------------------------

From: "scott little" <[EMAIL PROTECTED]>
Date: Thu, 2 Mar 2000 00:52:46 +1100
Subject: Re: vmodem?

> Or maybe you can just specify /dev/tty (or whatever is name of
> current terminal on Linux) to pass it to DosEmu.

what about the 'real' keyboard/screen? the program still needs to be able to
read/write the local screen buffer, and poll for keyboard input. however
none of this should be visible to the user.



------------------------------

From: [EMAIL PROTECTED]
Date: Wed, 01 Mar 2000 16:05:03 MET
Subject: Re: vmodem?

Date: Thu, 2 Mar 2000 00:52:46 +1100

>> Or maybe you can just specify /dev/tty (or whatever is name of
>> current terminal on Linux) to pass it to DosEmu.
> what about the 'real' keyboard/screen? the program still needs to be able to
> read/write the local screen buffer, and poll for keyboard input. however
> none of this should be visible to the user.

I am afraid I might incorrectly understand what is to be the
_direction_ of the redirection: do you need DosEmu to see some
streams as its COM port, or you need some COM port to be used
as DosEmu input/output? The first is probably easy, the other
I tried and had serious troubles. Finally I use expect and
telnet to invoke DosEmu. Maybe things can be simplified, maybe
DosEmu must be invoked by a program which passes terminal type
in environment, and when I used pty/tty it was not set to any
reasonable default? DosEmu must assume some terminal type (say
VT100) for screen I/O to work - otherwise it terminates. And
seems it does not accept redirection from/to a file. I assume
it is especially important for output - for screen addressing.

If you want use DosEmu in a way one can phone your machine,
and invoke DosEmu, there is a must to determine terminal type
for the DosEmu to be able to display correctly on terminal.

Also, seems you can use some getty version for all the job...
just display info like "for login enter terminal type, one of
vt100, vt220, ....", and for every of these names define user
which invokes DosEmu for respective terminal type.

Jerzy

------------------------------

From: "scott little" <[EMAIL PROTECTED]>
Date: Thu, 2 Mar 2000 04:50:37 +1100
Subject: Re: vmodem?

> I am afraid I might incorrectly understand what is to be the
> _direction_ of the redirection: do you need DosEmu to see some
> streams as its COM port, or you need some COM port to be used
> as DosEmu input/output?

the former. perhaps a crash course in BBSing might help...

DOS BBS programs are unlike any Unix program. They have TWO inputs and TWO
outputs. The local screen (ie. the monitor)+keyboard, and the COM port (to
which the user has connected to via modem). All these programs write their
output twice, once to the local screen, and once to the com port.
And vice versa.

The local console is only ever used by the sysop (the guy that runs the BBS,
who is sitting at the physical machine). That means it has god powers - a
status bar with user info on it, and the ability to modify the user's
security and so on. if not for that there would be no problem - I could just
run all the BBS stuff in 'local mode' (ie. the program uses only the local
console - DOSEMU handles this just fine).



Normally, I can telnet to my machine, run DOSEMU and I'll see a DOS prompt -
DOS is assuming it's writing to the physical screen, and reading from the
physical keyboard - not my telnet session. And I assume that this is indeed
the case - DOSEMU has a screen buffer, and is sending it's contents across
to my terminal. Probably the same as the program 'screen' does.

This has to be somehow disconnected. The program will still need to write to
the screen buffer, but it will not be sent to my terminal. It will still
need to poll for keyboard input, but there will never be any.

So, DOSEMU has stopped reading/writing my terminal as though it were DOS's
console. What it needs to do instead is connect the COM port (that is, a
fake COM port within DOSEMU, not a real com port) to my terminal. So if I
type "foo" over my telnet session, those characters will be placed in the
incoming buffer on DOSEMU's COM port. If the program sends "bar" to the COM
port, those characters will be sent to my terminal.

clear as mud? :)



------------------------------

From: "scott little" <[EMAIL PROTECTED]>
Date: Sat, 4 Mar 2000 01:29:50 +1100
Subject: Date:   Sat, 4 Mar 2000 01:29:50 +1100

Trying to compile dosemu versions 0.66.7 or 0.98.2 gives me messages such
as:

mkfatimage16.c:91: initializer element is not constant
make[3]: *** [mkfatimage16] Error 1
make[3]: Leaving directory
`/var/usr/local/src/dosemu-0.66.7/src/tools/periph'
make[2]: *** [tools/periph] Error 2
make[2]: Leaving directory `/var/usr/local/src/dosemu-0.66.7/src'
make[1]: *** [doslibnew] Error 2
make[1]: Leaving directory `/var/usr/local/src/dosemu-0.66.7/src'
make: *** [default] Error 2

what could be wrong?

applying the vmodem patch doesn't work either, but if I can't compile it
without, there's not much point worrying about the patch yet...



------------------------------

From: [EMAIL PROTECTED]
Date: Fri, 3 Mar 2000 16:34:20 GMT
Subject: FreeOnlineads.com advertise your product, service, website for FREE.

Dear Sir/madam

I found your site on the internet and thought you might intrested in 
our FREE service.
Initally let me intoduce ourselves to you as www.freeonlineads.com,
we are a FREE internet Classified service.  Whether you're looking 
to promote, sell, hire or simply let the world know who you are and 
what you or your organization, club or community group is doing, 
we're sure www.freeadsonle.com will make your experience fast, 
easy, fun and absolutly free.

We hope you like the site and find it useful to your business.

Best regards

Sam Lunar
www.freeonlineads.com

------------------------------

From: "Personal Data" <[EMAIL PROTECTED]>
Date: Fri, 03 Mar 2000 17:52:43 PST
Subject: dosemu

I am unable to acces my B: drive (/dev/fd1). Although I can easily mount all 
diskettes from linux and see their contents. Dosemu reports itaself as v0.98 
at startup. Is there a way this could be fixed?
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

------------------------------

From: Franco De Angelis <[EMAIL PROTECTED]>
Date: Mon, 6 Mar 2000 18:43:20 +0100
Subject: Help: hot to use LPT1 ?

Hello,

I'm not subscribed to the list so, please, reply me privately or I'll miss the
answer.

I have dosemu 0.99.13 shipped with RedHat 6.1 and I don't manage to allow a DOS
program to access a standard LPT1 port.

How do I have to do? I did read  the FAQ but:

$_ports { device /dev/lp1 fast range 0x378 0x37f } # lpt1

gives syntax errors and Hans Lermen's suggestion note in the sam FAQ doesn't
work either, as is. I tried with:

$_ports = "device /dev/lp1 fast range 0x378 0x37f"

or with 

$_ports = "range 0x378,0x37f"

and many other combinations without success.
Could somebody please send me the exact command to use (or tell me the "secret
tricks" that I don't know)?

Thank you a lot in advance,
Regards,
Franco
- -- 
e-mail: [EMAIL PROTECTED]

------------------------------

From: Hans Lermen <[EMAIL PROTECTED]>
Date: Tue, 7 Mar 2000 01:13:03 +0100 (MET)
Subject: dosemu-1.0.0 available

Hi Friends and Users of DOSEMU,

Finaly, after 8 years of development, we decided to give our baby the
freedom to call itself 'production ready'. We could not realize all our
wishes, but the stuff which is in should be as stable as it can be with
DOS in the background :-)

Thanks to all people involved, those still active as well as those
formerly active ones ;-) Special thanks to all the former co-ordinators
who 'governed' the development team befor me:

        - Matthias Lautner, started the DOSEMU project 1992
        - Robert Sanders, took over government 1993
        - James B. MacLean, who was the longest staying on
          this project: 1994 .. 1996

Since 1997 being the co-ordinator of this exiting project, I'm very happy
that it finally reaches its aim.

dosemu-1.0.0 is uploaded to the usual place:

  ftp.dosemu.org:/dosemu/
                     .../Development/patchset-0.99.14.tgz
                     .../patchset-1.0.0.tgz
                     .../dosemu-1.0.0.tgz
                     .../dosemu-1.0.0-1.i386.rpm

In the meantime it got mirrored and also is available on:

  ftp://metalab.unc.edu/pub/Linux/system/emulators/dosemu/*

The md5sums are:

17b8ce057b257b0c1e287a2fbfdbb451  patchset-0.99.14.tgz
3d25264f530fb67f1e2af58b62d8e621  patchset-1.0.0.tgz
f6b4338aeddc75845c68baf509fd0261  dosemu-1.0.0.tgz
9d3f39f8424130d1c65d563956188423  dosemu-1.0.0-1.i386.rpm


Note that 1.0.0 was built out of 0.99.13 ==> 0.99.14 and that 0.99.14
is the 'fork point' which will continue unchanged as 1.1.x.
1.0.0 is identical to 0.99.14 except it has no cpu-emu.


A final remark: For those compiling dosemu themselves with some (latest?)
glibc-2.1.3 variants, it maybe necessary to set 'slangforce off' in
./compiletime-settings to use their own Slang library, else linkage may
fail. Though I got report of this problem, I can't reproduce it. The
system on which I checked the compilation with gcc-2.95.2/glibc-2.1.3 had
no problems at all.


Have a lot of fun,
Hans
<[EMAIL PROTECTED]>




------------------------------

From: Mark Rejhon <[EMAIL PROTECTED]>
Date: Tue, 07 Mar 2000 00:24:33 -0500
Subject: Re: dosemu-1.0.0 available

Hi,

Count me as one of the formerly active ones from '93 and '94!

Let me extend a belated congratulations to all of you.   

Although I am not a DOSEMU at the moment on my current Linux server,
some of you oldtimers may remember me as the one who rewrote the
serial emulation code back in 1994 and helped with timer support
to make DOS/4GW videogames such as DOOM to work at full 100% speed.
I even see my name is still there, splattered all over the serial
code these days.  Yes, those good old James B. MacLean days!

Congratulations for bringing the version number all the way to 1.0,
it has been a really long journey!

Thanks,
Mark Rejhon
http://www.marky.com


Hans Lermen wrote:
> Hi Friends and Users of DOSEMU,
> 
> Finaly, after 8 years of development, we decided to give our baby the
> freedom to call itself 'production ready'. We could not realize all our
> wishes, but the stuff which is in should be as stable as it can be with
> DOS in the background :-)
> 
> Thanks to all people involved, those still active as well as those
> formerly active ones ;-) Special thanks to all the former co-ordinators
> who 'governed' the development team befor me:
> 
>         - Matthias Lautner, started the DOSEMU project 1992
>         - Robert Sanders, took over government 1993
>         - James B. MacLean, who was the longest staying on
>           this project: 1994 .. 1996

------------------------------

From: "Narr, McPaper" <[EMAIL PROTECTED]>
Date: Tue, 7 Mar 2000 08:50:59 +0100 
Subject: RE: dosemu-1.0.0 available

Hi,

I'm a ordinary user only, but wishing to thank you
for this long, great work.
Have had some trouble with the 0.98.8 (8-bit keyb.
- -input) and will give it a new try now.
I'm using it for an old ACUCOBOL-app. with DOS4GW
etc. and most of all worked fine.

Once again, thank you to the whole team.
Wolfgang
[EMAIL PROTECTED]


------------------------------

From: [EMAIL PROTECTED]
Date: Tue, 7 Mar 2000 11:21:56 Gmt +2:00
Subject: Message-id: <[EMAIL PROTECTED]>

Many thanks to all the wonderful and dedicated, and most
responsive developers of dosemu, for a most superb job
you have done !

Thanks again for releasing the ver. 1.0 of dosemu !!


_________________________________________
Free web based e-mail with Pop access at http://www.newmail.net

------------------------------

From: "Narr, McPaper" <[EMAIL PROTECTED]>
Date: Tue, 7 Mar 2000 12:12:16 +0100 
Subject: RE: Help: hot to use LPT1 ?

Hi,
if you use the same port as Linux (for printing) you won't
have success. You can't use one port twice...
If possible try $_printer = "lp" or whatever the Linux-name
of your printer is (see /etc/printcap and /etc/dosemu.conf).
If you _really_ need a bare port you should add a second one,
 exclusive for dos. Here it's ok to specify the portaddress.

Maybe you should test the dosemu_0.98.8 or the brand-new 1.0.
Yours 0.99.13 is developer and may have problems!
 
Hope this helps.
Greetings
Wolfgang


- -----Original Message-----
From: Franco De Angelis [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 06, 2000 6:43 PM
To: [EMAIL PROTECTED]
Subject: Help: hot to use LPT1 ?


Hello,

I'm not subscribed to the list so, please, reply me privately or I'll miss
the
answer.

I have dosemu 0.99.13 shipped with RedHat 6.1 and I don't manage to allow a
DOS
program to access a standard LPT1 port.

How do I have to do? I did read  the FAQ but:

$_ports { device /dev/lp1 fast range 0x378 0x37f } # lpt1

gives syntax errors and Hans Lermen's suggestion note in the sam FAQ doesn't
work either, as is. I tried with:

$_ports = "device /dev/lp1 fast range 0x378 0x37f"

or with 

$_ports = "range 0x378,0x37f"

and many other combinations without success.
Could somebody please send me the exact command to use (or tell me the
"secret
tricks" that I don't know)?

Thank you a lot in advance,
Regards,
Franco
- -- 
e-mail: [EMAIL PROTECTED]

------------------------------

From: Martin Konold <[EMAIL PROTECTED]>
Date: Tue, 7 Mar 2000 12:46:21 +0100 (CET)
Subject: Re: dosemu-1.0.0 available

On Tue, 7 Mar 2000, Hans Lermen wrote:

> Finaly, after 8 years of development, we decided to give our baby the
> freedom to call itself 'production ready'. We could not realize all our
> wishes, but the stuff which is in should be as stable as it can be with
> DOS in the background :-)

My congratulations and deep respect! You did an excellent job.

Yours,
- -- martin

// Martin Konold, Stauffenbergstr. 107, 72074 Tuebingen, Germany  //   
KDE:  The most advanced GUI for a reliable OS.


------------------------------

From: Marcel Landman <[EMAIL PROTECTED]>
Date: Tue, 07 Mar 2000 12:58:49 +0000
Subject: Re: dosemu

Personal Data wrote:

> I am unable to acces my B: drive (/dev/fd1). Although I can easily mount all
> diskettes from linux and see their contents. Dosemu reports itaself as v0.98
> at startup. Is there a way this could be fixed?

You can fix this in the dosemu.conf

- -mln


>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com


------------------------------

From: Marcel Landman <[EMAIL PROTECTED]>
Date: Tue, 07 Mar 2000 13:14:15 +0000
Subject: Re: dosemu-1.0.0 available

Thanks and well done. The Dosemu team has saved me at least 200 reboots, and
another 3 today.

Marcel Landman


Hans Lermen wrote:

> Hi Friends and Users of DOSEMU,
>
> Finaly, after 8 years of development, we decided to give our baby the
> freedom to call itself 'production ready'. We could not realize all our
> wishes, but the stuff which is in should be as stable as it can be with
> DOS in the background :-)
>
> Thanks to all people involved, those still active as well as those
> formerly active ones ;-) Special thanks to all the former co-ordinators
> who 'governed' the development team befor me:
>
>         - Matthias Lautner, started the DOSEMU project 1992
>         - Robert Sanders, took over government 1993
>         - James B. MacLean, who was the longest staying on
>           this project: 1994 .. 1996
>
> Since 1997 being the co-ordinator of this exiting project, I'm very happy
> that it finally reaches its aim.
>
> dosemu-1.0.0 is uploaded to the usual place:
>
>   ftp.dosemu.org:/dosemu/
>                      .../Development/patchset-0.99.14.tgz
>                      .../patchset-1.0.0.tgz
>                      .../dosemu-1.0.0.tgz
>                      .../dosemu-1.0.0-1.i386.rpm
>
> In the meantime it got mirrored and also is available on:
>
>   ftp://metalab.unc.edu/pub/Linux/system/emulators/dosemu/*
>
> The md5sums are:
>
> 17b8ce057b257b0c1e287a2fbfdbb451  patchset-0.99.14.tgz
> 3d25264f530fb67f1e2af58b62d8e621  patchset-1.0.0.tgz
> f6b4338aeddc75845c68baf509fd0261  dosemu-1.0.0.tgz
> 9d3f39f8424130d1c65d563956188423  dosemu-1.0.0-1.i386.rpm
>
> Note that 1.0.0 was built out of 0.99.13 ==> 0.99.14 and that 0.99.14
> is the 'fork point' which will continue unchanged as 1.1.x.
> 1.0.0 is identical to 0.99.14 except it has no cpu-emu.
>
> A final remark: For those compiling dosemu themselves with some (latest?)
> glibc-2.1.3 variants, it maybe necessary to set 'slangforce off' in
> ./compiletime-settings to use their own Slang library, else linkage may
> fail. Though I got report of this problem, I can't reproduce it. The
> system on which I checked the compilation with gcc-2.95.2/glibc-2.1.3 had
> no problems at all.
>
> Have a lot of fun,
> Hans
> <[EMAIL PROTECTED]>


------------------------------

From: Jan Stobbe <[EMAIL PROTECTED]>
Date: Tue, 7 Mar 2000 17:39:43 +0100
Subject: germen umlaute in dosemu 1.0.0.0 / telnet

Hi,

is still try to setup a clipper apllication in a dos box but it's
still not possible to use german "umlaute" when i use dos via telnet.

i use dosemu-1.0.0.0 and kernel 2.2.14. as telnet client i use secure crt
when i telnet to linux i can see umlaute in the bash when i start dosemu i 
see nothing when i use umlaute.

do you have some tips ?

thanks, Jan Stobbe

------------------------------

From: "Frank R. Larsen" <[EMAIL PROTECTED]>
Date: Tue, 07 Mar 2000 20:54:40 +0100
Subject: Tranport Tycoon Deluxe in Dosemu?

Hello.

Sorry if this is not quite the correct forum. 

I'm trying to use dosemu to run Transport Tycoon Deluxe. 
Using the default dosemu.conf I get the following error (from tycoon.exe):

Error TNT.20035: The 386 chip is currently executing
in virtual 8086 mode under the control of another program.  You must turn
off this other program in order to use TNT DOS-Extender to run in
protected mode.  

If I edit the file and adds $_dpmi = (2048) i get (from xdos):
ERROR: HLT requested: lina=0x4!

Are there anyone who have managed to get tycoon working? It would be 
great to get this game working. It would save me many reboots. :)

FrankRL



------------------------------

From: Hans Lermen <[EMAIL PROTECTED]>
Date: Tue, 7 Mar 2000 23:47:01 +0100 (MET)
Subject: Re: germen umlaute in dosemu 1.0.0.0 / telnet

On Tue, 7 Mar 2000, Jan Stobbe wrote:

> is still try to setup a clipper apllication in a dos box but it's
> still not possible to use german "umlaute" when i use dos via telnet.

This problem will be addressed in the 1.1.x series. With the current
Slang terminal its not possible to handle those problems, but the code
which does (and is a pretty big patch), wasn't stable enough to be put
into 1.0.      ... stay tuned.

Hans
<[EMAIL PROTECTED]>



------------------------------

From: [EMAIL PROTECTED] (Hans-Joachim Baader)
Date: Tue, 7 Mar 2000 22:16:07 +0100 (CET)
Subject: Re: dosemu-1.0.0 available

In article <[EMAIL PROTECTED]> you write:
>Finaly, after 8 years of development, we decided to give our baby the
>freedom to call itself 'production ready'. We could not realize all our
>wishes, but the stuff which is in should be as stable as it can be with
>DOS in the background :-)

Congratulations to the whole DOSEMU team! It has been a long and
successful journey. I used DOSEMU since 0.49 or even earlier and
I'm still using it for one program that I'm too lazy to replace.

Regards,
hjb
- -- 
http://www.pro-linux.de/ - Germany's largest volunteer Linux support site
You feel strangely lucky...

------------------------------

From: =?iso-8859-1?Q?=22Heilmann=2C_J=F6rg=22?= <[EMAIL PROTECTED]>
Date: Wed, 8 Mar 2000 10:21:04 +0100 
Subject: problem with clipper under dosemu

I still have a problem with my application program written in CA-Clipper and
linked with Blinker.
I have to call the program three times befor it then runs.
An error BLX286: 1309 out of memory occurs. 
This error also occurs sometimes during runtime.
My computer is a Pentium 75 (too slow?) with 32 MB RAM.
The DOS partitions has 150 MB free space.

MEM/C says:  available memory for programs:  608 K
                      extended memory (XMS)             33 MB

Do you know a workaround ?

------------------------------

From: Andris Pavenis <[EMAIL PROTECTED]>
Date: Thu, 9 Mar 2000 13:36:21 +0200 (EET)
Subject: Problem using DOSEMU after compiling

After compiling DOSEMU-1.0.0 I'm getting following output from
xdos:

hal:~$ xdos
kernel CPU speed is 200457779 Hz
Running on CPU=586, FPU=1
ERROR: cpu exception in dosemu code outside of VM86()!
trapno: 0x0d  errorcode: 0x00000000  cr2: 0x00000000
eip: 0x082cb003  esp: 0xbffff82c  eflags: 0x00010206
cs: 0x0023  ds: 0x002b  es: 0x002b  ss: 0x002b
General protection exception
GDT selector: 0x0000
Exception was caused by DOSEMU

- ------------------------------------------------
/usr/bin/dos        : works Ok. 
/usr/bin/dos -X     : crashes

System:  kernel 2.2.15pre13, 
         gcc-2.95.2 (I tried also egcs-1.1.2 without changes),
         binutils-2.95.1.0.27,
         glibc-2.1.3 
(updated from Slackware-7.0)

Binaries from dosemu-1.0.0-1.i386.rpm works Ok (no such problem)

Configure command
        ./default-configure --prefix=/usr --enable-linuxstatic \
                            --enable-dodebug

I didn't get reasonable stack trace with gdb so I'm not including
this info.

Andris  

 


------------------------------

From: Hans Lermen <[EMAIL PROTECTED]>
Date: Thu, 9 Mar 2000 17:10:50 +0100 (MET)
Subject: Re: Problem using DOSEMU after compiling

On Thu, 9 Mar 2000, Andris Pavenis wrote:

> After compiling DOSEMU-1.0.0 I'm getting following output from
> xdos:
> General protection exception
> GDT selector: 0x0000
> Exception was caused by DOSEMU
> ...
> Binaries from dosemu-1.0.0-1.i386.rpm works Ok (no such problem)

So your compilation is broken.

> 
> Configure command
>       ./default-configure --prefix=/usr --enable-linuxstatic \
>                             --enable-dodebug

hmm, this is _not_ the recommended procedure (and the docs explitely tell
you _how_ to reconfigure).

You need either to use ./setup-dosemu or edit compiletime-settings:

  config {
    ...
    dodebug on
    ...
  }

then do

   $ make distclean
   $ make

Hans
<[EMAIL PROTECTED]>


------------------------------

From: Andris Pavenis <[EMAIL PROTECTED]>
Date: Thu, 9 Mar 2000 19:53:34 +0200
Subject: Re: Problem using DOSEMU after compiling

On Thu, 09 Mar 2000, Hans Lermen wrote:
> On Thu, 9 Mar 2000, Andris Pavenis wrote:
> 
> > After compiling DOSEMU-1.0.0 I'm getting following output from
> > xdos:
> > General protection exception
> > GDT selector: 0x0000
> > Exception was caused by DOSEMU
> > ...
> > Binaries from dosemu-1.0.0-1.i386.rpm works Ok (no such problem)
> 
> So your compilation is broken.
> 
> > 
> > Configure command
> >     ./default-configure --prefix=/usr --enable-linuxstatic \
> >                             --enable-dodebug
> 
> hmm, this is _not_ the recommended procedure (and the docs explitely tell
> you _how_ to reconfigure).
> 
> You need either to use ./setup-dosemu or edit compiletime-settings:

This was thing I tried at first (static binaries, don't force included slang,
...). The result was the same

Andris

PS. I had such problem also earlier with 0.99.13.  Seems that problems appeared
after upgrading to Slackware-7 (Last successfull binary was from September 25
1999). glibc-2.1 should not be guilty here as I had it installed already in
Spring 1999.

------------------------------

From: =?ISO-8859-1?Q?M=E4kip=E4=E4_Mikko?= <[EMAIL PROTECTED]>
Date: Sat, 11 Mar 2000 01:32:34 +0200 (EET)
Subject: whine

hi,
I was trying to get dosemu to work and set /dev/hda1 (my main dos
partition) to be the hdimage, then ran dosemu and it gave error

ERROR: general protection at 0x99fff: 0
ERROR: SIGSEGV, protected insn...exiting!

the partition works fine from linux, but trying to boot to dos it
says c: invalid media type etc.  so it seems the partition somehow doesn't
know its a vfat partition now.
I'd be happy to see some kind of solution to the problem and be able to
boot to windows again, it would make I life a lot easier and wouldn't have
to bring back everything from backups...

Mikko
[EMAIL PROTECTED]


------------------------------

From: Chris Willis-Ford <[EMAIL PROTECTED]>
Date: Fri, 10 Mar 2000 21:32:13 -0800 (PST)
Subject: XDos crash

Hi all...
I just compiled dosemu 1.0.0.0 and i'm having troubles with xdos...
using the dosemu.conf file that comes with it, changing nothing except for
the bootdir part of it, it crashes when trying to switch to mode 13. In
fact, I wrote a quick little assembly program to prove the crash...

mov ax, 13
int 10
mov ax, 4c00
int 21

note that it crashes in at least these 3 cases: running that program,
doing a "SCREEN 13" in qbasic, and running DOOM. It does NOT crash when
doing a "SCREEN 12" in qbasic, although the graphics look funny (this is
expected from my previous experiences with xdos). Also, doom worked fine
in the last version I had (0.99.13)

the error it gives me (apart from the DOOM case, which doesn't return an
error but quits xdos for me) is:

- ----SNIP----
ERROR: cpu exception in dosemu code outside of VM86()!
trapno: 0x0e  errorcode: 0x00000006  cr2: 0x8b61b533
eip: 0x0821e001  esp: 0xbffff55c  eflags: 0x00010206
cs: 0x0023  ds: 0x002b  es: 0x002b  ss: 0x002b
Page fault: write instruction to linear address: 0x8b61b533
CPU was in user mode
Exception was caused by non-available page
- ----SNIP----

Any thoughts? I'm running kernel 2.2.14, compiled the thing with pgcc, and
i've tried all the different settings for $_mapping without any apparent
difference in the behavior.

Thanx!

Chris Willis-Ford


------------------------------

From: Suds <[EMAIL PROTECTED]>
Date: Sat, 11 Mar 2000 18:02:46 +0000 (GMT)
Subject: [HELP]: Sending arrow keys to dosemu from shell

Hi all,

I've breaking my head with this small problem of sending arrow keys to
dosemu from the shell. I could not find in docs (README.txt) etc the
sequence that needs to be sent for dosemu to interpret it as a down arrow
key. So, I'm trying to send the whole escape sequence ^[[B but invain.
Here is what I'm doing at the mo.

#/usr/bin/dos -I 'keystroke "\r\rfp.exe\r\^[[B"' 
(there are few more keystrokes after that which I've not included..)

Any help or clue would be greatly appreciated.

OTOH, sending 'ESC' character works fine most of the time but this
specific dos program does not take it in..any ideas why?

cheers
suds.


------------------------------

From: Suds <[EMAIL PROTECTED]>
Date: Sat, 11 Mar 2000 20:23:27 +0000 (GMT)
Subject: Re: [HELP]: Sending arrow keys to dosemu from shell

Apologies for following-up my own message, but I found the way to pass
arrow keys on command line (searched thru code and found it in
src/base/keyboard/prestroke.c) the documentation seems to be a bit old
(hopefully I'll try to update soon...)
It is done by send \M8 (for down arrow) etc...

I still have the problem with one of the dos program ignoring only the ESC
character.

cheers
suds.

On Sat, 11 Mar 2000, Suds wrote:

> Hi all,
> 
> I've breaking my head with this small problem of sending arrow keys to
> dosemu from the shell. I could not find in docs (README.txt) etc the
> sequence that needs to be sent for dosemu to interpret it as a down arrow
> key. So, I'm trying to send the whole escape sequence ^[[B but invain.
> Here is what I'm doing at the mo.
> 
> #/usr/bin/dos -I 'keystroke "\r\rfp.exe\r\^[[B"' 
> (there are few more keystrokes after that which I've not included..)
> 
> Any help or clue would be greatly appreciated.
> 
> OTOH, sending 'ESC' character works fine most of the time but this
> specific dos program does not take it in..any ideas why?
> 
> cheers
> suds.
> 


------------------------------

From: Curt Daugaard <[EMAIL PROTECTED]>
Date: Sat, 11 Mar 2000 17:45:31 -0600
Subject: How can I get a cursor in xdos?

I run IBM Passport for dos, which I need to establish a session
with a mainframe host.

Everything works great until my session on the mainframe actually
begins, at which time the cursor disappears.  I've tried diddling
with every video and graphics setting in the X-window section of
the dosemu config file, but with no change.  (None of the
settings in the application help either--not suprising since
everything is fine in native dos and dosemu at the console.)

I can get a cursor if I run the application under xtermdos, but
the terminal emulation is way too flaky.  I'd use the console but
I absolutely need to be able to cut and paste.

I'd be very greatful if anyone could give a clue about something
new to try.  (Better yet, a flat out solution!)

Thanks.

Curt
[EMAIL PROTECTED]

------------------------------

From: Suds <[EMAIL PROTECTED]>
Date: Sun, 12 Mar 2000 11:16:22 +0000 (GMT)
Subject: Where is 'kdos' ?

Hi there,

Does anyone know the whereabouts of the dosemu frontend 'kdos'?


cheers
suds.



------------------------------

From: Example user S.u.S.E. Linux 5.3 <[EMAIL PROTECTED]> 
Date: Fri, 10 Mar 2000 16:41:06 -0500
Subject: dosemulator

Example user S.u.S.E. Linux 5.3 <[EMAIL PROTECTED]> 
 Hi;
I have SuSE Linux v5.3, and I have installed the DosEmulator v0.66.7.0, it
works fine but some options of the same aplication were printed and others
not. e.g when I made a report that work directily with data base, it print
everything, but when I try to do something else it said that printer is no
ready.
 What could be happen with my emulator?

[ Saludos;
tengo SuSE Linux v5.3, y tengo instalado el DosEmulator v0.66.7.0, me
trabaja sin problemas, pero con algunas opciones dentro de la misma puedo
imprimrir y en otras no. ej: cuando trato de hacer un reporte que trabaja
directamente con las bases de datos, este imprime todo sin problemas, pero
cuando trato de hacer otra cosa, por ejemplo una factura, me dice que la
impresora no esta lista.
 Que puede estar pasando con mi emulador?]

                Rommel

  
                




------------------------------

From: Esa Tikka <[EMAIL PROTECTED]>
Date: Tue, 14 Mar 2000 09:50:14 +0200 (EET)
Subject: Re: dosemulator

On Fri, 10 Mar 2000, Example user S.u.S.E. Linux 5.3 wrote:

> Example user S.u.S.E. Linux 5.3 <[EMAIL PROTECTED]> 
>  Hi;
> I have SuSE Linux v5.3, and I have installed the DosEmulator v0.66.7.0, it

You  have a very old version of dosemu. The newest is dosemu-1.0.0.
List of servers to download it from is at ftp://ftp.dosemu.org/mirrors.txt

- -- 
Esa Tikka          ---  esa dot tikka at lut dot fi  ---
LTKK/ti3      ---> .satan, oscillate my metallic sonataS  <---
Vote against spam in EU @ http://www.politik-digital.de/spam


------------------------------

From: Iztok Saje <[EMAIL PROTECTED]>
Date: Tue, 14 Mar 2000 09:41:48 +0100
Subject: XDOS + Borland BP BGI + 640*480*16

Hello !

A while ago I wrote nice program using Borland Pascal 7.0 + BGI.
It runs in plain VGA mode: 640*480, 16 colours. 
I would like to run it in xdos (Using Slackware 7, 2.2.14)
I get blue colour picture somehow resembling real screen.

Now... I tried just everything that come to my mind, including
reading DOCs, this lists archives, recompiling my code,
changing dosemu.conf ...

I overlooked something obvious. 

Any advice ??

best regards,

   Iztok

xdos -DX produced this (partially edited).

debug flags:
debug flags: X
X: X_init
X: visual class is TrueColor
X: using true color visual
X: pixel size is 16 bits/pixel
X: MIT-SHM ErrorBase: 128
X: using MIT-SHM
X: X_keymap_init: X server vendor is "The XFree86 Project, Inc"
X: X_keymap_init: using DOSEMU's internal keycode translation
X: Using font "vga", size = 8 x 16
X: X_init: parent window: 0x26
X: X_init: screen = 0, root = 0x26, mainwindow = 0x6400002
X: X_init: mouse grabbing disabled
X: X_setmode: video_mode 0x3 (TEXT), size 80 x 25 (720 x 400 pixel)
X: expose event
X: window mapped
X: refresh_text_palette: 0 (0 -> 0)
X: refresh_text_palette: 1 (0 -> 21)
X: refresh_text_palette: 2 (0 -> 1344)
X: refresh_text_palette: 3 (0 -> 1365)                                          

X: refresh_text_palette: 7 (0 -> 44373)
X: refresh_text_palette: 8 (0 -> 21162)
X: refresh_text_palette: 9 (0 -> 21183)
X: refresh_text_palette: 10 (0 -> 22506)
X: refresh_text_palette: 11 (0 -> 22527)
X: refresh_text_palette: 12 (0 -> 64170)
X: refresh_text_palette: 13 (0 -> 64191)
X: refresh_text_palette: 14 (0 -> 65514)
X: refresh_text_palette: 15 (0 -> 65535)
X: focus in
 
X_keycode_process_key: keycode=36, scancode=28, released
X_put_keycode: scan=0x001c, released=1
X: X_setmode: video_mode 0x12 (GRAPH), size 80 x 30 (640 x 480 pixel)
X::NewXErrorHandler: error using shared memory
X: expose event
X: expose event
X: Mouse leaving window
X: X_setmode: video_mode 0x12 (GRAPH), size 80 x 30 (640 x 480 pixel)
X: focus out

------------------------------

From: "Henri J. Schlereth" <[EMAIL PROTECTED]>
Date: Tue, 14 Mar 2000 14:44:41 -0600 (CST)
Subject: Hello?

> Am I actually on a list or am I just sitting in a black-hole?
> 
> I will try question(s), is there a list somewhere that shows
> programs that have been successfully run and what tweaks
> were needed to run them?
> I just installed the latest and greatest and have had a
> variety of failures on some games like doom/doom2 that
> I was sure run on this. The documentation is a bit sparse
> but the mention of an Emusuccess.txt file was hopeful but not
> found.
> 
> I am running this on RH61+ and dosemu 1.0.0
> 
> My main goal is to shrink my Win95/Dos partitions on the only
> dual boot machine I have. I will gnash my teeth and leave it
> if there is no choice for games but not w/o trying.
> 
> Guess I will slap wine on as well while I await any/your
> response.
> 
> Newbie only to DOSEMU,
> Henri J. Schlereth
> "The Geezer Geek"
> 
> -- 
> -------------------------------------------------------------
> "All data leaves a trail. The search for data leaves a trail.
> The erasure of data leaves a trail.The absence of data, under
> the right circumstances,can leave the clearest trail of all-
> Dr. Kio Masada" 
> -------------------------------------------------------------
> 
> 

- -- 
- -------------------------------------------------------------
"All data leaves a trail. The search for data leaves a trail.
The erasure of data leaves a trail.The absence of data, under
the right circumstances,can leave the clearest trail of all-
Dr. Kio Masada" 
- -------------------------------------------------------------

------------------------------

From: Steffen Winterfeldt <[EMAIL PROTECTED]>
Date: Wed, 15 Mar 2000 14:07:17 +0100 (CET)
Subject: Re: XDOS + Borland BP BGI + 640*480*16

Hi,

On Tue, 14 Mar 2000, Iztok Saje wrote:
> A while ago I wrote nice program using Borland Pascal 7.0 + BGI.
> It runs in plain VGA mode: 640*480, 16 colours. 
> I would like to run it in xdos (Using Slackware 7, 2.2.14)
> I get blue colour picture somehow resembling real screen.
> 
> Now... I tried just everything that come to my mind, including
> reading DOCs, this lists archives, recompiling my code,
> changing dosemu.conf ...
> 
> I overlooked something obvious. 

It simply doesn't work yet. This includes all 16 color modes.


Bye,

Steffen

- -- 
"If, by chance, he does not like the food which you have given him, and if he
is desirous of eating human flesh, and would like to eat you, allow yourself
to be eaten."
(Montezuma, before sending his emissary Teoctlamacazqui to Cortes)


------------------------------

From: Victoria Welch <[EMAIL PROTECTED]>
Date: Tue, 14 Mar 2000 15:45:47 -0800
Subject: printer port works ?!?

Hi Y'all,

This isn't my first query on this matter, so I thought I would
try again and hopefully have better luck getting a response this
time.

I'm running RH 6.1 on an AMD K6-2/500 with 96 meg of RAM, the
dosemu version in question is:

dosemu-0.99.13.0

I used one of the 0.60 releases for a while with very good luck. 
I've been fighting with the versions that came with the last
couple of RH releases with discouragingly little luck :(.

I need to run microcontroller programmers and EPROM programmers
and to get fully over to linux, this HAS to happen.  I've been
head bashing for the past couple of days on this now (current
attempt), and if the answer is in the docs, I missed it :(.

I've also tried the #linix IRC channels on several of the IRC
networks and it seems that I am the only one trying to use dosemu
:(.

Basically all I want to do is to access the parallel port
(PC/x86) at 378 - it is currenly configured as an EPP/ECP (v1.7)
[1.9 didn't work either].

I am *TERMINALLY* confused as to how to do this, nothing I have
tried in the dosemu.conf file has made ANY difference (the port
remains unaccessable).  I'm going to delete this and reinstall
the RPM for it to get back to a known point, I'm more than sure
that the installation is fully scrambled at this point for all
the thrashing I have been doing :-(.

Any help would be most appreciated.  MORE THAN YOU KNOW!

Thanks for any assistance you can provide, I will be most
greatful!

Take care, Vikki.
- --
[EMAIL PROTECTED]

------------------------------

End of linux-msdos-digest V1 #168
*********************************

To subscribe to linux-msdos-digest, send the command:

Reply via email to