linux-msdos-digest Tuesday, 19 January 1999 Volume 01 : Number 131
In this issue:
----------------------------------------------------------------------
From: UNIXMAN <[EMAIL PROTECTED]>
Date: Tue, 12 Jan 1999 13:20:16 -0500 (EST)
Subject: Re: How do I access 'C' drive?
try editing your autoexec.bat to include the lredir command, I can't
remember the syntax off hand but that is what will give you access to
your dos partirion.
On Tue, 12 Jan 1999, Scott Dudley wrote:
>
> Hi folks. Sorry I sound so newbie but it's been a couple of years since
> I used dosemu. Yes, back then I had it all figured out and all setup
> but haven't used it in as long and my memory's not what it was. Just
> installed dosemu-0.98.4-1 on Red Hat 5.1. Ran ./setup-hdimage and
> edited msdos.sys and set BootGUI=0 (Win95). When I start dosemu, I get
> the following:
>
> Linux DOS emulator 0.98.4.0 $Date: 98/12/12 $
> Last configured at Fri Dec 11 22:58:08 MET 1998 on linux
> This is work in progress.
> Please test against a recent version before reporting bugs and problems.
>
> Bugs, Patches & New Code to [EMAIL PROTECTED]
>
> Starting Windows 95...
>
> [Host File System] drive D: is directory /
> [dosemu EMS 4.0 driver installed]
>
> The following file is missing or corrupted: C:\WINDOWS\IFSHLP.SYS
> Bad command or file name
>
> Cannot find WIN.COM, unable to continue loading Windows
>
> C:\>
>
> One more thing... how do I set it up so that when dos is started, I'm
> actually in my 'C' directory? The 'C" drive is mounted as vfat from
> Linux (/c). Seems like I used to use the subst command or somesuch but
> that's no longer valid in Win95.
>
> Many thanks.
>
> --
> Regards,
>
> Scott Dudley
>
>
>
>
------------------------------
From: [EMAIL PROTECTED]
Date: Tue, 12 Jan 99 20:23:35 MEZ
Subject: hdimage accessible via loopfs?
Is it possible to access a hdimage file from Linux by loop-mounting it ?
I already know that i can use mtools, and that i could probably use lredir
if i installed a commercial DOS.
Should i use a special offset (the 128 from do_mtools didn't help), any
other magical mount option, or is it simply not possible ?
Martin
- --
Dr. Martin Kroeker, daVeg GmbH Darmstadt CAD/CAM/CAQ [EMAIL PROTECTED]
------------------------------
From: Sebastian Unger <[EMAIL PROTECTED]>
Date: Tue, 12 Jan 1999 20:11:19 +0100
Subject: Re: xdos crashing my console
Jim Morris wrote:
>
> Reinhard Karcher wrote:
>
> > as far as I know, 4 Bit Graphics is not supported in xdos. Perhaps we'll
> > get
> > an answer from an expert.
>
> I looked into this about 6 months ago, and you have hit the nail on the
> head. xdos does NOT support any 4-bit graphics modes. I think the guys
> that work on xdos decided that the planar video modes would be more
> trouble to emulate than they are worth. And having done VGA graphics
> programming quite a bit when it came out, they are probably right.
>
> The only answer for now is that if you have a program that runs in a
> 16-color graphics mode under DOS, then you need to run it use DOSEMU on
> a console, and not under X.
First of all: Thanks for the answers.
Still I have two questions:
1. How is it possible, that any X program using standard X-lib calls (I
suspect dosemu does this ;-) can almost crash the X-Server? Doesn't this show
that there must be a bug in X as well? Should I send this to any X-related
Mailing list and if yes do you know the address?
2. On the console, VPA doesn't run either. There it isn't a problem with
graphics (at least I don't think so.) But once VPA has established graphics
mode and writes text to the screen all digits save 0 simply disapear. (Better
are not drawn from the beginning.) VPA writes some text in another font
(probably with it own routines) and there it is all just fine. However, the
status display and some other information (important information) is written
with the system font (and thus I suspect, by calling dos or BIOS routines)
and there all characters except 1-9 don't make it to the screen.
Has any body run into this before? And, even more important, has anybody any
suggestions about how to fix it? (I have tried virtually all combinations of
the relevant settings in dosemu.conf, but to no avail)
Bye, Seb
- --
*****************************************************************************
* Sebastian Unger | "Dear Watson, it is not difficult to *
* EMail: | get a good information. It is much *
* [EMAIL PROTECTED] | more to find it again." *
*****************************************************************************
------------------------------
From: "V.Yavuz" <[EMAIL PROTECTED]>
Date: Tue, 12 Jan 1999 21:50:33 +0200
Subject: character set
Hi All
My telnet and Linux (kernel version 2.0.32 ) can show Turkish character
ISO 8859-5 Latin5 ) but I have problem in dosemulator (version 0.98 ) when
I press Turkish specific characters there nothing but all English characters
works.Is there any way to setup user defined character & keyboard in
dosemulator.
Thanks in advance
------------------------------
From: Alan Tam <[EMAIL PROTECTED]>
Date: Wed, 13 Jan 1999 14:58:58 +1200
Subject: Compiling Dosemu-0.98.4.tgz
Hi,
After I ' tar -xzf dosemu-0.98.4.tgz ' as root in /, a
directory /dosemu-0.98.4
is created; and changed to that directory and started to compile by
issuing make.
After lots of message running across the screen finally it comes to an
error "command yacc not found"
Where can I get this command ?
Thanks
Alan
------------------------------
From: Nathan Reeves <[EMAIL PROTECTED]>
Date: Tue, 12 Jan 99 23:46:00 PST
Subject: Keymaps
Hopefully someone can point me in the right direction regarding this one.
I've loaded a linux server with DOSEMU 98.4 that I am going to use to run
a DOS app at a remote site. I've got DOSEMU running fine, the only
problem I'm having is getting some of the keys to work in the telnet
session. I read in the Readme that there is a keymap that I can load
which will allow me to use most of the keys (section 16), the only
problem is that I can't find the keymap that it refers to. Does anyone
have any idea what the readme is refering to, or if people have managed
to get their dos apps running which respond to the correct keystrokes in
telnet I would be extremely grateful to hear of any tips or ideas you may
have.
Hope someone can help
Thanks in advance
Nathan Reeves
Perth, Western Australia
------------------------------
From: Reinhard Karcher <[EMAIL PROTECTED]>
Date: Wed, 13 Jan 1999 07:28:09 +0100
Subject: Re: Compiling Dosemu-0.98.4.tgz
Alan Tam wrote:
>
> After I ' tar -xzf dosemu-0.98.4.tgz ' as root in /, a
> directory /dosemu-0.98.4
> is created; and changed to that directory and started to compile by
> issuing make.
> After lots of message running across the screen finally it comes to an
> error "command yacc not found"
>
Hi Alan,
install bison (the gnu equivalent for yacc)
Reinhard
------------------------------
From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: 13 Jan 1999 00:03:42 -0600
Subject: Re: hdimage accessible via loopfs?
>>>>> "MK" == mk <[EMAIL PROTECTED]> writes:
MK> Is it possible to access a hdimage file from Linux by loop-mounting it ?
Yes.
MK> I already know that i can use mtools, and that i could probably use lredir
MK> if i installed a commercial DOS.
MK> Should i use a special offset (the 128 from do_mtools didn't help), any
MK> other magical mount option, or is it simply not possible ?
The hdinfo tool (found in src/tools/periph) will tell you the correct offset
On one of mine it is 8832
Eric
------------------------------
From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: 12 Jan 1999 23:56:41 -0600
Subject: Re: xdos crashing my console
>>>>> "SU" == Sebastian Unger <[EMAIL PROTECTED]> writes:
SU> Jim Morris wrote:
>>
>> Reinhard Karcher wrote:
>>
>> > as far as I know, 4 Bit Graphics is not supported in xdos. Perhaps we'll
>> > get
>> > an answer from an expert.
Last I looked there was some limited 4 Bit graphics support,
(writes to only one plane at a time), but no full support.
>>
>> I looked into this about 6 months ago, and you have hit the nail on the
>> head. xdos does NOT support any 4-bit graphics modes. I think the guys
>> that work on xdos decided that the planar video modes would be more
>> trouble to emulate than they are worth. And having done VGA graphics
>> programming quite a bit when it came out, they are probably right.
>>
>> The only answer for now is that if you have a program that runs in a
>> 16-color graphics mode under DOS, then you need to run it use DOSEMU on
>> a console, and not under X.
SU> First of all: Thanks for the answers.
SU> Still I have two questions:
SU> 1. How is it possible, that any X program using standard X-lib calls (I
SU> suspect dosemu does this ;-) can almost crash the X-Server? Doesn't this show
SU> that there must be a bug in X as well? Should I send this to any X-related
SU> Mailing list and if yes do you know the address?
Yes. There is a bug in the X Server.
No. I don't know the address.
Yes. I've seen something similiar related to palattes and the X server
but I have not tracked.
SU> 2. On the console, VPA doesn't run either. There it isn't a problem with
SU> graphics (at least I don't think so.) But once VPA has established graphics
SU> mode and writes text to the screen all digits save 0 simply disapear. (Better
SU> are not drawn from the beginning.) VPA writes some text in another font
SU> (probably with it own routines) and there it is all just fine. However, the
SU> status display and some other information (important information) is written
SU> with the system font (and thus I suspect, by calling dos or BIOS routines)
SU> and there all characters except 1-9 don't make it to the screen.
SU> Has any body run into this before? And, even more important, has anybody any
SU> suggestions about how to fix it? (I have tried virtually all combinations of
SU> the relevant settings in dosemu.conf, but to no avail)
I don't know about this latter one at all.
ERic
------------------------------
From: Esa Tikka <[EMAIL PROTECTED]>
Date: Wed, 13 Jan 1999 11:26:01 +0200 (EET)
Subject: Re: xdos crashing my console
On Tue, 12 Jan 1999, Sebastian Unger wrote:
> 2. On the console, VPA doesn't run either. There it isn't a problem with
> graphics (at least I don't think so.) But once VPA has established graphics
> mode and writes text to the screen all digits save 0 simply disapear. (Better
> are not drawn from the beginning.) VPA writes some text in another font
> (probably with it own routines) and there it is all just fine. However, the
> status display and some other information (important information) is written
> with the system font (and thus I suspect, by calling dos or BIOS routines)
> and there all characters except 1-9 don't make it to the screen.
> Has any body run into this before? And, even more important, has anybody any
> suggestions about how to fix it? (I have tried virtually all combinations of
> the relevant settings in dosemu.conf, but to no avail)
Funny enough, I was just about to ask about this matter.
Too bad I've got no idea of how to make it work, but I've studied this
behaviour a little further.
It seems that dosemu isn't capable to display correctly text in hi-res
ega/vga graphics. I tested this with my old dos programs which use 4 bit
colors, and sorted out the not-displayed characters to be (in ascii, dec)
33, 34, 36..47, 49..64, 123..126
(in the screens in vpa where everything is ok it uses either standard text
mode or low-res graphics)
Hope someone can help with this, using VPA (or any app using this mode) is
quite useless without those characters.
- --
Esa Tikka --- esa dot tikka at lut dot fi ---
LTKK/ti2 ---> .satan, oscillate my metallic sonataS <---
------------------------------
From: [EMAIL PROTECTED]
Date: Wed, 13 Jan 99 12:24:33 MEZ
Subject: Re: hdimage accessible via loopfs?
Eric W. Biederman wrote:
>
>The hdinfo tool (found in src/tools/periph) will tell you the correct offset
>On one of mine it is 8832
Thanks. It appears to work quite well. Perhaps this could be added to
the documentation, unless loop-mounting is considered to be too
linux-specific ?
Martin
- --
Dr. Martin Kroeker, daVeg GmbH Darmstadt CAD/CAM/CAQ [EMAIL PROTECTED]
------------------------------
From: Hector Gutierrez <[EMAIL PROTECTED]>
Date: Wed, 13 Jan 1999 08:26:02 -0400 (VET)
Subject: lredir question
Hi,
I have just installled dosemu 0.98 in my Linux box (RedHat 5.1)
and I wonder if it is posible to access my linux partition using
lredir. There is not DOS partition in my machine, I just want to install
(and run) a couple of dos programs in my home directory. I have tried
the following command:
lredir D: linux\fs\<my home directory>
but just get:
error f0c2 redirecting drive D: to linux\fs\<...>
Is there anything wrong with lredir ?
thanks in advance
Hector Gutierrez
------------------------------
From: Reinhard Karcher <[EMAIL PROTECTED]>
Date: Wed, 13 Jan 1999 13:46:32 -0800
Subject: Re: lredir question
Hector Gutierrez wrote:
>
> I have just installled dosemu 0.98 in my Linux box (RedHat 5.1)
> I and wonder if it is posible to access my linux partition using
> lredir. There is not DOS partition in my machine, I just want to install
> (and run) a couple of dos programs in my home directory. I have tried
> the following command:
> lredir D: linux\fs\<my home directory>
> but just get:
> error f0c2 redirecting drive D: to linux\fs\<...>
>
> Is there anything wrong with lredir ?
>
Hi Hector,
if you use freedos (which came with 0.98.x): lredir doesn't work yet
under freedos;
you have to use MS-, DR-, NOVELL-DOS to get that functionality.
Reinhard
------------------------------
From: Alistair MacDonald <[EMAIL PROTECTED]>
Date: Wed, 13 Jan 1999 23:02:24 +0000 (GMT)
Subject: Re: Keymaps
On Tue, 12 Jan 1999, Nathan Reeves wrote:
> session. I read in the Readme that there is a keymap that I can load
> which will allow me to use most of the keys (section 16), the only
> problem is that I can't find the keymap that it refers to. Does anyone
> have any idea what the readme is refering to, or if people have managed
I guess this would be one of the files in the './etc/keymap' directory.
(Source distribution only ?)
Alistair
------------------------------
From: Alistair MacDonald <[EMAIL PROTECTED]>
Date: Wed, 13 Jan 1999 22:59:54 +0000 (GMT)
Subject: Re: hdimage accessible via loopfs?
On Wed, 13 Jan 1999 [EMAIL PROTECTED] wrote:
> Eric W. Biederman wrote:
> >
> >The hdinfo tool (found in src/tools/periph) will tell you the correct offset
> >On one of mine it is 8832
>
> Thanks. It appears to work quite well. Perhaps this could be added to
> the documentation, unless loop-mounting is considered to be too
> linux-specific ?
Fine - you write it, I'll get it included.
Alistair
------------------------------
From: "Sergey Koltogyan" <[EMAIL PROTECTED]>
Date: Thu, 14 Jan 1999 08:00:37 +0200
Subject: Error when make dosemu.
Hello.
I`m beginer.
I`m get dosemu-0_98_4.tgz.
Copy to the / (root)
tar -zxvf dosemu-0_98_4.tgz
Created directory /dosemu-0.98.4
go to this directory and write( as writed in QuickStart):
make
Process start and go to the Error:
lib/libenv_video.a(attremu.o): In function 'Attr_init':
attremu.o(.text+0x7): undefined references to 'vga'
make[2]: *** [/dosemu-0.98.4/0.98.4.0/bin/dos] Error 1
make[2]: Leaving directory '/dosemu-0.98.4/src'
make[1]: *** [default] Error 2
make[1]: Leaving directory '/dosemu-0.98.4'
What is this and what can i do ?
My computer: P233,32 Ram,Ide, 4GHd,S3V2Dx
RaedHat 2 :
uname --r
version: 2.0.36
uname --m
i586
uname --p
unknown
uname --v
uname (GNU sh-utils) 1.16
Koltogyan Sergey
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Date: Thu, 14 Jan 99 11:13:48 MEZ
Subject: Re: hdimage accessible via loopfs?
Alistair MacDonald wrote:
>
>Fine - you write it, I'll get it included.
>
Will do. However i would like to get additional input first:
a) is the loopfs concept a Linux speciality or does it work in *BSD*
as well ? If so, which options ?
b) It seems that any changes to the mounted hdimage (added or deleted files)
are not visible to an already running dosemu.
Furthermore, they will become visible to dosemu only after umounting it,
even if i use the "sync" mount option. Bug ? Feature ? Don't ever do
this ?
Martin
- --
Dr. Martin Kroeker, daVeg GmbH Darmstadt CAD/CAM/CAQ [EMAIL PROTECTED]
------------------------------
From: "V.Yavuz" <[EMAIL PROTECTED]>
Date: Thu, 14 Jan 1999 19:56:06 +0200
Subject: character set again
Hi All
My telnet and Linux (kernel version 2.0.32 ) can show Turkish character ISO
8859-5 Latin5 ) but I have problem in dosemulator (version 0.98 ) when I
press Turkish specific characters there nothing but all English characters
works.Is there any way to setup user defined character & keyboard in
dosemulator.
Thanks in advance
------------------------------
From: Sebastian Unger <[EMAIL PROTECTED]>
Date: Thu, 14 Jan 1999 21:09:04 +0100
Subject: Re: xdos crashing my console
Esa Tikka wrote:
>
> On Tue, 12 Jan 1999, Sebastian Unger wrote:
>
>
> Funny enough, I was just about to ask about this matter.
> Too bad I've got no idea of how to make it work, but I've studied this
> behaviour a little further.
>
> It seems that dosemu isn't capable to display correctly text in hi-res
> ega/vga graphics. I tested this with my old dos programs which use 4 bit
> colors, and sorted out the not-displayed characters to be (in ascii, dec)
> 33, 34, 36..47, 49..64, 123..126
>
> (in the screens in vpa where everything is ok it uses either standard text
> mode or low-res graphics)
>
> Hope someone can help with this, using VPA (or any app using this mode) is
> quite useless without those characters.
As the video cards native ROM should be responsible for creating the
characters, lets compare our video hardware. If it is the same, thats a good
indication that the cards BIOS is to blame.
My graphics card is a Diamond Stealth64 Video 2001 with BIOS version 2.06
Seb
- --
*****************************************************************************
* Sebastian Unger | "Dear Watson, it is not difficult to *
* EMail: | get a good information. It is much *
* [EMAIL PROTECTED] | more to find it again." *
*****************************************************************************
------------------------------
From: Esa Tikka <[EMAIL PROTECTED]>
Date: Fri, 15 Jan 1999 13:31:41 +0200 (EET)
Subject: Re: xdos crashing my console
On Thu, 14 Jan 1999, Sebastian Unger wrote:
> Esa Tikka wrote:
> > It seems that dosemu isn't capable to display correctly text in hi-res
> > ega/vga graphics. I tested this with my old dos programs which use 4 bit
> >
> As the video cards native ROM should be responsible for creating the
> characters, lets compare our video hardware. If it is the same, thats a good
> indication that the cards BIOS is to blame.
>
> My graphics card is a Diamond Stealth64 Video 2001 with BIOS version 2.06
Uh, mine is MiroVideo 22SD (Trio64V+ based) with bios version 1.06, so it
won't help us (very unlikely at least)...
- --
Esa Tikka --- esa dot tikka at lut dot fi ---
LTKK/ti2 ---> .satan, oscillate my metallic sonataS <---
------------------------------
From: Hans Lermen <[EMAIL PROTECTED]>
Date: Sat, 16 Jan 1999 00:12:02 +0100 (MET)
Subject: Re: character set again
On Thu, 14 Jan 1999, V.Yavuz wrote:
> Hi All
> My telnet and Linux (kernel version 2.0.32 ) can show Turkish character ISO
> 8859-5 Latin5 ) but I have problem in dosemulator (version 0.98 ) when I
> press Turkish specific characters there nothing but all English characters
> works.Is there any way to setup user defined character & keyboard in
> dosemulator.
> Thanks in advance
Sorry, but we don't have a turkish keytable, and to make one we need help
from a turkish guy like you ;-) So, go head and send us patches.
As a starting point look at etc/keymap/*, take one appropriate file, copy
it to /var/lib/dosemu/keymap/tr-latin5 and edit it to your needs.
In dosemu.conf you set
$_layout = "load tr-latin5"
$_X_keycode = (on) # if you want the table in X too
to get it loaded. The format of the keytable is described in
doc/README-tech.txt, chapter 2.2.11.
However, if you are using the Slang terminal (xterm, non-graphics console,
telnet e.t.c) this won't work because Slang handles such things itself
over TERMCAP or terminfo.
Hans
<[EMAIL PROTECTED]>
------------------------------
From: Hans Lermen <[EMAIL PROTECTED]>
Date: Sat, 16 Jan 1999 03:23:26 +0100 (MET)
Subject: dosemu-0.98.5 (stable) available
Hi Friends and Users of DOSEMU,
Just uploaded dosemu-0.98.5 (stable) to the usual places:
ftp.dosemu.org:/dosemu/Development/...
tsx-11.mit.edu:/pub/linux/ALPHA/dosemu/...
.../patchset-0.98.5.tgz
.../dosemu-0.98.5.tgz
.../dosemu-0.98.5-1.i386.rpm
The md5sums are:
a2a64946f1aec9d878c44ec454b016f7 dosemu-0.98.5-1.i386.rpm
75aa14e5b68abfc3dff94f4ffdc92d38 dosemu-0.98.5.tgz
e1d2a474ebad8085a4866a4171e4e216 patchset-0.98.5.tgz
Among some other fixes it now contains slang-1.2.2. Earlier
slang versions had a security whole, and if compiling dosemu with
a default setup, a vulnerable slang library was linked in.
This 'vulnerability' of dosemu <= 0.98.4 was reported on bugtrack and
lead to a deep diskussion on our internal developers list about
'security' of dosemu. The conclusion of this discussion was:
1. When running dosemu suid-root in full feature mode, its inherently
insecure (well, as DOS is itself;-). You may reduce the threat by
setting 'secure' in dosemu.conf, but that would not be a problem for
evil hackers. Hence, you _never_ should let a suid-root dosemu
run by untrusted users, period.
2. You _can_ savely control the access to dosemu via /etc/dosemu.users
and forbid/allow suid-root execution for dedicated users. This check
for dosemu.users is done at the very beginning _before_ any
initialization and before DOS actually is booted and, more important,
this also was done for the 'vulnerable' dosemu-0.98.x releases.
So, if you did configure your dosemu.users correctly, you had _not_
been vulnerable at any time, even with the vulnerable slang library.
3. _If_ you allow the world to execute your suid-root dosemu binary,
well, then a potential intruder would be very stupid to use the
complicated slang-lib exploit, its much easier to do other wise ;-)
4. If you want to run dosemu for unknown users, then let it run
non-suid-root. Though it then has restricted functionality, most
of what you want to offer to those users will be functional:
It can run on any slang terminal, it can run under X, it can
operate on serial ports, it can even execute DPMI programms
(what is very insecure when running suid-root).
Hence, just run dosemu non-suid-root if you want to be secure.
Conclusion: though we now have closed the bugtrack reported hole, please,
don't think you now can set the s-bit savely without tuning your
dosemu.users. You can't !!!
Nevertheless, have a lot of fun,
Hans
<[EMAIL PROTECTED]>
------------------------------
From: "Darrin Wortlehock" <[EMAIL PROTECTED]>
Date: Sat, 16 Jan 1999 12:51:23 +0800
Subject: Better Terminal/Telnet Support
Hi all,
I've been lurking for a while now, playing with Dosemu. First off, kudos to
the guys behind this gem.
I've been sifting thru the list archives and see that there has been
numerous calls for better terminal/telnet support. Specifically with
respect to scancode driven modes, ala wyse60/PCTerm. It seems to me that at
this stage, that these requests have not reached 'critical mass'.
I am interested in helping to co-ordinate the programmers, testers and
interested parties to give this a bit of a push. I would also be interested
in helping with the documentation for the non-console stuff. I have already
started to compile a list of terminals and emulators, and the results, as
well as my own how-to extensions.
So, I guess this could be considered a 'call to action'. Can any interested
parties email me privately so that I can put a contact list together and
start on a status-list, wish-list, success-stories-list and issues database.
Thanks In Advance.
Darrin Wortlehock
Aurum Computing.
mailto: [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Frank Knoll)
Date: Sat, 16 Jan 1999 18:50:03 +0000
Subject: DOSEMU 99.6
Hello,
i have a problem with dosemu-0.99.6 (also dosemu-0.98.4).
In directories with many files ( may this is one of the problem ...)
i start my make process under dos to make DSP code (cross-assembler, for
TI 3202X DSP),
i get the message " cant open/find "dmd.lst" and "dmd.obj". But the
DSP-Asm Prog. generates
this files , but they a not there !!! What goes wrong ??
With dosemu-0.97.10 i had no such problems ... Now i am using a SuSE6.0
Distribution
and now i can not compile dosemu-0.97.10. During compiling, it misses
the "socketio.h" file. But
now my system has no such file. ( ... i searched in all directories ...
) Furthermore i want to use
the newer dosemu versions.
Maybe you can give me some hints to solve the problem. Do you know the
problem with the
missing files ??
Thanks for your help
Frank Knoll, [EMAIL PROTECTED] or [EMAIL PROTECTED] )
------------------------------
From: Jim Howarth <[EMAIL PROTECTED]>
Date: Sun, 17 Jan 1999 01:36:59 -0500 (EST)
Subject: Time Bug
Unfortunately i was forced to reinstall Slack the other day which means I
needed to reinstall DOSEMU. I installed 0.98.5 and the time bug seems to
have come back.. at midnight it when nuts.. Can someone please repost
the patch?
Jim
------------------------------
From: Stefan Hudson <[EMAIL PROTECTED]>
Date: Sat, 16 Jan 1999 21:53:54 -0800
Subject: Re: Time Bug
On Sun, Jan 17, 1999 at 01:36:59AM -0500, Jim Howarth wrote:
> Unfortunately i was forced to reinstall Slack the other day which means I
> needed to reinstall DOSEMU. I installed 0.98.5 and the time bug seems to
> have come back.. at midnight it when nuts.. Can someone please repost
> the patch?
Sure. I take it that it worked for you, then? I never got any feedback
on it. It didn't make it into 98.5. Maintainers, what needs to be done
to get it in there?
This is against 98.4, but it should work against 98.5 if you just change the
path at the top. There were no modifications to this file in 98.5.
- --- dosemu-0.98.4/src/base/async/int.c Mon Nov 9 14:06:14 1998
+++ local-dosemu-0.98.4/src/base/async/int.c Sat Jan 2 18:40:28 1999
@@ -791,25 +791,31 @@
IBM and many clone BIOSes set the flag for AL rather than incrementing
it, leading to loss of a day if two consecutive midnights pass
without a request for the time (e.g. if the system is on but idle)
+ This appears to be irrelevant, because int8 sets the overflow flag,
+ so it can never be more than one here.
-> since the midnight flag is cleared, if an application calls this
-> function after midnight before DOS does, DOS will not receive the
-> midnight flag and will fail to advance the date
*/
case 0: /* read time counter */
+
+ /* has the midnight passed? Check and adjust offset. TICK_OVERFLOW_ADDR is set
+in int8. */
+ if (*(u_char *) TICK_OVERFLOW_ADDR) {
+ g_printf("TIMER: midnight overflow - adjusting offset.\n");
+ usr_delta_ticks -= 1573040; /* Adjust time base delta by a day. */
+ }
+
+ last_ticks = sys_base_ticks + usr_delta_ticks + (pic_sys_time >> 16);
/* it works because pic_sys_time has a zero reference. It doesn't
* account for timer speedups, but any decent DOS program should
* call back the original int8 at the 18.2 Hz rate... */
- - last_ticks = sys_base_ticks + usr_delta_ticks + (pic_sys_time >> 16);
- - /* has the midnight passed? */
- - if (last_ticks > 1573040) {
- - *(u_char *) (TICK_OVERFLOW_ADDR) += 0x1;
- - last_ticks -= 1573040;
- - }
+ if(last_ticks < 0) last_ticks = 0; /* Make sure return value is valid */
+
LO(ax) = *(u_char *) (TICK_OVERFLOW_ADDR);
LWORD(ecx) = (last_ticks >> 16) & 0xffff;
LWORD(edx) = last_ticks & 0xffff;
- - g_printf("TIMER: read timer = %lu\n", last_ticks);
+ g_printf("TIMER: read timer = %lu overflow = %d\n", last_ticks, *(u_char
+*)TICK_OVERFLOW_ADDR);
set_ticks(last_ticks); /* set_ticks is in rtc.c */
break;
- --
/// Stefan Hudson <[EMAIL PROTECTED]>
__ /// Senior Network Administrator - Monterey Bay Internet
\\\/// http://www.mbay.net/ - Email: [EMAIL PROTECTED]
\XX/ Voice: 831-642-6100 Fax: 831-642-6101 Modem: 831-642-6102
------------------------------
From: "Sokhwi Kim" <[EMAIL PROTECTED]>
Date: Sun, 17 Jan 1999 23:28:46 +0900
Subject: Can I print in dos program using dosemu?
This is a multi-part message in MIME format.
- ------=_NextPart_000_0007_01BE4271.2100F0C0
Content-Type: text/plain;
charset="euc-kr"
Content-Transfer-Encoding: base64
SSBoYXZlIHdpbmRvd3Mtb25seSBHREkgcHJpbnRlci4gDQpCdXQgaXQgb2ZmZXIgZG9zIGRyaXZl
ciBmb3Igd29yZHByb2Nlc3NvciBhbmQgQXV0b2NhZC4NClRvIHVzZSBkb3NlbXUgY2FuIEkgcHJp
bnQgaW4gdGhhdCBwcm9ncmFtPyANCg==
- ------=_NextPart_000_0007_01BE4271.2100F0C0
Content-Type: text/html;
charset="euc-kr"
Content-Transfer-Encoding: base64
PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBXMyBIVE1MLy9FTiI+DQo8SFRNTD4N
CjxIRUFEPg0KDQo8TUVUQSBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9a3NfY181NjAxLTE5
ODciIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlPg0KPE1FVEEgY29udGVudD0nIk1TSFRNTCA0Ljcy
LjMxMTAuNyInIG5hbWU9R0VORVJBVE9SPg0KPC9IRUFEPg0KPEJPRFkgYmdDb2xvcj0jZjBlOGQ4
Pg0KPERJVj48Rk9OVCBjb2xvcj0jMDAwMDAwIHNpemU9Mj5JIGhhdmUgd2luZG93cy1vbmx5IEdE
SSBwcmludGVyLiA8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSMwMDAwMDAgc2l6ZT0y
PkJ1dCBpdCBvZmZlciBkb3MgZHJpdmVyIGZvciB3b3JkcHJvY2Vzc29yIGFuZCANCkF1dG9jYWQu
PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+VG8gdXNlIGRvc2VtdSBjYW4gSSBwcmlu
dCBpbiB0aGF0IHByb2dyYW0/IA0KPC9GT05UPjwvRElWPjwvQk9EWT48L0hUTUw+DQo=
- ------=_NextPart_000_0007_01BE4271.2100F0C0--
------------------------------
From: Jim Howarth <[EMAIL PROTECTED]>
Date: Sun, 17 Jan 1999 12:07:07 -0500 (EST)
Subject: Re: Time Bug
> Sure. I take it that it worked for you, then? I never got any feedback
> on it. It didn't make it into 98.5. Maintainers, what needs to be done
> to get it in there?
Tee Hee... err.. it worked great... :) Sorry... :)
Now if only I could figure out why share.exe won't let me load up my
datafiles.
This is what I get (I doubt it is a DOSEMU problem):
(Openfile d:\home\bbs\bbs\data\archive.dat; Mode 65; Error 5)
Any ideas? This is using OpenDOS.
> This is against 98.4, but it should work against 98.5 if you just change the
> path at the top. There were no modifications to this file in 98.5.
Done... I'm surprised I figured that out.. :) This would be the second
time I have use a patch file..
!Xabbu
aka: Jim Howarth
------------------------------
From: Stafford Goodsell <[EMAIL PROTECTED]>
Date: Mon, 18 Jan 1999 01:33:49 +1030
Subject: Sound Code?
Hi there,
1st of all, congrats on creating a high quality program like dosemu -
well done.
What state is the sound code in? I have tried 98.5 and got the
following strange behaviour:
The sound works fine in the game Virtual Pool (apart from midi music), but
games that use DPMI such as Indycar 2 & Descent fail to auto detect &
cause a fault as follows:
TSF32: prev_tsf32 4C80
SS FF DS B7 ES FF FS 27F GS 27F
EAX 28 EBX 1C0 ECX 3 EDX 22C
ESI E000 EDI 28 EBP 406697D8 ESP 1724
CS:IP A7:000074CB ID 0D C0D 0 FLG 10202
CS= A7, USE16, byte granular, limit FFFF, base 9530, acc FB
SS= FF, USE32, byte granular, limit FFFF, base 18C10, acc 40F3
DS= B7, USE16, byte granular, limit FFFF, base 9530, acc F3
ES= FF, USE32, byte granular, limit FFFF, base 18C10, acc 40F3
FS= 27F, USE32, byte granular, limit 1000, base 40673000, acc 40F3
GS= 27F, USE32, byte granular, limit 1000, base 40673000, acc 40F3
CR0: unavailable
(This was taken from a run of setup.exe in descent shareware)
Dont trust this too much BTW, I had to type it in by hand, cos the
mouse pasting stuff wouldnt work in the video mode it went into (some
color text mode)
Anyway I have a real SB16, with kernel 2.0.36 & compiled dosemu 0.98.5 from
sources. Im wondering if its some configuration thing I did wrong, as I
know that the sound worked for these games in one of the later 0.64
releases? Heres what I put in the cfg file:
$_sound = (on) # sound support on/off
$_sb_base = (0x220)
$_sb_irq = (5)
$_sb_dma = (1)
$_sb_dsp = "/dev/dsp"
$_sb_mixer = "/dev/mixer"
$_mpu_base = "0x330"
(These are all the correct settings for my card)
If you want any more information, I will be glad to test for you, just ask.
Can you either tell me what im doing wrong, else this is a bug report :)
- --
Stafford Goodsell <[EMAIL PROTECTED]> _
C")
Programmer, administrator of marys.oz, (_)
avid gamer and all-round computer geek. -"-
------------------------------
From: Hans Lermen <[EMAIL PROTECTED]>
Date: Sun, 17 Jan 1999 16:14:05 +0100 (MET)
Subject: Re: Time Bug
yOn Sat, 16 Jan 1999, Stefan Hudson wrote:
> On Sun, Jan 17, 1999 at 01:36:59AM -0500, Jim Howarth wrote:
> > Unfortunately i was forced to reinstall Slack the other day which means I
> > needed to reinstall DOSEMU. I installed 0.98.5 and the time bug seems to
> > have come back.. at midnight it when nuts.. Can someone please repost
> > the patch?
>
> Sure. I take it that it worked for you, then? I never got any feedback
> on it. It didn't make it into 98.5. Maintainers, what needs to be done
> to get it in there?
You should prove that it doesn't break socalled 'compatible' DOS behave;-)
( We had a lot of kludges for this thing in the past. )
As it is currently, it servs the majority of DOS apps, with the patch
the behave for those apps could change. The midnight flag thing is a
design flaw of IBM (not dosemu) and you never can make happy all involved
parties;-)
As I last checked it, waiting for the role-over at the DOS prompt
doesn't show the bug. Polling the BIOS in the DOS application and
bypassing DOS, however, will lead to problems _due_ to the design flaw.
Hans
<[EMAIL PROTECTED]>
------------------------------
From: Stefan Hudson <[EMAIL PROTECTED]>
Date: Sun, 17 Jan 1999 11:57:44 -0800
Subject: Re: Time Bug
On Sun, Jan 17, 1999 at 04:14:05PM +0100, Hans Lermen wrote:
> > Sure. I take it that it worked for you, then? I never got any feedback
> > on it. It didn't make it into 98.5. Maintainers, what needs to be done
> > to get it in there?
>
> You should prove that it doesn't break socalled 'compatible' DOS behave;-)
> ( We had a lot of kludges for this thing in the past. )
> As it is currently, it servs the majority of DOS apps, with the patch
> the behave for those apps could change. The midnight flag thing is a
> design flaw of IBM (not dosemu) and you never can make happy all involved
> parties;-)
I don't think so... the problem is in INT 1A:00, and the midnight flag is
ALWAYS cleared when this function exits, when it calls set_ticks(). I
think the problem you are refering to is when the timer is read directly,
*without* using INT 1A.
The problem is that INT 1A, as it exists in 98.5, adjusts last_ticks
directly when the midnight overflow is set. usr_delta_ticks, which
contains the offset in ticks of the current time of day relative to
the start of the emulator, is not reset. So, the next tine INT 8 is
called, which is once every 20 seconds or so, it will reset the midnight
flag, causing the date to advance again.
The patch adjusts usr_delta_ticks INSTEAD of last_ticks, which seems to
be the right thing to do. It doesn't affect the loss of the midnight
flag directly; it just keeps it from getting reset after it is cleared.
> As I last checked it, waiting for the role-over at the DOS prompt
> doesn't show the bug. Polling the BIOS in the DOS application and
> bypassing DOS, however, will lead to problems _due_ to the design flaw.
It is DEFINATELY visable from DOS. Just start the emulator, set the clock
to 23:59 or so with the date command, then wait until after the rollover.
Type "time" to check the time. The first time, everything will seem fine.
Now, do it again. The day will have advanced by one. Each time you
do anything that calls INT1A:00, the day will advance by one. In fact,
if you just let the time command sit at it's prompt for a while, the
day will advance a few times, because time calls INT1A every few seconds
while it is running.
Programs that call INT1A many times per second, like in the busy loop of
a BBS, will appear to accelerate years at a time.
- --
/// Stefan Hudson <[EMAIL PROTECTED]>
__ /// Senior Network Administrator - Monterey Bay Internet
\\\/// http://www.mbay.net/ - Email: [EMAIL PROTECTED]
\XX/ Voice: 831-642-6100 Fax: 831-642-6101 Modem: 831-642-6102
------------------------------
From: Mario Moreira <[EMAIL PROTECTED]>
Date: Mon, 18 Jan 1999 12:40:14 -0000
Subject: Another (same) keyboard problem
Hi,
First of all, congratulations for this great software. Now for the problems
:)
I need to run an old accounting program for DOS remotelly. I setup a Linux
machine that acts as fileserver (with samba) and installed dosemu 0.98.2
(and .4 later). The accounting program runs over Baby/36 (a IBM system 36
emulator for DOS), and it runs ok if I run it on the console with
$_rawkeyboard = (on). If I run in X with xdos it also runs ok. But I need to
run it remotelly from a win95 machine connected to the Linux box with PPP.
So I've telneted to the machine and start dosemu and the program but some
keys doesn't work. The keys that doesnt work are the '-' and the '+' grey
keys on the keypad. My guess is that the Baby/36 emulator uses that keys
scancode to interpret them differentlly to emulate some keys on the original
IBM terminals. In telnet they just give the - and + signs (in console or
xdos those keys move to the next field).
How can I fix this? Is it possible to fix?
Thankx
- --
Mario Moreira
DID/CET Portugal Telecom
+351 34 8913200
------------------------------
From: "Darrin Wortlehock" <[EMAIL PROTECTED]>
Date: Tue, 19 Jan 1999 02:59:03 +0800
Subject: Re: Another (same) keyboard problem
Mario,
I'm actively chasing a similar solution.
I'm getting some pretty interesting results by using a VNC X Server as the
display for an xdos session, and then viewing it on the win95 machines with
the VNC windows client. This works brilliantly, except for the fact that I
can't work out how to call xdos from the console, and direct its output to a
(remote) display. You apparently have to call it from an xterm window, or
something. I really want to work out how to spawn a new vncserver running
nothing but xdos.... no window manager, no xterm, etc. Any ideas anyone?
I have not yet tested this method over a slower link.
I recently mentioned in this list that I am putting together whatever
resources I can find regarding the building of a multi-user DOS terminal
server system which is network aware. If you don't mind, I'd like to add
you to my list of people with similar interests. I guess I am trying to put
together the beginnings of a Special Interests Group for this topic.
One idea that came to me while playing with Dosemu and VNC was the
possibility of grafting a raw VNC server into Dosemu. I think this would
work well, because it would allow us to run our DOS apps anywhere, be it via
the svga VNC client, the X VNC client, or even our Windows 95 VNC clients.
There would be no problems (as far as I can see - which is probably not very
far) with graphics modes, or keyboard scancode capturing. I believe there
are already some folks playing with some VNC server code that takes stdin
and stdout. This could be our starting point ???? Any comments from the
programming gurus? Am I dreaming?
Regards,
Darrin Wortlehock.
Aurum Computing.
- -----Original Message-----
From: Mario Moreira <[EMAIL PROTECTED]>
To: '[EMAIL PROTECTED]' <[EMAIL PROTECTED]>
Date: Monday, 18 January 1999 20:25
Subject: Another (same) keyboard problem
>
>Hi,
>
>First of all, congratulations for this great software. Now for the problems
>:)
>
>I need to run an old accounting program for DOS remotelly. I setup a Linux
>machine that acts as fileserver (with samba) and installed dosemu 0.98.2
>(and .4 later). The accounting program runs over Baby/36 (a IBM system 36
>emulator for DOS), and it runs ok if I run it on the console with
>$_rawkeyboard = (on). If I run in X with xdos it also runs ok. But I need
to
>run it remotelly from a win95 machine connected to the Linux box with PPP.
>So I've telneted to the machine and start dosemu and the program but some
>keys doesn't work. The keys that doesnt work are the '-' and the '+' grey
>keys on the keypad. My guess is that the Baby/36 emulator uses that keys
>scancode to interpret them differentlly to emulate some keys on the
original
>IBM terminals. In telnet they just give the - and + signs (in console or
>xdos those keys move to the next field).
>
>How can I fix this? Is it possible to fix?
>
>Thankx
>
>
>--
>Mario Moreira
>DID/CET Portugal Telecom
>+351 34 8913200
------------------------------
From: Sebastian Unger <[EMAIL PROTECTED]>
Date: Mon, 18 Jan 1999 22:00:18 +0100
Subject: Re: xdos crashing my console
Esa Tikka wrote:
>
> On Thu, 14 Jan 1999, Sebastian Unger wrote:
>
> > Esa Tikka wrote:
> > > It seems that dosemu isn't capable to display correctly text in hi-res
> > > ega/vga graphics. I tested this with my old dos programs which use 4 bit
> > >
> > As the video cards native ROM should be responsible for creating the
> > characters, lets compare our video hardware. If it is the same, thats a good
> > indication that the cards BIOS is to blame.
> >
> > My graphics card is a Diamond Stealth64 Video 2001 with BIOS version 2.06
>
> Uh, mine is MiroVideo 22SD (Trio64V+ based) with bios version 1.06, so it
> won't help us (very unlikely at least)...
>
Ok, I'm at a loss now. Does anybody out there, who knows the dosemu
internals, have any suggestions how dosemu may influence the BIOS's display
routines in hires VGA-graphics modes when using console graphics or am I
completly wrong with the assumption that the cards BIOS is responsible for
displaying characters in these modes?
Seb
- --
*****************************************************************************
* Sebastian Unger | "Dear Watson, it is not difficult to *
* EMail: | get a good information. It is much *
* [EMAIL PROTECTED] | more to find it again." *
*****************************************************************************
------------------------------
From: Andrzej Pruski <[EMAIL PROTECTED]>
Date: Mon, 18 Jan 1999 23:18:13 +0100
Subject: Other keyboard problem
Hi.
This is a piece of Readme - Section 14 - Setting Hogthreshold:
> Notes: If your application is unkind enough to do waits using an int16h fcn 1h loop
>without calling the keyboard idle interrupt (int 28h), this
> code is not going to help much. If someone runs into a program like this, let me
>([EMAIL PROTECTED] ) know and I'll rewrite something into
> the int16 bios.
>
I'm using Borland Pascal 7.01 in DosEmu box and I encountered such a problem:
While editing with BP 7 IDE dosemu gets about 70% of power of my box. (PII
333). Unfortunnately mail address showed above looks no more available.
Any suggestions?
Andrzej Pruski
INT Gdansk, Poland
------------------------------
From: Roger Williams <[EMAIL PROTECTED]>
Date: 18 Jan 1999 19:39:33 -0500
Subject: Some DPMI functionality still missing?
I'm having trouble running a Cosmic (Whitesmiths) cross-assembler,
X6816, under dosemu (<= 0.98.5):
C:\>x6816 ctempc.c1
#error X6816 V3.60 (2) ctempc.c1:0 can't create tmp0.xE
The DOS extender ("Blinker 3.10 DOS Extender") used here appears to
detect and use a DPMI, VCPI or XMS host (but the only hints I have
were extracted from the executable with "strings", as the release
notes don't discuss DOS memory management).
The other associated development tools work OK, but they were built
with a later version of the same DOS extender ("Blinker 4.10").
$_dpmi is set to 8192 (other memory settings seem to be unimportant,
but X6816 hangs when $_dpmi is off). CONFIG.SYS is pretty minimal,
only increasing the environment space, and not loading HIMEM.SYS or a
memory manager.
The reason I suspect missing DPMI functionality is that this works
fine under OS/2 Warp (our previous development environment) and NT4
(as well as PC-DOS 7 and Win 3.1, of course).
Any ideas?
- --
Roger Williams finger me for my PGP public key
Coelacanth Engineering Inc consulting & turnkey product development
Middleborough, Massachusetts wireless * datacomm * DSP * ATE
tel +1 508 947-5585 * fax +1 508 861-0278 * http://www.coelacanth.com/
------------------------------
From: Dennis Reichel <[EMAIL PROTECTED]>
Date: Tue, 19 Jan 1999 01:27:54 -0500
Subject: difficulties with keyboard handler and foxpro 2.5
Hi, I have tried dosemu .98.5 and .99.6 on a x86 2.0.35 linux box.
It is working very nicely for my text based applications - except
in some cases the keyboard handling seems to be improper.
A MS Foxpro 2.5 application has defined thus:
on key label Alt-M <some action>
The Alt-M is not intercepted and the action is not dispatched.
Also:
In the built-in text editor, keystrokes such as Ctr-F <find> and
Ctrl-W, exit-save - are not handled properly. Ctr-M does insert a <cr>
but other Ctrl keys which should be active hot keys only will cause
the insertion of a literal character.
Are there any solutions available for this problem?
n.b. For this application to work properly in a DOS environment via
PcAnywhere (a remote control application) the special keyboard handler
level 2 must be selected.
Also, can someone tell me if there are any archives of this mailing list
which I may access?
Thanks, Dennis Reichel
------------------------------
From: "reuven" <[EMAIL PROTECTED]>
Date: Tue, 19 Jan 1999 00:55:11 PST
Subject: mouse problems
Hi,
I noticed that some dos software get stuck
when I move the mouse pointer out from the xdos
window. When I bring the pointer again to the
xdos window, if I have luck, it starts reacting
again and if not, it may start reacting even
after 10 minutes.
If I try the same thing not in X, i.e. with
dos under tcsh, there is no problem.
I have 2 questions:
1. I got the feeling that disabling the mouse
under xdos, will solve the problem for this
software. How can I disable it ? I use
$_com1 = ""
$_mouse = ""
$_mouse_dev = ""
and it is still detected.
2. What setup can be changed to make this
problem disapear?
Thanx in advance.
_______________________________________________________
Get your free, private email at http://mail.excite.com/
------------------------------
From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: 19 Jan 1999 00:36:14 -0600
Subject: Re: hdimage accessible via loopfs?
>>>>> "mk" == mk <[EMAIL PROTECTED]> writes:
mk> Alistair MacDonald wrote:
>>
>> Fine - you write it, I'll get it included.
>>
mk> Will do. However i would like to get additional input first:
mk> a) is the loopfs concept a Linux speciality or does it work in *BSD*
mk> as well ? If so, which options ?
Unknown. The BSD support has lagged in recent releases do to lack of interest.
mk> b) It seems that any changes to the mounted hdimage (added or deleted files)
mk> are not visible to an already running dosemu.
mk> Furthermore, they will become visible to dosemu only after umounting it,
mk> even if i use the "sync" mount option. Bug ? Feature ? Don't ever do
mk> this ?
Don't ever mount a partition or hdimage under linux while at the same time using
it with dosemu. For the partition case we have some checks to warn about this.
Eric
------------------------------
From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: 19 Jan 1999 00:43:16 -0600
Subject: Re: Another (same) keyboard problem
>>>>> "DW" == Darrin Wortlehock <[EMAIL PROTECTED]> writes:
DW> Mario,
DW> I'm actively chasing a similar solution.
DW> I'm getting some pretty interesting results by using a VNC X Server as the
DW> display for an xdos session, and then viewing it on the win95 machines with
DW> the VNC windows client. This works brilliantly, except for the fact that I
DW> can't work out how to call xdos from the console, and direct its output to a
DW> (remote) display. You apparently have to call it from an xterm window, or
DW> something. I really want to work out how to spawn a new vncserver running
DW> nothing but xdos.... no window manager, no xterm, etc. Any ideas anyone?
Set DISPLAY before you call dosemu and call dosemu with dos -X.
That should be all it takes. . .
But I won't garantee it. Especially with respect to pallate switching.
Eric
------------------------------
From: "Jarno Kesteloo" <[EMAIL PROTECTED]>
Date: Tue, 19 Jan 1999 12:50:35 +0100
Subject: Problem with DOSEMU !!!
Hello,
How can i see the free memory in DOSEMU for example a command that do the
same as mem in MS-Dos.
Can you help me ?
I have DOSEMU 0.98.0, the orginal by RedHat 5.2.
Greatings Jarno
------------------------------
From: Mario Moreira <[EMAIL PROTECTED]>
Date: Tue, 19 Jan 1999 18:24:34 -0000
Subject: RE: Another (same) keyboard problem
> Mario,
>
> I'm actively chasing a similar solution.
>
> I'm getting some pretty interesting results by using a VNC X
> Server as the
> display for an xdos session, and then viewing it on the win95
> machines with
> the VNC windows client. This works brilliantly, except for
[...]
> I have not yet tested this method over a slower link.
I think it wont be very fast. In my case, I have only a 33.6 Kbps modem
connecting the two machines.
I was thinking of using a nice console telnet for win (95/NT) that I've
found, so the win95 machine doesn't event need to see the windows (telnet in
fullscreen mode). This would be the perfect solution to me. Most strange, is
that the msdos edit program works ok (using TERM=linux). The Alt+F for
opening the File menu and so on. It's just the keypad that isn't working.
> I recently mentioned in this list that I am putting together whatever
> resources I can find regarding the building of a multi-user
> DOS terminal
> server system which is network aware. If you don't mind, I'd
> like to add
> you to my list of people with similar interests. I guess I
> am trying to put
> together the beginnings of a Special Interests Group for this topic.
:)
I've read the archives of this list for similar questions, and didn't find
any answer to my problem, and it seems lot's of people are having similar
problems.
> One idea that came to me while playing with Dosemu and VNC was the
> possibility of grafting a raw VNC server into Dosemu. I
The use of a thin Xserver (any suggestion?) on the Windows machine, and
starting xdos with the DISPLAY could do, but will it work over a 33.6K link?
I don't really know the internals of dosemu, but why it works with xdos,
even in a remote machine, and it doesn't work with telnet? Can somebody
explain that to me?
Regards,
- --
Mario Moreira
DID/CET Portugal Telecom
+351 34 8913200
------------------------------
From: "Darrin Wortlehock" <[EMAIL PROTECTED]>
Date: Wed, 20 Jan 1999 03:09:27 +0800
Subject: AALib and full graphics support for terminals!!!
Has anybody looked at the AALib (Ascii Art) graphics library?
I have only just started to become acquainted with the source for DOSEMU,
but from what I've seen of how we currently handle graphics mode for the
console, I think that this crazy idea might just work.
If we could modify the existing video code to use AALib instead of VGALib,
we would have approximated full video mode for terminals and telnet
sessions. There is even a drop-in replacement version of VGALib available.
I can see it now ..... Doom for VT-100!!!! ;-)
Regards,
Darrin Wortlehock
Aurum Computing.
------------------------------
From: [EMAIL PROTECTED]
Date: Tue, 19 Jan 1999 20:57:26 +0100 (MET)
Subject: Re: hdimage accessible via loopfs?
On 19-Jan-99 Eric W. Biederman wrote:
Eric,
You wrote:
>
> Don't ever mount a partition or hdimage under linux while at the same time
> using
> it with dosemu. For the partition case we have some checks to warn about
> this.
>
I'm using DOSEmu for two-and-a-half year now and my DOS-partition is _ALWAYS_
mounted. I have had no problems with that so far...
However, I don't access the partition from within Linux while running DOSEmu.
Is that the reason for my 'no problems'?
- ---
"Of course power tools and alcohol don't mix. Everyone knows power
tools aren't soluble in alcohol ..."
-- Crazy Nigel
Best regards, don't let the bits byte!
Ivo Naninck
~
~
wq!
------------------------------
From: [EMAIL PROTECTED]
Date: Tue, 19 Jan 99 21:20:54 MEZ
Subject: Re: hdimage accessible via loopfs?
Ivo Naninck wrote:
>I'm using DOSEmu for two-and-a-half year now and my DOS-partition is _ALWAYS_
>mounted. I have had no problems with that so far...
>However, I don't access the partition from within Linux while running DOSEmu.
>Is that the reason for my 'no problems'?
My experience with the loop-mounted hdimage is similar - and of course i
have avoided writing to it from both 'sides' at the same time. Things you
can survive unpunished are not always things you can tell other people about
in a README file...
Martin
- --
Dr. Martin Kroeker, daVeg GmbH Darmstadt CAD/CAM/CAQ [EMAIL PROTECTED]
------------------------------
End of linux-msdos-digest V1 #131
*********************************
To subscribe to linux-msdos-digest, send the command:
