linux-msdos-digest         Friday, April 14 2000       Volume 01 : Number 171

In this issue:

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

From: Logan Mayfield <[EMAIL PROTECTED]>
Date: Wed, 05 Apr 2000 11:22:39 -0500
Subject: Installation Problem

hey,
I'm new to the list/Linux.  I'm trying to get Red Hat Linux 6.2 installed on my
computer.  I have a PII 400MHz pressor, 64 MB RAM, 2 Harddrives.  On one
HArddrive I'm running Windows 98, and I'm trying to get Linux Installed on the
other hardrive.  I downloaded the image file and madea bootable CD.  Whenever it
starts the installation if freezes.  THe screen says it's installing packages,
but nothing is happeneing.  The box that says creating loopback file system is
still there.  I even let it sit for several hours (while i slept) to see if it
was just going really slow.

So, anyone got any suggestions? I really want to get Linux up and running on my
system (I'll be runing a dual boot system, I got too much stuff in Windows to
just abandon it).  Any help would be greatly appriciated.

- -Logan




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

From: Robert Cronk <[EMAIL PROTECTED]>
Date: Wed, 5 Apr 2000 11:03:18 -0600 
Subject: DOSEMU Question

Greetings,

I have been looking for a _very very long time_ for an int33 mouse handler
which provides basic MOUSE.COM functionality that I can embed into a
protected mode graphical program that I'm writing for DOS.  I basically need
to make it so that my users don't have to run MOUSE.COM before running my
application to get mouse support.  I stumbled across your site and found
some mouse.c and mouseint.c files in your archives and I am pretty excited.
I was just wondering if that code can be used by itself or if it must be
compiled with all of the rest of the source code in the archive.  Also, if
it can be used as I have described above, what function(s) would I need to
call at the start of my program to get the equivalent of running MOUSE.COM
before running my application?

Also, If I'm way off track and this will not work at all and I'm in the
wrong place, could you please direct me to what I'm looking for, if you know
of a place that has what I described above?  Thanks in advance!

Robert Cronk

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

From: Bart Oldeman <[EMAIL PROTECTED]>
Date: Wed, 5 Apr 2000 19:15:23 +0100 (BST)
Subject: Re: DOS graphics mode

On Tue, 4 Apr 2000, Tom Serkowski wrote:

> Yup. It's xdos.  I just tried running dos on the console and the app
> does 'nothing' when it starts up - just a blank screen.  Do I need to
> shut down X first?  I just switched to an alternate console with
> C-ALT-F1.
That doesn't matter. The particular type of graphics card you use does
matter.

Did you enable $_console=(1), $_graphics=(1), etc., as described in the
README file?

Bart


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

From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: 05 Apr 2000 14:21:30 -0500
Subject: Re: Clock time in version 1.0.0

"Trachier, Gary M ERDC" <[EMAIL PROTECTED]> writes:

> Hi all,
> 
> I had been running dosemu v0.99.13.1 on a RedHat Linux system.  The hardware
> clock is set to UTC and using timezone set the Linux local time to eastern
> standard time.  Using 'date' would show eastern standard time.  This earlier
> version of dosemu booted up and used the local time to set the DOS clock.
> Yesterday I installed v1.0.0 and it initializes the DOS clock to UTC
> (matching the hardware clock).  Is there way that I can tell dosemu to
> initialize using the Linux local time?  This may seem like a trivial matter,
> but it causes all of the clocks in my dataloggers to be changed thus
> throwing off the date/time stamp on the data.  Thanks for your help.

This problem has been reported several times but it isn't trivial
repeatable. In particular I have never experience this problem.

Is /etc/localtime set the the correct timezone?
Have you been messing with the TZ variable.

Are you running a different version of dos in dosemu?

Is dosemu suid root, and does it have a ports command that
allows it to access the real hardware clock?

If there was a clue perhaps this could get fixed?


Eric

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

From: Cole Petersburg <[EMAIL PROTECTED]>
Date: Wed, 05 Apr 2000 23:03:18 -0500
Subject: Dos Drivers

Can Dos/Win drivers be used in Dosemu? I'm sure if software modem support
worked it would be announced, but will this ever be the case? Does software
modem support rely on Windows as well as Dos? Or maybe this could only work
within Dosemu? Will it someday be possible to run Windows in Dosemu and try
to use software modem drivers?

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

From: "Brian K. White" <[EMAIL PROTECTED]>
Date: Thu, 06 Apr 2000 01:29:05 -0400
Subject: Re: Dos Drivers

Cole Petersburg wrote:
> 
> Can Dos/Win drivers be used in Dosemu? I'm sure if software modem support
> worked it would be announced, but will this ever be the case? Does software
> modem support rely on Windows as well as Dos? Or maybe this could only work
> within Dosemu? Will it someday be possible to run Windows in Dosemu and try
> to use software modem drivers?

I've used dos drivers in dosemu to use a CDROM for which there was no linux
driver.
worked in dosemu without a glitch. This was on dosemu from at least 3 years
ago too.
I just had to know all the ports and irq the drive & driver wanted and I
told dosemu to "passthru" those. no problem, since nothing in linux was ever
touching them, since as I said, there was (and still isn't, and likeley
never will be now) no such thing as a linux driver for it.

I'm speaking of the one weird exception to the phillips CM-205 driver, lmsi
interface, on a PAS-16. it's not the card or the interface that's the
sticking point, it's the drive. *shrug*

- -- 
Brian K. White                   http://www.squonk.net/users/linut
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani

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

From: =?iso-8859-1?q?Etienne=20Lorrain?= <[EMAIL PROTECTED]>
Date: Thu, 6 Apr 2000 16:45:44 +0200 (CEST)
Subject: O.T. Video BIOS

  Hello,

  Just an off topic question - sorry but I do not know
 where to find the right people (it is for a GPL soft);
 and INTER60.zip do not say anything about it.

  Do someone remember if it is possible to display
 char > 127 (accented letters) with video interrupts
 INT10/AH=09h or INT10/AH=0Ah - on a _real_ video BIOS,
 and how to do it? What is the trick ? (if it is a DOS
 trick - I do not even run io.sys so it is not done)
 It do not seems to be a problem of font because 
 INT10/AH=13h do display them - but it also scrolls
 if you write to the bottom right char - and do not
 handle correctly background color in 256 color modes.
 I am just tring to get my soft working even if the
 video board is not VESA compatible, Linux do not need
 VESA...

  Thanks, any pointers are welcome,
  and sorry to be OT.
  Etienne.

Note: DOSEMU is helping me debugging my soft,
 I just would like to see implemented the BIOS
 serial timeout at address 40:7C..7F, and that
 INT10/AX=1130h: GET FONT INFORMATION
 return one font address in es:bp in xdos instead of 0...

___________________________________________________________
Do You Yahoo!?
Achetez, vendez! � votre prix! Sur http://encheres.yahoo.fr

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

From: Bart Oldeman <[EMAIL PROTECTED]>
Date: Thu, 6 Apr 2000 16:07:52 +0100 (GMT)
Subject: Re: O.T. Video BIOS

On Thu, 6 Apr 2000, Etienne Lorrain wrote:

>   Just an off topic question - sorry but I do not know
>  where to find the right people (it is for a GPL soft);
>  and INTER60.zip do not say anything about it.
> 
>   Do someone remember if it is possible to display
>  char > 127 (accented letters) with video interrupts
>  INT10/AH=09h or INT10/AH=0Ah - on a _real_ video BIOS,
>  and how to do it? What is the trick ? (if it is a DOS
>  trick - I do not even run io.sys so it is not done)

This is from Ralph Brown's interrupt list:

INT 1F - SYSTEM DATA - 8x8 GRAPHICS FONT
Desc:   this vector points at 1024 bytes of graphics data, 8 bytes for
each
          character 80h-FFh
Note:   graphics data for characters 00h-7Fh stored at F000h:FA6Eh in 100%
          compatible BIOSes
SeeAlso: INT 10/AX=5000h,INT 43

GRAFTABL is a DOS program which initializes this table (maybe it's not 
necessary for VGA, but it was for CGA, at least). If it (vector
0:7ch) points to a correct table, all the BIOS functions should work
correctly with these. DOSEMU on the console with $_graphics=(1) gives a
real BIOS anyway.

Bart


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

From: "Richard Davis" <[EMAIL PROTECTED]>
Date: Thu, 06 Apr 2000 11:38:58 PDT
Subject: Dos emulator

Any help would be greatly appreciated.  I am trying to use the Dos emulator, 
version .98 included with Red Hat 6.1.  I thought it might have been set to 
a default value that would work for Windows '98, so I tried running it and 
got a "no hdimage.first" error.  So I decided to create my own hdimage.  
Problem is, the mkdexe program doesn't work when I type "mkdexe 
/var/lib/dosemu/myhdimage -o noapp" or when I try to add extra options.  It 
says that no such command is found and later says that the m_tools directory 
is not found.  Is the mkdexe command on Red Hat Linux incomplete?

Also, when I type dos, I get a general protection error @ 0x19df7: 66.  I 
also get an error: SIGESV, protected insn...exiting.  I was wondering if you 
had any idea what was going wrong.

Thanks,

Richard Davis(newbie in need)
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


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

From: Tom Serkowski <[EMAIL PROTECTED]>
Date: Thu, 06 Apr 2000 21:04:42 -0600
Subject: Re: DOS graphics mode

Ahh - thanks, got it working now!  Response seems a bit better than in
windoze.

- -Tom

Bart Oldeman wrote:
> 
> On Tue, 4 Apr 2000, Tom Serkowski wrote:
> 
> > Yup. It's xdos.  I just tried running dos on the console and the app
> > does 'nothing' when it starts up - just a blank screen.  Do I need to
> > shut down X first?  I just switched to an alternate console with
> > C-ALT-F1.
> That doesn't matter. The particular type of graphics card you use does
> matter.
> 
> Did you enable $_console=(1), $_graphics=(1), etc., as described in the
> README file?
> 
> Bart

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

From: =?iso-8859-1?q?Etienne=20Lorrain?= <[EMAIL PROTECTED]>
Date: Fri, 7 Apr 2000 10:36:53 +0200 (CEST)
Subject: Re: O.T. Video BIOS

- --- Bart Oldeman <[EMAIL PROTECTED]> a �crit:
> On Thu, 6 Apr 2000, Etienne Lorrain wrote:
> >   Do someone remember if it is possible to display
> >  char > 127 (accented letters) with video interrupts
> >  INT10/AH=09h or INT10/AH=0Ah - on a _real_ video BIOS,
> >  and how to do it? What is the trick ? (if it is a DOS
> >  trick - I do not even run io.sys so it is not done)
> 
> INT 1F - SYSTEM DATA - 8x8 GRAPHICS FONT
> Desc:   this vector points at 1024 bytes of graphics data, 8 bytes for
> each
>           character 80h-FFh
> Note:   graphics data for characters 00h-7Fh stored at F000h:FA6Eh in 100%
>           compatible BIOSes
> SeeAlso: INT 10/AX=5000h,INT 43

  I have already tried that, and few others INT10 AH=0x11, and re-check
 yesterday: same problem, all chars over 128 are printed like "space",
 as if they were disabled in software - I do not have any garbage on
 the screen, just blanks, whatever I put in interrupt 0x1F. It is the
 same with or without DOSEMU ($_graphics=(1)), and the same for
 modes with an 8x8 font (0x13) or 8x14 (0x11) or 8x16 font, in text
 or graphic. If I alternate calls to INT10/AH=13h and INT10/AH=11h,
 I get the accented letters with the former and space with the latter.

> GRAFTABL is a DOS program which initializes this table (maybe it's not 
> necessary for VGA, but it was for CGA, at least). If it (vector
> 0:7ch) points to a correct table, all the BIOS functions should work
> correctly with these. DOSEMU on the console with $_graphics=(1) gives a
> real BIOS anyway.

  Maybe my solution is in GRAFTABL - boring it is not GPL!

  Thanks,
  Etienne.

___________________________________________________________
Do You Yahoo!?
Achetez, vendez! � votre prix! Sur http://encheres.yahoo.fr

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

From: "Dmitri B.Gofmekler" <[EMAIL PROTECTED]>
Date: Sat, 08 Apr 2000 05:49:11 +0300
Subject: HEEELP: Printing.

        Hi All!

Need to print from dosemu.

The problem is that I've setup a dosemu and spent a 3 nights for getting it 
works without any reslult.

I have a x86 machine with Mandrake 7.0 (tried also RH 5.1, 6.1, SuSE 6.1 & 
Slackware), dosemu 98 (also tried 99.13). + freedos.

Tried to use "print" command: almost does not works: sometimes start to 
print a spooled job after a "touching" a floppy drive!?!?!

Coping autoexec.bat to lpt1 (lpt0, prn, lp2) caused a dosemu's crash.

dosemu.conf:

1 variant:
$_printer = "lp"
$_printer_timeout = "20" # Tried also 0, 1, 5, 10, ...
$_ports = ""
(Linux lp queue configued and works under linux well)

2 variant:
$_printer = "lp"
$_printer_timeout = "20" # Tried also 0, 1, 5, 10, ...
$_ports = " 0x378 "
(Linux lp queue configued and works under linux well)

3 variant:
#$_printer = "lp"
#$_printer_timeout = "20" # Tried also 0, 1, 5, 10, ...
$_ports = " 0x378 "
(Linux lp queue deleted)

4 variant:
#$_printer = "lp"
#$_printer_timeout = "20" # Tried also 0, 1, 5, 10, ...
$_ports = " 0x378 "
(Linux lp queue configued and works under linux well)

and also many other variants....

I think that I'm getting crazy very soon...

IF SOMEBODY CAN HELP ME WITH IT - PLEASE, PLEASE, PLEASE.

Advices about replacing an user is not funny any more, because I monday 
morning I can loose a job...

PS. After subscribing to this list I did not received neither welcome 
message nor authorization request, so please include [EMAIL PROTECTED] in CC: 
field.


Many, many, many thanks in advance,
- ----
Dmitri B. Gofmekler <[EMAIL PROTECTED]>, ICQ: 8168758
- ----
"http://www.sill.ee/~gosha/gosha.asc" - for PGP Encrypted messages.
=====================================
Phone: (+372) 6 563981
Fax: (+372) 6 563000
A-Arvid Computers Ltd. < http://www.arvid.ee >


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

From: Bart Oldeman <[EMAIL PROTECTED]>
Date: Sat, 8 Apr 2000 15:21:05 +0100 (BST)
Subject: Re: HEEELP: Printing.

On Sat, 8 Apr 2000, Dmitri B.Gofmekler wrote:

> Need to print from dosemu.
> 
> Coping autoexec.bat to lpt1 (lpt0, prn, lp2) caused a dosemu's crash.

I saw the same with the default hdimage.first with Freedos. However, with
dr-dos it works fine.

Use this

> 1 variant:
> $_printer = "lp"
> $_printer_timeout = "20" # Tried also 0, 1, 5, 10, ...
> $_ports = ""
> (Linux lp queue configued and works under linux well)

and download dr-dos from ftp.lineo.com/pub/drdos. A mirror is at
ftp.mirror.ac.uk/sites/ftp.calderathin.com.

The license seems to be: only free for either non-commercial or 90 day
evaluation use, but this gets you out of trouble for the time being.

Bart



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

From: Tony Cappellini <[EMAIL PROTECTED]>
Date: Sat, 08 Apr 2000 10:13:12 -0700
Subject: DOSEMU old page docs

Hello

Where are the documentation files for DOSEMU on the old page ?
The links display nothing.

thanks

Tony


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

From: Alistair MacDonald <[EMAIL PROTECTED]>
Date: Sat, 8 Apr 2000 18:41:42 +0100 (BST)
Subject: Re: DOSEMU old page docs

On Sat, 8 Apr 2000, Tony Cappellini wrote:

> Where are the documentation files for DOSEMU on the old page ?
> The links display nothing.

Because that is the old page -- it was kept around simply because there
were some links on there which had not been transferred to the new pages.
The Documentation has been so the links have never been fixed.

Alistair


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

From: Paolo Carballo <[EMAIL PROTECTED]>
Date: Sun, 09 Apr 2000 11:32:08 +0800
Subject: Re: Dos emulator

At 11:38 AM 04/06/2000 PDT, Richard Davis wrote:
>
>Any help would be greatly appreciated.  I am trying to use the Dos emulator, 
>version .98 included with Red Hat 6.1.  
Is it really .98? Though I haven't used Red Hat for quite some time, 
I checked the rpms on my 6.1 cd and got the ff:
dosemu-freedos-0.99.13-1.i386.rpm
dosemu-0.99.13-1.i386.rpm
and 
mtools-3.9.1-5.i386.rpm

>I thought it might have been set to 
>a default value that would work for Windows '98, so I tried running it and 
>got a "no hdimage.first" error.
You could have tried to insert a windows'98 bootable floppy in A: or B:
and then typed `dos -A` or `dos -B` as the case may be.
At least, your next boot would have been a pleasant surprise.

>  So I decided to create my own hdimage.  
If your plan was to make dosemu run with Win98, you follow a different track.
1. First make sure your dos partition is visible. Probably mounting it under
/mnt/dos_hda1 if RH6.1 didn't do so already.
2. Create a directory such as "bootdir" under /var/lib/dosemu/
3. Copy msdos.sys, config.sys and autoexec.bat from your dos parttion's
rootdir
to /var/lib/dosemu/bootdir
 3.a. Edit config.sys and place a semicolon (;) before any occurrences of
 himem.sys, emm386.exe (linux will provide XMS & EMS) and any scsi or ide 
 device drivers.
 3.b Edit autoexec.bat and place a double colon (::) before any occurrences
 of mscdex.exe, and any other device drivers and tsr's.
 4. Create softlinks in /var/lib/dosemu/bootdir to io.sys, command.com and
any 
 other directories you want to access from your dos partition.
 x. Add bootdir to the following /etc/dosemu.conf line:
 $_hdimage = "bootdir hdimage.first" # list of hdimages under /var/lib/dosemu
 5. Finally, type `dos`, (I prefer 'dos -cVk').
 6. If it works, start to add your specific tsr's one by one.

>Problem is, the mkdexe program doesn't work when I type "mkdexe 
>/var/lib/dosemu/myhdimage -o noapp" or when I try to add extra options.  It 
>says that no such command is found and later says that the m_tools directory 
>is not found.  Is the mkdexe command on Red Hat Linux incomplete?
Red Hat 6.1, like Mandrake has everything except the proverbial kitchen sink.
You probably didn't choose to install it. 

>Also, when I type dos, I get a general protection error @ 0x19df7: 66.  I 
>also get an error: SIGESV, protected insn...exiting.  I was wondering if you 
>had any idea what was going wrong.
Hmmm, to the list! To the list my comrades! There we shall meet our destiny!
:)

>
>Thanks,
>
>Richard Davis(newbie in need)


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
= Juan Paolo L. Carballo
= PGP 2.6.3ia RSA KeyID: 63F4DC4D
= PGP 5.5.3i DSS KeyID: 00914A9F
= The importance of information is directly 
=  proportional to its improbability.
= Fundamental Theorem of Information Theory
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


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

From: Paolo Carballo <[EMAIL PROTECTED]>
Date: Sun, 09 Apr 2000 14:19:06 +0800
Subject: dosemu-1.0.0-3mdk.i586.rpm rocks!

Greetings to the dosemu team!
Yesterday, I downloaded and installed the new version 1.0.0-3 from
mandrakesoft.
It's the same as ever, still rocks!
Since v.0.98, the first version I tried, I've been able to compile and run
a program I made to communicate with a pre-paid card device using a
proprietary synchronous serial communications protocol thru COM1 or COM2.
There is no degradation even though I'm running it under Mandrake 6.1 on a
32 Meg Pentium 60.
With Turbo C available for free from Inprise and DRDOS still being
supported by Caldera, there's not much one can't compile and/or run that
was once compiled/run on M$-DOS, which is already extinct as far as M$ is
concerned. The only other way to get MS-DOS is to buy Winblows, which
crawls on a Pentium-60. Wine does just fine under the same cicumstances.
My favorite 3D game is still a DOS app called LHX: Attack Chopper circa
1990 by Brent Iverson and Electronic Arts, which doesn't complain a bit
under dosemu. It and other apps I still have on floppies live on, oblivious
to the fact that the OS they used to run on is emulating their access to
the hardware.
This is truly a great piece of work. There's still hope for the two decades
worth of applications written for DOS on the Simtel network.
Keep up the good work and more power!

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
= Juan Paolo L. Carballo
= PGP 2.6.3ia RSA KeyID: 63F4DC4D
= PGP 5.5.3i DSS KeyID: 00914A9F
= The importance of information is directly 
=  proportional to its improbability.
= Fundamental Theorem of Information Theory
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


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

From: Paolo Carballo <[EMAIL PROTECTED]>
Date: Sun, 09 Apr 2000 13:09:20 +0800
Subject: Re: DOSEMU old page docs

Ummm, may I know where the new pages are?
Links please. I'm not sure if the current pages I'm 
accessing are the new one's or not.
Is it still www.dosemu.org?

At 06:41 PM 04/08/2000 +0100, you wrote:
>On Sat, 8 Apr 2000, Tony Cappellini wrote:
>
>> Where are the documentation files for DOSEMU on the old page ?
>> The links display nothing.
>
>Because that is the old page -- it was kept around simply because there
>were some links on there which had not been transferred to the new pages.
>The Documentation has been so the links have never been fixed.
>
>Alistair



=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
= Juan Paolo L. Carballo
= PGP 2.6.3ia RSA KeyID: 63F4DC4D
= PGP 5.5.3i DSS KeyID: 00914A9F
= The importance of information is directly 
=  proportional to its improbability.
= Fundamental Theorem of Information Theory
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


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

From: Paolo Carballo <[EMAIL PROTECTED]>
Date: Sun, 09 Apr 2000 13:06:31 +0800
Subject: Re: HEEELP: Printing.

At 05:49 AM 04/08/2000 +0300, you wrote:
>       Hi All!
>
>Need to print from dosemu.
>
>The problem is that I've setup a dosemu and spent a 3 nights for getting it 
>works without any reslult.
>Coping autoexec.bat to lpt1 (lpt0, prn, lp2) caused a dosemu's crash.
{snip}{snip}
>I think that I'm getting crazy very soon...
>
>IF SOMEBODY CAN HELP ME WITH IT - PLEASE, PLEASE, PLEASE.
>
I think this has something to do with freedos' inability to
redirect input/output. According to the documentation, 
one cannot boot dosemu with freedos installed on the 
hard drive because of the same reason.
Try using these DOS clones:
ROM-DOS www.datalight.com
- - Note: Very small implementation of an MS-DOS 6.22 environment,
        but has support for Long File Names!
DR-DOS http://www.calderathin.com/products/drdos/resources.html
- - Note: Mr. Bart Oldeman <[EMAIL PROTECTED]>, has links 
        to it in his mail to you.

>Advices about replacing an user is not funny any more, because I monday 
>morning I can loose a job...
>
>PS. After subscribing to this list I did not received neither welcome 
>message nor authorization request, so please include [EMAIL PROTECTED] in CC: 
>field.
Try resending your application to the list.

To: [EMAIL PROTECTED]

with the following in the body, (not the subject line!), 
of your message:

subscribe linux-msdos

You should receive something like this:
- --

Welcome to the linux-msdos mailing list!

Please save this message for future reference.  Thank you.

If you ever want to remove yourself from this mailing list,
you can send mail to <[EMAIL PROTECTED]> with the following
command in the body of your email message:


{snip}{snip}

>Many, many, many thanks in advance,
>----
>Dmitri B. Gofmekler <[EMAIL PROTECTED]>, ICQ: 8168758
>----
>"http://www.sill.ee/~gosha/gosha.asc" - for PGP Encrypted messages.
>=====================================
>Phone: (+372) 6 563981
>Fax: (+372) 6 563000
>A-Arvid Computers Ltd. < http://www.arvid.ee >




=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
= Juan Paolo L. Carballo
= PGP 2.6.3ia RSA KeyID: 63F4DC4D
= PGP 5.5.3i DSS KeyID: 00914A9F
= The importance of information is directly 
=  proportional to its improbability.
= Fundamental Theorem of Information Theory
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


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

From: Alistair MacDonald <[EMAIL PROTECTED]>
Date: Sun, 9 Apr 2000 23:47:05 +0100 (BST)
Subject: Re: DOSEMU old page docs

On Sun, 9 Apr 2000, Paolo Carballo wrote:

> Ummm, may I know where the new pages are?
[...]
> Is it still www.dosemu.org?

Yes - the old page in question is a link from the homepage.

> At 06:41 PM 04/08/2000 +0100, you wrote:
> >On Sat, 8 Apr 2000, Tony Cappellini wrote:
> >
> >> Where are the documentation files for DOSEMU on the old page ?
> >> The links display nothing.
> >
> >Because that is the old page -- it was kept around simply because there
> >were some links on there which had not been transferred to the new pages.
> >The Documentation has been so the links have never been fixed.


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

From: =?iso-8859-1?q?Etienne=20Lorrain?= <[EMAIL PROTECTED]>
Date: Mon, 10 Apr 2000 11:33:24 +0200 (CEST)
Subject: Re: O.T. Video BIOS

  Hello,

  I just have to correct myself, my problem with
 printing chars > 128 was absolutely not related
 to fonts - I had a "mov sign extended" instead of
 a "mov zero extended", or more precisely a line like:
 asm ("int $0x10" : : "a" (0x0900 | thechar));
 when "thechar" is a signed char, it is promoted to
 an int before the OR and everything happenning after
 is my fault.

  Thanks for pointing me that the BIOS was working,
 and sorry for the last message.

  Etienne.

P.S.:
 Just a little on-topic thing: to detect the number of
 hard drives on a PC, I am using the BIOS data
 at 0x0040:0x0075

MEM 0040h:0075h - FIXED DISK - NUMBER OF FIXED DISK DRIVES
Size:   BYTE
SeeAlso: MEM 0040h:0076h"FIXED DISK",MEM 0040h:0077h"FIXED DISK"

  Because:
INT 13 - DISK - GET DISK TYPE (XT 1/10/86 or later,XT286,AT,PS)
BUGS:   several different Compaq BIOSes incorrectly report high-numbered
  drives (such as 90h, B0h, D0h, and F0h) as present, giving them the
  same geometry as drive 80h; as a workaround, scan through disk
  numbers, stopping as soon as the number of valid drives encountered
  equals the value in 0040h:0075h

  It would be nice to have this value filled in for DOSEMU - just
 to remove warnings to stderr when running DOSEMU, because I have
 then to ask for "get disk type" on maybe abscent drives, to see
 if someone is there.
INT 13 - DISK - GET DRIVE PARAMETERS (PC,XT286,CONV,PS,ESDI,SCSI)
 returns "DL = number of drives" but this seems to be not
 reliable.

___________________________________________________________
Do You Yahoo!?
Achetez, vendez! � votre prix! Sur http://encheres.yahoo.fr

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

From: Damian Walker <[EMAIL PROTECTED]>
Date: Mon, 10 Apr 2000 18:13:20 +0100
Subject: VGA in X11

Hello there,

I'm trying to get a graphical display with Dosemu under X11, specifically
so that I can run the emulator for the Psion Series 3a handheld, which needs
plain VGA.  I need to use the X version since I have a fixed frequency monitor,
and the only res I can use with it at the moment is 1280x1024.

Without graphics, xdos runs without a problem.  This is version 0.98 I have
here, as distributed with Slackware 3.6.  When I try the VGAON utility (just
as a test) I get the following output in the console window:

        ERROR: CAN'T DO VIDEO INIT, BIOS NOT MAPPED!

According to my understanding of the config file, the BIOS *is* mapped (we are
talking about the video BIOS here, I assume).  The relevant bits are:

        $_graphics = (on)
        $_videoportaccess = (on)
        $_vbios_seg = (0xc000)
        $_vbios_size = (0x10000)
        $_vmemsize = (1024)
        $_chipset = "cirrus"

Could the above error mean that the BIOS is mapped to the *wrong* address, 
rather than not being mapped at all as it implies?

Any help would be appreciated.
- -- 
Damian Walker
Accrington, UK


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

From: Bart Oldeman <[EMAIL PROTECTED]>
Date: Mon, 10 Apr 2000 19:42:47 +0100 (BST)
Subject: Re: VGA in X11

On Mon, 10 Apr 2000, Damian Walker wrote:

> Without graphics, xdos runs without a problem.  This is version 0.98 I have
> here, as distributed with Slackware 3.6.  When I try the VGAON utility (just
> as a test) I get the following output in the console window:
> 
>       ERROR: CAN'T DO VIDEO INIT, BIOS NOT MAPPED!
> 
> According to my understanding of the config file, the BIOS *is* mapped (we are
> talking about the video BIOS here, I assume).  The relevant bits are:
> 
>       $_graphics = (on)
>       $_videoportaccess = (on)
>       $_vbios_seg = (0xc000)
>       $_vbios_size = (0x10000)
>       $_vmemsize = (1024)
>       $_chipset = "cirrus"
> 
> Could the above error mean that the BIOS is mapped to the *wrong* address, 
> rather than not being mapped at all as it implies?

You are confused between console graphics and X-graphics. The above
settings and vgaon/vgaoff all apply to console graphics. For X you don't
need vgaon. Note that a program that uses a standard vga 16 colour mode
most likely does not work in X. The 2, 4 and 256 colour modes most
likely do work.

Bart


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

From: Andrzej Pruski <[EMAIL PROTECTED]>
Date: Tue, 11 Apr 2000 01:30:23 +0200
Subject: Dosnet patch for kernel 2.3.99

Is somethere available such a patch?

apro


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

From: Hans Lermen <[EMAIL PROTECTED]>
Date: Tue, 11 Apr 2000 02:00:42 +0200 (MEST)
Subject: Re: Dosnet patch for kernel 2.3.99

On Tue, 11 Apr 2000, Andrzej Pruski wrote:

> Is somethere available such a patch?
> 

Not one I know of.

Hans
<[EMAIL PROTECTED]>


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

From: "Darren Mark" <[EMAIL PROTECTED]>
Date: Tue, 11 Apr 2000 18:04:59 -0600
Subject: From : Darren Mark

This is a multi-part message in MIME format.

- ------=_NextPart_000_0006_01BFA3E0.7371C1A0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I am not able to not able to
- --------------------------------------------------------------
Brain Bridge Advtg. & Mktg. Pvt. Ltd.
119, Swami Vivekanad Marg
Allahabad 211 003
Tel.:(0532) 402157,402150, 405098
Fax :(0532) 402157, 606831

- ------=_NextPart_000_0006_01BFA3E0.7371C1A0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I am not able to not able =
to</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>--------------------------------------------------------------<B=
R>Brain=20
Bridge Advtg. &amp; Mktg. Pvt. Ltd.<BR>119, Swami Vivekanad =
Marg<BR>Allahabad=20
211 003<BR>Tel.:(0532) 402157,402150, 405098<BR>Fax :(0532) 402157,=20
606831</FONT></DIV></BODY></HTML>

- ------=_NextPart_000_0006_01BFA3E0.7371C1A0--


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

From: medcure <[EMAIL PROTECTED]>
Date: Tue, 11 Apr 2000 10:57:39 -0400
Subject: hardware

To: Dos Emu
From: John Plunkett

Do you know of a hardware vendor that actively supports DOSEMU?

Thanks,



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

From: Paolo Carballo <[EMAIL PROTECTED]>
Date: Wed, 12 Apr 2000 08:29:19 +0800
Subject: Re: hardware

If you mean PC hardware, Sorry, none that I know of.
Or do you mean embedded systems?
Of course DOSEMU is too large for embedded systems.

At 10:57 AM 04/11/2000 -0400, you wrote:
>To: Dos Emu
>From: John Plunkett
>
>Do you know of a hardware vendor that actively supports DOSEMU?
>
>Thanks,
>


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
= Juan Paolo L. Carballo
= PGP 2.6.3ia RSA KeyID: 63F4DC4D
= PGP 5.5.3i DSS KeyID: 00914A9F
= The importance of information is directly 
=  proportional to its improbability.
= Fundamental Theorem of Information Theory
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


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

From: Stephen Moore <[EMAIL PROTECTED]>
Date: Wed, 12 Apr 2000 12:20:13 +1000
Subject: Graphics Mode

I can run a dos program when I set
$_console = (1)         # use 'console' video
$_graphics = (1)        # use the cards BIOS to set graphics

and run the program in console mode

However I was hoping to run the program in X with xdos. When I run it in
xdos mode I get

[EVALUATION DR DOS 7.03] C:\FLUFF>fluff6

Illegal function call in module VXLOGO   at address 0D58:009D

Hit any key to return to system

All the program does is flash up a banner screen then goes to a dos
application (which I am sure would run in xdos)


Am I out of luck?


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

From: "Ciro A. Toscano" <[EMAIL PROTECTED]>
Date: Wed, 12 Apr 2000 00:41:04 -0300
Subject: Error f0b8 redirecting drive C: to LINUX\FS\

command:     lredir d: linux\fs\
return:        Error f0b8 redirecting drive D: to LINUX\FS\

command:    lredir d: linux\fs\root
return:        Error f0bc redirecting drive D: to LINUX\FS\

:^( help


dosemu 0.99
freedos
kernel 2.2.x


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

From: Justin Zygmont <[EMAIL PROTECTED]>
Date: Tue, 11 Apr 2000 13:57:51 -0400 (EDT)
Subject: Re: hardware

It would be neat if someone made a hardware accelerator card with Dosemu
built on eh?  sort of like the Sun SelectPC (I think that's what it's
called).

On Wed, 12 Apr 2000, Paolo Carballo wrote:

> If you mean PC hardware, Sorry, none that I know of.
> Or do you mean embedded systems?
> Of course DOSEMU is too large for embedded systems.
> 
> At 10:57 AM 04/11/2000 -0400, you wrote:
> >To: Dos Emu
> >From: John Plunkett
> >
> >Do you know of a hardware vendor that actively supports DOSEMU?
> >
> >Thanks,
> >
> 
> 
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> = Juan Paolo L. Carballo
> = PGP 2.6.3ia RSA KeyID: 63F4DC4D
> = PGP 5.5.3i DSS KeyID: 00914A9F
> = The importance of information is directly 
> =  proportional to its improbability.
> = Fundamental Theorem of Information Theory
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> 
> 


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

From: Oscar Alonso <[EMAIL PROTECTED]>
Date: Wed, 12 Apr 2000 14:51:14 +0200
Subject: Problem with characters > 127

Hi:

In DOSEMU I'm trying to type on the console characters > 127 but
DOSEMU does nothing.  However, those characters are correctly printed
in screen when generated by the application instead the keyboard.
What's the matter?
Another problem is that configuring $_layout in dosemu.conf does nothing.  :-(
Any help will be very appreciated.

- -- 
Greetings,
�scar Alonso
[EMAIL PROTECTED]



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

From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: 12 Apr 2000 10:39:31 -0500
Subject: Re: Error f0b8 redirecting drive C: to LINUX\FS\

"Ciro A. Toscano" <[EMAIL PROTECTED]> writes:

> command:     lredir d: linux\fs\
> return:        Error f0b8 redirecting drive D: to LINUX\FS\
> 
> command:    lredir d: linux\fs\root
> return:        Error f0bc redirecting drive D: to LINUX\FS\
> 
> :^( help
> 
> 
> dosemu 0.99
> freedos
> kernel 2.2.x

Get the latest freedos ker2019 and this should work.
Of course you mignt want to get dosemu-1.0.0 as well...

Eric


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

From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: 12 Apr 2000 10:44:47 -0500
Subject: Re: Problem with characters > 127

Oscar Alonso <[EMAIL PROTECTED]> writes:

> Hi:
> 
> In DOSEMU I'm trying to type on the console characters > 127 but
> DOSEMU does nothing.  However, those characters are correctly printed
> in screen when generated by the application instead the keyboard.
> What's the matter?
> Another problem is that configuring $_layout in dosemu.conf does nothing.  :-(
> Any help will be very appreciated.

An updated patchset of my ongoing work rewriting the keyboard code
& various other internationalization type tweaks,  is now avaiable at:
http://www.dosemu.org/~eric/
http://www.users.uswet.net/~ebiederman/files/
as:
dosemu-1.0.0.eb1.20.patchset.tar.gz

At last test yes.  This did properly handle umlauts and other
accented characters via telnet.

And of course $_layout is recognized but for telnet it only affects
the scancodes generated not how the input is interpreted.

Eric

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

From: Bart Oldeman <[EMAIL PROTECTED]>
Date: Wed, 12 Apr 2000 18:02:41 +0100 (BST)
Subject: Re: Error f0b8 redirecting drive C: to LINUX\FS\

On 12 Apr 2000, Eric W. Biederman wrote:

> > command:     lredir d: linux\fs\
> > return:        Error f0b8 redirecting drive D: to LINUX\FS\
> > 
> > command:    lredir d: linux\fs\root
> > return:        Error f0bc redirecting drive D: to LINUX\FS\

> Get the latest freedos ker2019 and this should work.
> Of course you mignt want to get dosemu-1.0.0 as well...

Finally! After all these years it's getting useful under 
dosemu. Congratulations to you and the freedos team for getting this
done. Now if they would fix the 512mb harddisk bug it could be useful for
the occasional real dos session as well: I wasn't really sure if they
meant 512mb partition or hard disk, tried it on a 128 mb partition on my
6.4 GB hard disk, and it trashed some of my data, so I quickly got away
with it. Under dosemu, at least you can try it in a more isolated,
protected environment (part is read-only for instance) so at least I can
take the risk ;-).

Bart  


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

From: Jay Rogers <[EMAIL PROTECTED]>
Date: Wed, 12 Apr 2000 22:24:13 -0400
Subject: All /usr/local install?

How do I install dosemu (including default /etc config files)
entirely in /usr/local?

www.dosemu.org lists the latest stable release as 0.98.8.  Is
this correct?  If not, what's the latest stable release?

- --
Jay Rogers
[EMAIL PROTECTED]

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

From: Justin Zygmont <[EMAIL PROTECTED]>
Date: Wed, 12 Apr 2000 04:14:51 -0400 (EDT)
Subject: Re: All /usr/local install?

I don't think you can really do that...maybe i'm wrong though.  version
1.0 came out a little while back.

On Wed, 12 Apr 2000, Jay Rogers wrote:

> How do I install dosemu (including default /etc config files)
> entirely in /usr/local?
> 
> www.dosemu.org lists the latest stable release as 0.98.8.  Is
> this correct?  If not, what's the latest stable release?
> 
> --
> Jay Rogers
> [EMAIL PROTECTED]
> 


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

From: root <[EMAIL PROTECTED]>
Date: Thu, 13 Apr 2000 15:44:05 +0300
Subject: I want to run dosemu over a serial line (dial-up)

I want to do the thing in the subject but i cannot... i've searched in
all docs that comes with dosemu,
and looking through dosemu-HOWTO i was about tou scream  "EVRIKA" but
i've discovered
that there is no answer to the question:)
Please if there is anyone who can help me....
thanx, alex

                       This is caused by your VGA BIOS. I have found
that by enabling the IO port trace and seeing where it was clobbered.

                       Disable the "allowvideoportaccess on" line in
config and it will work fine. When you then have problems with the
video, try to enable more selective ranges of IO
                       addresses (e.g., 40-43).

                       4.6 How do I use dosemu over the serial ports?

                       4.7 How can I switch between dosemu and a shell
over the serial line?

                       John Taylor ([EMAIL PROTECTED]) reported
(94/5/25) that

                       I am running Linux 1.1.13 and want to point out a
great feature that should be protected and not taken out (IMHO). With
the 52 version, I can run the program,
                       "screen." From screen, i can invoke dos -D-a.
What is really great (IMHO) is the screen commands (the CTRL-A cmds)
still work. This means I can do a CTRL-A
                       C and add another unix shell, and switch between
the two (DOS / UNIX). This allows me to use dosemu over the serial line
really well, because switching is made
                       easy.

                       4.8 How can I get the parallel ports to work?

                       The dosemu.conf has lines at the end to redirect
printers to either lpr or a file. If you want direct access to the bare
metal, comment out these emulation lines, and add
                       the line

                              $_ports { device /dev/lp0 fast range 0x3bc
0x3bf } # lpt0

                       for the "monitor card" printer port (corresponds
to /dev/lp0), or


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

From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: 13 Apr 2000 10:05:08 -0500
Subject: Re: I want to run dosemu over a serial line (dial-up)

root <[EMAIL PROTECTED]> writes:

> I want to do the thing in the subject but i cannot... i've searched in
> all docs that comes with dosemu,
> and looking through dosemu-HOWTO i was about tou scream  "EVRIKA" but
> i've discovered
> that there is no answer to the question:)
> Please if there is anyone who can help me....

Just put a standard login prompt for the serial line.
Something like:
s2:2345:respawn:/sbin/uugetty ttyS2 DT38400 vt100 
(Though this is for a fixed serial line not a dial-in one).
Make certain dosemu is not suid root.
And let all of your users run dos.

You could also make dosemu a login shell but I don't recommend it.

Eric

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

From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: 13 Apr 2000 10:15:54 -0500
Subject: Re: All /usr/local install?

Jay Rogers <[EMAIL PROTECTED]> writes:

> How do I install dosemu (including default /etc config files)
> entirely in /usr/local?
It should be possible but it is definentily non-trivial.

The truly important one to change is the location of /etc/dosemu.users,
and /var/lib/dosemu/global.conf
The other files should pretty much drive off of those.

> 
> www.dosemu.org lists the latest stable release as 0.98.8.  Is
> this correct?  If not, what's the latest stable release?
1.0.0 is, the web page is behind :(

Eric

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

From: Grzegorz Prokopski <[EMAIL PROTECTED]>
Date: Thu, 13 Apr 2000 20:12:29 +0200
Subject: Where are the problems with file locks in dosemu ?

Hi!

I've seen similar topics on that list, but this time I'll
problably be going to try solving this problem myself.
It looks this way:
We want remote acces to an dos database application.
Everything's works just fine, everything but file locks ;(

I did some simple investigation (dosemu 0.99-1 - it was
before You released 1.0 , but I don't think problem was
solved there; and MS-DOS 6.22 ):
1. I checked a few dosemu's on ONE computer and dosemu
file locking works fine (strange - why ?, how ?) 
2. When I run a samba or (real) novell serwer in enviroment
where are Windows clients, and (i checked one, but only for
tests, in future I would like to run more) Linux box with
a few dosemu's. File locking worked (partially) only in one
case. I lock file with dosemu - Windows sees it - I unlock
lock from dosemu - Windows doesn't see it ;( and program
waits until interrupted. Otherwise locks are not seen.
3. My friend told me (but I can't say he *must* be right)
that locks worked "better" with mars_nwe novell emulator.

(At the moment I can't exactly say what flock's the dos
program needs - probably it locks all the file, that
nobody else has acces to it at the moment)

What I need and why I wrote it ?
I haven't yet looked at all the code, but I see that problem
can be in a few layer's. I think (maybe Iam wrong at some
point?) there are such:
- - Application call dos function (lock/unlock)
- - it goes thru lredir
- - file lock i set on UNIX FS layer
- - automaticaly it goes set on server by specific server
client (smb or netware)

I would like to know where the problem is (or where isn't).
And how hard will it be to solve this. Is it possible
to solve anyway ? Where to start ? 

How should be this done "right" way ? Any advices, thoughts,
any help - is welcome. ;) (To priv'a addres I think)

I'am sure dosemu team knows this problem for long time.
Have you been trying to solve this? Sure - yes.
What are Your expiriences ? Where to look for doc's, spec's ?

I wish I could push dosemu to be better a bit. I'am sure
lot's of people has similar problem. And *maybe* (hope so)
I got an occasion to clean that issue. Need to know more
about the problem.

                                        GREG__

PS: Sorry for longness of my post, but with my English I
prefer to say some things twice just to be better
understood.

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

From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: 14 Apr 2000 00:00:05 -0500
Subject: Re: Where are the problems with file locks in dosemu ?

Grzegorz Prokopski <[EMAIL PROTECTED]> writes:

> Hi!
> 
> I've seen similar topics on that list, but this time I'll
> problably be going to try solving this problem myself.
> It looks this way:
> We want remote acces to an dos database application.
> Everything's works just fine, everything but file locks ;(
> 
> I did some simple investigation (dosemu 0.99-1 - it was
> before You released 1.0 , but I don't think problem was
> solved there; and MS-DOS 6.22 ):
> 1. I checked a few dosemu's on ONE computer and dosemu
> file locking works fine (strange - why ?, how ?) 
> 2. When I run a samba or (real) novell serwer in enviroment
> where are Windows clients, and (i checked one, but only for
> tests, in future I would like to run more) Linux box with
> a few dosemu's. File locking worked (partially) only in one
> case. I lock file with dosemu - Windows sees it - I unlock
> lock from dosemu - Windows doesn't see it ;( and program
> waits until interrupted. Otherwise locks are not seen.
> 3. My friend told me (but I can't say he *must* be right)
> that locks worked "better" with mars_nwe novell emulator.
> 
> (At the moment I can't exactly say what flock's the dos
> program needs - probably it locks all the file, that
> nobody else has acces to it at the moment)
> 
> What I need and why I wrote it ?
> I haven't yet looked at all the code, but I see that problem
> can be in a few layer's. I think (maybe Iam wrong at some
> point?) there are such:
> - Application call dos function (lock/unlock)
> - it goes thru lredir
> - file lock i set on UNIX FS layer
> - automaticaly it goes set on server by specific server
> client (smb or netware)
> 
> I would like to know where the problem is (or where isn't).
> And how hard will it be to solve this. Is it possible
> to solve anyway ? Where to start ? 

In dosemu the file to look at is: src/dosext/mfs/mfs.c
look for struct flock.

> 
> How should be this done "right" way ? Any advices, thoughts,
> any help - is welcome. ;) (To priv'a addres I think)

Get traces at each layer, and see what is going on.

For the dosemu layer start running dosemu as dos -D+d -o debug_file
which should record all of the locking/unlocking calls
as well as many other disk based things...

An interesting thing to look for is:
Unlock file region 
It looks like that is a call without code behind it.
But the LOCK_FILE_REGION call seems to have unlocking code...

> 
> I'am sure dosemu team knows this problem for long time.
> Have you been trying to solve this? Sure - yes.
> What are Your expiriences ? Where to look for doc's, spec's ?

Ralph Brown's interrupt list is handy for the dos side.
But if you can create a straigh linux program with the
same problems, (a) you remove a layer. (b) make it possible
to go talk to the Samba folks or whatever...

Locking has come up now and then but we haven't done much.

> 
> I wish I could push dosemu to be better a bit. I'am sure
> lot's of people has similar problem. And *maybe* (hope so)
> I got an occasion to clean that issue. Need to know more
> about the problem.

Well dig in, the code is a little on the rough side
but it it's readable enough.

Hope my hints help,

Eric

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

From: Bernhard Sander <[EMAIL PROTECTED]>
Date: Fri, 14 Apr 2000 12:27:12 +0200
Subject: Re: Where are the problems with file locks in dosemu ?

Hi Grzegorz Prokopski 

> We want remote acces to an dos database application.
> Everything's works just fine, everything but file locks ;(

The basic problem seems to be that Unix (and also Linux) doesn't know
record locking (aka byte range locking), only file locking. But DOS
database programs like clipper need record locking.
Samba and Mars_nwe emulate record locking.

I had a similar problem: in a small company they use a clipper program
in a network. The workstations are 3 DOS and 1 Win98. And there is
another station that dials in from elsewhere via ISDN.

My solution was:
Server runs Linux with Samba, Mars_nwe.
- - The DOS stations connect to the Linux box by Novell clients and runs
the clipper program on the connected drive.
- - The Win98 station connect to the Linux box by Samba and runs the
clipper program in a dos box on the connected drive.
- - The remote station dials in and connects to a vncserver. The vncserver
serves xdos. This xdos connects to the Linux disk by a Novell client
(like the DOS clients). Within xdos runs the clipper program.

Bernhard Sander

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

From: Grzegorz Prokopski <[EMAIL PROTECTED]>
Date: Fri, 14 Apr 2000 19:20:00 +0200
Subject: Re: Where are the problems with file locks in dosemu ?

Bernhard Sander wrote:
> 
> Hi Grzegorz Prokopski
> 
> > We want remote acces to an dos database application.
> > Everything's works just fine, everything but file locks ;(
> 
> The basic problem seems to be that Unix (and also Linux) doesn't know
> record locking (aka byte range locking), only file locking. But DOS
> database programs like clipper need record locking.
> Samba and Mars_nwe emulate record locking.
It would be better to lock all the file, than not to lock
it at all. Gonna dig into it.

> My solution was:
> - The remote station dials in and connects to a vncserver. The vncserver
> serves xdos. This xdos connects to the Linux disk by a Novell client
> (like the DOS clients). Within xdos runs the clipper program.
I've tested (not too carefully). If I run one dosemu with
threesold 0, and IPX with novell client inside, it worked
but running second dosemu on the same machine (with threesold 0
too) was always causing a crash... 100% cpu usage and only
way to get out was hard reset...
Maybe for one client it's good, but I need 5-10 dosemu per
machine. Anyway - I'll check this out too.

                                        GREG__

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

From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: 14 Apr 2000 18:20:38 -0500
Subject: Re: Where are the problems with file locks in dosemu ?

Bernhard Sander <[EMAIL PROTECTED]> writes:

> Hi Grzegorz Prokopski 
> 
> > We want remote acces to an dos database application.
> > Everything's works just fine, everything but file locks ;(
> 
> The basic problem seems to be that Unix (and also Linux) doesn't know
> record locking (aka byte range locking), only file locking. But DOS
> database programs like clipper need record locking.
> Samba and Mars_nwe emulate record locking.

Nope.  Unix knows record locking & we emulate it.
Not the bsd flock call but sysv and I think posix  fcntl(F_GETLK, &
fcntl(F_SETLK calls

Eric

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

From: Josef Drexler <[EMAIL PROTECTED]>
Date: Fri, 14 Apr 2000 20:34:40 -0400
Subject: Dosemu segfaults at software interrupt with CPU prefix [longish]

Hi everybody,

I hope this one proves somewhat interesting.  First, let me give you a
short bit of background history to understand what I'm trying to do.

I'm in the process of writing a wrapper for an old game (Ultima VII).  This
game uses special protected mode instructions which are incompatible with
nearly everything else, including in particular any protected mode OS, so
I'm trying to replace these instruction and make it possible to run the
game under modern hardware.  I intended to use Dosemu for testing and
debugging, so that I don't have to reboot every time I make a mistake.

The way this wrapper will work is by replacing all access beyond real-mode
memory, i.e. all those instructions which have the operand-size prefix
(0x67) by a software interrupt instruction which will then emulate the
protected mode memory.  For example, instead of 
        66 67 8b 1e     MOV EBX,[ESI]
I would have
        66 cd a0 xx     INT A0

This may look a bit weird, but it is necessary to do what I need to do.
The CPU will ignore all prefixes to an int call, and the interrupt handler
can then look at them and emulate the instruction accordingly.  xx is a
special code for interrupt handler determining the exact instruction, and
is not executed when returning from the interrupt by manipulating the IP on
the stack.

So far, so good.  It seems to work pretty well in a Windows 95 DOS box as
well as in real DOS.  However, these are a pain to develop under, and when
I try to run this in Dosemu, I get a segmentation violation for all
interrupts with a prefix.  The unprefixed interrupts, for example in the
case where I replace
        67 8a 06                MOV AL,[ESI]
with
        cd a0 xx                INT A0
work fine, but any time there is a prefix, dosemu crashes with a segfault.

Now, I understand that this is a pretty unique problem, so I'm very much
willing to fix it myself and hopefully supply a patch to the dosemu team,
but I've been looking through the source code and tried to understand why
or where the crash happens, but unfortunately I didn't get very far.  I'm
not even sure where exactly I'd have to look.

So, does anybody have any idea why this is happening, and what I can do to
fix it?  Why does a prefixed int xx cause a segfault when a regular one
works fine?

Oh, and if anybody wants to look at the source code of my wrapper, it's
available here: http://publish.uwo.ca/~jdrexler/ultima/u7patch/ . It's
written in Borland C++ 3.1.  (I can't use DJGPP because it has to be real
mode.)  You'd also need Ultima VII to test it, though.

I would welcome and very much appreciate any help I could get on this.
Ultima VII is considered by many to be a classic, and it's a shame that you
have to jump through hoops to make it run on today's hardware.  But
developing the wrapper under Win95 is tedious.  I'd much prefer if I could
use dosemu under Linux, then I wouldn't have to reboot every few minutes...

Thanks again for reading this and for all comments you can give.


- --
Josef Drexler ([EMAIL PROTECTED])
http://publish.uwo.ca/~jdrexler/


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

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

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

Reply via email to