mabdoor@cs.vu.nl (Doorn van MAB) (04/18/91)
I use OS/2 EE 1.3. I have a serious problem with the OS2.INI file. Somehow the OS2.INI file got corrupted (I installed a 1.2 program ?? ) When I try to boot OS/2 the screen turns gray (as normal), but then the system hangs... (no Desktop Manager, no DOS box icon, no mouse pointer) 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) Now I can work with OS/2 normally, but all my group information, PM colors, window position information has gone... Question: How can I restore the info of the original OS2.INI ? 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 Neither is it possible to boot with the corrupted OS2.INI and fix it, simply because I CAN'T BOOT with the corrupted OS2.INI... It isn't possible to copy OS2INI.OLD to OS2.INI, because OS2.INI "is in use". It isn't possible to use INIEDIT after a boot with the Install diskette, because INIEDIT requires the Presentation Manager !!! :-) HELP !!! You can contact me by e-mail: mabdoor@cs.vu.nl Regards, Matthijs van Doorn ________________________________________________________________________ | " To do is to be - Nietsche | /| /| / \ | To be is to do - Kant | mabdoor@cs.vu.nl / | / | / | | Do be do be do - Sinatra " | VU Amsterdam / | / | / | |________________________________|_____________________/___|/___|/_____/
wbonner@yoda.eecs.wsu.edu (Wim Bonner) (04/20/91)
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
goldman@mbcl.rutgers.edu (04/20/91)
In article <9756@star.cs.vu.nl>, mabdoor@cs.vu.nl (Doorn van MAB) writes: > I use OS/2 EE 1.3. > > I have a serious problem with the OS2.INI file. > > Somehow the OS2.INI file got corrupted (I installed a 1.2 program ?? ) > > When I try to boot OS/2 the screen turns gray (as normal), but then the > system hangs... (no Desktop Manager, no DOS box icon, no mouse pointer) > > 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) > > Now I can work with OS/2 normally, but all my group information, PM colors, > window position information has gone... > > Question: How can I restore the info of the original OS2.INI ? > > 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 > > Neither is it possible to boot with the corrupted OS2.INI and fix it, simply > because I CAN'T BOOT with the corrupted OS2.INI... > > It isn't possible to copy OS2INI.OLD to OS2.INI, because OS2.INI "is in use". > > It isn't possible to use INIEDIT after a boot with the Install diskette, > because INIEDIT requires the Presentation Manager !!! :-) For what it's worth, the OS2 ini editor I use is JPOS2INI.EXE, written by a guy at IBM. It looks quite nice, but I tried & wasn't able to get it to load a different ini file. However, I did come across a program (NEWINI.ZIP) is the name of the zip file that claims to allow you to switch .INI files while you're running. YOu could try this. I put it in the anonymous ftp directory on this machine; anon ftp to this node & cd to os2. There's a 0index file to get you started. It might help... > > > HELP !!! > > You can contact me by e-mail: mabdoor@cs.vu.nl > > Regards, > > Matthijs van Doorn > > ________________________________________________________________________ > | " To do is to be - Nietsche | /| /| / \ > | To be is to do - Kant | mabdoor@cs.vu.nl / | / | / | > | Do be do be do - Sinatra " | VU Amsterdam / | / | / | > |________________________________|_____________________/___|/___|/_____/ -- Adrian Goldman | Internet: Goldman@MBCL.Rutgers.Edu Molecular Biology Computing Laboratory | Bitnet: Goldman@BioVAX Waksman Insitute, | Phone: (908) 932-4864 Rutgers University, | Fax: (908) 932-5735 Piscataway, NJ 08855 USA |
cur022%cluster@ukc.ac.uk (Bob Eager) (04/21/91)
In article <9756@star.cs.vu.nl>, mabdoor@cs.vu.nl (Doorn van MAB) writes: > Somehow the OS2.INI file got corrupted (I installed a 1.2 program ?? ) > > Neither is it possible to boot with the corrupted OS2.INI and fix it, simply > because I CAN'T BOOT with the corrupted OS2.INI... > > It isn't possible to copy OS2INI.OLD to OS2.INI, because OS2.INI "is in use". > Boot with the installation diskette and hit ESC at the logo screen. Copy the current OS2.INI to, say, XOS2.INI. Boot OS/2 proper. Edit CONFIG.SYS and change the OS2.INI bit of the PROTSHELL= line to XOS2.INI. Reboot and you'll be using that one. Then use INIEDIT. Reverse the procedure (if you wish) when you've finished. The INI filenames aren't cast in stone. -------------------------+------------------------------------------------- Bob Eager | University of Kent at Canterbury | +44 227 764000 ext 7589 -------------------------+-------------------------------------------------
gah@hood.hood.caltech.edu (Glen Herrmannsfeldt) (04/23/91)
I don't know about INIEDIT, but OS2.INI is not the only name this file can have. You can copy it, change the PROTSHELL= ... line to use the copy, and then do anything you want with the other one. I have OS2X.INI, as a result of a similar process.