linux-msdos-digest Friday, 7 May 1999 Volume 01 : Number 141
In this issue:
----------------------------------------------------------------------
From: Mark Lawrence <[EMAIL PROTECTED]>
Date: Fri, 30 Apr 1999 20:52:23 +0930 (CST)
Subject: Re: Serial ports and c++ 'outp'
Hi again,
I had a crash right after downloading some mail and lost about five
messages. If anyone replied to my original post could they please re-send
it.
Thanks,
Mark.
- --
,-_|\
/ . \ Mark Lawrence
\_,-._/ [EMAIL PROTECTED]
v
- ---------- Forwarded message ----------
Date: Thu, 29 Apr 1999 20:46:48 +0930 (CST)
From: Mark Lawrence <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Serial ports and c++ 'outp'
Greetings all,
I have a problem to do with a c++ program written for dos, which makes
heavy us of an 'outp' (dos system/library call? - I have not seen this
before) to communicate with a serial device. 'outp' appears to write
directly to a port address (along the likes of 0x3f8,9,a,b,c etc). I
assume that because it uses this call that setting $_com1 to a value will
not be of any use, and so I need to define a list of ports that dosemu
will allow to be directly written to.
I do not find any evidence of these calls failing. In fact, if I turn on
enough dosemu debugging I can see that port read and write calls are being
made, yet the dos program fails to recognise that the device is on the end
of the line. The program works extremely reliably under standard dos.
Communication with the COM? ports works fine with other programs when I
set $_com?, so, I was wondering if anyone knows of something else I can
try, or how I can write to the COM? devices from dos using some more
standard call that doesn't attempt to write directly to the hardware.
Thanks,
Mark.
- --
,-_|\
/ . \ Mark Lawrence
\_,-._/ [EMAIL PROTECTED]
v
------------------------------
From: Bjorn Eriksson <[EMAIL PROTECTED]>
Date: Fri, 30 Apr 1999 14:02:39 +0200
Subject: SV: Serial ports and c++ 'outp'
Hello Mark,
>I had a crash right after downloading some mail and lost about five
>messages. If anyone replied to my original post could they please re-send
>it.
>I have a problem to do with a c++ program written for dos, which makes
>heavy us of an 'outp' (dos system/library call? - I have not seen this
>before) to communicate with a serial device. 'outp' appears to write
>directly to a port address (along the likes of 0x3f8,9,a,b,c etc). I
>assume that because it uses this call that setting $_com1 to a value will
>not be of any use, and so I need to define a list of ports that dosemu
>will allow to be directly written to.
'outp' and 'inp' (or outportb, inportb depending on what compiler you use) are MS-DOS
compiler intrinsics that translates directly to assembly instruction 'out' resp. 'in'.
I haven't looked at dosemu's source but I'd be a bit suprised if it didn't emulate
the IO-ports 0x3F8 and 0x2F8 considering that _all_ programs use these directly since
the BIOS and system support for serial kommunication (int 0x14) is so poor.
//Bj�rn.
------------------------------
From: <[EMAIL PROTECTED]>
Date: Fri, 30 Apr 1999 15:00:13 GMT
Subject: Printing problems
Hi, Im sure you all remember me, I had a problem with printing
in Dosemu.
I am running a program written in FoxPro, quite complex actually,
and for the most part it runs! Great! No more windows needed....almost.
The Problem is it tends to crash just after printing.
It's not exactly consistent, once in awhile the program
continues without a problem, but usually it crashes,
not when printing, but after printing when you try and continue
on into a menu.
So what I need help with is how to fix this.
It's #1 on my priority list as an employee.
How can I learn to read the error printouts when dosemu crashes...
(sorry, i didnt specify...dosemu crashes...not just the program itself)
I have to figure this out...no matter how long it takes...so
where do I start, if noone knows the answer.
- -Josh
------------------------------
From: Julien Sylvestre <[EMAIL PROTECTED]>
Date: Fri, 30 Apr 1999 12:13:42 EDT
Subject: video mode with a Diamond 64, I Meg
What video configuration should I use to make dosemu ver 0.64.3 works with my Diamond
64, 1Meg card ?
Thanks,
Julien Sylvestre.
------------------------------
From: Bill Bond <[EMAIL PROTECTED]>
Date: Fri, 30 Apr 1999 10:27:08 -0700 (PDT)
Subject: [none]
"No gates, no windows, ... it's open!"
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
------------------------------
From: Rodney Fisk <[EMAIL PROTECTED]>
Date: Fri, 30 Apr 1999 12:48:33 -0500
Subject: Re: Printing problems
Hi,
This may or may not matter, but what version of DOS are you using?
Regards,
Rod Fisk<[EMAIL PROTECTED]>
[EMAIL PROTECTED] wrote:
> Hi, Im sure you all remember me, I had a problem with printing
> in Dosemu.
>
> I am running a program written in FoxPro, quite complex actually,
> and for the most part it runs! Great! No more windows needed....almost.
>
> The Problem is it tends to crash just after printing.
>
> It's not exactly consistent, once in awhile the program
> continues without a problem, but usually it crashes,
> not when printing, but after printing when you try and continue
> on into a menu.
>
> So what I need help with is how to fix this.
> It's #1 on my priority list as an employee.
>
> How can I learn to read the error printouts when dosemu crashes...
> (sorry, i didnt specify...dosemu crashes...not just the program itself)
>
> I have to figure this out...no matter how long it takes...so
> where do I start, if noone knows the answer.
>
> -Josh
------------------------------
From: [EMAIL PROTECTED] (David Hodges)
Date: Sat, 1 May 1999 08:46:09 +3600 (NZST)
Subject: Re: Printing problems
> I am running a program written in FoxPro, quite complex actually,
> and for the most part it runs! Great! No more windows needed....almost.
>
> The Problem is it tends to crash just after printing.
It says in the dosemu HOWTO:
FoxPro 2.6 won't run on network drives.
So if you are using lredir, try not using it and see whether the problem
goes away.
>dosemu crashes...not just the program itself
If a program running under dosemu does something illegal, such as
generating a General Protection Exception, trying to execute an
invalid instruction etc., dosemu will print an error message and
terminate. This (usually) means a bug in the dos program, not in
dosemu. If it was a bug in dosemu it would not be so hard to debug
because we have the source code for dosemu but a bug in a dos program
that only manifests because dosemu does not perfectly emulate the PC
environment that the program expects is much harder to debug because
usually you do not have the source code for the dos program.
------------------------------
From: "Dave Olson" <[EMAIL PROTECTED]>
Date: Fri, 30 Apr 1999 15:01:09 PDT
Subject: dosemu 0.99.6 problems
I have a problem, and maybe someone here could help me out. I'm running
RedHat 5.2 on my i486, and I've been trying to get a few problems fixed with
dosemu 0.99.6 on my machine. One of the biggest problems is that everytime
I try and access the floppy drive, the computer locks up. If I run a dir a:
command, it gives me the directory listing of the disk, and then locks up.
The other problem is with the graphics. When I was running redhat 5.0 and
dosemu 0.66, I managed to successfully install such programs as warcraft and
the old, classic game doom and run them on my machine. Now, however, it
installs the program, but every time I try and run a setup or the program
itself, it gives me this error message:
ERROR: general protection at 0x1696f: 66
ERROR: SIGSEGV, protected insn...exiting!
I'm logged in as root when this occurs, and there's no difference in any
other account. The other problem I have seen is that when I try and use
graphics view on Word Perfect 6.0 for dos with any account EXCEPT root, it
locks up.
Being pretty new with linux, I can't figure out what exactly is going wrong,
but I'd like to be able to fix it. I've asked a few people I know, and they
can't figure it out either. I thought maybe someone there could look at it,
or hopefully even already know the problem and how to fix it. Just some
info on my system:
i486 dx2 66MHz
16Mb RAM
Trident tgui9400CXi VL-Bus chipset
1024k video ram
If you need more than this, let me know and I'll get you what I can. Thanks
for everything, and let me know if you can help me find a solution.
Dave Olson
_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com
------------------------------
From: "Dave Olson" <[EMAIL PROTECTED]>
Date: Fri, 30 Apr 1999 16:11:21 PDT
Subject: error
Somehow on my last message regarding errors in my dosemu I said I was using
dosemu 0.99.6 I meant 0.98.6 if that would make a difference.
Thanks again
Dave
_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com
------------------------------
From: David Hodges <[EMAIL PROTECTED]>
Date: Sat, 01 May 1999 15:40:51 +1200
Subject: new version of dosemu HOWTO
I've stuck the html version at
http://www.geocities.com:80/SiliconValley/Byte/4602/dosemu-HOWTO.html
I tried to upload the SGML version as well but geocities only allows
HTML and images.
If you have the time and knowledge, please have a look and let me know
if I have made
any mistakes or if you have any suggestions.
------------------------------
From: [EMAIL PROTECTED] (David Hodges)
Date: Sat, 1 May 1999 18:37:31 +1200 (NZST)
Subject: Re: dosemu 0.99.6 problems
> dosemu 0.66, I managed to successfully install such programs as warcraft and
> the old, classic game doom and run them on my machine. Now, however, it
> installs the program, but every time I try and run a setup or the program
> itself, it gives me this error message:
>
> ERROR: general protection at 0x1696f: 66
> ERROR: SIGSEGV, protected insn...exiting!
I think I better put this in the frequently asked questions list.
You need to change the line
$_dpmi = (off)
to
$_dpmi = (4096)
(or more) to run programs such as Doom that use DPMI
(I believe it's off by default because DPMI programs can theoretically do
naughty things (but probably not accidentally so it's only a problem if you
don't trust the program you're running))
------------------------------
From: Sam Steingold <[EMAIL PROTECTED]>
Date: 01 May 1999 16:00:38 -0400
Subject: dosemu-0.99.10-4
When running a graphical application under dos -X, the window is resized
to the icon size (about 3x4 cm) - apparently due to the low res used by
the DOS program. Is it possible to make dosemu to display several
pixels for each one that the app displays? I tried:
$_X_mode13fact = (4) # initial size factor for video mode 0x13 (320x200)
$_X_winsize = "80,50" # "x,y" of initial windows size (defaults to float)
no good.
Changing X resolution just to run the dos game is not an option.
- --
Sam Steingold (http://www.goems.com/~sds) running RedHat5.2 GNU/Linux
Micros**t is not the answer. Micros**t is a question, and the answer is Linux,
(http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation.
Yeah, yeah, I love cats too... wanna trade recipes?
------------------------------
From: [EMAIL PROTECTED] (David Hodges)
Date: Sun, 2 May 1999 08:19:50 +1200 (NZST)
Subject: Re: dosemu-0.99.10-4
> When running a graphical application under dos -X, the window is resized
> to the icon size (about 3x4 cm) - apparently due to the low res used by
> the DOS program. Is it possible to make dosemu to display several
> pixels for each one that the app displays?
Yes, it is.
Clicking on the edge of the window and dragging it to resize it
(just like any other X application) works for me (there is an
option to enable/disable this I think documented in one of
README.txt or README-tech.txt - can't remember what it's called
off hand)
------------------------------
From: Hans Lermen <[EMAIL PROTECTED]>
Date: Sat, 1 May 1999 22:07:25 +0200 (MEST)
Subject: Re: dosemu 0.99.6 problems
On Sat, 1 May 1999, David Hodges wrote:
> > dosemu 0.66, I managed to successfully install such programs as warcraft and
> > the old, classic game doom and run them on my machine. Now, however, it
> > installs the program, but every time I try and run a setup or the program
> > itself, it gives me this error message:
> >
> > ERROR: general protection at 0x1696f: 66
> > ERROR: SIGSEGV, protected insn...exiting!
>
> I think I better put this in the frequently asked questions list.
> You need to change the line
> $_dpmi = (off)
> to
> $_dpmi = (4096)
> (or more) to run programs such as Doom that use DPMI
>
> (I believe it's off by default because DPMI programs can theoretically do
> naughty things (but probably not accidentally so it's only a problem if you
> don't trust the program you're running))
Yes, but this is only true if DOSEMU runs suid-root.
If DOSEMU runs non-suid (low feature) its save to allow DPMI.
===
DOSEMU now can run most of DOS-applications under X, even when not running
suid-root, so 'low feature' mostly applies on not being able to access
hardware ports / RAM directly and to get real IRQs passed.
Hans
<[EMAIL PROTECTED]>
------------------------------
From: [EMAIL PROTECTED]
Date: Sat, 1 May 1999 21:29:17 GMT
Subject: file sharing bug + patch
Hi,
On at least MS-DOS 6.0 with SHARE.EXE installed, INT21 function 3CH,
"Create a File", fails if the file exists and is currently opened by
another program.
R:base 1.01, an old database program, relies on that behavior to protect
against simultaneous access to the same database.
However, DOSEMU allows the function to succeed.
Here is a patch that implements the MS-DOS behavior. It moves Maxim
Ruchko's file-sharing code into a separate function, and replaces
"open(O_TRUNC)" with "open(); check sharing; ftruncate()".
Nick Duffek
[EMAIL PROTECTED]
- --- dosemu-0.99.11/src/dosext/mfs/mfs.c.orig Thu Apr 22 16:47:42 1999
+++ dosemu-0.99.11/src/dosext/mfs/mfs.c Sat May 1 17:03:37 1999
@@ -2531,6 +2531,59 @@
return (TRUE);
}
+static boolean_t
+share(int fd, boolean_t writing, sft_t sft)
+{
+ /*
+ * Return whether FD doesn't break any sharing rules. FD was opened for
+ * writing if WRITING and for reading otherwise.
+ *
+ * Written by Maxim Ruchko, and moved into a separate function by Nick
+ * Duffek <[EMAIL PROTECTED]>. Here are Maxim's original comments:
+ *
+ * IMHO, to handle sharing modes at this moment,
+ * it's impossible to know wether an other process already
+ * has been opened this file in shared mode.
+ * But DOS programs (FoxPro 2.6 for example) need ACCESS_DENIED
+ * as return code _at_ _this_ _point_, if they are opening
+ * the file exclusively and the file has been opened elsewhere.
+ * I place a lock in a predefined place at max possible lock length
+ * in order to emulate the exclusive lock feature of DOS.
+ * This lock is 'invisible' to DOS programs because the code
+ * (extracted from the Samba project) in mfs lock requires that the
+ * handler wrapps the locks below or equal 0x3fffffff (mask=0xC0000000)
+ * So, 0x3fffffff + 0x3fffffff = 0x7ffffffe
+ * and 0x7fffffff is my start position. --Maxim Ruchko
+ */
+ struct flock fl;
+ int share_mode = ( sft_open_mode( sft ) >> 4 ) & 0x7;
+ fl.l_whence = SEEK_SET;
+ fl.l_start = 0x7fffffff;
+ fl.l_len = 1;
+ fl.l_pid = 0;
+ switch ( share_mode ) {
+ case COMPAT_MODE:
+ case DENY_ALL:
+ case DENY_WRITE:
+ case DENY_READ:
+ fl.l_type = !writing ? F_RDLCK : F_WRLCK;
+ break;
+ case DENY_ANY:
+ fl.l_type = F_RDLCK;
+ break;
+ default:
+ fl.l_type = F_WRLCK;
+ Debug0((dbg_fd, "internal SHARE: unknown sharing mode %x\n",
+ share_mode));
+ break;
+ }
+ if ( fcntl( fd, F_SETLK, &fl ) == 0 )
+ return (TRUE);
+
+ Debug0((dbg_fd, "internal SHARE: access denied by locks fd=%x\n", fd));
+ return (FALSE);
+}
+
static int
dos_fs_redirect(state)
state_t *state;
@@ -3103,49 +3156,10 @@
SETWORD(&(state->eax), ACCESS_DENIED);
return (FALSE);
}
- - {
- - /* IMHO, to handle sharing modes at this moment,
- - * it's impossible to know wether an other process already
- - * has been opened this file in shared mode.
- - * But DOS programs (FoxPro 2.6 for example) need ACCESS_DENIED
- - * as return code _at_ _this_ _point_, if they are opening
- - * the file exclusively and the file has been opened elsewhere.
- - * I place a lock in a predefined place at max possible lock length
- - * in order to emulate the exclusive lock feature of DOS.
- - * This lock is 'invisible' to DOS programs because the code
- - * (extracted from the Samba project) in mfs lock requires that the
- - * handler wrapps the locks below or equal 0x3fffffff (mask=0xC0000000)
- - * So, 0x3fffffff + 0x3fffffff = 0x7ffffffe
- - * and 0x7fffffff is my start position. --Maxim Ruchko
- - */
- - struct flock fl;
- - int share_mode = ( sft_open_mode( sft ) >> 4 ) & 0x7;
- - fl.l_whence = SEEK_SET;
- - fl.l_start = 0x7fffffff;
- - fl.l_len = 1;
- - fl.l_pid = 0;
- - switch ( share_mode ) {
- - case COMPAT_MODE:
- - case DENY_ALL:
- - case DENY_WRITE:
- - case DENY_READ:
- - fl.l_type = ( unix_mode == O_RDONLY ) ? F_RDLCK : F_WRLCK;
- - break;
- - case DENY_ANY:
- - fl.l_type = F_RDLCK;
- - break;
- - default:
- - fl.l_type = F_WRLCK;
- - Debug0((dbg_fd, "internal SHARE: unknown sharing mode %x opening %s\n",
- - share_mode, fpath));
- - break;
- - }
- - if ( fcntl( fd, F_SETLK, &fl ) ) {
- - close( fd );
- - Debug0((dbg_fd, "internal SHARE: access denied by locks fd=%x\n", fd));
- - SETWORD(&(state->eax), ACCESS_DENIED);
- - return (FALSE);
- - }
+ if (!share(fd, unix_mode != O_RDONLY, sft)) {
+ close( fd );
+ SETWORD(&(state->eax), ACCESS_DENIED);
+ return (FALSE);
}
}
@@ -3243,14 +3257,14 @@
bs_pos = i;
}
- - if ((fd = open(fpath, (O_RDWR | O_CREAT | O_TRUNC),
+ if ((fd = open(fpath, (O_RDWR | O_CREAT),
get_unix_attr(0664, attr))) < 0) {
strncpy(buf, fpath, bs_pos);
buf[bs_pos] = EOS;
find_file(buf, &st);
strncpy(fpath, buf, bs_pos);
Debug0((dbg_fd, "trying '%s'\n", fpath));
- - if ((fd = open(fpath, (O_RDWR | O_CREAT | O_TRUNC),
+ if ((fd = open(fpath, (O_RDWR | O_CREAT),
get_unix_attr(0664, attr))) < 0) {
Debug0((dbg_fd, "can't open %s: %s (%d)\n",
fpath, strerror(errno), errno));
@@ -3261,6 +3275,14 @@
#endif
return (FALSE);
}
+ }
+
+ if (!share(fd, TRUE, sft) || ftruncate(fd, 0) != 0) {
+ Debug0((dbg_fd, "unable to truncate %s: %s (%d)\n",
+ fpath, strerror(errno), errno));
+ close(fd);
+ SETWORD(&(state->eax), ACCESS_DENIED);
+ return FALSE;
}
if (can_do_root_stuff) {
------------------------------
From: "M. Leo Cooper" <[EMAIL PROTECTED]>
Date: Sat, 1 May 1999 20:02:11 -0700 (MST)
Subject: MSDOS partition access
The following topics may already have been dealt with, but I lost my
list archives in a HD crash (didn't backup in time).
This advice is courtesy of Professor Trial-and-Error.
- -------------------------------------------------------------------
How to directly access an MSDOS partition from dosemu without using
lredir.
- -------------------------------------------------------------------
1) /etc/dosemu.users should read:
root c_all
all c_all
This lets ordinary users run dosemu, which is fine for a single-user system.
If you run dosemu on a network, you might consider restricting user privileges
for security reasons.
2) Edit the '$_hdimage' line in /etc/dosemu.conf (or ~/.dosemurc) to read:
$_hdimage = "/dev/hda4"
Note that this assumes the DOS partition is on /dev/hda4. If otherwise,
change accordingly. Be aware also that the DOS partion will also need
to be 'umounted' before it can be accessed by dosemu.
3) In /usr/bin, the file permissions for 'dos' and its progeny are as follows.
- -rwxr-xr-x 1 root 1013425 Apr 29 22:21 dos*
lrwxrwxrwx 1 root 3 Apr 25 14:59 dosexec -> dos*
- -rwxr-xr-x 1 root 105 Feb 23 20:01 rundos*
lrwxrwxrwx 1 root 3 Apr 25 15:16 xdos -> dos*
- -rwsr-xr-x 1 root 2806 Apr 29 22:21 xtermdos*
Note that 'dos' itself is *not* suid, but that xtermdos is. This permits dos,
xdos, and xtermdos to be run by ordinary users.
4) Finally, in /dev, change the file permissions for both the hard drive and
for the DOS partition itself to allow ordinary users access.
brw-rw-rw- 1 root 3, 0 May 5 1998 hda
brw-rw-rw- 1 root 3, 4 May 5 1998 hda4
Again, this assumes your hard drive is /dev/hda and the DOS partition is at
/dev/hda4. If different change accordingly.
To change the permissions, as root, 'chmod 666 hda hda4'.
- -------------------------------------------------------------------
Step #4 above was the most difficult to figure out. If you do not do this, you
might get the following strange error messages:
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
ERROR: X: Can't open display ":0.0"
I hope this will help some people.
They said, "You have a blue guitar,
You do not play things as they are."
The man replied, "Things as they are
Are changed upon the blue guitar."
---Wallace Stevens
===============================================
+ http://personal.riverusers.com/~thegrendel/ +
===============================================
------------------------------
From: Brad Joyce <[EMAIL PROTECTED]>
Date: Mon, 03 May 1999 18:45:27 +1000
Subject: linux replacing system manager
Hi,
I have a client who has system manager. (A multitasking dos based
operating system that is not y2k compliant) The terminals are a mix of
ethernet and serial connections.
Can anyone help in the design of a linux based system to replace it?
The current system has a dos based database point of sale system that is
resident on the system manager server. It is able to run three copies of
the software on terminals and on the servers own monitor.
The server is a pentium 200 with 32Mb Ram and the terminals are a 386
runing win3.11, a pentium 166 running win95 and a remote connection via
modem. The remote computer is running win 95 on a laptop.
There are 2 printers. one on the pentium server and the other on the
pentium workstation.
The POS dos program is essential.
This is just a preliminary letter to see if anyone can help and at what cost.
Awaiting your promt reply.
Brad Joyce.
------------------------------
From: [EMAIL PROTECTED]
Date: Mon, 19 Apr 99 00:45:01 Pacific Daylight Time
Subject: adv: Important Psychic Message For You...
LIVE PERSONAL PSYCHIC! (as seen on T.V.)
LEARN TODAY WHAT YOUR FUTURE HOLDS FOR
LOVE, MONEY, MARRIAGE, JOB, & HEALTH
ASTROLOGY CLAIRVOYANCY
NUMEROLOGY TAROT
ALL QUESTIONS ANSWERED IMMEDIATELY!
REALIZE YOUR DESTINY! CALL RIGHT NOW!
1-900-226-4140 or 1-800-372-3384 for VISA, MC, & AMEX
(These are not sex lines!)
This message is intended for Psychic Readers, Psychic Users and people who are
involved in the $1 Billion a year Psychic Industry. If this message has reached you in
error, please disregard it and accept our apoligies. To be removed from this list,
please respond with the subject "remove". Thank You.
LIVE PERSONAL PSYCHIC! (as seen on T.V.)
LEARN TODAY WHAT YOUR FUTURE HOLDS FOR
OVE, MONEY, MARRIAGE, JOB, & HEALTH
------------------------------
From: "Mark P. Fishman" <[EMAIL PROTECTED]>
Date: Mon, 3 May 1999 10:09:38 -0400 (EDT)
Subject: ERROR running DR-DOS 7.03
DOSEMU version 0.98.1
- - Created hdimage file with mkfatimage16 -k 10240 -f myimage
- - edited /etc/dosemuconf so $_hdimage="myimage"
- - ran dos -A with DR-DOS 7.03 (current Caldera product)
installation floppy in floppy drive
- - installed DR-DOS 7.03 to drive C: (myimage file)
- - exiting installation exits dosemu (possible problem #1);
screen shows two lines:" ERROR: DISK: null dp " and
" ERROR: Sector not found 1! "
- - ran dos, boots myimage file as C:
- - everything seems to work, but on exiting, the screen shows the
same two error lines.
Note that these error messages also show up if the installation
is aborted instead of completed. They seem to come when booting
DR-DOS from floppy *or* from "hard disk".
The same two errors show up with OpenDOS 7.01 (Caldera's
slightly earlier product). No such errors appear with either IBM
PC-DOS 7.0, or with MS-DOS 6.22/6.20/5.0 (these are the versions
I have to test).
As the errors do not seem to occur with the TinyDOS
hdimage.703.eval file that Caldera has posted for download, I am
puzzled about the differences. The first 128 bytes of the
TinyDOS file look more like the result of mkhdimage than what
comes out of mkfatimage16. There is no documentation for
mkhdimage, though, and I am unable to determine how to use it.
Cheers -- Mark F.
- --
reply to: mfishman at alum dot em eye tee dot ee dee ewe
------------------------------
From: Rodney Fisk <[EMAIL PROTECTED]>
Date: Mon, 03 May 1999 14:30:07 -0500
Subject: Re: linux replacing system manager
Hi Brad,
Caldera's DRDOS may be an expedient.
It overcomes the Y2K thing by lying to programs about the year, after the date
changes to 2000.
That may keep you up and running until you can get Linux online.
Although, I do believe Linux is the way to go, this may give you time to get
there.
Regards,
Rodney Fisk<[EMAIL PROTECTED]>
Brad Joyce wrote:
> Hi,
> I have a client who has system manager. (A multitasking dos based
> operating system that is not y2k compliant) The terminals are a mix of
> ethernet and serial connections.
> Can anyone help in the design of a linux based system to replace it?
>
> The current system has a dos based database point of sale system that is
> resident on the system manager server. It is able to run three copies of
> the software on terminals and on the servers own monitor.
> The server is a pentium 200 with 32Mb Ram and the terminals are a 386
> runing win3.11, a pentium 166 running win95 and a remote connection via
> modem. The remote computer is running win 95 on a laptop.
> There are 2 printers. one on the pentium server and the other on the
> pentium workstation.
>
> The POS dos program is essential.
>
> This is just a preliminary letter to see if anyone can help and at what cost.
>
> Awaiting your promt reply.
>
> Brad Joyce.
------------------------------
From: <[EMAIL PROTECTED]>
Date: Mon, 3 May 1999 16:33:46 -0500 (CDT)
Subject: Spamming Through Mailing List
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to [EMAIL PROTECTED] for more info.
- ---1865350110-1616931063-925767226=:6050
Content-Type: TEXT/PLAIN; charset=US-ASCII
Somebody has been spamming us with false return address about some Psychic
stuff. The message is attached. The message was originated from a Windoze
machine at
ppp-206-191-150-56.emeraldnet.net
If we complain to emeraldnet.net they might be able to do something about
it.
FT
- ---1865350110-1616931063-925767226=:6050
Content-Type: TEXT/PLAIN; charset=US-ASCII; name=emer
Content-Transfer-Encoding: BASE64
Content-ID: <[EMAIL PROTECTED]>
Content-Description:
DQpGcm9tIG93bmVyLWxpbnV4LW1zZG9zLW91dGdvaW5nQHZnZXIucnV0Z2Vy
cy5lZHUgIE1vbiBNYXkgIDMgMTY6MDg6MDcgMTk5OQ0KUmV0dXJuLVBhdGg6
IDxvd25lci1saW51eC1tc2Rvcy1vdXRnb2luZ0B2Z2VyLnJ1dGdlcnMuZWR1
Pg0KUmVjZWl2ZWQ6IGZyb20gbGlzdHNlcnYuZnVuZXQuZmkgKGxpc3RzZXJ2
LmZ1bmV0LmZpIFsxMjguMjE0LjI0OC4yN10pDQoJYnkgbmV3cy5pY25zLmNv
bSAoOC44LjcvOC44LjcpIHdpdGggRVNNVFAgaWQgUUFBMDU5NjANCglmb3Ig
PG1hd2FsaUBuZXdzLmljbnMuY29tPjsgTW9uLCAzIE1heSAxOTk5IDE2OjA4
OjAwIC0wNTAwDQpSZWNlaXZlZDogZnJvbSB2Z2VyLnJ1dGdlcnMuZWR1IChb
MTI4LjYuMTkwLjJdOjU2MzYgIkVITE8gdmdlci5ydXRnZXJzLmVkdSIgaWRl
bnQ6ICJOTy1JREVOVC1TRVJWSUNFWzJdIikgYnkgbGlzdHNlcnYuZnVuZXQu
Zmkgd2l0aCBFU01UUCBpZCA8MTU5MDMtNzE3ND47IFR1ZSwgNCBNYXkgMTk5
OSAwMDowMTozNiArMDMwMA0KUmVjZWl2ZWQ6IGJ5IHZnZXIucnV0Z2Vycy5l
ZHUgdmlhIGxpc3RleHBhbmQgaWQgPDE1NDcwMi0zODU1PjsgTW9uLCAzIE1h
eSAxOTk5IDEzOjE5OjIyIC0wNDAwDQpSZWNlaXZlZDogYnkgdmdlci5ydXRn
ZXJzLmVkdSBpZCA8MTU0NTMwLTM4NTQ+OyBNb24sIDMgTWF5IDE5OTkgMTI6
MzQ6MTkgLTA0MDANClJlY2VpdmVkOiBmcm9tIFsyMDAuMTYuMTk3LjE3N10g
KFsyMDAuMTYuMTk3LjE3N106MjYxNCAiSEVMTyBjbGF2aXMxLmNsYXZpcy5j
b20uYXIiIGlkZW50OiAiTk8tSURFTlQtU0VSVklDRVsyXSIpIGJ5IHZnZXIu
cnV0Z2Vycy5lZHUgd2l0aCBTTVRQIGlkIDwxNTUyNzMtMTQ4MjM+OyBTdW4s
IDIgTWF5IDE5OTkgMTc6NTk6NDEgLTA0MDANClJlY2VpdmVkOiBmcm9tIFsy
MDYuMTkxLjE1MC41Nl0gYnkgY2xhdmlzMS5jbGF2aXMuY29tLmFyDQogIChT
TVRQRDMyLTQuMCkgaWQgQTlGQTE3MTAxNEU7IE1vbiwgMTkgQXByIDE5OTkg
MDQ6NTY6NDIgLTA3MDANCkZyb206IHNpbHZpYV9icm93bkB1c2EubmV0DQpT
dWJqZWN0OiBhZHY6IEltcG9ydGFudCBQc3ljaGljIE1lc3NhZ2UgRm9yIFlv
dS4uLg0KRGF0ZTogCU1vbiwgMTkgQXByIDk5IDAwOjQ1OjAxIFBhY2lmaWMg
RGF5bGlnaHQgVGltZQ0KWC1NYWlsZXI6IE1pY3Jvc29mdCBPdXRsb29rIEV4
cHJlc3MNClgtUHJpb3JpdHk6IDMNClgtTVNNYWlsUHJpb3JpdHk6IE5vcm1h
bA0KSW1wb3J0YW5jZTogTm9ybWFsDQpNZXNzYWdlLUlkOiA8MTk5OTA1MDIy
MTU5NDZaMTU1MjczLTE0ODIzKzg1NTdAdmdlci5ydXRnZXJzLmVkdT4NClRv
OiB1bmxpc3RlZC1yZWNpcGllbnRzOjsgKG5vIFRvLWhlYWRlciBvbiBpbnB1
dCkNClNlbmRlcjogb3duZXItbGludXgtbXNkb3NAdmdlci5ydXRnZXJzLmVk
dQ0KUHJlY2VkZW5jZTogYnVsaw0KWC1Mb29wOiBtYWpvcmRvbW9Admdlci5y
dXRnZXJzLmVkdQ0KWC1PcmNwdDogcmZjODIyO2xpbnV4LW1zZG9zLW91dGdv
aW5nLWRpZw0KU3RhdHVzOiBSTw0KWC1TdGF0dXM6IA0KDQpMSVZFIFBFUlNP
TkFMIFBTWUNISUMhICAgIChhcyBzZWVuIG9uIFQuVi4pDQoNCkxFQVJOIFRP
REFZIFdIQVQgWU9VUiBGVVRVUkUgSE9MRFMgRk9SDQpMT1ZFLCAgTU9ORVks
ICBNQVJSSUFHRSwgIEpPQiwgICYgSEVBTFRIDQoNCkFTVFJPTE9HWSAgICAg
ICAgICBDTEFJUlZPWUFOQ1kNCk5VTUVST0xPR1kgICAgICAgIFRBUk9UDQoN
CkFMTCBRVUVTVElPTlMgQU5TV0VSRUQgSU1NRURJQVRFTFkhDQoNClJFQUxJ
WkUgWU9VUiBERVNUSU5ZISAgICAgIENBTEwgUklHSFQgTk9XIQ0KDQoxLTkw
MC0yMjYtNDE0MCAgb3IgMS04MDAtMzcyLTMzODQgZm9yIFZJU0EsIE1DLCAm
IEFNRVgNCg0KKFRoZXNlIGFyZSBub3Qgc2V4IGxpbmVzISkNCg0KVGhpcyBt
ZXNzYWdlIGlzIGludGVuZGVkIGZvciBQc3ljaGljIFJlYWRlcnMsIFBzeWNo
aWMgVXNlcnMgYW5kIHBlb3BsZSB3aG8gYXJlIGludm9sdmVkIGluIHRoZSAk
MSBCaWxsaW9uIGEgeWVhciBQc3ljaGljIEluZHVzdHJ5LiBJZiB0aGlzIG1l
c3NhZ2UgaGFzIHJlYWNoZWQgeW91IGluIGVycm9yLCBwbGVhc2UgZGlzcmVn
YXJkIGl0IGFuZCBhY2NlcHQgb3VyIGFwb2xpZ2llcy4gVG8gYmUgcmVtb3Zl
ZCBmcm9tIHRoaXMgbGlzdCwgcGxlYXNlIHJlc3BvbmQgd2l0aCB0aGUgc3Vi
amVjdCAicmVtb3ZlIi4gVGhhbmsgWW91Lg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCkxJVkUgUEVSU09OQUwgUFNZQ0hJQyEgICAgKGFzIHNlZW4g
b24gVC5WLikNCg0KDQpMRUFSTiBUT0RBWSBXSEFUIFlPVVIgRlVUVVJFIEhP
TERTIEZPUg0KDQpPVkUsICBNT05FWSwgIE1BUlJJQUdFLCAgSk9CLCAgJiBI
RUFMVEgNCg0KDQoNCg0K
- ---1865350110-1616931063-925767226=:6050--
------------------------------
From: "Michael Kao" <[EMAIL PROTECTED]>
Date: Mon, 03 May 1999 16:11:35 PDT
Subject: DOSEMU kicking out!
Hi,
I downloaded DOSEMU 0.98.6-1 binary for RedHat 5.2. I
installed it without problems. I encounter the following
error message and got kicked out of DOSEMU when I tried
to run an old dos program called "impax.exe". Can you
plese help me.
Running on CPU=486, FPU=1, rdtsc=0
ERROR: general protection at 0xb00bf: 0
ERROR: SIGSEGV, protected insn...exiting!
- -Michael Kao
_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com
------------------------------
From: [EMAIL PROTECTED]
Date: Mon, 3 May 1999 19:05:52 -0400 (EDT)
Subject: Problems with file-sharing permissions (DENY_ANY)
DOSemu developers,
Earlier, I reported that Phar Lap's DOSXNT.EXE won't
work with DOSemu > 0.66.7. The solution is to enable DPMI
in dosemu.conf.
I also wrote a patch to report the century (19h or 20h)
when CMOS byte 50 is read. Some stupid applications report
the year as "0099" without this patch.
With DOSemu 0.98 or 0.99 on a Linux 2.2 kernel, Micro-
soft LINK 5.01.20 cannot write to a file. I tracked down
the following report, which describes the problem better
than I can:
http://www.penguin.cz/~stano/en/dosemu-0.98.4-denyany.html
His patch works for me.
Also, I like how 0.99.11 lets me use a regular UNIX
directory as my C: drive. Quite a useful feature.
These patches may be applied to either 0.98.6 or 0.99.11:
- --- dosemu-0.99.11/src/base/dev/misc/cmos.c Fri Jan 8 20:05:19 1999
+++ dosemu-0.99.11/src/base/dev/misc/cmos.c Thu Apr 29 19:16:34 1999
@@ -60,6 +60,7 @@
case CMOS_DOM: /* day of month */
case CMOS_MONTH:
case CMOS_YEAR:
+ case CMOS_CENTURY:
holder = cmos_date(cmos.address); goto quit;
case CMOS_CHKSUML:
- --- dosemu-0.99.11/src/base/dev/misc/rtc.c Fri Jan 8 20:05:19 1999
+++ dosemu-0.99.11/src/base/dev/misc/rtc.c Thu Apr 29 19:17:18 1999
@@ -76,6 +76,9 @@
else
return BCD(tm->tm_year);
+ case CMOS_CENTURY:
+ return BCD(tm->tm_year/100 + 19);
+
default:
h_printf("CMOS: cmos_time() register 0x%02x defaulted to 0\n", reg);
return 0;
- --- dosemu-0.99.11/src/dosext/mfs/mfs.c Thu Apr 22 16:47:42 1999
+++ dosemu-0.99.11/src/dosext/mfs/mfs.c Thu Apr 29 22:31:15 1999
@@ -3132,7 +3132,7 @@
fl.l_type = ( unix_mode == O_RDONLY ) ? F_RDLCK : F_WRLCK;
break;
case DENY_ANY:
- - fl.l_type = F_RDLCK;
+ fl.l_type = ( unix_mode == O_RDONLY ) ? F_RDLCK : F_WRLCK;
break;
default:
fl.l_type = F_WRLCK;
Dave Coffin 5/3/99
- --
Dave Coffin, BIOS Engineer, Linux & Internet guru
Microid Research / Unicore Software
1538 Turnpike Street, North Andover, MA 01845-6221
E-mail: [EMAIL PROTECTED] Lat: 42 38'32"N
Phone: 978-686-6468x341 Lon: 71 05'00"W
Fax: 978-683-1630 Alt: 57 meters
------------------------------
From: "Alexander G. Carver [Data]" <[EMAIL PROTECTED]>
Date: Tue, 04 May 1999 00:12:29 -0400
Subject: Missing characters and serial port problems
I've been trying to set up dosemu on a clean system so that I can run
the control software for some silicon processing equipment. This
software uses two serial ports and also VGA graphics mode.
I've already configured the serial ports and graphics in the
conf file (com1 is /dev/ttyS0 and com2 is /dev/ttyS1, the
video card is a trident 8900 unit). Here's the problems:
A) None of the numbers are showing up on the screen. I can
see most of the display just fine. But wherever there's supposed
to be a number (i.e. 0-9) nothing shows. The letters show just fine.
B) The software doesn't seem to be accessing the serial ports
properly. I know linux is operating just fine because I've checked
the ports through it. It's just not translating through dosemu.
Any help would be appreciated. I'm trying desparately to get rid
of the base Win95 system on the original controller computer
and put this in its place.
- -Alexander Carver
------------------------------
From: [EMAIL PROTECTED] (David Hodges)
Date: Tue, 4 May 1999 18:57:43 +1200 (NZST)
Subject: Re: DOSEMU kicking out!
> I downloaded DOSEMU 0.98.6-1 binary for RedHat 5.2. I
> installed it without problems. I encounter the following
> error message and got kicked out of DOSEMU when I tried
> to run an old dos program called "impax.exe". Can you
> plese help me.
>
> Running on CPU=486, FPU=1, rdtsc=0
> ERROR: general protection at 0xb00bf: 0
> ERROR: SIGSEGV, protected insn...exiting!
This could be caused by the program attempting to use DPMI
(in which case you need to have a line like
$_dpmi = (4096) # or some other size in kilobytes, depending on how much
# memory the program needs
in your /etc/dosemu.conf file, not $_dpmi = (off).
If you do this (or even if you don't), it is better to run dosemu under
X as an ordinary user, rather than on the console as root.
Alternatively it could be caused by the program attempting to switch
to protected mode via some other means, such as VCPI (see the file
EMUfailure.txt) in which case it will never work under dosemu.
------------------------------
From: "Raimund Sacherer" <[EMAIL PROTECTED]>
Date: Tue, 4 May 1999 09:42:05 +0200
Subject: Using DosEmu on Terminals?!
Hi, i have a Problem.
We are selling Computer Cash Desk now for 10 years. The Cashdesk Software is
a DOS Program. We have now Problems with Windows because it kills the xBase
Databases.
I explain the Cashdesk now how it works on the PC�s
There is a PC for every Cashdesk, mostly 1-3, and one PC for the Office
Work. These Computers are connected over Ethernet via RG58 or
PatchPanel/Hubs. The CashDesk consist of a Computer with a CashBox. The
CashBox is connected over a COMPort to the PC. The work is done over this
CashBox and the normal PC-Keyboard is very rarly used.
Now the Linux Situation how i want it that it works:
I want now create a Server using Linux and DosEmu which is also used as
office working place.
There is the first problem, but i think this don�t belong to you: I need an
AutoLogon.
Connected to this Server are 1,2 or 3 Terminals, i think over a ethernet.
This Terminals should be the Cash Desks.
Now the Problem is: I have to connect the CashBox to the Terminal via COM.
How does DOSEMU like this? If i run DosEmu on this Terminal, is the Comport
of the Terminal used or that from the Server? I have to turn on the
Terminal, then automaticaly the Logon to the Server have to bee made AND the
CashBox Program has to be Started AND after working the connection has to be
closed.
Please I hope you can help me there...
I am using SuSE Linux 6.1 with Kernel 2.2.5, DosEmu 98.? (I believe 6).
Regards
The Ray
Where i work http://www.ultrasonic.at
------------------------------
From: [EMAIL PROTECTED]
Date: Tue, 4 May 1999 20:26:56 +0000
Subject: HELP! for 3com-3C905B-TX network card
I am installing RedHat Linux5.2 and having problem for new
network card of 3Com-3C905B-TX to access HP server on
HP-UX10.20 through NFS.
The objective for RedHat5.2 installation is to acivate PC with
partition created and install and configure with Linux NFS
mounting to HP server for application use.
Some background information:
We have TWO HP servers, (a) one with the HP-UX 10.20 with
RedHat Linux 5.2 and (b) one with the HP-UX 9.07 with
redHat Linux 5.1.
Network cards are (a) 3Com-3C905B-TX (New card), (b)
3Com-3C509B-TX (old card)
CASE #1: Old network card, 3C509B-TX on either Pentium I
or Pentium II able to NFS configuration and mount to HP-UX
9.07 with Linux 5.1 BUT UNABLE WITH HP-UX 10.20 with
Linux 5.2.
No error message, JUST HANG.
CASE #2: New network card, 3C905B-TX on either Pentium I
or II UNABLE to NFS configuration and mount to HP-UX 9.07
or HP-UX 10.20
error message : mount clntudp_create : RPC : mapper failure
- - RPC : Timed out
Anybody welcome suggestion and advise how to resolve it.
Thanks in advance.
Philip
------------------------------
From: [EMAIL PROTECTED]
Date: Tue, 04 May 1999 14:15:39 MET_DST
Subject: Re: Using DosEmu on Terminals?!
> From: "Raimund Sacherer" <[EMAIL PROTECTED]>
> Date: Tue, 4 May 1999 09:42:05 +0200
>I explain the Cashdesk now how it works on the PC�s
>
>There is a PC for every Cashdesk, mostly 1-3, and one PC for the Office
>Work. These Computers are connected over Ethernet via RG58 or
>PatchPanel/Hubs. The CashDesk consist of a Computer with a CashBox. The
>CashBox is connected over a COMPort to the PC. The work is done over this
>CashBox and the normal PC-Keyboard is very rarly used.
But what is kind of communication between these computers?
One of possibilities is Mars on Linux machine to work as
file server, and workstations accessing files from the server
using Novell Netware client (NCP over IPX protocol).
Disadvantages: it is a bit slow for heavy database use,
every machine must be capable to run the CashDesk software.
>Now the Linux Situation how i want it that it works:
>
>I want now create a Server using Linux and DosEmu which is also used as
>office working place.
>There is the first problem, but i think this don�t belong to you: I need an
>AutoLogon.
>Connected to this Server are 1,2 or 3 Terminals, i think over a ethernet.
>This Terminals should be the Cash Desks.
>Now the Problem is: I have to connect the CashBox to the Terminal via COM.
I have similar problem: I have database on central server,
and I want to run programs in DosEmu on the server, for
speed reason (database search over ethernet is too slow).
I plan writing some program to give access to remote COM
port (on the terminal from program on the server).
My idea is to use IPX protocol for communication between
Linux and terminal, on terminal side it needs some TSR to
send data between COM port and the net, on Linux side it
needs a program which allocates pseudo-tty, assigns it as
COM port for DosEmu and starts DosEmu, and later sending
data between pseudo-tty and the net: in DosEmu the pseudo-
- -tty is seen as COM port, and any data written to it gets
to COM port on terminal, any data received by COM port on
the terminal can be read from emulated COM port in DosEmu.
Problems: 1. need some time to write the program;
2. need know IPX address of the terminal (I don't know
how to - seems Linux will not tell it, maybe need identify
it by sending unique data using IPX in one direction and
using TCP/IP in another, e.g. Linux side to terminal "send
me keystrokes abcdef", then terminal does it, then on Linux
they are read from stdin and identified - no, wrong, if
another terminal receives Linux will get unexpected input,
better write controlling tty name to known position on
screen and ask terminals for text from the position - one
should reply with the text just written);
3. need ideas: what command would be useful (com_write,
com_listen, read_screen, what more? file access? maybe it
would be nice to be able to access disks on terminals?).
>How does DOSEMU like this? If i run DosEmu on this Terminal, is the Comport
>of the Terminal used or that from the Server? I have to turn on the
Unfortunately, Linux machine has access to its local ports
only - this is a reason for which I want to write the program.
>Terminal, then automaticaly the Logon to the Server have to bee made AND the
>CashBox Program has to be Started AND after working the connection has to be
>closed.
In principle it is possible, and even not so hard: run telnet
from autoexec.bat on the terminal, and - if really autologon
is needed - put the few keypresses into keyboard buffer (there
are a few programs simulating keypresses in DOS available on
Simtel, try them - all you need is to send login name - but
maybe it is better to allow operators to login themselves?
unless you want to have computers without keyboards...).
Jerzy Tarasiuk
------------------------------
From: [EMAIL PROTECTED]
Date: Tue, 04 May 1999 14:43:34 MET_DST
Subject: Re: COM Ports and Pseudo TTY's
> Date: Tue, 27 Apr 1999 14:23:44 -0700
> From: Matt Clay <[EMAIL PROTECTED]>
>
> Does anyone know how to setup a pseudo tty to look like a COM port and
> modem connection to programs running under DOS Emu?
I remember there is an utility called modemu, which emulates
a modem for DosEmu, using pseudo-tty-s. And it DOES NOT WORK
on my machine - first allocated pty has improper protection!
On ftp://sunsite.unc.edu/pub/Linux/apps/serialcomm/dialout,
it is utility which allows to run modem applications using
Linux connected to Internet - just put target machine name
in place of dialed number and this should work. 26kB source.
Jerzy Tarasiuk
------------------------------
From: Rodney Fisk <[EMAIL PROTECTED]>
Date: Tue, 04 May 1999 13:54:09 -0500
Subject: Re: Printing problems
Hello gang,
If anyone on the list can help here, please feel free.
I'm thinking it doesn't, but does FoxPro possibly require dpmi?
I noticed you don't have any.
This also just occurred to me; have you tried to print with any other programs under
dosemu?
Maybe being imperical about this may just help us stumble into the solution.
If we eliminate all possibilities, no matter how unlikely, then the one which
remains must be it.
So, if perhaps you can't print with some other program under dosemu, then maybe it's
a dosemu problem.
At least if we try we'll know.
I'll try to print tonight myself.
Regards,
Rod Fisk
[EMAIL PROTECTED] wrote:
> Ok, here is a small piece of my current dosemu.conf
> file, I assume these are default values on all the
> machines I have installed dosemu on because I havnt
> changed these ever.
>
> $_xms = (1024)
> $_ems = (1024)
> $_ems_frame = (0xe000)
> $_dpmi = (off)
> $_dosemu = (640)
> $_hardware_ram = ""
>
> So I take it I should change xms and ems, I'm a little rusty with
> dos, and cant remember, if you could help me out....
>
> much appreciative,
> -Josh
>
> Rodney Fisk writes:
>
> > Hi Josh,
> >
> > I'm posting these messages to the list, so if anyone knows more than I do, they
> > can interject.
> > Yes, you do have to specify how much ram dosemu gets.
> > In fact, you must specify dpmi, ems, and lower.
> > The choices are provided for you in dosemu.conf.
> > Simply read the notes surrounding the entries.
> > Hopefully that's your only problem.
> >
> > Run man strace if you'd like to run it, but I suggest some fiddling with
> > dosemu.conf first.
> > I hope this helps.
> >
> > Sincerely,
> > Rod.
> >
> > [EMAIL PROTECTED] wrote:
> >
> > > > Have you tried running strace on dosemu?
> > > I have never run trace...I'm new at dosemu,
> > > is there documentation I can read on doing this?
> > > Do you have to be an engineer to understand the readout :)?
> > >
> > > > Beware that it will more than likely produce 4.231655728 tons of readout to
> > > > have to sift through.
> > > > Use that -o outputfile option, so you can use dosemu unencumbered.
> > >
> > > > Also, how much ram do you have available for dos?
> > > Ram available for dos, how/where is that specified, in the
> > > /etc/dosemu.conf file? I just leave whatever the default is.
> > > The machine has lots of memory, but by what you are asking,
> > > it seems I have to specify what to give dos.
> > >
> > > Thanks for the help,
> > > Josh
> >
------------------------------
From: Rodney Fisk <[EMAIL PROTECTED]>
Date: Tue, 04 May 1999 15:35:35 -0500
Subject: Re: Spamming Through Mailing List
I will dispatch a letter tonight.
[EMAIL PROTECTED] wrote:
> Somebody has been spamming us with false return address about some Psychic
> stuff. The message is attached. The message was originated from a Windoze
> machine at
> ppp-206-191-150-56.emeraldnet.net
>
> If we complain to emeraldnet.net they might be able to do something about
> it.
>
> FT
>
> ------------------------------------------------------------------------
>
> From [EMAIL PROTECTED] Mon May 3 16:08:07 1999
> Return-Path: <[EMAIL PROTECTED]>
> Received: from listserv.funet.fi (listserv.funet.fi [128.214.248.27])
> by news.icns.com (8.8.7/8.8.7) with ESMTP id QAA05960
> for <[EMAIL PROTECTED]>; Mon, 3 May 1999 16:08:00 -0500
> Received: from vger.rutgers.edu ([128.6.190.2]:5636 "EHLO vger.rutgers.edu" ident:
>"NO-IDENT-SERVICE[2]") by listserv.funet.fi with ESMTP id <15903-7174>; Tue, 4 May
>1999 00:01:36 +0300
> Received: by vger.rutgers.edu via listexpand id <154702-3855>; Mon, 3 May 1999
>13:19:22 -0400
> Received: by vger.rutgers.edu id <154530-3854>; Mon, 3 May 1999 12:34:19 -0400
> Received: from [200.16.197.177] ([200.16.197.177]:2614 "HELO clavis1.clavis.com.ar"
>ident: "NO-IDENT-SERVICE[2]") by vger.rutgers.edu with SMTP id <155273-14823>; Sun, 2
>May 1999 17:59:41 -0400
> Received: from [206.191.150.56] by clavis1.clavis.com.ar
> (SMTPD32-4.0) id A9FA171014E; Mon, 19 Apr 1999 04:56:42 -0700
> From: [EMAIL PROTECTED]
> Subject: adv: Important Psychic Message For You...
> Date: Mon, 19 Apr 99 00:45:01 Pacific Daylight Time
> X-Mailer: Microsoft Outlook Express
> X-Priority: 3
> X-MSMailPriority: Normal
> Importance: Normal
> Message-Id: <[EMAIL PROTECTED]>
> To: unlisted-recipients:; (no To-header on input)
> Sender: [EMAIL PROTECTED]
> Precedence: bulk
> X-Loop: [EMAIL PROTECTED]
> X-Orcpt: rfc822;linux-msdos-outgoing-dig
> Status: RO
> X-Status:
>
> LIVE PERSONAL PSYCHIC! (as seen on T.V.)
>
> LEARN TODAY WHAT YOUR FUTURE HOLDS FOR
> LOVE, MONEY, MARRIAGE, JOB, & HEALTH
>
> ASTROLOGY CLAIRVOYANCY
> NUMEROLOGY TAROT
>
> ALL QUESTIONS ANSWERED IMMEDIATELY!
>
> REALIZE YOUR DESTINY! CALL RIGHT NOW!
>
> 1-900-226-4140 or 1-800-372-3384 for VISA, MC, & AMEX
>
> (These are not sex lines!)
>
> This message is intended for Psychic Readers, Psychic Users and people who are
>involved in the $1 Billion a year Psychic Industry. If this message has reached you
>in error, please disregard it and accept our apoligies. To be removed from this list,
>please respond with the subject "remove". Thank You.
>
> LIVE PERSONAL PSYCHIC! (as seen on T.V.)
>
> LEARN TODAY WHAT YOUR FUTURE HOLDS FOR
>
> OVE, MONEY, MARRIAGE, JOB, & HEALTH
------------------------------
From: [EMAIL PROTECTED] (David Hodges)
Date: Wed, 5 May 1999 08:58:32 +1200 (NZST)
Subject: Re: HELP! for 3com-3C905B-TX network card
This is not a very good place to ask this question, if you want
to get a helpful answer. You are more likely to get help if you
post to an appropriate Linux newsgroup - I think there is one
called comp.os.linux.networking, or possibly you could try
comp.os.linux.hardware.
When you post there, you could also mention:
what version(s) of the Linux kernel you are using and what
happens if you try something else like ping, telnet or ftp instead
of NFS.
> I am installing RedHat Linux5.2 and having problem for new
> network card of 3Com-3C905B-TX to access HP server on
> HP-UX10.20 through NFS.
>
> The objective for RedHat5.2 installation is to acivate PC with
> partition created and install and configure with Linux NFS
> mounting to HP server for application use.
>
> Some background information:
>
> We have TWO HP servers, (a) one with the HP-UX 10.20 with
> RedHat Linux 5.2 and (b) one with the HP-UX 9.07 with
> redHat Linux 5.1.
>
> Network cards are (a) 3Com-3C905B-TX (New card), (b)
> 3Com-3C509B-TX (old card)
>
> CASE #1: Old network card, 3C509B-TX on either Pentium I
> or Pentium II able to NFS configuration and mount to HP-UX
> 9.07 with Linux 5.1 BUT UNABLE WITH HP-UX 10.20 with
> Linux 5.2.
>
> No error message, JUST HANG.
>
> CASE #2: New network card, 3C905B-TX on either Pentium I
> or II UNABLE to NFS configuration and mount to HP-UX 9.07
> or HP-UX 10.20
>
> error message : mount clntudp_create : RPC : mapper failure
> - RPC : Timed out
------------------------------
From: "Michael Kao" <[EMAIL PROTECTED]>
Date: Tue, 04 May 1999 18:15:25 PDT
Subject: Re: DOSEMU kicking out!
Hi,
> > I downloaded DOSEMU 0.98.6-1 binary for RedHat 5.2. I
> > installed it without problems. I encounter the following
> > error message and got kicked out of DOSEMU when I tried
> > to run an old dos program called "impax.exe". Can you
> > plese help me.
> >
> > Running on CPU=486, FPU=1, rdtsc=0
> > ERROR: general protection at 0xb00bf: 0
> > ERROR: SIGSEGV, protected insn...exiting!
I just installed MS-DOS 6.22 and the program impax.exe works, but
it is giving me a repeating error message in the background
ERROR: bad dos helper function: AX=0x05d7
ERROR: bad dos helper function: AX=0x05d7
ERROR: bad dos helper function: AX=0x05d7
ERROR: bad dos helper function: AX=0x05d7
The program seems to work, but this error message makes it unreadable
as it overwrites the text prompts and outputs. Any ideas how I may
solve this?
- -Michael Kao
_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com
------------------------------
From: root <[EMAIL PROTECTED]>
Date: Wed, 5 May 1999 11:27:01 +1000
Subject: dosemu
Hello,
I have a problem with a program I need to use,
C:\ezy>ezy
ERROR: cpu exception in dosemu code outside of VM86()!
trapno: 0x0e errorcode: 0x00000006 cr2: 0x3f1ca5cc
eip: 0x401332e0 esp: 0xbffffd28 eflags: 0x00010212
cs: 0x0023 ds: 0x002b es: 0x002b ss: 0x002b
Page fault: write instruction to linear address: 0x3f1ca5cc
CPU was in user mode
Exception was caused by non-available page
#
(it auto quits dosemu back to linux prompt)
Is there any way of getting around this?
I have been trying to get around it for month or more now
Hopeing someone can help!
Regards
Noel
------------------------------
From: Hans Lermen <[EMAIL PROTECTED]>
Date: Wed, 5 May 1999 10:07:12 +0200 (MEST)
Subject: Re: DOSEMU kicking out!
On Tue, 4 May 1999, Michael Kao wrote:
> I just installed MS-DOS 6.22 and the program impax.exe works, but
> it is giving me a repeating error message in the background
>
> ERROR: bad dos helper function: AX=0x05d7
then the application uses INTe6, which is the DOSEMU Helper interupt,
for own purposes.
> The program seems to work, but this error message makes it unreadable
> as it overwrites the text prompts and outputs. Any ideas how I may
> solve this?
$ dos ... 2>/dev/null
Hans
<[EMAIL PROTECTED]>
------------------------------
From: "Michael Kao" <[EMAIL PROTECTED]>
Date: Wed, 05 May 1999 10:29:42 PDT
Subject: Re: DOSEMU kicking out!
Hi,
> > I just installed MS-DOS 6.22 and the program impax.exe works, but
> > it is giving me a repeating error message in the background
> >
> > ERROR: bad dos helper function: AX=0x05d7
>
>then the application uses INTe6, which is the DOSEMU Helper interupt,
>for own purposes.
>
> > The program seems to work, but this error message makes it unreadable
> > as it overwrites the text prompts and outputs. Any ideas how I may
> > solve this?
>
> $ dos ... 2>/dev/null
>
>Hans
><[EMAIL PROTECTED]>
>
>
The error messages went away, but the program now crashes shortly
after I start it. Now even when I start dos with just
$ dos
the program still crashes at the same place! What does
$ dos ... 2>/dev/null
do?
I know the program requires a printer connected in order for
it to work correctly, but I haven't installed a printer
for Linux yet. Can that be the cause of the error?
I need this program, but it doesn't run correctly on my NT
Workstation. It halts on calculations that requires printout
at the same time. I hope this might help you debug the problem.
Thanks.
- -Michael Kao
_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com
------------------------------
From: [EMAIL PROTECTED]
Date: Thu, 6 May 1999 09:48:14 +0200
Subject: screen / lina / 600 bps
Hi,
a DOS textmode program that I wanted to run (for communicating
with a multimeter) tells me 'no suitable screen' and dosemu
ver. 0.98.4 stops with 'ERROR: HLT requested: lina=0x8d!' and
CPU usage of dos goes up to 100%. This happens even if I use
80x25 SVGAText mode.
On a related matter, I have a short BASIC prog that should be
able to comm. with the multimeter at 600 bps but QBASIC hangs
when running it.
Could someone be so kind and give me some hints on
- - possible reasons why this (relatively simple) app barfs?
- - possible workarounds for the screen thing?
- - whether dosemu supports 600 bps ser. comm. and if not,
where to look for this?
TIA, ralf
- --
http://rws.home.pages.de/
Turbocapitalism is anonymous dictatorship by fond managers.
------------------------------
From: Stefan Reuther <[EMAIL PROTECTED]>
Date: Thu, 6 May 1999 11:02:47 +0200 (MET DST)
Subject: Re: DOSEMU kicking out!
Hi,
> > > ERROR: bad dos helper function: AX=0x05d7
[...]
> > $ dos ... 2>/dev/null
> The error messages went away, but the program now crashes shortly
> after I start it. Now even when I start dos with just
>
> $ dos
>
> the program still crashes at the same place! What does
>
> $ dos ... 2>/dev/null
>
> do?
Hide the error messages by redirecting them to /dev/null.
Nothing else.
> I know the program requires a printer connected in order for
> it to work correctly, but I haven't installed a printer
> for Linux yet. Can that be the cause of the error?
Don't know. According to Ralf Brown's Interrupt List,
INT E6h is only used by DOSEMU, the IBM ROM BASIC interpreter
and CP/M-86, the latter two are rather uncommon these days.
Maybe your program requires a crazy driver program?
> I need this program, but it doesn't run correctly on my NT
> Workstation. It halts on calculations that requires printout
> at the same time. I hope this might help you debug the problem.
> Thanks.
If you haven't the driver program under NT, the program will
crash there the same way as it does under DOSEMU. The difference
is that NT doesn't print a message when it receives a bad
INT E6h request.
Stefan
------------------------------
From: "Stan E. Cook" <[EMAIL PROTECTED]>
Date: Thu, 06 May 1999 19:08:09 -0700
Subject: missing files...
Hi;
I am trying to compile dosemu on a Powerbook G3. Kernel is linuxppc
2.2.1. When I run "./default-config" everything looks fine until the
very bottom, when it complains it can't find "as86" or "ld86" I suspect
these files are an assembler and a linker, which run under linux. I
cannot seem to find them. (I will continue to search even after I have
sent this letter.
thank you.
Stan
*********************************************************************
Coming to you via LINUXPPC!
It is enough to know that WinDoze users get exactly what they deserve!
*********************************************************************
------------------------------
From: "Alexander G. Carver [Data]" <[EMAIL PROTECTED]>
Date: Thu, 06 May 1999 23:42:30 -0400
Subject: No serial ports, missing characters in video
I've got two problems:
Problem one: while using a particular piece of control software for some
equipment (written for DOS), I can't see any of the numbers 1 to 9 on the
display. All alpha characters appear and so does the zero, but not 1 to 9.
Slightly bad since this software displays almost all numbers. :)
Problem two: dosemu doesn't see my com ports. I have the conf file set to
use /dev/ttyS0 and /dev/ttyS1 which are my two com ports. I've verified
that linux (debian 2.1) sees them just fine and can communicate with them.
But, within dosemu, they're not available.
I'm using the latest stable release (0.98.6) which seems to have compiled
fine.
TIA for any help/advice.
- -Alexander Carver
------------------------------
From: Hans Lermen <[EMAIL PROTECTED]>
Date: Fri, 7 May 1999 10:16:32 +0200 (MEST)
Subject: Re: missing files...
On Thu, 6 May 1999, Stan E. Cook wrote:
> Hi;
>
> I am trying to compile dosemu on a Powerbook G3. Kernel is linuxppc
^^^
Not sure you will have success with DOSEMU on that machine:-(
Currently it will only run on i386-Linux. Note that the heart of DOSEMU's
kernel needs is vm86(), which is placed in linux/arch/i386/kernel
^^^^^^^^^
> 2.2.1. When I run "./default-config" everything looks fine until the
> very bottom, when it complains it can't find "as86" or "ld86" I suspect
> these files are an assembler and a linker, which run under linux.
Right, you normaly have as86 and ld86 on a i386 Linux box, it else would
complain when compiling the Linux kernel. The package is called 'bin86'
(or similar).
Hans
<[EMAIL PROTECTED]>
------------------------------
From: Ari Moisio <[EMAIL PROTECTED]>
Date: Fri, 7 May 1999 10:58:17 +0300 (EET DST)
Subject: Re: dosnet.o and alternatives
On Wed, 28 Apr 1999, Matt Clay wrote:
> It sounds like you have a problem similar to one I'm working on. I'm
> trying to connect a telnet session to a program running in DOSEmu that
> uses the com port/modem for input/output.
>
> My approach so far (to avoid using null modem cables), is to use pseudo
> tty's. They are devices that come in pairs like "/dev/ptypN" and
> "/dev/ttypN". Where N is a single hex digit. You should be able to run
> agetty on "/dev/ptypN" and tell DosEmu to use "/dev/ttypN" as the com
> port (I havn't actually done it this way myself). Make sure you use a
> psuedo tty that is not already in use (telnet connections use psedo
> tty's).
Thanks for advice.
I tried several configurations with pty's and tty's with no success.
Most promising was to use named pipe and redirect bash stdin and stodu to
to it like
bash <> /dev/testpipe
and configuring this pipe as a serial devide at dosemu.conf. Most os the
stuff went thru but for reason or another not all stdout. All stderr text
were missed.
More strange this worked only with com2:, not com3: for example.
I thingk it would be useful feature to broaden serial device redirection
for example to to test terminal emulator / workstation / network stack
programs usin only single machine. Unfortunately i am not skilled enough
to make these drivers myself:<
- --
Ari Moisio, Niittykatu 7, 41160 Tikkakoski, +358-40-5055239
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
PGP 0x3FAF0F05, fp 8A91 96E2 9864 D04D 575E 3EEE 72E9 DDD2
WWW: http://www.sci.fi/~armoi,http://www.arlainst.fi/~arimo
------------------------------
End of linux-msdos-digest V1 #141
*********************************
To subscribe to linux-msdos-digest, send the command:
