OS2World OLD-STATIC-BACKUP Forum
OS/2 - Technical => Hardware => Topic started by: ofey on 2009.11.26, 06:45:16
-
Hello world,
I've inherited an ancient X-Ray Photoelectron Spectrometer which uses a DELL PC running OS/2 Warp as a controller. I used to have problems booting the operating system but once I sorted the hardware and replaced the CMOS battery I had a while where I was running OS/2 day in day out. However in recent days, the OS refuses to start.
I get through the bios screens no problem and the OS/2 Warp Ver 3.0 splash screen comes up before the whole system stops at a blinking white cursor in position 1,1 in the top left corner of the screen. I am using a basic 1280X800 LCD monitor in tandem with the Dell system.
I'm not au fait with OS/2 and would appreciate any help anyone can provide... .
-
Hi ofey,
Assuming nothing has changed on the machine, I would check for a failing hard drive or a changed CMOS setting pertinent to the hard drive.
You can check virtually any IDE hard drive, and most SCSI drives on non-RAID controllers using IBM/Hitachi Drive Fitness Test. Do an "Advanced Test" - it will not overwrite any data.
You can alternatively try hitting "Alt-F1" when the OS/2 boot blob appears on the screen (before the logo screen) and selecting "F2" from the list of options presented to see if it boots to command prompt.
Let us know what you find.
Best,
Robert
-
Thanks for the quick reply Rob. Correction it's OS/2 Ver 3.
Nothing has changed in the machine. It was just left disconnected and off for a long time.
I did the Alt-F1 keystroke and it went to "Recovery Choices Screen"
The choices there were:
Esc -> Continue boot
Result was the same blinking cursor >:(
C -> Command Line
Took me to a command line prompt could do DIR and all! ::)
V-> Video reset
Did this and the OS/2 screen came up, displayed the start up of my software interface to my spectrometer then it goes back to the blinking cursor again! >:(
M-> Restart system to Maintainence Desktop.
Didn't dare try this
X-> will replace config.sys with some back up.
Didn't dare do this :-\
After I had replaced the CMOS clock battery in the past, I left this computer running for a week without any problems! It's never left the room and it's sealed air conditioned room.
So if its a case of HDD crash, surely, the OS/2 Warp start screen shouldn't have come up at all!?
-
Can you do a chkdsk on the C: drive?
AFAIK, Maintenance desktop is non-destructive. Think of it as Safe Mode. You have a minimal GUI boot that allows you to do some work you may need to do to fix up the system or back up your data.
-
Can you do a chkdsk on the C: drive?
AFAIK, Maintenance desktop is non-destructive. Think of it as Safe Mode. You have a minimal GUI boot that allows you to do some work you may need to do to fix up the system or back up your data.
No, do NOT go to Maintenance Desktop!
It will revert your desktop to the default one and you will lose settings and such.
-
.. I thought that after you reboot it will return you to your full desktop?
-
@Sajin_Naib: Beat me to it. :P
I did run a chkdsk *memories of an old school DOS user came flooding back*
Besides the blurb of
... current HDD is C:
... File System is HPFS
SYS0552 : System found FS errors on the disk
CHKDSK removed the corrupted file \OS2\OS2SYS.INI
CHKDSK corrected a disk space allocation error
CHKDSK removed the corrupted file \VGS7000\SYS\INSTLOG.DAT
SYS0562: System detected lost data
...
blurb of all HDD stats
No cigar, I chanced a reboot. Still have a blinking cursor... .
-
That is very, very not good.
The Os2.ini holds all the configuration info and what not. If I recall, there is a way to make a new default one but I haven't the foggiest how to do it.
Try rebooting... See if it will boot. If not, try to restore an earlier backup. If that doesn't work, I'd suggest Maintenance desktop.
But, listen to Rob over me, he knows more.
-
Nope rebooted into a blinking cursor... . So still jammed... .
No backup obviously
Options?
1. Maintenance Desktop *chance it?*
2. Making a new OS2.ini !?
-
Hmmm... in this case, use IBM/Hitachi Drive Fitness Test to scan the drive for problems. It is likely the following that caused it:
(1) Serious crash while updating the INI files.
(2) The hard drive is failing (most likely media errors)
Use the method I outlined below to boot to the command prompt. You can recreate the INI files in the following manner once you do that:
CD OS2 (ENTER)
MAKEINI os2.ini ini.rc (ENTER)
MAKEINI os2sys.ini inisys.rc (ENTER)
Reboot
-
Well, I think any damage the Maintenance Desktop could have caused is overshadowed by the fact that you no longer have an OS2.ini.
I'd say try it.
Or do Rob's thing. Either way, you've lost your config data. However, provided the harddrive is not on the way out, your program data should still be intact. You'll just lack shortcuts, etc to them.
-
But, listen to Rob over me, he knows more.
No, I just fake it better. ;D
-
Well, I think any damage the Maintenance Desktop could have caused is overshadowed by the fact that you no longer have an OS2.ini.
I'd say try it.
Or do Rob's thing. Either way, you've lost your config data. However, provided the harddrive is not on the way out, your program data should still be intact. You'll just lack shortcuts, etc to them.
Saijin is correct. Booting to the Maintenance Desktop will not hurt and may also resolve the issue. But definitely scan the drive for errors/problems.
-
Hmmm... in this case, use IBM/Hitachi Drive Fitness Test to scan the drive for problems. It is likely the following that caused it:
Sorry but what is this IBM/Hitachi Drive Fitness Test? Never heard of it... .
Is it on the drive?
-
Boot floppy of the utility.
http://www.hitachigst.com/hdd/support/downloads/dft32_v416_b00_install.IMG
ReadMe of how to make it (under linux)
http://www.hitachigst.com/hdd/support/dft-linux-readme.htm
If you are more comfortable using Windows, you can write the image with RawWrite
http://www.chrysocome.net/rawwrite
For OS/2, I'm not sure what util you need to write .IMG to a floppy.
This program MAY work, but you need a working OS/2 GUI environment:
http://www.ecomstation.it/ecsoft2/prog.php?progid=1481&name=EMT4PM&sys=os2+ecomstation
-
Boot floppy of the utility.
http://www.hitachigst.com/hdd/support/downloads/dft32_v416_b00_install.IMG
Thanks for that. Now all I have to do is to find a floppy...and how to get it to the floppy from my Macbook... . *grrrr*
-
Boot floppy of the utility.
http://www.hitachigst.com/hdd/support/downloads/dft32_v416_b00_install.IMG
Thanks for that. Now all I have to do is to find a floppy... .
There is a CD Image you can use as well...
http://www.hitachigst.com/hdd/support/downloads/ftool_215.iso
Can be burned with Nero Burning ROM or ImgBurn.
-Rob
-
This might take awhile... . Hope you guys check back when I next post!
You've been MOST helpful so far. I'd be lost without you boys... . ???
-
Hate to bail, but its bed-time for me.
Good luck. I'm sure you'll get it booting. Do you need this system for work/research? Can it wait a bit before you get it back online?
-
I'll be around for a bit still... and I will undoubtedly be online most of tomorrow afternoon to late night.
Best,
Robert
-
Hey world,
whatever happened to pg 1? ??? Whenever I click on pg 1, I get a blank page.
Anyways, as an update, I managed to get a floppy and a PC to write the boot disk. The disk check program failed. So I still went back and booted through Alt-F1 to the command prompt and issued the makeini commands as per RobertM's instructions.
CD OS2 (ENTER)
MAKEINI os2.ini ini.rc (ENTER)
MAKEINI os2sys.ini inisys.rc (ENTER)
The first was successful but the 2nd didn't complete and hung the computer. I used ctl-alt-del to reset and got back in and OS/2 booted up normally but obviously all my desktop settings are gone. Programs are still in their folders but i haven't tried running anything for fear something else might kick in.
Are there any more things I can do at this stage? I'm afraid to power down the system. Can I? will it re-start to this GUI again?
I'd also like to append the config.sys and autoexec.bat to optimize them abit more. any advice here?
-
I'd say that if it has booted once, you should be fairly safe.
However, now would be a great time to FTP or copy the programs off interest off the (possibly) failing drive to a secure location.
I would recommend that you make a clean install on a new, verified working disk and then copy the programs back to this new environment.
If this is not possible, the only other alternative I can think of is to keep a copy of the (currently) working OS2.ini and os2sys.ini files on hand as back-ups.
As for page one, it still exists. There is a bug in the (bridge?) between the forum software and the site software. To access a misbehaving thread, go to www.os2world.com/forum/ and find it that way.
-
Saijin is right on the money on this one.
Now another option you have is this. Get a new drive, boot off the OS/2 Install disks, partition the drive (make it bootable, or install boot manager and set the partition bootable via BootManager), then xcopy the original drive to it. Remove the original drive, set the new drive as master, and work on fixing any remaining issues from there.
Best,
Robert
-
Will he need to do the SYSINST X command after imaging? Not if the partition names (volume/drive letters) remain the same, correct?
-
As for page one, it still exists. There is a bug in the (bridge?) between the forum software and the site software. To access a misbehaving thread, go to www.os2world.com/forum/ and find it that way.
Of course, that may not work either - the thread on WDBasic is currently not available however I try to get to it. Yes, I went to the forum page and searched for WDBasic, clicked on the link and - there it isn't.
I do wish this could be fixed.
Regards
Pete
-
If you click the "forum" button you are still accessing it through the site's software.
You have to literally type www.os2world.com/forum/ into the URL bar to get out of the site's software and access the SM Forum directly.
-
Pete, try this link:
http://www.os2world.com/forum/index.php/topic,1999.0/topicseen.html
-
Hi Saijin_Naib
Yes, that works.
and Robert: No http://www.os2world.com/component/option,com_smf/Itemid,63/ does not work.
Thanks
Pete
-
Hi Saijin_Naib
Yes, that works.
and Robert: No http://www.os2world.com/component/option,com_smf/Itemid,63/ does not work.
Thanks
Pete
Pete,
No, wrong link. Copy and paste this.
http://www.os2world.com/forum/index.php/topic,1999.0/topicseen.html
I know the other does not work. That is due to an error in the Joomla component that neither we nor they can resolve.
Rob
-
Hi Robert
Yes, the copy'n'paste of http://www.os2world.com/forum/index.php/topic,1999.0/topicseen.html opens the correct page.
Seems my mistake was to click on that url in your previous post.
Regards
Pete
-
OK I'm going to take the advice to try and get a back up HDD. Will buy another 540MB HDD off eBay and back up the current HDD to that.
Is there a DOS based command for me to copy the whole of the current HDD to the new one when it arrives? Either as an image or into a folder? Sorry but I come from the world of GUI so I'm quite lost here.
Further then to my first question. How can I optimise my autoexec.bat and command.sys?
-
I think that XCOPY should copy everything over from one drive to the next.
The way I would do it (assuming that what files/filesystem on the drive are not corrupted) would be to boot a floppy or CD of Dfsee trial and use that to image the one drive to the other directly.
-
Saijin is correct.
The steps I would take are as follows...
(1) remove all hard drives from the computer.
(2) Install new hard drive and install boot manager and create partitions (and format)
(2a) boot off OS/2 disks to do this
(3) shut down and install old hard drive in computer (as secondary drive on controller - not as primary).
(3a) boot off OS/2 disks again
(4) xcopy from old drive to new one in this fashion (when at OS/2 command prompt on Drive C/new drive):
xcopy d:\* /h /o /t /s /e /r
Substitute d:\ with whatever drive letter the old one is assigned.
(5) shut down (control-alt-delete and turn off at bios screen) and remove old hard drive.
-
Hi Robert
The /o option is overwrite - not needed with a blank disk.
The /v option - verify - should probably be used though.
Regards
Pete
-
Hi Pete,
Forgot about the /o removal for a new drive. Left off the /v simply because I am guessing it verifies against the original, on an already failing drive, so I wanted to minimize the usage of that drive.
Best,
Rob