Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!ns.uoregon.edu!milton!serval!yoda.eecs.wsu.edu!wbonner
From: wbonner@yoda.eecs.wsu.edu (Wim Bonner)
Newsgroups: comp.os.os2.misc
Subject: Re: corrupted OS2.INI
Message-ID: <1991Apr19.173253.23930@serval.net.wsu.edu>
Date: 19 Apr 91 17:32:53 GMT
References: <9756@star.cs.vu.nl>
Sender: news@serval.net.wsu.edu (USENET News System)
Organization: Washington State University
Lines: 29

In article <9756@star.cs.vu.nl> mabdoor@cs.vu.nl (Doorn van MAB) writes:
>I solved this by renaming the OS2.INI file, and created a new OS2.INI
>with MAKEINI OS2.INI INI.RC (I booted with the Install-diskette)
>
>Note: I can't use INIEDIT, because this program can only edit OS2.INI, and
>not a copy of it (e.g. OS2INI.OLD). So I can't boot with the clean OS2.INI
>and then fix the old OS2.INI

I recent;y found an ini editor that I downloaded from a listserve somewhere
which will open any INI file, I suppose it was written for 1.2 or above, 
where this was possible.   Anyway, As soon as I can find the name 
of the file...  

Ok, the file name is INIUTIL1.ZIP.

I believe it is available from the listserv@blekul11  (Or whatever the spelling
is correctly)  

The interface to this program is not as nice as that of some of the other INI
editors out there, but It seemed to be able to deal with multiple INI Files.

That listserv is a mail file server, so if you don't know how to use it, 
respond, and I'll give instructions for getting the file.

Wim.
-- 
|  wbonner@yoda.eecs.wsu.edu  | The Loft BBS
| 27313853@wsuvm1.csc.wsu.edu | (509)335-4339
|  72561.3135@CompuServe.com  | USR HST Dual Standard HST/V.32