HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Books
From: "Lloyd M. Ballinger, Manager of Networks & Comm."<LMBALLINGER@GALLUA.BITNET>
Date: 21 Dec 1992 22:19:31 -0500
X-VMS-Cc: LMBALLINGER
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=ISO-8859-1
Content-transfer-encoding: 8BIT

Date sent:  21-DEC-1992 22:15:00
 
I bought a book in Las Vegas during DECUS sympsoium and called
"The Complete Guide to PathWORKS" was written by Kenneth L. Spencer
ISBN 1-878956-22-b CBM Books 101 Wiitmer Road,
Horsham, Pa 19044 ($31.95) Includes 3 1/2" diskette.
 
Lloyd
 
>From:  IN%"LANWORKS@MIAMIU.BITNET"  "A discussion of Digital's PCSA product" 17
   -DEC-1992 15:39:45.83
>To:    IN%"LMBALLIN@gallua.bitnet"  "LLOYD M.BALLINGER", IN%"PKUN@gallua.bitnet
   "  "'Peter K. Un'"
>CC:
>Subj:  Books
>
>Return-path: <LANWORKS@MIAMIU.BITNET>
>Received: from Jnet-DAEMON by gallua.bitnet (PMDF #2663 ) id
> <01GSFEDHXPDS8ZEE26@gallua.bitnet>; Thu, 17 Dec 1992 15:39:15 EST
>Received: From GWUVM(MAILER) by GALLUA with Jnet id 1811 for
> LMBALLINGER@GALLUA; Thu, 17 Dec 92 15:39 EST
>Received: from GWUVM.BITNET by GWUVM.GWU.EDU (Mailer R2.08) with BSMTP id 9087;
> Thu, 17 Dec 92 15:37:08 EDT
>Date: 17 Dec 1992 13:35:09 -0700
>From: George Yobst <george@RANKIN.LIB.UMT.EDU>
>Subject: Books
>Sender: A discussion of Digital's PCSA product <LANWORKS@MIAMIU.BITNET>
>To: "LLOYD M.BALLINGER" <LMBALLIN@gallua.bitnet>,
> "'Peter K. Un'" <PKUN@gallua.bitnet>
>Reply-to: A discussion of Digital's PCSA product <LANWORKS@MIAMIU.BITNET>
>Message-id: <01GSFEGL4EM28ZEE26@gallua.bitnet>
>Content-transfer-encoding: 7BIT
>X-To:         lanworks@miamiu.acs.muohio.edu
>
>Hi all,
>
>Can someone give me the names & authors of some books written about
>Pathworks for DOS V4.1.   Thank you! - George
>=============================================================================
>George Yobst, Automation Specialist              Internet:
>Mansfield Library                                  GEORGE@RANKIN.LIB.UMT.EDU
>University of Montana    Phone: (406) 243-2539   MUSENET:
>Missoula, MT 59812-1195  FAX:   (406) 243-2060     RANKIN::GEORGE
>'If you want to make enemies, try to change something.' - Woodrow Wilson
*----------------------------------------------------------------------------*
|                G a l l a u d e t   U n i v e r s i t y                     |
|----------------------------------------------------------------------------|
|    Lloyd M. Ballinger, Manager   * InterNet: lloyd@gallux.gallaudet.edu    |
|    Gallaudet University          * BitNet: lmballinger@gallua              |
|    Computer Services             * Phone: 202/651-5048 (TDD)               |
|    Networks/Communications       *        202/651-5300 (Voice)             |
|    800 NE Florida Ave.           *        202/651-5477 (FAX)               |
|    Washington, DC 20002          *                                         |
*----------------------------------------------------------------------------*
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Want to get 437usa directory out of the path
From: SYSMGR@IPG.PH.KCL.AC.UK
Date: 22 Dec 1992 13:55:07 -0300 (BST)
Content-transfer-encoding: 7BIT
Via: uk.ac.kcl.ph.ipg; Tue, 22 Dec 1992 13:56:17 +0000
Originally-to: CBS%UK.AC.NSFNET-RELAY::EDU.MUOHIO.ACS.MIAMIU::LANWORKS
Originally-from: SYSMGR "Nigel"
Mailer: Janet_Mailshr V3.4 (23-May-1989)

>> Does anyone want to share any bright ideas about how to deal with path
>> length problems?
 
Hopefully constructive mild flame follows.
 
Yes, apply enough pressure on your software suppliers  to get them to write
their software sensibly. At present, just about all of them assume that
the path is theirs and theirs alone to do with whatever they like.
 
Suggested 'standard'. The executable(s) in the package can be run from
any directory, renamed to any filename you chose. Coded internally is
the name of an environment variable xxx_ppppp where xxx is an abbreviation
of the supplier's name (DEC, MS, BOR, etc.) and ppppp is the product name
(PWORKS, WORD, QUATTRO, ...)
 
This environment variable is defined as the path appropriate to that
product. For example, DEC_PATHWORKS would be defined as the three directories
that Pathworks looks in.
 
All filename searches done by the product will use the translation of its own
environment variable to locate files belonging to itself. PATH is reserved
for locating files being created or modified by the PC's USER, such as
word documents or spreadsheets. Use of PATH for any other purpose causes
the supplier to be scorned, derided and generally pilloried until he makes
his product conform to the above simple 'standard'. By all means search PATH
before the private list, but only if there's a sensible reason why the user
may have chosen to make a private file to override the supplied one.
 
As well as bypassing the PATH length problem, this would make installing
N (>26) products on a network one heck of a lot easier. Put each product
in its own disk service. To access it, connect the disk service on any
free drive X: and then do a local-standard invocation like X:SETUP X:
where SETUP.BAT defines the environment variable(s) used by the product on
X:, plus educate your users to invoke X:PRODUCT rather than just PRODUCT
when running a networked application. A little local coding with QBASIC
could make this easier still for the users ("Welcome: which products do
you want to use" plus a menu :-)
 
While I'm at it, any manufacturer who doesn't segregate files created/altered
by users from the files which should be READ-ONLY to the user deserves
to be shot.
 
        Enough flaming. Merry Xmas,
 
                Nigel Arnot
 
                NRA%ipg.ph.kcl.ac.uk@nsfnet-relay.ac.uk   (internet)
                NRA%uk.ac.kcl.ph.ipg@ukacrl.bitnet        (bitnet)
 
 
PS Anyone know whether Windows NT has re-invented the logical name, as well
   as the QIO and the IRP :-)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: kermit program
From: "JEFFERY CHEW NSEP-CIM, TEL:604-837211 EX 268, FAX604-833894"<vccmep%epmv50.dnet@GPO.NSC.COM>
Date: 23 Dec 1992 23:13:25 -0800
Content-transfer-encoding: 7BIT

This may not be a list for such question but I am not sure of any other
list that talks about KERMIT.  If you do know, please let me know.
 
In the mean while, I do hope someone out there can help me with this.
 
I try running MS Kermit 3.11 on  MS DOS machine using TCP/IP protocol on a
SMC ethernet card.  It will run fine if I use the WD8003E.COM in autoexec
but when I use WD8003E.SYS in the config.sys file, it does not work.  I
need to have the driver loaded in config.sys file in order for my PC-NFS to
work.  Does anyone know of a way round this problem?
 
The second problem is trying to upload MS-DOS exe files from VAX to MSDOS
machine using kermit file transfer.  I try to set both kermits to binary
but after the file has been transfered, it does not run.  Any solution to
this?
 
p/s : Is there a list for PC-NFS?
 
You can e-mail me direct so as not to choke up this list.
 
Merry Christmas & Happy New Year
 
Rgs,
 
Jeffery Chew
vccmep%epmv50.dnet@gpo.nsc.com
From: dunnett@mala.bc.ca (Malcolm Dunnett)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: LAT Parallel Print Servers
Date: 19 Dec 92 09:41:35 -0700
Organization: Malaspina College


  Another possibility if you have Pathworks ( which I assume most
folks reading this group do ) :

  Take your favourite noname 386SX clone ( stripped down versions can be
had for $300-400 ), buy a Pathworks client license for it ($200 or so ), an
Ethernet Card ($150-200) and a couple of parallel ports. 

  Make up a boot disk which installs LAT and serves the local printer
ports(s) over LAT. There's no need to set the box up as a full client
or connect to a file service - all we're interested in is LAT. You will
need to assign it a DECNet node number, but as you won't actually be
using DECNet the number can be any arbitrary one, even if it's not in
your regular areas.

  The instructions for all of this are in the Pathworks documentation,
you may need to do a bit of tweaking to get reasonable performance out
of it.

  You now have a 1 or 2 port LAT only parallel print server for a cost of
around $800.

Note: the only reason I say you need to already have Pathworks is that
you need the DOS client kit, and buying one just to build a print server
doesn't seem reasonable. You don't need to have Pathworks installed on
the VAXen which will print to this server, it's all done via LAT. YOU
DO NEED A CLIENT LICENSE FOR THE PRINT SERVER.

-- 
========================================================================
Malcolm Dunnett    Malaspina College         Email: dunnett@mala.bc.ca
Computer Services  Nanaimo, B.C. CANADA        Tel: (604)755-8738
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: LANSESS, NET USE, MS WINDOWS
From: "John M. George" <GEORGEJM%AM.A7141.mrouter@VIKING.NAVAIR.NAVY.MIL>
Date: 18 Dec 1992 09:55:20 -0500 (EST)
Content-transfer-encoding: 7BIT

Does anyone know if Digital is planning to fix the problem
with running a NET USE command in a DOS SHELL under
windows while LANSESS is running?  Most of my users use
LANSESS because it significantly speeds up I/O to file
services.  DECNet is GREAT in a wide area environment, but
why should I be forced to use it when my file server is
down the hall from my workstation?
 
 
Thanks in advance,
 
John George
Information Systems Division
Naval Air Systems Command HQ
Washington DC
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: White paper on Windows for Workgroups & Pathworks
From: Gregg Pentecost X6228 IC44 <PENTECOST@BROOK.BITNET>
Date: 18 Dec 1992 09:46:23 -0400
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

>      Here is the document - just like you asked.  I hope that
>      it's not too long to post here!  I tried these steps and
>      Windows for Workgroups worked like a charm!  Amazing, isn't
>      it?
 
Jenett,
 
The message I received wasn't too long, in fact it was only ten lines :-)
 
If I'm the only one who had a problem receiving it, I'd appreciate it if
you sent me a copy at PENTECOST@BROOK.BITNET.
 
Thanks a lot.  Gregg.
From: SASIADJW%WPO1P%WPO2V@SNYCENVA.BITNET (Joe Sasiadek)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Set Server Time
Date: 30 Dec 92 14:40:00 GMT
Content-transfer-encoding: 7BIT

We use our Pathworks Server to set time for our PC Pathworks
clients and I find that we're often 3 or 4 minutes off
frequently.

I have NIST (National Institute of Standards and Technology) Time
setting DOS software and Windows Software that I use to set the
time accurately on indiviual PCs (call costs about 34 cents from
Albany) but...

Does anyone know of VMS Software like NIST Time software, that
will dial up (or even Telnet) to NIST and set the VMS Pathworks
Server time correctly (so that it, in turn, will sett our PC
client's time correctly)?

.-------------------.--------------------------.
| Joe Sasiadek      | SASIADJW@SNYCENVA.BITNET |
| SUNY Central OIT  | State Univ of New York   |
| (518) 443-5548    | FAX (518) 443-5799       |
`-------------------'--------------------------'
Newsgroups: vmsnet.networks.desktop.pathworks
From: ccksb@trentu.ca (Ken Brown)
Subject: Re: White paper on Windows for Workgroups & Pathworks
Organization: Trent University, Ontario
Date: Tue, 22 Dec 1992 17:03:14 GMT

I would like a copy also.


-- 
Ken Brown                                   internet: kbrown@trentu.ca
Trent University Computing & Telecommunications  tel: (705)748-1540
Peterborough, Ontario, Canada, K9J 7B8           fax: (705)748-1246
Organization: Rohm and Haas Company
Date: Tue, 22 Dec 1992 08:53:01 EST
From: Aengus Lawlor <RBYAML@rohvm1.rohmhaas.com>
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: LAT Parallel Print Servers

In article <01GSL0E92C0W8ZEEL4@CBE.AB.CA>, "Glen Larwill, Computing Services,
(403)294-8380" <NETMGR02@CBE.AB.CA> says:
>
>>>I'm looking for a 2 port inexpensive parallel print server.
>>>
>>>I see the DECserver 250 in DECdirect... but this is a little two expensive  r
>fo
>>>our tastes.... and over kill for our application.....
>>>
>>>Thanks in advance.... any and all will be appreciated....
>>>
>>>Mark Montanez
>>>
>>It seems so obvious, doesn't it? All these ethernet ports for printers that
>>have to support various versions of IPX, and remote printer stuff, and queue
>>management, yet nobody seems to sell a simple LAT terminal server with a
>>single parallel port for output. They've been making big one with lots of
>>serial ports for years, so a little one with one or two parallel ports
>doesn't
>>sound like too much to ask for, does it.......
>
>Terminal servers that contain parallel ports DO exist.  The DECServer 250
>has 2 parallel ports and 4 asynch ports.  I have never used one, but I
>don't imagine that they work much differently from the simple asynch
>terminal servers.
Look at the original message! The 250 is a terminal server, and priced as
such. The market is for a HP compatible expansion card that can be a LAT
device. I could set up a queue on the VAX, and plug my printer anywhere
on the network, and it would work without any need for external power
supplies, or printer cables, or 1000 block files at 9600 baud! You can
already do it with TCP/IP, and Novell workstations are doing it with IPX.
But DEC, who've been using distributed printing for years, getting the
data to the terminal server at ethernet speeds, are still pushing the
data through a 9600 baud bottleneck to the printer.

If PathWorks 5.0 lets Novell workstations print to VMS queues, then you'll
get a very clear choice. Easy distributed print queue setup and management,
with 9600 baud bottlenecks, or Novells distributed/remote printing, with
it's potential headaches, but ethernet speeds to the printer. You pays
you money, and you takes your choice....

>     Glen Larwill, Network Technician,
>     Calgary Board of Education
>     Internet:   netmgr02@cbe.ab.ca
Aengus
--
RBYAML@ROHMHAAS.COM                    Aengus Lawlor
RBYAML@ROHVM1.BITNET                   (who used to be ALAWLOR@DIT.IE)
"How about some of that famous Dublin wit, Barman?"
"Certainly, sir. Would that be Dry or Sparkling?"
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: Books
From: "Prof. David Miller" <DMILLER%BSU.DECNET@MSUS1.BITNET>
Date: 22 Dec 1992 09:41:00 -0600 (CST)
Content-transfer-encoding: 8BIT

LLOYD M.BALLINGER ("LMBALLIN@gallua.bitnet") writes
 
> I bought a book in Las Vegas during DECUS sympsoium and called
> "The Complete Guide to PathWORKS" was written by Kenneth L. Spencer
> ISBN 1-878956-22-b CBM Books 101 Wiitmer Road,
> Horsham, Pa 19044 ($31.95) Includes 3 1/2" diskette.
 
I realize that the amount of readables is overwhelming, but I would be very
interested in your opinion of the book. Is it new material? Is it a
condensation of the DEC documentation? Is it well organized? Does it talk
about both the client and the server? Is it work $40? (the phone order price)
 
Dave.
 
DMILLER@VAX1.Bemidji.MSUS.EDU
Bemidji (Minn) State University
Newsgroups: vmsnet.networks.desktop.pathworks
From: karcher@jevex.waisman.wisc.edu
Subject: RE: LANSESS, NET USE, MS WINDOWS
Organization: Waisman Center, University of Wisconsin-Madison
Date: 23 DEC 92 18:01:35 CST

In a previous article, houseman@Turing.ORG (Carl Houseman) wrote:

>Get the Pathworks/DOS client patch kit from DEC Customer support.
>It fixes a great number of problems, including this one.

The patch is known as CSCPAT #3046 V1.3 and includes a new PCSA.DRV, DECNET.386
and DECNB.386.


Carl Karcher                          Internet: KARCHER@WAISMAN.WISC.EDU
Waisman Center                        Bitnet:   KARCHER@WISCMACC
University of Wisconsin-Madison       PSTnet:   (608) 263-5896
From: brian_u@verifone.com
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: kermit program
Date: 2 Jan 93 01:23:58 -1000
Organization: VeriFone Inc., Honolulu HI

In article <garber.19.0@aru.dom.uab.edu>, garber@aru.dom.uab.edu (David W. Garber) writes:
> In article <9212240713.AA09016@gpo.nsc.com> "JEFFERY CHEW NSEP-CIM, 
> TEL:604-837211 EX 268, FAX604-833894"<vccmep%epmv50.dnet@GPO.NSC.COM> writes:
>>Subject: kermit program
>> 
>>The second problem is trying to upload MS-DOS exe files from VAX to MSDOS
>>machine using kermit file transfer.  I try to set both kermits to binary
>>but after the file has been transfered, it does not run.  Any solution to
>>this?
>> 
> Please post replies or carbon them to me.  I have the same problem.  I've 
> "solved" it by uu-encoding and decoding, and sending ascii files, but this 
> obviously dramatically increases transmission file sizes, which I want to 
> avoid.  Thanks.
> David W. Garber (garber@aru.dom.uab.edu)

If the VMS file has file/record org stream_lf, Kermit may not handle binary 
down load correctly.  Try changing the file/record org to fixed length 
record, 512 bytes then Kermit down loading.

-- 
Brian K. Uechi     | brian_u@verifone.com   (Internet)
VeriFone Inc.      | uunet!verifone!brian_u (UUCP)
100 Kahelu Ave.    | 808-623-2911           (Voice)
Mililani, HI 96789 | 808-625-3201           (FAX)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: How to use a non-DEC postscript printer???
From: Eschew Obfuscation <brydon@DSN.SINET.SLB.COM>
Date: 31 Dec 1992 11:08:21 +0000 (GMT)
X-VMS-Cc: BRYDON
Content-transfer-encoding: 7BIT
X-Vms-From: PSI%DSN::BRYDON       "Eschew Obfuscation"

Lars Seibert (...!drilex!wrglex!katec!l_seibert) asks:

>I have a problem to use a postscript printer as a postscript printer under VMS.
>The printer is a Brother HL-10PS, it is connected serial with the DECserver200
>and everything is working fine as long as I use it as a text printer, but as
>soon as I send a postscript file or I connect it to a queue created with DEC's
>CPS-software, it doesn't print anything. If it is connected to a text queue,
>the printer tells me IGNORE DATA. If it is connected to a CPS queue, it takes
>sometime and then the queue is stalled.

CPS software supports only LN03R, LN05, LN06, LN07, LN08, Oce and [NEC/DEC]
Colormate PS [actually a NEC Colormate PS-80] printers.  All others are
unsupported.  Not only that, but it appears that DEC has gone out of their way
to make other printers NOT work with it.  Various people including myself have
made changes to the CPS setup modules to get something to print on various
printer types.  Significant changes are required for each printer type, but
the use of 'real' Adobe Postscript makes the job easier.  I'm pretty sure that
your Brother printer uses somebody else's postscript.  We briefly made a
cursory effort to get a Brother HT-500PS printer going, but were unsuccessful.
I have personally spent several man-months on this problem.  If you manage to
get the Brother going, I'd be very interested in seeing what your setup
modules look like.
_______________________________________________________________
Harvey Brydon         | Internet:   brydon@dsn.SINet.slb.com
Dowell Schlumberger   | P.O.T.S.:   (918)250-4312
Software is like sex.  Software for free costs much more than software for
money.
Newsgroups: vmsnet.networks.desktop.pathworks
From: mcrowley@MtHolyoke.edu (Michael A. Crowley)
Subject: Re: LAT Parallel Print Servers
Organization: Mount Holyoke College
X-Newsreader: Tin 1.1 PL5
Date: Fri, 25 Dec 1992 23:36:24 GMT

Malcolm Dunnett (dunnett@mala.bc.ca) wrote:
> 
>   Another possibility if you have Pathworks ( which I assume most
> folks reading this group do ) :
> 
>   Take your favourite noname 386SX clone ( stripped down versions can be
> had for $300-400 ), buy a Pathworks client license for it ($200 or so ), an
> Ethernet Card ($150-200) and a couple of parallel ports. 
> 

We did this with a couple of our old, mothballed 256K dual floppy PCs with
monochrome display and printer adapter cards and a second parallel card.  
A bit bulky, but works fine.
	.mac.
From: dunnett@mala.bc.ca (Malcolm Dunnett)
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: LAT Parallel Print Servers
Date: 19 Dec 92 09:24:10 -0700
Organization: Malaspina College

In article <92353.133348RBYAML@rohvm1.rohmhaas.com>,
    Aengus Lawlor <RBYAML@rohvm1.rohmhaas.com> writes:

> It seems so obvious, doesn't it? All these ethernet ports for printers that
> have to support various versions of IPX, and remote printer stuff, and queue
> management, yet nobody seems to sell a simple LAT terminal server with a
> single parallel port for output. They've been making big one with lots of
> serial ports for years, so a little one with one or two parallel ports doesn't
> sound like too much to ask for, does it.......
> 

  There's the P2501 from Emulex ( 1 Parallel )
  The EPS-1 from Lantronix ( 1 Parallel and 1 Serial )
  The Xconnect(?) from XCD ( 1 Parallel )

  All of the above do LAT and TCP/IP - some also do IPX and Appletalk.

  Disclaimer: all of the above is quoted from memory, contact the vendors
for accurate information.

> (So if anyone has an answer to Marks question, post it here for the rest of
> us too!)
> 
   I don't believe any of the above have 2 parallel ports ( which the
original poster asked about ), but they're cheap enough that buying
two of them might be a viable solution. Some have 1 parallel and 1 serial,
which can be used simultaneously, so this might be an adequate solution.

-- 
========================================================================
Malcolm Dunnett    Malaspina College         Email: dunnett@mala.bc.ca
Computer Services  Nanaimo, B.C. CANADA        Tel: (604)755-8738
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: SUMMARY: LANSESS & WINDOWS 3.1 & DOS 5.0
From: EGGER <egger@MPI-FG-KOELN.MPG.DBP.DE>
Date: 22 Dec 1992 07:22:34 -0500
Content-transfer-encoding: 7BIT
P1-message-id: de*dbp*mpg;921222130115
Priority: normal
X400-Trace: de*dbp*mpg; arrival Tue, 22 Dec 92 13:01+0100 action Relayed
X400-Trace: de*dbp*GMD; arrival Tue, 22 Dec 92 13:02+0100 action Relayed

Hello,
here is the promised summary of the answers to my question about how to
load lansess into EMS and still be able to use the 'EXIT TO DOS'- function
from within windows.
A few people mentioned not to use EMS at all to load PCSA components, but
we use it now for a few years and it works fine. On the other hand the
benefit you achieve in conventional memory is enormous and in some cases
you can't even run programs without that amount of memory.
Someone else gave the advice not to load lansess into EMS. That didn't fix
the problem. The PC still started to hang after you tried to return to
WIndows. In some cases i couldn't even use the USE- command.
P. Grieggs' wrote that one have to insert the
following statements in the [386ENH] section of the SYSTEM.INI.
 
        NETNoBlock=FALSE
        DNETHeapSize=64
 
So i tried this and it solved the problem. When I tried to find these
parameters in the Windows Resource Kit i failed. So i called Microsoft at
Munich, but they didn't even heard of those parameters and told me to call
DEC.
They explained why that fixes the problem, which wasn't unknown to them.
The NETNoBlock tells windows to ignore all changes to the environment of
that child-process that were made by such network task.
The function of DNETHeapSize was unknown to them, but they told me, that
there was a fix available. It consist of two files, DECNB.386 and
DECNET.386. This realy seems to solve the problem. None of the above
described entries in SYSTEM.INI is necessary.
At last i want to thank everyone who helped. Mery Christmas and a happy
new year.