I tried Tutordo and didn't like it, some things didn't even work.  Maybe it
would now?  But I don't think I really like it, unless it was greatly improved
since the last version.  I was running in OS/2 Warp 4 VDM, no longer available
now that OS/2 Warp 4 quit on me with Trap 000d (or was it 000e?) during a period
of idleness.  I could no longer access my hard disks with either MS-DOS 5, 6.22
or DR-DOS 7.03, or Linux, am left with Texel, now Plextor, internal 2x CD-ROM on
same SCSI (Trantor T130B) with external Iomega Zip 250, and my 3.5" 1.44 MB
diskette drive still works.  I am running with DR-DOS 7.03, mail and news with
UKA_PPP, searching the WWW for recovery tools with DOS Lynx386.  Arachne failed
to start due to a shortage > 70 KB of low memory.  I didn't have DOS=UMB in
CONFIG.SYS, maybe that would help?  I am using VDISK.

Miraculously, after running DR-DOS setup, I was able to access the first hard
disk again, subsequently I was able to boot into the old Linux and access both
hard disks.  But the attempt to mount the HPFS partition read-only failed due to
"dirty" flag, which would be reset when OS/2 is shut down normally but not when
OS/2 abends, which would also be the case when power is suddenly interrupted.
Then I booted OS/2 Warp 4 again, it automatically CHKDSKed, slowly, but then
halted with Trap 000d.  After that, the hard disks were no longer accessible.
Is that how OS/2 got Warp as part of its name?  I thought only Windoze did
things like that.  So I don't know if it's a hardware problem: controller or the
disks themselves, or if OS/2 Warp 4 farkled an important part of the hard disk.
I'd like to see if I can retrieve some of the data on those hard disks.  Any
ideas on hardware recovery tools for DOS or Linux?

I tried booting the OS/2 Warp 4 installation diskettes, got Trap 000d before I
could do anything.  When I buy that new computer and install DR-DOS 7.03, Linux
and NetBSD, I can tell the OS/2 and eComStation people that I didn't give up on
OS/2, it quit on me.

Reply via email to