linux-msdos-digest Monday, 14 June 1999 Volume 01 : Number 147
In this issue:
----------------------------------------------------------------------
From: Declan Moriarty <[EMAIL PROTECTED]>
Date: Tue, 8 Jun 1999 14:54:00 +0000
Subject: RE: KVT problem
On Fri, 04 Jun 1999, Tim Duggan wrote:
>Hi Declan,
>
>Can you login as a different user and duplicate the problem.
>If not there is probably a .kde file or directory (I don't remember which)
>in /home/your_username where it will store user specific default info.
>You should be able to fix it from there.
>
Isn't it pathetic? I can see my thinking blinkered by too many
years of Microsoft Logic (if that's not a contradiction in terms). Now
I try fiddling with Linux, and screw up at once. Mind you, I have
things to say about Linux too at times.... writing 10,000 little notes
to itself and hiding them all in obscure directories so that no human
can find them.
~/.kde/share/config/kvtrc, and kvtrc1 are the config files. I deleted
them and it's fine. Thanks.
--
Regards,
Declan Moriarty
------------------------------
From: [EMAIL PROTECTED]
Date: Tue, 08 Jun 1999 17:57:31 MET_DST
Subject: Re: DOS EMU through Telnet
> What kind of support is there for running DOS apps through telnet. So
> far it appears to work, except the Function keys are dead. Is this a
> terminal application problem, or just lack of support for extended
> keyboard commands when telnetting in?
I suppose you are telnetting from DOS machine to DosEmu - yes?
There is a way to solve the problem - as I remember except CapsLock
key which cannot be passed to DosEmu. I wrote a DOS program which
converts some keys to sequences which DosEmu sees as these keys.
It is not, and cannot be full emulation: on PC key sends make code,
repeats the code if held, and sends break code when released. This
will be on DosEmu side with general shift keys: Shift, Ctrl - both
left and right are received as the same, Alt, AltGr (right Alt).
All other are received as make+break every time they are sent from
terminal. And CapsLock has no code for DosEmu: if it is on, letters
will be uppercased on terminal side. I am not sure how is received
uppercase letter on DosEmu side when scancodes are read...
Let me know if you need the program. Caution: it cause troubles
if there is no DosEmu on second side: e.g. Shift is sent as
Ctrl-^ S and it is hard to type shell commands (up arrow does
not work as you want). You can hold CapsLock to disable the key
translation done by it, but on many keyboards some keys does not
work correctly while CapsLock is held. I can send you its source
so you can change it. Or, maybe terminal emulator can redefine keys?
Jerzy
------------------------------
From: [EMAIL PROTECTED]
Date: Tue, 08 Jun 1999 18:04:05 MET_DST
Subject: Re: Lantastic
> From: John Duthie <[EMAIL PROTECTED]>
> Has anyone had any luck using lantastic in dosemu and accessing the net card
I tried with negative result. REDIR.EXE (part of Lantastic)
refused to work in DosEmu (saying there is a redirector already).
This is for Lantastic 6.0 - maybe other version will work.
I do not remeber what way I tried: you can enable DosEmu to
access network adapter through ports, and driver for the card,
or try to find something to emulate NDIS on packet driver
(but I don't remember if such a program exists).
Jerzy
------------------------------
From: Martin =?iso-8859-1?Q?S=FCfke?= <[EMAIL PROTECTED]>
Date: Tue, 08 Jun 1999 15:05:05 +0200
Subject: Re: How to do DMA transfer under dosemu ?
Alistair MacDonald schrieb:
>
> OK .. Maybe this will help:
>
> DMA in DOSEMU is EMULATED. You can ONLY do DMA to internal DOSEMU devices
> (eg SBEMU) or (possibly) MEMORY-to-MEMORY.
Whoops ...
> That said, *I* didn't understand *exactly* what you were asking because
> *you* didn't provide any details of the source and target of the transfer.
Ok... the DMA is supposed to transfer 625kb/s on 16 bit DMA #5 from a
satellite receiver card to memory.
If it is emuated, I see that it won't transfer data from that receiver
hardware.
Would there be any way to get that DMA work ?
- --
Wr8Ul8r,
Martin
- --
Visit: www.computermuseum.fh-kiel.de
------------------------------
From: Per Erik Stendahl <[EMAIL PROTECTED]>
Date: Wed, 09 Jun 1999 01:40:15 +0200
Subject: Trying to run some old games in xdos
Hi.
I'm trying get those old SSI games "Pool of radiance" with friends
to work in DOSEMU under X. Problem is that the graphics is a
little screwed up. They use EGA graphics which I know next
to nothing about. They seem to use some "text-mode" within
the graphics mode, or maybe it's just graphics mode - I don't
know. Anyway, the screen won't clear and some of it looks
strange. Does anyone know what causes this or/and what I
can do to remedy it?
Also, I cannot run them in the console. When switching to
graphics nothing happens at all or I get a screen of complete
garbage. This is with a Permedia2 based Leadtek L2300.
Cheers
------------------------------
From: Mike Gardiner <[EMAIL PROTECTED]>
Date: Tue, 8 Jun 1999 23:04:25 -0400 (EDT)
Subject: Re: glibc freezing dosemu - not anymore
I requested some help a week or three back with a problem that dosemu
would freeze up after being compiled with the new glibc. All the
suggestions sent did nothing. I downloaded the new 0.98.7 and all is well
now. I don't know what the difference is, but as long as it works, I
don't care much. Thanks for all the suggestions anyway, I should get
such response from a commercial vendor. :-)
============================================================================
Mike Gardiner |"The game is never over, Doctor, and the prize is
[EMAIL PROTECTED] | never won. Broken doors, broken dreams, it's all
[EMAIL PROTECTED] | the same thing. A doors' purpose is to conceal
[EMAIL PROTECTED] | the contents of a room, and dreams are the doors
http://www.msen.com/~mwg | of the mind." - Mysterious Figure, _Broken Doors_
- ----------------------------------------------------------------------------
Unsolicited commercial E-mail subject to $500 processing charge. Sending
such messages constitutes agreement to pay.
============================================================================
------------------------------
From: [EMAIL PROTECTED] (David Hodges)
Date: Wed, 9 Jun 1999 18:37:33 +1200 (NZST)
Subject: Re: Trying to run some old games in xdos
> I'm trying get those old SSI games "Pool of radiance" with friends
> to work in DOSEMU under X. Problem is that the graphics is a
> little screwed up. They use EGA graphics which I know next
> to nothing about. They seem to use some "text-mode" within
> the graphics mode, or maybe it's just graphics mode - I don't
> know. Anyway, the screen won't clear and some of it looks
> strange. Does anyone know what causes this or/and what I
> can do to remedy it?
the 16 colour modes are not implemented under X.
> Also, I cannot run them in the console. When switching to
> graphics nothing happens at all or I get a screen of complete
> garbage. This is with a Permedia2 based Leadtek L2300.
I tried a whole bunch of old games in dosemu 0.98.6 under X and found that
most of them did not work (I did not try any of them on the console):
Of the games I tried, these games worked perfectly:
Doom 2
Carmen San Diego
Forest Squirrel
Mystic Towers
Jumpman
Champ Kong
Captain Comic
and these games didn't work perfectly (most of them didn't work at all) -
possibly some or most of them try to use 16 colour modes (but not all,
because some of them almost work - the display is a bit messed up but
still readable):
Crystal Caves
Historik
Hocus Pocus
Jazz Jackrabbit
Maths Rescue
Paganitzu
Pickle Wars
Robocod
Sea School
Vikings
Wacky Wheels
Word Rescue
(and several others I can't remember now)
------------------------------
From: UNIXMAN <[EMAIL PROTECTED]>
Date: Wed, 9 Jun 1999 04:15:32 -0400 (EDT)
Subject: Re: DOS EMU through Telnet
I recognize the subject but I couldn;t read the message in HTML.
I have dosemu working which I can invoke from an xterm or telnet session
remotely. I've also got dosemu to work from WABI and XFCE. just type
dos :-)
On Tue, 8 Jun 1999 [EMAIL PROTECTED] wrote:
> > What kind of support is there for running DOS apps through telnet. So
> > far it appears to work, except the Function keys are dead. Is this a
> > terminal application problem, or just lack of support for extended
> > keyboard commands when telnetting in?
>
> I suppose you are telnetting from DOS machine to DosEmu - yes?
>
> There is a way to solve the problem - as I remember except CapsLock
> key which cannot be passed to DosEmu. I wrote a DOS program which
> converts some keys to sequences which DosEmu sees as these keys.
> It is not, and cannot be full emulation: on PC key sends make code,
> repeats the code if held, and sends break code when released. This
> will be on DosEmu side with general shift keys: Shift, Ctrl - both
> left and right are received as the same, Alt, AltGr (right Alt).
> All other are received as make+break every time they are sent from
> terminal. And CapsLock has no code for DosEmu: if it is on, letters
> will be uppercased on terminal side. I am not sure how is received
> uppercase letter on DosEmu side when scancodes are read...
>
> Let me know if you need the program. Caution: it cause troubles
> if there is no DosEmu on second side: e.g. Shift is sent as
> Ctrl-^ S and it is hard to type shell commands (up arrow does
> not work as you want). You can hold CapsLock to disable the key
> translation done by it, but on many keyboards some keys does not
> work correctly while CapsLock is held. I can send you its source
> so you can change it. Or, maybe terminal emulator can redefine keys?
>
> Jerzy
>
------------------------------
From: [EMAIL PROTECTED]
Date: Wed, 9 Jun 1999 23:28:44 +1200 (NZST)
Subject: Boot errors with dosemu-98.7
I set up a bootdir.first (generated by ./setup-bootdir) with MSDOS 6.22.
Booting to this results in "Invalid system disk" error.
The dosemu error log gives repeated instances of
SIGILL while in vm86()
ERROR: LOCK prefix not permitted
Are these error messages connected? Any suggestions as to what
might be going wrong and how to fix?
Thanks for any help,
Roger Young.
PS I haven't had this problem with earlier versions of dosemu...
------------------------------
From: Per Erik Stendahl <[EMAIL PROTECTED]>
Date: Wed, 09 Jun 1999 14:03:02 +0200
Subject: Re: Trying to run some old games in xdos
David Hodges wrote:
> > I'm trying get those old SSI games "Pool of radiance" with friends
> > to work in DOSEMU under X. Problem is that the graphics is a
> > little screwed up. They use EGA graphics which I know next
> > to nothing about. They seem to use some "text-mode" within
> > the graphics mode, or maybe it's just graphics mode - I don't
> > know. Anyway, the screen won't clear and some of it looks
> > strange. Does anyone know what causes this or/and what I
> > can do to remedy it?
>
> the 16 colour modes are not implemented under X.
>
It seems to be a little bit implemented since some of the graphics
does work. I might be intrested in spending some time to get this
to work so I would appreciate it if someone would point me to
some relevant DOSEMU and EGA documentation.
Cheers,
Per Erik Stendahl
------------------------------
From: Alistair MacDonald <[EMAIL PROTECTED]>
Date: Wed, 9 Jun 1999 23:27:19 +0100 (BST)
Subject: Re: How to do DMA transfer under dosemu ?
On Tue, 8 Jun 1999, Martin [iso-8859-1] S�fke wrote:
> Alistair MacDonald schrieb:
> > That said, *I* didn't understand *exactly* what you were asking because
> > *you* didn't provide any details of the source and target of the transfer.
> Ok... the DMA is supposed to transfer 625kb/s on 16 bit DMA #5 from a
> satellite receiver card to memory.
> If it is emuated, I see that it won't transfer data from that receiver
> hardware.
> Would there be any way to get that DMA work ?
Only in the same way that you could get *any* DMA to work. You have to get
the kernel to give a user space program (eg DOSEMU) rights to manipulate
the DMA registers (and to prevent problems, the kernel tables that go with
it).
I *DID* receive a patch that provided a series of *devices* which enabled
*ANY* application to pick & manipulate the IRQs & DMA channels. *However*
the only security hole *bigger* than this would be having just a single
user on a machine (root) and having all processess run/owned by this user
(and, of course, logging in as this user all the time). Oh - and for good
measure you would probably want the root password to be an empty string
....
In case that last paragraph *didn't* frighten you enough, I'll put it a
different way. Allowing arbitrary software access to control & manipulate
your IRQs & DMA channels allows *any* process to trash your OS, Disks and
(virtually) anything else you care to mention.
This will *never* become part of DOSEMU *unless* this issue can be
resolved.
Alistair
------------------------------
From: [EMAIL PROTECTED]
Date: Thu, 10 Jun 1999 19:54:50 +1200 (NZST)
Subject: Can't boot to bootdir.first
I'm reposting this enquiry because I'm still haven't resolved
the issue. I am able to boot with hdimage.first, with a floppy,
but not bootdir.first. I followed the instructions in QuickStart
to set up bootdir.first. The system files are identical to those
in hdimage.first and on the floppy. Why am I getting these error
messages? Nobody replied to my original enquiry (below). Is this
because my mistake is embarassingly obvious (like, RFTM), or because
everyone is mystified?
Thanks for your help,
Roger Young.
........................................................................
I set up a bootdir.first (generated by ./setup-bootdir) with MSDOS 6.22.
Booting to this results in "Invalid system disk" error.
The dosemu error log gives repeated instances of
SIGILL while in vm86()
ERROR: LOCK prefix not permitted
Are these error messages connected? Any suggestions as to what
might be going wrong and how to fix?
Thanks for any help,
Roger Young.
PS I haven't had this problem with earlier versions of dosemu...
------------------------------
From: [EMAIL PROTECTED] (David Hodges)
Date: Thu, 10 Jun 1999 20:00:24 +1200 (NZST)
Subject: Re: How to do DMA transfer under dosemu ?
> On Tue, 8 Jun 1999, Martin [iso-8859-1] S�fke wrote:
> > Alistair MacDonald schrieb:
> > > That said, *I* didn't understand *exactly* what you were asking because
> > > *you* didn't provide any details of the source and target of the transfer.
> > Ok... the DMA is supposed to transfer 625kb/s on 16 bit DMA #5 from a
> > satellite receiver card to memory.
> > If it is emuated, I see that it won't transfer data from that receiver
> > hardware.
> > Would there be any way to get that DMA work ?
>
> Only in the same way that you could get *any* DMA to work. You have to get
> the kernel to give a user space program (eg DOSEMU) rights to manipulate
> the DMA registers (and to prevent problems, the kernel tables that go with
> it).
>
> I *DID* receive a patch that provided a series of *devices* which enabled
> *ANY* application to pick & manipulate the IRQs & DMA channels. *However*
> the only security hole *bigger* than this would be having just a single
> user on a machine (root) and having all processess run/owned by this user
> (and, of course, logging in as this user all the time). Oh - and for good
> measure you would probably want the root password to be an empty string
> ....
>
>
> In case that last paragraph *didn't* frighten you enough, I'll put it a
> different way. Allowing arbitrary software access to control & manipulate
> your IRQs & DMA channels allows *any* process to trash your OS, Disks and
> (virtually) anything else you care to mention.
>
> This will *never* become part of DOSEMU *unless* this issue can be
> resolved.
I don't know much about DMA but if the DMA is emulated, I would suspect
it would not be too
difficult to get the code that emulates it to ensure that transfers
only occur between:
1. memory that belongs to DOS
2. devices in a list of allowed devices
------------------------------
From: Petr Hlustik <[EMAIL PROTECTED]>
Date: Thu, 10 Jun 1999 13:10:06 -0400
Subject: DOSEMU failure: VT_ACTIVATE Operation not permitted
Hello,
I've installed dosemu-0.98.1 on a RedHat-5.2 system and it quits right
after the inital messages (CPU speed set to 334/1 MHz; Running on CPU=586,
FPU=1, rdtsc=1). Using the -debug flag gives:
VT_ACTIVATE: Operation not permitted
and sometimes (I guess when I tried to quit)
VT_DEALLOCATE: Device or resource busy
Any ideas? I have not found anything in the /usr/doc/dosemu-0.98.1.
Thanks
Petr
------------------------------
From: Israel Ortiz Robledo <[EMAIL PROTECTED]>
Date: Thu, 10 Jun 1999 23:24:34 -0500
Subject: Help !! marsnwe-dosemu
Hi there!!!:
I have a problem with mars-nwe:
I need to connect dosemu with a "marsnwe-host" , but I can�t do
this.!!!!!!
I configure my host netware emulator in the same way the HOWTO says.
I�m using dosemu with a real Novell Netware O.S. without problems, but
when I change this Hosts with de "Host-novell-emulator" I can do any
conection.This situation just happen with dosemu, my windows95 clients
can detect this "emulator".
I�m using something like this configuration in dosemu to make ipx
conections, and start with:
Autoexec.bat
LSL.com
Pdether
ipxodi.com
With this configurati�n I don�t have problems with Real Novell Host, but
with mars-nwe I really have seriuos problems.
This doesn�t happen with windows95 Clients, that can do conection with
both hosts.
Can somebody help me? I really appreciate this.....
Thanks
ISrael O.
------------------------------
From: Leonardo Ruoso <[EMAIL PROTECTED]>
Date: Fri, 11 Jun 1999 11:53:45 -0300 (EST)
Subject: Inscricao em lista de discussoes!
------------------------------
From: Roland Nagtegaal <[EMAIL PROTECTED]>
Date: Fri, 11 Jun 1999 17:24:10 +0200
Subject: msfoxpro
Hi, I'm new to this list and I already have a question?
Has anyone been succesful in running MS FOXPRO under dosemu ?
I need this to be able to run the dos version of AccountView.
Dosemu segfaults, help with the rights memory settings would be very much
appreciated.
thanks in advance anyone,
Roland Nagtegaal
- ----------------------------------------------------------------------
UNIX isn't dead, it just smells funny...
Run Linux! Keep The Net Free!
- ----------------------------------------------------------------------
------------------------------
From: neirofer <[EMAIL PROTECTED]>
Date: Fri, 11 Jun 1999 21:48:29 +0200
Subject: Bug found in Dosemu
This is a multi-part message in MIME format.
- --------------96EF237C9A960EFDDA2E8949
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
I have found a bug while I was running Sculptor 1.16 for DOS:
When I try to use an acute key (like '=E1'), the program prints'( =E1' an=
d I
can't remove the
'(' character without remove the '=E1'. This problem doesn't occur in
other programs.
Here you have my /etc/dosemu.conf
Thanks
- --------------96EF237C9A960EFDDA2E8949
Content-Type: text/plain; charset=us-ascii;
name="dosemu.conf"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="dosemu.conf"
$_debug = "-a"
$_features = ""
$_timint = (on)
$_mathco = (on)
$_cpu = "80486"
$_rdtsc = (on)
$_cpuspeed = (0)
$_pci = (off)
$_xms = (1024)
$_ems = (1024)
$_ems_frame = (0xe000)
$_dpmi = (off)
$_dosmem = (640)
$_hardware_ram = ""
$_secure = "ngd"
$_odd_hosts = ""
$_diskless_hosts = ""
$_emusys = ""
$_emubat = ""
$_emuini = ""
$_hogthreshold = (0)
$_irqpassing = ""
$_speaker = "emulated"
$_term_char_set = ""
$_term_color = (on)
$_term_updfreq = (4)
$_escchar = (30)
$_rawkeyboard = (on)
$_layout = "es-latin1"
$_keybint = (on)
$_X_updfreq = (5)
$_X_title = "DOS in a BOX"
$_X_icon_name = "xdos"
$_X_keycode = (on)
$_X_blinkrate = (8)
$_X_font = ""
$_X_mitshm = (on)
$_X_sharecmap = (off)
$_X_fixed_aspect = (on)
$_X_aspect_43 = (on)
$_X_lin_filt = (off)
$_X_bilin_filt = (off)
$_X_mode13fact = (2)
$_X_winsize = ""
$_X_gamma = (1.0)
$_X_vgaemu_memsize = (1024)
$_X_lfb = (on)
$_X_pm_interface = (on)
$_X_mgrab_key = ""
$_X_vesamode = ""
$_video = "vga"
$_console = (off)
$_graphics = (on)
$_videoportaccess = (on)
$_vbios_seg = (0xc000)
$_vbios_size = (0x10000)
$_vmemsize = (1024)
$_chipset = "cirrus"
$_dualmon = (off)
$_vbootfloppy = ""
$_floppy_a = "threeinch"
$_floppy_b = ""
$_hdimage = "hdimage.first"
$_hdimage_r = $_hdimage
$_aspi = ""
$_com1 = "/dev/mouse"
$_com2 = ""
$_com3 = ""
$_com4 = ""
$_ttylocks = "/var/lock"
$_mouse = "mousesystems"
$_mouse_dev = "/dev/mouse"
$_mouse_flags = ""
$_mouse_baud = (0)
$_printer = "lp"
$_printer_timeout = (20)
$_ports = ""
$_ipxsupport = (off)
$_novell_hack = (off)
$_vnet = (off)
$_sound = (off)
$_sb_base = (0x220)
$_sb_irq = (5)
$_sb_dma = (1)
$_sb_dsp = "/dev/dsp"
$_sb_mixer = "/dev/mixer"
$_mpu_base = "0x330"
- --------------96EF237C9A960EFDDA2E8949--
------------------------------
From: [EMAIL PROTECTED] (David Hodges)
Date: Sat, 12 Jun 1999 09:09:43 +1200 (NZST)
Subject: Re: msfoxpro
> Hi, I'm new to this list and I already have a question?
>
> Has anyone been succesful in running MS FOXPRO under dosemu ?
> I need this to be able to run the dos version of AccountView.
> Dosemu segfaults, help with the rights memory settings would be very much
> appreciated.
There is some information about FoxPro in the HOWTO, at
http://www.dosemu.org
------------------------------
From: Dwight Johnson <[EMAIL PROTECTED]>
Date: Fri, 11 Jun 1999 20:54:42 -0700 (PDT)
Subject: Anyone try TAS books?
I am trying to run an older MS-DOS bookkeeping program called TAS
books. My platform is SuSE 6.1, dosemu-0.98.6.
I find most of my MS-DOS programs run under dosemu, but TAS books,
instead of starting up, gives me the cryptic error:
key file not found Line # 10
Anyone out there have a clue what this might be about? In TAS books,
programs and data all run in the same directory. I access the logical
drive TAS books is located on with:
lredir.com d: linux\fs/opt/DOS
I suspect it is failing some kind of low level test function for the
existence of the file which was used on '86 vintage PCs and became
possibly obsolete later.
Of course the exact same software works out of the same directory when
I mount it under MS-DOS.
Any suggestions welcomed,
Dwight
- --
Dwight Johnson All the Latest
[EMAIL PROTECTED] Linux News
360-681-6961
- ------------------->>http://linuxtoday.com
------------------------------
From: "Akarat Laoharattanawiboon ([EMAIL PROTECTED])"
<[EMAIL PROTECTED]>
Date: Sat, 12 Jun 1999 11:39:42 +0700
Subject: Request to dosemu
Dear dosemu team developer,
I would like request to make dosemu version to can be run program "CW" in dos
you can be download "CW"
from
http://www.nectec.or.th/pub/pc/cu-writer/
or
ftp://ftp.nectec.or.th/pub/pc/cu-writer/
I can not run this program in dosemu
but this is not BUG in dosemu
I think about display compatible nad other.
for "CW" or "Word Chula"
that are public domain software
develop by Chula University
http://www.chula.ac.th or http://www.chula.edu
CW are software Word Processor.
this program hit and poppula from dos era.
I would like to run on dosemu for can be tryping my word processor on my
local language in linux.
you can test to run CW in MS-DOS for see program running.
this program are my local language word processor or are THAI LANGUAGE Word
Processor.
can be swite between thai and english menu for easy using.
or other you can recomplier CW sorce code availiable for do.
for complier to compatible with you dosemu replace way to change or modify
you dosedu.
for CW.EXE are Thai Language Word Processor on dos.
and
THAI.COM are program thai driver,
thai.com are run on dos for use thai language on other program on dos
use run befor using program ,thai.coma are TSR or resident program in memory.
program will be change display to can display charector of thai language
so, if I would like to use dos EDIT editor program and Thai language, I
will be run thai.com before using.
and other have thai software at.
http://www.nectec.or.th/pub/thailinux/software/
and
http://www.nectec.or.th/pub/thailinux/software/All/
all software are on linux.
other resource
http://www.nectec.or.th/pub/pc/thai-lib/
adnd
http://www.nectec.or.th/pub/pc/word/
Rama word are thai word processor on dos like CW but have more feature
about thail language check spelling and
for poppula thai word processor on dos are have 3-4 program
1. CW. = Chula Word = CU. = (one program have many name call to) = Public
domain
2. RW = Word Rachavitee processor = Public domain developby computer
center of Rachavitee Hospital. and Dr.
3. Rama = Word Rama = Rama Word = I am not sure Public Domain or Freeware
(may be Shareware) can be use free and can copy free distribute free.
4. thai.com = Thai Driver for dos.
for thai word processor in linux are develop and not yet perfect.
team developer are can be make enable for using read and typing charector,
but processor note yet complete.
and may be good if can be use free software from dos run and use replace in
the way ot use.
Thank you.
Respect,
Akarat Laoharattanawiboon.
note.
http://www.nectec.or.th/pub/pc/cu-writer/
http://www.nectec.or.th/pub/pc/cu-writer/00_index.txt
cusrc-1.zip CU-Writer 1.52 Source (1/4)
cusrc-2.zip CU-Writer 1.52 Source (2/4)
cusrc-3.zip CU-Writer 1.52 Source (3/4)
cusrc-4.zip CU-Writer 1.52 Source (4/4)
cw.zip
cw152.zip CU-Writer 1.52
cw152man.zip Manual for CU-Writer 1.52
cw160.zip CU-Writer 1.60
cwdocs.zip Document for CU-Writer (Thi)
cwengdoc.zip Document for CU-Writer (Eng)
cww.zip CU-Writer for Windows (Final Release)
------------------------------
From: Chris Albertson <[EMAIL PROTECTED]>
Date: Fri, 11 Jun 1999 23:18:06 -0700
Subject: Re: Request to dosemu
Hello,
I see a lot of posts that read "I which program XX would run
under dosemu." I know saying this on a dosemu list is to
risk getting flammed but... Have to tried "vmware"? Look at
http://www.vmware.com What vmware gives you is a virtual machine.
the virtual machine is robust enough that you can run Windows NT
on it or even another version of Linux, or FreeBSD or ... DOS.
DOS under VMware does seems to be pretty solid. This is comercial
not-free software but if it works and you really need it maybe
worth it. A 30 day eval. period is free. So try it out.
- --
--Chris Albertson home: [EMAIL PROTECTED]
Redondo Beach, California work: [EMAIL PROTECTED]
------------------------------
From: Andre Majorel <[EMAIL PROTECTED]>
Date: Sat, 12 Jun 1999 13:01:46
Subject: Boom and MBF
Did anyone manage to get Boom and MBF to work under Dosemu ?
With $_xms = (8192) and $_dpmi = (8192), both abort immediately and
silently.
After bumping $_dpmi to (16384), MBF still aborts immediately but
says :
Failed trying to allocate DOS near pointers
and Boom is a little more verbose :
Failed trying to allocate DOS near pointers
Cannot continue from exception, exiting due to signal 0121
Division by Zero at eip=0004c7d4
<register dump snipped>
Both Boom and MBF are DJGPP programs and use Allegro.
In any case, when running cwsdpmi I get :
Protected mode not accessible.
Andr� Majorel <[EMAIL PROTECTED]>
http://www.teaser.fr/~amajorel/
------------------------------
From: Dwight Johnson <[EMAIL PROTECTED]>
Date: Sat, 12 Jun 1999 10:23:06 -0700 (PDT)
Subject: File read error in dosemu-0.98.6
I am getting the cryptic error:
key file not found Line # 10
when I try to run an older MS-DOS bookkeeping program called TAS
books. My platform is SuSE 6.1, dosemu-0.98.6.
Most of my other MS-DOS programs run under dosemu.
Anyone out there have a clue what this might be? In TAS books,
programs and data all run in the same directory. I access the logical
drive with:
lredir.com d: linux\fs/opt/DOS
I suspect it is failing some kind of low level test function for the
existence of the file which was used on '86 vintage PCs and became
possibly obsolete later.
Of course, the exact same software works out of the same directory when
I mount it under MS-DOS.
Any suggestions welcomed,
Dwight
- --
Dwight Johnson All the Latest
[EMAIL PROTECTED] Linux News
360-681-6961
- ------------------->>http://linuxtoday.com
------------------------------
From: Martin =?iso-8859-1?Q?S=FCfke?= <[EMAIL PROTECTED]>
Date: Sat, 12 Jun 1999 13:02:06 +0200
Subject: Re: Help !! marsnwe-dosemu
Israel Ortiz Robledo schrieb:
> I need to connect dosemu with a "marsnwe-host" , but I can�t do
> this.!!!!!!
>
> I configure my host netware emulator in the same way the HOWTO says.
> I�m using dosemu with a real Novell Netware O.S. without problems, but
> when I change this Hosts with de "Host-novell-emulator" I can do any
> conection.This situation just happen with dosemu, my windows95 clients
> can detect this "emulator".
>
> I�m using something like this configuration in dosemu to make ipx
> conections, and start with:
>
> Autoexec.bat
> LSL.com
> Pdether
> ipxodi.com
>
> With this configurati�n I don�t have problems with Real Novell Host, but
> with mars-nwe I really have seriuos problems.
Don't you load a redirector ? (VLM / NetX )
> This doesn�t happen with windows95 Clients, that can do conection with
> both hosts.
Unfortunately, you don't give a too detailed description of your
network configuration...
My first guess: You might have trouble with the IPX-network-adresses /
frame types.
As Win95 is auto-probing them, it wouldn't care, but DOS-clients do.
try "ifconfig" on your mars-nwe machine to see weather the network
adresses / frame types are the
same as those of the real Novell-machine.
BTW: did you think on having DOSEMU do all the network stuff for you ?
(AFAIK you 'd then only have to load the redirector (VLM or similar)
- --
Wr8Ul8r,
Martin
- --
Visit: www.computermuseum.fh-kiel.de
------------------------------
From: Martin =?iso-8859-1?Q?S=FCfke?= <[EMAIL PROTECTED]>
Date: Sat, 12 Jun 1999 17:51:33 +0200
Subject: Changelog ?
Maybe I haven't seen it yet ....
Is there a changelog wich is kept up-to-date ?
- --
Wr8Ul8r,
Martin
- --
Visit: www.computermuseum.fh-kiel.de
------------------------------
From: Dwight Johnson <[EMAIL PROTECTED]>
Date: Sun, 13 Jun 1999 14:32:03 -0700 (PDT)
Subject: Low traffic -- the reason?
This list appears to have much less traffic than when I last
subscribed two years ago. Is there a more active list or has the
action moved to Wine?
Dwight
- --
Dwight Johnson All the Latest
[EMAIL PROTECTED] Linux News
360-681-6961
- ------------------->>http://linuxtoday.com
------------------------------
From: Ralph Alvy <[EMAIL PROTECTED]>
Date: Sun, 13 Jun 1999 17:52:52 -0400
Subject: CAPS LOCK
I notice that my CAPS LOCK key fails to do anything in an xdos dosemu
session, but works fine in a regular dos dosemu session. Does anyone else
notice this? I'm using dosemu 0.98.7 under kernel 2.0.36.
Ralph Alvy
[EMAIL PROTECTED]
------------------------------
From: Alistair MacDonald <[EMAIL PROTECTED]>
Date: Sun, 13 Jun 1999 23:08:00 +0100 (BST)
Subject: Re: How to do DMA transfer under dosemu ?
On Thu, 10 Jun 1999, David Hodges wrote:
Be careful with the quoting - It isn't clear who wrote what here ...
[Intermediate quotes (level '> > ') are from me ....]
> > On Tue, 8 Jun 1999, Martin [iso-8859-1] Sfke wrote:
> > > Alistair MacDonald schrieb:
> > > > That said, *I* didn't understand *exactly* what you were asking because
> > > > *you* didn't provide any details of the source and target of the transfer.
> > > Ok... the DMA is supposed to transfer 625kb/s on 16 bit DMA #5 from a
> > > satellite receiver card to memory.
> > > If it is emuated, I see that it won't transfer data from that receiver
> > > hardware.
> > > Would there be any way to get that DMA work ?
> >
> > Only in the same way that you could get *any* DMA to work. You have to get
> > the kernel to give a user space program (eg DOSEMU) rights to manipulate
> > the DMA registers (and to prevent problems, the kernel tables that go with
> > it).
[...]
> I don't know much about DMA but if the DMA is emulated, I would suspect
> it would not be too
> difficult to get the code that emulates it to ensure that transfers
> only occur between:
> 1. memory that belongs to DOS
> 2. devices in a list of allowed devices
The point is not that *we* can't police it, but that the *kernel* can't
police it. It cannot distinguish between *us* asking for this and *any
other* program asking for it.
IE if *we* can do it, *any* piece of software can.
*SPECIFICALLY* a piece of software can be written that can prevent
interrupts from being allocated later (eg by running before the sound
module is loaded) or can use DMA channels for it own purposes (eg by
taking copyies of "private" memory, or by overwriting this same memory.)
Alistair
------------------------------
From: "K.A. Steensma" <[EMAIL PROTECTED]>
Date: Sun, 13 Jun 1999 20:32:14 -0700
Subject: Can't get TeraTerm to sent F1-F5 to Clipper EXE
I don't exectly which newsgroup or mailing list would most likely have
someone that has gotten this to work, but:
I'm using a Win9x terminal program called TeraTerm to control a MS-DOS
compiled Clipper program that is executing inside the Linux ('dosemu')
MS-DOS emulator. Don't shudder, it's a fairly reliable (and off-used)
method of running programs on a Linux network. That is all fine and
responds to all normal keystrokes just 'as defined'.
The problem is: The TeraTerm keyboard can be configured by modifying an
associated .CFG file. By doing this, almost any keycode can be
configured and assigned to a key on the keyboard. In the case of
function keys #6 through #10 (on a standard 101/104-key keyboard), they
operate fine. But I can not understand the author's instructions for
getting function keys #1 through 5 to work.
I even wrote a 'quick & dirty' Clipper program that would report out the
'lastkey()' code. And just like expected, function keys #1 through 5 do
nothing.
Is there someone who has solved this? If so, I would appreciate a copy
of the 'keyboard.cfg' that is set up correctly.
TIA Keith
------------------------------
From: UNIXMAN <[EMAIL PROTECTED]>
Date: Mon, 14 Jun 1999 04:22:36 -0400 (EDT)
Subject: Re: Low traffic -- the reason?
hmmm, that sounds like that could be bad news, maybe DOS is dieing :-(
On Sun, 13 Jun 1999, Dwight Johnson wrote:
> This list appears to have much less traffic than when I last
> subscribed two years ago. Is there a more active list or has the
> action moved to Wine?
>
> Dwight
> --
> Dwight Johnson All the Latest
> [EMAIL PROTECTED] Linux News
> 360-681-6961
> ------------------->>http://linuxtoday.com
>
>
------------------------------
From: Declan Moriarty <[EMAIL PROTECTED]>
Date: Sun, 13 Jun 1999 16:26:58 +0000
Subject: Re: Anyone try TAS books?
On Sat, 12 Jun 1999, Dwight Johnson wrote:
>I am trying to run an older MS-DOS bookkeeping program called TAS
>books. My platform is SuSE 6.1, dosemu-0.98.6.
>
>I find most of my MS-DOS programs run under dosemu, but TAS books,
>instead of starting up, gives me the cryptic error:
>
>key file not found Line # 10
>
>Anyone out there have a clue what this might be about? In TAS books,
>programs and data all run in the same directory. I access the logical
>drive TAS books is located on with:
>
>lredir.com d: linux\fs/opt/DOS
I'm no expert, but I can help here. I had TAS books. It has a
batch file (books.bat or something) which will have pathnames in there.
Have you hacked this to replace the paths with the DOSEMU location of
C:\TAS, or wherever you had it? Try that. I'd suggest a copy of the
batch file with a different name.
T
--
Regards
(now at [EMAIL PROTECTED])
Declan Moriarty
------------------------------
From: Lars Oliver Bausch <[EMAIL PROTECTED]>
Date: Mon, 14 Jun 1999 13:53:19 +0200
Subject: Dosemu over vt
Hi !
I've some problem with dosemu over an VT.
The native dos programm shows the chars ofer 128 (ASCII>128) on the
console correct.
But over a colored vt220 the signs over 128 are not correctet displayed.
Can I resolve the problem with
a) changing to vtXXX
b) dosemuconfiguration
Thanks
Lars
------------------------------
From: Israel Ortiz Robledo <[EMAIL PROTECTED]>
Date: Mon, 14 Jun 1999 19:06:14 -0500
Subject: Re: Help !! marsnwe-dosemu
This is a multi-part message in MIME format.
- --------------E7D8BD564BE975E715C6735C
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Martin S�fke wrote:
> Israel Ortiz Robledo schrieb:
>
> > I need to connect dosemu with a "marsnwe-host" , but I can�t do
> > this.!!!!!!
> >
> > I configure my host netware emulator in the same way the HOWTO says.
> > I�m using dosemu with a real Novell Netware O.S. without problems, but
> > when I change this Hosts with de "Host-novell-emulator" I can do any
> > conection.This situation just happen with dosemu, my windows95 clients
> > can detect this "emulator".
> >
> > I�m using something like this configuration in dosemu to make ipx
> > conections, and start with:
> >
> > Autoexec.bat
> > LSL.com
> > Pdether
> > ipxodi.com
> >
> > With this configurati�n I don�t have problems with Real Novell Host, but
> > with mars-nwe I really have seriuos problems.
>
> Don't you load a redirector ? (VLM / NetX )
Yes, of course I do , in fact I try to use VLM with the mars-nwe,later I try
to use NetX but in both ways it doesn�t work.
>
>
> > This doesn�t happen with windows95 Clients, that can do conection with
> > both hosts.
>
> Unfortunately, you don't give a too detailed description of your
> network configuration...
> My first guess: You might have trouble with the IPX-network-adresses /
> frame types.
I checked It. I actually using three types of frame following recommendations
of the "Novell.txt" in the dosemu documentation. I actually using 802.2 802.3
and EtherII frames.
>
> As Win95 is auto-probing them, it wouldn't care, but DOS-clients do.
> try "ifconfig" on your mars-nwe machine to see weather the network
I Will.
>
> adresses / frame types are the
> same as those of the real Novell-machine.
I want to substitute de real Novell-machine by this mars-nwe-machine, so I
shutdown the real-machine before I "wake up" mars-nwe-linux machine.
>
> BTW: did you think on having DOSEMU do all the network stuff for you ?
> (AFAIK you 'd then only have to load the redirector (VLM or similar)
>
> --
> Wr8Ul8r,
> Martin
> --
> Visit: www.computermuseum.fh-kiel.de
By the way I Send my mars-nwe configuration, and I would apreciate if you
tell me what�s wrong with this file, if exist something wrong.
Thanks a lot
Israel O.
- --------------E7D8BD564BE975E715C6735C
Content-Type: text/plain; charset=us-ascii; name="nwserv.conf"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="nwserv.conf"
#
# This is the configuration-file for "mars_nwe", a free netware-emulator
# for Linux.
#
# last changed: 08-Feb-98
#
# !! section 5 : deleting of ipx devices/routes changed in 0.99.pl6 !!
# !! section 4 : automatic creation of ipx-interfaces changed in 0.98.pl9 !!
#
# since version 0.98.pl11:
# the most important options in config.h can now be altered in
# this file begin at section 60.
#
# Most configuration errors depend on section 4.
# !! Please read section 4 very carefully. !!
#
# This file specifies which Linux-resources (printers, users, directories)
# should be accessible to the DOS-clients via "mars_nwe". Furthermore
# some general parameters are configured here.
# Some options of "mars_nwe" can only be altered by editing the the file
# `config.h' and re-compiling "mars_nwe", please see there for more
# information.
# Syntax of this config-file:
# - everything after a "#" is treated as a comment (particularly
# it does never belong to the values themselves)
# - entries _must_ begin with a number, indicating the section
# they belong to
# - hexadecimal values are prepended by "0x"
#
# All examples are verbatim.
#
# The term "DOS-client" does not refer to the special operating-system
# "DOS" in _this_ file. "DOS-client" is only a synomym for all possible
# ipx-clients (it's choosen for the people who are confused by the
# meaning of "client" and "server").
# The "Linux-side" of the game is always the "mars_nwe"-server.
# =========================================================================
# Section 1: volumes (required)
#
# In this section you list all Linux-directories accessible via "mars_nwe".
#
# To be more precise: a mapping from Linux-directories to mars_nwe-volumes
# is done. (Volumes are the beasts you can map to drive letters under DOS
# using "map.exe").
#
# Linux-directory mars_nwe-volume map.exe DOS-Drive
# /var/local/nwe/SYS -------> SYS -------------> W:
#
# More than one entry is allowed in this section.
# The maximum number of volumes must be specified in `config.h'
# or in section 61 in this file.
#
# Please note that at least the volume "SYS" must be defined and it must
# contain the following sub-directories: LOGIN, PUBLIC, SYSTEM, MAIL.
# See the installation-instructions in the doc-directory for more infos
# and the info to section 16 (tests on startup) in this file.
#
# !! NOTE !!
# First defined volume should always named 'SYS'.
#
#
# -------------------------------------------------------------------------
# Syntax:
# 1 VOLUMENAME DIRECTORY [OPTIONS] [UMASKDIR UMASKFILE]
#
# VOLUMENAME: the name of the mars_nwe-volume (max. 8 characters)
# DIRECTORY: the directory on your Linux-system associated with that
# volume; use the special name "~" to refer to the users
# individual home-directory.
# A directory entry like "~/tmp" also work since 0.99.pl3.
#
# If the netadmin wants to map the homedirectories with the MAP-Command to
# every user, he can do it in two variants:
# We suppose that the user test2 is logged in MARS_NWE. He has files
# earlier stored in his homedirectory /home/test2.
# In case of entry 1 in /etc/nwserv.conf (naturally amongst other entries)
# there are other results of the MAP-command.
#
# Variant 1 Variant 2
#
#DOS-Command MAP H:=MARS\HOMEDIR: MAP H:=MARS\HOMEDIR:
#
#Entry in /etc/nwserv.conf
# 1 HOMEDIR ~ k 1 HOMEDIR /home k
#
#Result of DIR *.* All files stored in All homedirs of the
# /home/test2 will shown. users will shown.
# Showing his own files
# it is a command like
# CD test2 and then
# dir *.* necessary.
#
# OPTIONS: none or some of the following characters (without a seperator)
# - Placeholder.
# Next two options control DOS and OS/2 namespace.
# i ignore case, handle mixing upper/lowercase filenames (slow)
# should only be used if you really need it.
# k use lowercase-filenames (if you don't set this,
# and you don't set 'i' all files _must_ be upper-case)
# m removable volume (e.g. cd-roms) or volumes, which
# should be remountable when mars_nwe is running.
# r volume is read-only and always reports "0 byte free"
# (this is intended for copies of CD-ROMs on harddisks)
# o (lowercase o)
# volume has only one filesystem/device/namespace
# this is for filesystems with high inode > 0xFFFFFFF.
# because for namespace services mars_nwe normally use the
# first 4 bit of 32 bit inode for distinguish
# between several devices/namespaces for one volume.
# p "PIPE"-filesystem. All files are pipe commands.
# See `doc/PIPE-FS'.
#
# additional Namespaces
# O (uppercase o)
# + OS/2 namespace (useful for Win95 clients, see doc/FAQS).
# N + NFS namespace (not really tested).
#
#
# UMASKDIR: default directory creat umask.
# UMASKFILE: default file creat umask.
# value are always octal, overwrite standard section 9 entries
# for this specific volume.
#
# -------------------------------------------------------------------------
#
# Examples:
# 1 SYS /var/local/nwe/SYS k
# 1 CDROM /cdrom kmor
# 1 HOME ~ k -1
# 1 HOMETMP ~/tmp kiO
# 1 PRIVAT ~/privat kO 700 600
# 1 WORLD /var/world kiO 777 666
1 SYS /var/mars_nwe/sys k
##############################################################
# Modificaciones hechas por Israel Ortiz Robledo 01/02/1999
##############################################################
1 PROVER /PTC2/Prover k
1 TDM /PTC2/Tdm k
1 SISTEMA /PTC2/Sistema k
# =========================================================================
# Section 2: servername (optional)
#
# The servername is the name under which this server will show up when
# using tools like "slist" (server-list).
#
# If you don't supply an entry for this section, the hostname of your
# Linux-machine will be converted to all-uppercase and used as the servername.
#
# -------------------------------------------------------------------------
# Syntax:
# 2 SERVERNAME
#
# SERVERNAME: a name for this nw-server
# -------------------------------------------------------------------------
#
# Example:
# 2 MARS # name of the server would be "MARS"
#####################################################################
# Modificaciones Hechas por Israel Ortiz Robledo el 01/02/1999
#####################################################################
2 SISTEMA
# =========================================================================
# Section 3: Number of the internal network (required)
#
# If have dealt with the TCP/IP-configuration of your Linux-Box, the term
# "ip-address" may be familiar to you. It's a numer that uniquely
# identifies your machine in the internet.
# As you might already expect, even the IPX-people use a unique number to
# identify each other. Addresses in the IPX-world always consist of a
# 4-byte "network-number" plus a 6-byte "node-number" (remember the
# ip-addresses also use 4-bytes).
#
# The numbering-rule for ipx-clients is easy: their "address" is the
# external-network of the server they are connected to plus the
# hardware-address of their own ethernet-card (6 byte). As a result of this
# rule, the clients can determine their address automatically (by listening
# to the server and looking at their own ethernet-hardware) and no
# configuration-files on the clients-side have to be maintained. (It would
# really be a nasty thing if you think of very many DOS-clients [remember:
# DOS is an OS where ordinary users can screw up the configuration files].)
#
# For internal routing purposes, a netware-server has an "internal network"
#
# As there is no organisation which regulates the use of network-numbers
# in the IPX-world, you have to run "slist" (under DOS or Linux) to
# determine a number that isn't already used by another server on your
# net. You better double-check and ask the other network administrators
# before using a random value because not all servers might be on-line when
# you "listen" to the net.
#
# A reasonable choice for the internal net-number of your mars_nwe-server
# could be the ip-address of your Linux-Box. It is reasonable because
# ip-addresse are unique and if every nw-administrator uses only this uniqe
# value, potential conflicts will be minimized. Of course this choice is
# no guarantee and it only works if your Linux-Box IP is well configured.
#
# Please note that you have to specify the address of your "internal
# ipx-network" in hexadecimal format (the leading "0x" indicates it).
#
#
# -------------------------------------------------------------------------
# Syntax:
# 3 INTERNAL_NET [NODE]
#
# INTERNAL_NET: the hexadecimal value of your "internal ipx-network". Use
# "0x0" or "auto" to refer to your ip-addresse (it's a kind of
# automagically setup)
# NODE: use "1" if you don't know what this entry is for (optional)
# -------------------------------------------------------------------------
#
# Example:
# 3 auto 1 # 'automatic' setup, use ip-number as internal net
3 auto 1
# =========================================================================
# Section 4: IPX-devices (strongly recommended)
#
# This section contains information for the ipx-router built into mars_nwe
# and/or the external program "nwrouted".
# Both processes exchange the ipx-packets between your machine and the rest
# of the world (in other words: their functionallity is essential). Of
# course, to use one of both is already sufficient.
#
# Note for people with other IPX/NCP servers on the net:
# - choose the same frame-type as the other servers use
# - make sure your network-number is not already in use by another
# server (see the output of "slist" under Linux or DOS)
#
# Under Linux, it is possible to let the kernel creat all ipx-devices
# automatically for you. This is only possible (and only makes sense then)
# if there are other IPX/NCP servers on the same net which are setup
# correctly. It can be switched on in section '5'.
# -------------------------------------------------------------------------
# Syntax:
# 4 NET_NUMBER DEVICE FRAME [TICKS]
#
# NET_NUMBER: this number is determined by the router of the physical
# network you're attached to. Use "0x0" to use the entry
# for all network number match.
#
# DEVICE: the network-interface associated with the NET_NUMBER. Use
# a "*" (star) to use this entry for all devices match.
#
# FRAME: the frame-type of the data-packets on your local network.
# Possible values are:
#
# ethernet_ii :best for mixed(ipx, ip) environments
# 802.2 :Novell uses this as default since 3.12
# 802.3 :older frame typ, some boot proms use it
# snap :normally not used
# token :for token ring cards
# auto :automatic detection of the frame-type used
# in your ipx-environment
#
# TICKS: the time data-packets need to get delivered over a
# certain interface. If your connection goes through several
# routers, the shortest path can be determined by summing up
# all ticks for every route and compare the results.
# (1 tick = 1/18th second), default=1
# Note: If ticks > 6 then the internal router handles
# RIP/SAP specially. (RIP/SAP filtering)
#
# !! NOTE !!
# Automatic detection in this section means that ipx-interfaces which
# are created by other instances than the server/router,
# e.g. pppd, ipppd or ipx_interface, will be detected and inserted/removed
# in internal device/routing table at runtime.
#
# Automatic kernel creation of interfaces can be switched on in section 5.
# -------------------------------------------------------------------------
#
# Examples:
# 4 0x10 eth0 802.3 1 # setup ethernet with frame 802.3
# 4 0xa20 arc0 802.3 1 # standard arcnet (TRXNET)
#
# 4 0x0 * AUTO 1 # auto detection of all ipx-interfaces.
# 4 0x0 eth0 AUTO 1 # auto detection of eth0 frames.
# 4 0x0 eth0 802.2 1 # auto detection of eth0 frame 802.2.
#
# Note: If ticks > 6 then the internal router handles RIP/SAP specially.
# (RIP/SAP filtering)
# 4 0x0 isdn0 802.3 7 # auto isdn interface with ethernet encap.
# 4 0x0 ippp0 AUTO 7 # auto ippp0 (isdn ppp) interface.
# 4 0x0 ppp0 AUTO 7 # auto detection of ppp0 interface.
# 4 0x0 eth0 AUTO 1
4 0xa eth0 ethernet_ii 1
4 0xb eth0 802.3 1
4 0xc eth0 802.2 1
# Section 5: special device flags
# =========================================================================
# Flags
# 0x1 do not remove by nwserv/nwrouted added routes and ipx-devices
# beyond the lifetime of the server or router.
# If this flag is not set then all by nwserv/nwrouted added
# ipx-devices/routes will be deleted when
# nwserv/nwrouted ends (default).
#
# 0x2 Switch on automatic kernel creation of ipx-interfaces.
# The automatic kernel creating of ipx-devices sometimes
# make trouble (Win95). It should only be used in the
# beginning or for testing.
#
# 0x4 do remove ALL routes and ipx-devices
# beyond the lifetime of the server or router.
# If this flag is set then all ipx-devices/routes
# will be deleted when nwserv/nwrouted ends.
# This was the default prior mars_nwe 0.99.pl6 !
#
#
# other flags may follow.
# value will be interpreted as hex value.
5 0x2
# =========================================================================
# Section 6: version-"spoofing"
#
# Some clients work better if the server tells that it is a 3.11 Server,
# although many calls (namespace services) of a real 3.11 Server are
# missing yet.
# -------------------------------------------------------------------------
# Syntax:
# 6 SERVER_VERSION [FLAGS]
#
# SERVER_VERSION: the version-number reported to DOS-clients
# 0 Version 2.15 (was default till version 0.98.pl7)
# 1 Version 3.11 (is default now)
# 2 Version 3.12
#
# If you want to use longfilenamesupport and/or namespace routines
# you should set this section to '1' or '2'
# And you should read doc/FAQS.
#
# FLAGS: some flags
# &1 enable burst mode connections.
# If you want to test Burst mode this flag must be set.
# and in config.h you must set ENABLE_BURSTMODE to 1.
#
# other flags may follow.
# value will be interpreted as hex value.
# -------------------------------------------------------------------------
#
6 1 &1
# =========================================================================
# Section 7: password handling of DOS-clients (required)
#
# When changing your "mars_nwe"-password from a DOS-client, this client
# (think of "LOGIN.EXE", "SYSCON.EXE" or "SETPASS.EXE") can encrypt your
# password before sending it to the "mars_nwe"-server (this improves
# security a little bit).
# In this section you can enforce encryption of user-passwords or allow
# not-encrypted sending of passwords over the net.
#
#
# On the Linux-side, passwords will only be stored in encrypted format.
#
#
# -------------------------------------------------------------------------
# Syntax:
# 7 Value
#
# Value:
# 0 enforce encryption of _all_ passwords by the DOS-client
# (default)
# 1 as "0", but allow the non-encrypted version of the
# "change password"-routine.
# 7 allow all non-encrypted stuff but no empty nwe passwords.
# 8 allow all non-encrypted stuff and also allow empty
# nwe-passwords.
# 9 use all non-encryted calls + "get crypt key" will always fail
# so the login program will use the old unencryted calls.
# this will *not* work with all clients !! (OS2/client)
# -------------------------------------------------------------------------
7 0
# Section 8: special login/logout/security and other flags.
# =========================================================================
# Flags
# 0x1 allow changing dir/accessing other files than login/*
# when not logged in, if the client supports it.
# ( this was standard till mars_nwe-0.98.pl4 )
#
# 0x2 switch on strange compatibility mode for opening files.
# If an opencall do an open for writing but
# the file is readonly then this call will not fail
# but open the file readonly.
#
# 0x4 allow the rename file call (NCP function 0x45)
# renaming of directories.
# normally the rename file call returns an error if this
# routine is used for renaming directories.
#
# 0x8 ignore station/time restrictions for supervisor.
#
# 0x10 allows deleting a file even if the file is opened by
# other process.
# ( this was standard before mars_nwe-0.99.pl0 )
#
# 0x20 store file base entries for later use.
# Normally only directory base entries are stored.
# necessary if using ncpfs as mars_nwe client.
#
# 0x40 limit's volume's free space info to 2 GB.
# in some volume info calls.
# some DOS clients need it.
#
# other flags may follow.
# value will be interpreted as hex value.
8 0x0
# Section 9: Standard creat mode for creating directories and files.
# =========================================================================
#
# mkdir mode (creat mode directories), creat mode files
# values are always interpreted as octal values !
# if 0 is specified the standard umask will be used.
# if -1 is specified for directories the st_mode of parent directory
# will be used.
# Volumes depended values can be set in section 1.
# 9 -1 0664
#
9 0755 0664
# Section 10: UID and GID with minimal rights
# =========================================================================
#
# When loading the netware-drivers in the "autoexec.bat" of your
# DOS-client, you automatically "attach" to a netware-server.
# As a result, a new drive-letter is accessible under DOS, usally
# containing the programs "login.exe" and "slist.exe".
# Because you haven't logged in, nothing else of the netware-server
# will be visible to you. All actions requested from the DOS-client
# will be done with the following UID and GID on the Linux-side in this
# case.
# To achieve some level of security, the user/group asscociated with
# the UID and GID should only have _read_ rights on the files visible,
# _nothing_ else.
#
# On most Linux-systems, there is a user and group "nobody" defined in
# `/etc/passwd' and `/etc/group'. Use the number of that user/group
# for the following entries.
#
# -------------------------------------------------------------------------
# Syntax:
# 10 GID
# 11 UID
#
# GID numeric number of the group
# UID numeric number of the user
# -------------------------------------------------------------------------
#
# Example:
# 10 65534
# 11 65534
10 65534
11 65534
# =========================================================================
# Section 12: supervisor-login (required)
#
# The "supervisor" of a nw-server is much like "root" on the Linux-side.
#
# Specify a Linux-user that should be mapped to the supervisor of this
# mars_nwe-server.
# To improve security, don't use "root" for this purpose but create a
# seperate administrative account (under Linux) called "nw-adm" or similar.
#
# The nw-user defined in this section will have the mars_nwe internal UID
# "1" (remember even under Linux "root" must have the special UID "0"), so
# it is not possible to define a supervisor in section 13 (the users
# defined there will get random UIDs).
# You _can_ define a user with name "SUPERVISOR" in section 13, but he
# won't really be the "local god" on the "mars_nwe"-server.
# And of course you _can_ define a supervisor with name "GOD" or "ROOT"
# in _this_ section, which would only break the traditional naming-scheme
# of the netware-world.
#
#
# -------------------------------------------------------------------------
# Syntax:
# 12 NW_LOGIN LINUX_LOGIN [PASSWORD]
#
# NW_LOGIN: the login-name for the "mars_nwe"-server (traditionally,
# this is "SUPERVISOR")
# LINUX_LOGIN: the account on the Linux-side associated with the NW_LOGIN
# PASSWORD: the password for the NW_LOGIN. It must be clear-text but
# will be encrypted and permanent stored in the
# bindery-files, so it (the password or the whole section, at
# your option) can be deleted after the first start of
# "nwserv".
#
# Make sure this file is not world-readable as long
# as the password stands here.
#
# If you leave this field blank when starting "mars_nwe" the
# first time, the supervisor-login will be completely
# disabled. In other words: there is no way to supply the
# supervisor with no password ("null-password").
# -------------------------------------------------------------------------
#
# Example:
# 12 SUPERVISOR nw-adm top-secret
12 SUPERVISOR root biosfera
# =========================================================================
# Section 13: user-logins (optional)
#
# You can provide mappings from the regular login-names of your Linux-Box
# to "mars_nwe"-logins here.
# Every "mars_nwe"-user _must_ have a login-name on the Linux side (even
# if he can't log in into the account associated with the login-name,
# because you locked it with a "*") in order to "own" files.
# If you specify a Linux-login that doesn't exist (one could think of a
# typo), the user will only have the minimal rights defined in
# sections 10/11.
#
# You may also map different mars_nwe user to the same unix user.
#
# See section 12 for a description of the syntax.
#
# Unlike in section 12, you can define users with no password.
# If you explizit want to set 'no password' here then use
# a '-' sign as password.
# -------------------------------------------------------------------------
# Syntax:
# 13 NW_LOGIN LINUX_LOGIN [PASSWORD] [FLAGS]
#
# FLAGS must be a hex value begin with 0x
# the only FLAG value in the moment is 0x1 for 'fixed passwords'
# which cannot be changed by user.
# Example:
# 13 MARTIN martin
# 13 DAREK martin
# 13 COMMON common gast 0x1 # no password change by user.
# 13 COMMON common 0x1 # syntax is allowed too.
###############################################################
# Sintaxis modificada por Israel Ortiz Robledo 11/02/99
###############################################################
13 guest cotiza 0x1
# Section 14: currently not used
# =========================================================================
# Section 15: automatic mapping of logins (decision required)
#
# If you have a large number of accounts on your Linux-machine, you may
# want to map all Linux-logins automatically to "mars_nwe"-logins.
#
# At this stage this section is only a quick hack to make life a bit
# easier for the administrator.
#
# WARNING: as there is no algorithm to convert the encrypted
# "Linux-passwords" into the encrypted format used by the DOS-clients (and
# therefore "mars_nwe"), you have to supply a common password for all
# automatically mapped users. This is a big security concern and you
# should never make this common password public (and, of course you
# should choose a sufficient "secure" (read: difficult) password).
# Type the common password to grant access to the users login and the
# command "setpass" instead of telling the password to the user.
#
# Only those Linux-logins will handled automatically that don't have a
# "x" or "*" as their encrypted password.
#
#
# -------------------------------------------------------------------------
# Syntax:
# 15 FLAG DEFAULT_PASSWORD
#
# FLAG:
# 0 DON'T map the Linux-logins automatically to
# "mars_nwe"-logins (default)
# 1 YES, DO the automatic mapping and provide every login
# created this way with the common password given with
# "DEFAULT_PASSWORD"
# 99 re-read the logins from /etc/passwd and overwrite even the
# already existing logins from the bindery (this will also
# reset all the passwords to "DEFAULT_PASSWORD")
#
# DEFAULT_PASSWORD: the common password for all automatically created
# logins (only needed if FLAG is not "0"); everything about
# password in section 12 applies to this.
# -------------------------------------------------------------------------
15 0 top-secret
# =========================================================================
# Section 16: Tests on startup
#
# If you want some sanity checks at startup, set this flag to 1.
# "mars_nwe" will try to create/change missing directories:
# SYS:LOGIN, SYS:MAIL, SYS:MAIL/XXX, SYS:PUBLIC, SYS:SYSTEM ...
# (with the "right" permissions, of course) if you enable this.
# should also be enabled when you use a new mars_nwe version.
# Disabling this test only spares little time when starting mars_nwe.
16 1
# Section 17-20: currently not used
# =========================================================================
# Section 21: print queues (optional)
#
# Which of the printers connected to your Linux-box should be accessible
# from the DOS-clients?
# Multiple entries are allowed.
#
# -------------------------------------------------------------------------
# Syntax:
# 21 QUEUE_NAME [QUEUE_DIR] [PRINT_COMMAND]
#
# QUEUE_NAME: the name of the print queue on client-side (to make it
# perfectly clear: _not_ the Linux-queue)
# QUEUE_DIR: spooling directory for the print-jobs.
# The name is the DOS (not Unix) name of this
# directory.
# It must be placed on the first defined volume.
# (standard name is SYS volume).
# Then it will be created at starttime of mars_nwe.
# It must exist before printing.
# (_not_ the spooling-directories of the Linux-lpd)
# NOTE !
# A '-' sign as QUEUE_DIR has special meaning of
# 'standard' queuedir name. ( SYS:\SYSTEM\queueid.QDR )
#
# PRINT_COMMAND: command used for serving the print-jobs under Linux
# (see "man lpr" and "man magicfilter" for details)
# if the '!' is last parameter of command then
# the queue-packet fields 'banner_user_name'
# and 'banner_file_name' will be added to the
# command as last parameters.
# NOTE !
# If a print command is not specified the job can/must be
# printed by any print server.
# (e.g. pserver (ncpfs utils) or external printserver)
#
# Examples:
# 21 LASER - lpr -Plaser
# 21 OCTOPUSS
# -------------------------------------------------------------------------
# =========================================================================
# Section 22: print server entries (optional)
# adds printserver entries into bindery
# e.g. to enable printing with ncpfs pserver
# -------------------------------------------------------------------------
# Syntax:
# 22 PSERVER_NAME QUEUE_NAME
# Examples:
# 22 PS1 OCTOPUSS
# =========================================================================
# Section 30: Burst mode values (optional)
#
# -------------------------------------------------------------------------
# Syntax:
# 30 MAX_BURST_READ_BUF MAX_BURST_WRITE_BUF
# default is 0x2000 0x2000
# Examples:
# 30 0x2000 0x2000
# =========================================================================
# Section 40ff: Some pathes (optional)
#
# -------------------------------------------------------------------------
# 40 = path for vol/dev/inode->path cache, needed for client-32,namespace
40 /var/spool/nwserv/.volcache
# 41 = path for share/lock files
41 /var/spool/nwserv/.locks
# 42 = path for spool dir, e.g. internal print queue handling
42 /var/spool/nwserv
#
#
# 45 = path for bindery file's
45 /etc
# 46 = path for attribute handling and later trustees
46 /var/lib/nwserv/attrib
# =========================================================================
# Section 50: Conversion tables by Victor Khimenko <[EMAIL PROTECTED]>
# Tables for DOS->Unix names translation & upper/lowercase translations
# For more information see doc/README.NLS
# some examples files exist in the examples directory.
# Conversation file must include 4 tables a 256 byte.
# 0 = dos2unix
# 1 = unix2dos
# 2 = down2up 'dosname'
# 3 = up2down 'dosname'
# -------------------------------------------------------------------------
# Syntax:
# 50 Filename of conversation file.
#
# Examples:
# 50 /etc/nwserv.cnv
# Changing defaults from config.h
# more information in config.h
# 60 10 # MAX_CONNECTIONS
# 61 10 # MAX_NW_VOLS
# 63 50 # MAX_DIR_BASE_ENTRIES
# 68 1 # USE_MMAP (use mmap=1, no mmap=0)
# 69 1 # HANDLE_ALL_SAP_TYPS (all sap typs=1, only typ 4=0)
# 70 0x44444444 # NETWORK_SERIAL_NMBR (4 byte)
# 71 0x2222 # NETWORK_APPL_NMBR (2 byte)
# --------------------------------------------------------
# You usally don't want to change anything below this line
# --------------------------------------------------------
# Sections 80-99: some more constants
# 80 50 # max_dir_search_handles (namspace.c)
# Sections 100-106: amount of debug-information
#
# FLAG:
# 0 no debug messages
# 1 errors and notes are reported
# 99 maximum debug levels
100 0 # debug IPX KERNEL (0 | 1)
101 1 # debug NWSERV
102 0 # debug NCPSERV
103 0 # debug NWCONN
104 0 # debug (start) NWCLIENT, should *always* be '0' !
105 0 # debug NWBIND
106 1 # debug NWROUTED
# Sections 200-202: logging of "nwserv"
#
200 1 # 0 = no logfile and dont daemonize nwserv/nwrouted
# 1 = daemonize nwserv/nwrouted and use logfile
201 /var/log/nw.log # filename of logfile
#201 syslog # if filename == syslog then syslogd will be used for
# all messages
202 0x1 # flag in hex notation
# 0x0=append all messages to logfile.
# & 0x1=creat new logfile instead of appending.
#202 0x3 # & 0x2=use syslogd for error messages instead of logfile.
# Sections 210,211: timing
210 10 # 1 .. 600 (default 10) seconds after server
# really goes down after a down command
211 60 # 10 .. 600 (default 60) broadcasts every x seconds
# Sections 300-302: loging of routing-information
300 1 # > 0 print routing info to file every x broadcasts.
# ( normally minutes )
301 /var/log/nw.routes # filename of logfile
302 0x1 # flags will be interpreted as hex value.
# 0 = append to this file
# & 0x1 = creat new routing info file
# & 0x2 = split info into several files
# (extensions = .1, .2, .3 ... )
# Section 310: watchdogs
310 7 # send wdog's only to device net < x ticks.
# 0 = always send wdogs. < 0 = never send wdogs
# Section 400:
# station file for special handling of stations.
400 /etc/nwserv.stations # for syntax see file in the examples directory.
# Section 401: nearest server
#
# for special handling of the 'get nearest server request'.
401 0 # 0 = ignore entry 400, get nearest response always enabled.
# 1 = 400 are excludes, get nearest response normally enabled.
# 2 = 400 are includes, get nearest response normally disabled.
# Section 402: station connect restrictions
#
# for special handling of the 'creat connection' (attach) call.
402 0 # 0 = ignore entry 400, create connection always enabled.
# 1 = 400 are excludes, create connection normally enabled.
# 2 = 400 are includes, create connection normally disabled.
- --------------E7D8BD564BE975E715C6735C--
------------------------------
End of linux-msdos-digest V1 #147
*********************************
To subscribe to linux-msdos-digest, send the command:
