Re: ?Disk Recovery (RE: Computer Failure )
Re: ?Disk Recovery (RE: Computer Failure )
TOP POSTED: Final results: read below for outcome of Microtime OS disk
recovery.
I must say I am somewhat surprised, but I admit I did have crossed fingers,
glad you now have both disks recovered.
"BAP" <BAP@discussions.microsoft.com> wrote in message
news:CFF20239-7531-4D2B-B8C6-39AE98452EB2@microsoft.com...
|
|
| "MEB" wrote:
|
| >
| >
| > "BAP" <BAP@discussions.microsoft.com> wrote in message
| > news:88CE8CC8-8EBE-4294-B7BE-6B90C62FCA38@microsoft.com...
| > |
| > |
| > | "MEB" wrote:
| > |
| > | >
| > | >
| > | > "BAP" <BAP@discussions.microsoft.com> wrote in message
| > | > news:1A8A6A60-BABD-4A6F-BF4C-EA33D7E79643@microsoft.com...
| > | > | The start of this new Post regarding the 'Computer Failure' Post
was
| > | > | suggested by "MEB", and rightly so, as the that earlier Post was
| > creating
| > | > | some confusion.
| > | > |
| > | > | As was discussed in the 'Computer Failure' Post, the Microtime
| > Computer,
| > | > | that I have been using for several years, has failed and I find it
| > rather
| > | > | difficult to get it operational, again. There is a Primary Master
and
| > a
| > | > | Secondary Master HD's installed in it. There are folders in both
that
| > have
| > | > | Data that I would like to recover. A more recent Computer, a Sony
| > VAIO,
| > | > | that I am currently using, appears to have all that I would need
to
| > | > connect
| > | > | those HD's and recover the desired Data and back up the same, if
| > desired,
| > | > | on CD's or Iomega Zip 250 MB Disks. The only obstacle is of
possible
| > | > | compatibility issues.
| >
| > {DELETED MATERIALS CONTAIN VAIO IFORMATION-
| > (refer to the post containing it for reference
| >
| > | > | Hopefully, this will mean something to you, "MEB" or anyone else
able
| > to
| > | > help.
| > | > | Thank you in advance for any reply!
| > | >
| > | > One issue you failed to mention, which may or will be an issue, is
that
| > the
| > | > other target drive [OS disk} had to be started in the other system
by
| > using
| > | > a boot disk or other work around.
| > | ****
| > | ?"MEB", that was not the case. Early on, there was nothing wrong with
the
| > | booting cycle, unless I
| > | needed or wanted to start with a Boot Disk. If I did that and inserted
the
| > | Boot Disk before
| > | starting the booting cycle, at the Dos Prompt I would find myself in
the
| > | Primary Slave HD. The
| > | Master HD would not be available. This surfaced when I replaced the
| > original
| > | HD, 10 GB in size,
| > | with a Maxtor with 40 GB. The MAX-BLAST software, that came with the
| > Maxtor
| > | HD, created
| > | an overlay. As mentioned, in a rather old post, few years back, in
order
| > | to boot from a Boot
| > | Disk properly, I had to break the progress of booting with a CTRL Key
and
| > | opt to boot from the
| > | Boot Disk that had to be inserted at that time.
| > | ***
| >
| > AAAAAh, thanks for clarifying, the MAXTOR drive contains a drive
overlay -
| > RE: that is the Microtime OS disk which you mentioned in the other
postings,
| > which is not recognized when placed into other computers.
| >
| > DRIVE OVERLAY programs use the computer's BIOS translation and access
| > routines when the algorythms are used to create and then use the overlay
| > with the manufacturer's tools.
| > This can even affect whether the hidden partition for the overlay
| > translation is addressed properly. Overlays are not Plug and Play,
changing
| > to meet differring BIOS needs and translations, PARTICULARLY as the
drive
| > adapter chip may interact with the BIOS in a different fashion, such as
when
| > the drive IS supported within the BIOS verses when the overlay was need
to
| > use the drive in an unsupportive BIOS and/or OS.
| > REMEMBER THIS: A different BIOS on another computer, OR *change within
the
| > original BIOS* related to that hard drive, will likely change how that
| > overlay addresses the drive.
| >
| > |
| > | But we can work from this {BTW, good
| > | > information to work from, thanks}. I had also created a new posting
for
| > your
| > | > VAIO attempt, which outlines what had been found to that point *
Sony
| > | > VAIO - WinME - hard drive usage and data recovery *. But we can work
| > from
| > | > here with this new information, as long as everyone reviews the
other
| > | > postings as well so redundant suggestions aren't provided.
| > | >
| > |
| > |
| > | > I also created two new posts for your other computers:
| > | > Risys running Win31 - 98SE disk recovery
| > | > Microtime - Win98SE - computer diagnostics and repair
| > | >
| > | > There is a small program which might provide some useful
information
| > | > provided by MiTeC:
| > | >
http://www.mitec.cz/Downloads/msi.zip - 782K - system information -
goto
| > | > Storage > Physical Devices for drive identification
| > | >
http://www.mitec.cz/ - main page with tools
| >
| > The above provides lots of information, without the necessity of an
| > installation of another bloated Windows program.
| >
| > | >
| > | > You can likely go ahead and try to connect the DATA drive to the
VAIO
| > as it
| > | > may already configured as SLAVE *IF* it was on the same cable as the
| > | > other/OS drive in the Microtime. Some info here:
| > | >
| >
http://support.gateway.com/support/manlib/cmponts/harddriv/8505896/05896.htm
| > | >
| > | > If the drive works, pull the data off.
| > | >
| > | ****
| > | ?"MEB", I did that and it worked, although the there was some
confusion
| > | about the ID of the Disks shown by 'My Computer'. Normally, Disk C:
is
| > the
| > | Partition 0 of the Primary Master - D: Partition 1 - E: DVD - F:
CD_ROM -
| > G:
| > | Zip Drive.
| >
| > Did you forget that I had advised of that in the prior post/thread? Let
me
| > repost so its in this discussion:
| > - - - PRIOR POST - - - -
| > | MEB:
| > | Here are potential issues when connecting a drive to the secondary
| > | connector on IDE0/channel1 - IRQ 14 [use SYSTEM > Device Manager >
Hard
| > Disk
| > | Controllers > Primary IDE Controller > settings and resources to
view].:
| > | *****
| > | BAP
| > | Sorry, I can't seem to find my way around to get to that pane.
| > |
| > | MEB - you are running ME which will have that in a different area.
| > |
| > | ***
| > |
| > | MEB:
| > | 1. The present drive [apparently 60 gig] is partitioned with C {the
| > primary
| > | boot partition} as a
| > | 15.5 gig drive, adding another drive would move the second partition
| > | presently being seen as the
| > | 41.6 gig drive D to drive E. The new hard drive would have to be
| > configured
| > | as a slave and the
| > | first hard drive as master with their jumpers or errors and potential
disk
| > | corruption could occur.
| > | There could also be a hidden partition involved for SONY specific
recovery
| > | or other, so it may be
| > | larger [an 80 gig drive perhaps, though that won't presently affect
what
| > we
| > | are discussing], what
| > | is the actual model and make of that drive?
| > | There MAY potentially be a hard drive conflict if the drives are not
| > | compatible. What are the two drive's makes and models?
| > |
| > | 2. The two drives on the second channel [CD and DVD] will be moved to
| > drive
| > | F and G, but only IF the OS has not had its drives limited to only see
| > | drives up to drive F: limited by either the driver settings, system
| > | settings, or something like TweakUI which modified the registry or an
| > | inclusion in the system.ini or config.sys [lastdrive=*]. If this is
the
| > | case, the lost/un-recognized drive will still cause errors even though
it
| > is
| > | not listed in Windows, it is still holding memory and CMOS/BIOS
addressing
| > | which Windows may try to assign to other needs, or may cause
conflicting
| > | system device issues..
| > |
| > | 3. The Iomega drive adds potential issues to the mix if it has been
set to
| > | always use some specific drive letter or IRQ, and/or if [as sometimes
| > | happens] it is incompatible with this older drive you are attempting
to
| > | access.
| > |
| > | 4. A drive overlay may be part of the issue, but beyond that, we may
also
| > be
| > | running across a disk or disks which have had Drive Space or Double
Space
| > | [or another drive compressor] used.
| > |
| > ------ END POST FROM OTHER DISCUSSIONS ^^^
| >
| > | With the Microtime Primary Slave in place, C: was still Sony's HD
Primary
| > | Master Partition 0 - D: the Microtime's Disk - E: Partition 1 of
Sony -
| > G:
| > | was showing as the ZIP disk. However, if I inserted a CD in the CD_ROM
| > drive,
| > | G became the CD_ROM Disk - F:, showing as removable Disk, was, in
effect,
| > | the ZIP Drive.
| >
| > This is exactly as I had advised.
| > This also indicates that the ZIP disk has been *assigned* a drive
letter.
| >
| > | No matter, 'though, as I was able to copy the contents of the
Microtime's
| > | Primary Slave HD.
| >
| > *STEP 1 - SUCCESS* accomplished: now that AUTO had been set in the
BIOS,
| > the Microtime DATA/storage disk has been recovered.
| >
| > | All my steps taken, to configure the Microtime's Primary Master and
make
| > it
| > | a Slave, did not succeed. The configuration shown on the HD about the
| > jumper
| > | positions did not work. However, the system detected that HD as a
Primary
| > | Slave.
| > | This was shown: (besides other info)
| > | Primary Master Disk: 61492 MB UDMA 5
| > | Orimary Slave Disk: 30750 MB UDMA 5
| > | Secondary Master Disk: CD-ROM UDMA 2
| > | Secondary Slave Disk: CD-ROM UDMA 2
| >
| > OKAY, let's not get ahead of ourselves here.
| >
| > The disk is a MAXTOR - WHAT {model/number}?
| >
| > |
| > | Without the Microtime's HD connected, this was shown:
| > | Primary Master Disk: 61492 MB UDMA 5
| > | Orimary Slave Disk: None
| > | Secondary Master Disk: CD-ROM UDMA 2
| > | Secondary Slave Disk: CD-ROM UDMA 2
| > |
| > | It was bothersome to see that the size of the Microtime's HD did not
| > appear
| > | to have the size that I thought it should have. I will check further
into
| > | that.
| >
| > PLEASE wait until we can determine how to address the MAXTOR disk in
this
| > new BIOS. Obviously the BIOS has built-in support, so to fudge the disk
and
| > attempt to access properly, we MAY need to attempt to manually set the
BIOS
| > to mimic what the Microtime would have used AND that drive will need
some
| > adjustments to its jumpers {configure as SLAVE} and its MBR/partition
table
| > {its presently configured with a hidden overlay partition AND as a BOOT
| > disk}.
| > HOWEVER, finish reading this post before responding.
| >
| > *IF* there's nothing you need from that drive, then use MAXTOR's [now
| > SEAGATE] disk tool to remove the overlay and the disk will be usable in
ALL
| > BIOSes which support it natively. DO NOT attempt to use fdisk and format
to
| > remove the overlay and its partition.
| >
| > *IF* you want to recover that dsk:
| >
| > 1. REMOVE the present SONY VAIO master disk or unhook the ribbon AND
power
| > cabling. Connect the ribbon and power to the Microtime MAXTOR mater/OS
disk,
| > leaving it as MASTER; have the DATA Microtime hard drive configured as
| > SLAVE, connected to the same ribbon. It would be best to disconnect the
ZIP
| > drive, and the CD and DVD for this part of the recovery attempt, as
well, as
| > they were not part of the prior setup on the Microtime. To disable the
CD
| > and DVD, disconnect their power, and the ribbon from the motherboard
{noting
| > where the color indicator/stripe was in relation to the MB connector}
| >
| ****
| ?I should have concentrated on the options you presented, 2, 3, 4 and 5
| that follow. Instead I got excited about the first option and what it was
| saying.
| Although sort of apprehensive about what I was doing, the suggested scheme
| of removing Sony's Primary Master HD and put in its place the Microtime's
| Primary. Master HD, brought good results. I had the ZIP, CD_ROM and the
DVD
| disconnected. There were several instances, during the booting cycle,
where
| warnings popped out that new hardware had been found and the system wanted
to
| find the best ways to deal with them and/or asked for the W98 installation
| Disk. I allowed some events to
| happen, then, rather fearful, I started canceling the suggested steps or
| closing the dialog boxes. Eventually, it did complete the booting process
and
| the HD became available, along with the same layout of the Desktop as the
| Microtime.
| All the folders and data were available.
| I powered it down reconnected all the disconnected Drives and
re-connected
| the
| companion Primary Slave. I re-booted (this time without warnings) and
| copied the desired Data from the Master to the Slave.
| Once done, I replaced the Primary Master with the Sony's Master and copied
| the Data from the Microtime's Slave to the Sony's second Partition. All
came
| out well.
| Later, I removed the Microtime's Primary Slave and closed up the tower of
| the Sony,
| All is back to normal. Hopefully, the warning boxes and the allowed steps
| did not create problems that may pop up in time.
| I will plan on backing up all that I want on CD's.
| Thank you, "MEB", for all your help!
| Thank you to all those who contributed to this issue!
| ***
OKAY then [sigh of relief], done issues for hard drive recoveries... Don't
worry about issues in the Millennium, all changes were made to the 98 disk
[except the addition of the temporary secondary hard drive, and BIOS/CMOS
change to auto detect, so that leaves just the CD DVD issue(s).
|
|
| > 2. Attempt to boot the computer into SAFE MODE. Do NOT use NORMAL
Startup as
| > that will attempt to reconfigure the Windows system which may not be
| > successful.
| > In Safe Mode, the disks will be using DOS compatibility mode, and the
MASTER
| > should have used the Drive Overlay upon initial boot.
| >
| > 3. IF there is a successful SAFE MODE boot, pull any files or data off
the
| > MASTER and put it on the SLAVE. IF the slave has insuficient space, as
you
| > now have that data saved, DELETE the SLAVE drive files, and transfer
what
| > ever files you need to it. Make sure those deleted files aren't taking
up
| > space by being stored in the Recycle Bin.
| >
| > 4. IF you successfully retreive that data or files, you will need to
| > determine what you intend to use that former Microtime OS disk for in
the
| > future.
| >
| > 5. IF SAFE MODE fails, attempt to start in pure DOS with either a boot
| > EBD/recovery floppy [preferred] or from the Windows Menu [Command Prompt
| > Only]. Type - fdisk /status - and post what it found.
| >
| >
| > | At any rate, 'My Computer' did not show this HD in the list of Disk
| > Drives.
| > | I wish there would be a way, but, I am glad that most of my data has
been
| > | recovered.
| > | Thank you for all the suggestions.
| > | ***
| >
| > Look above, and try that to see if that works, if not, we can attempt
to
| > make some modifications to the VAIO BIOS HD settings OR we can use some
| > other recovery techniques. For that we will need the model number of the
| > Microtime computer and/or the motherboard make and model/number so we
can
| > see what the BIOS was.
| >
| > | > Checking for that drive shows it is actually a Hitachi drive
DeskStar
| > 16GP:
| > | >
http://www.hitachigst.com/tech/techlib.nsf/products/Deskstar_16GP
| > | > Check those Hitachi jumpers!
| > | >
| > | > You can also try the drive fitness test, but do use no destructive
| > tests
| > | > until you recover the data:
| > | >
http://www.hgst.com/hdd/support/download.htm#DFT
| > | >
http://www.hgst.com/hdd/support/downloads/dft32_v412_b01.EXE Windows
--
MEB
http://peoplescounsel.orgfree.com
_________
