Name: John Gitzen Date: May 8, 2007 at 15:34:39 Pacific Subject: How to fix corrupted OS/2 ver 3 OS: OS/2 3, XP Pro SP2, CPU/Ram: 266 Mhz Pentium Pro/512MB Model/Manufacturer: IBM/PC Server 330
Comment:
We have two IBM PC 330 machines running OS/2 version 3 to support the IBM PC390 software which emulates a Mainframe on the PC330 system. The OS/2 installation of one of the machines became corrupted, it looks due to hardware error on the C: drive. The drive is up and working but I can't get my OS/2 Opsys to run. I tried comparing files in the root and OS2 directories between the two machines and then copied several of the files which showed a size of 0 on the non-working machine, but I still get a failure. Can I reinstall OS/2 from the CD's without loosing any configuration changes made to support the PC390 configuration, etc. I know with products I have installed in the past, they detect the existance of the previous version and only copy and or replace those files which are necessary to fix the OP Sys. Anybody know what to do in this case?
Can't get my Backupwiz to work either, although it appears it's backup may be too old to trust anyways.
Suggestions?
Be advised I am a total novice to OS/2
Thanks,
John Gitzen II "The opinion posted here is solely my position and does not represent the opinion of DTE Energy".
hi john, i don't know if is secure. make a backup for both system. restore the working system to corrupted system. if backup function well, only files corrupted will be changed.
Hi John, I've your same problem with one server 330 with a p390 mainframe card. The server doen't start giving a os2 error. I wanted to know how you solved the problem ? Thanks Marco
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE