Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Win98/Your Eyes Only

0 views
Skip to first unread message

Garry Goodwin

unread,
Sep 17, 1998, 3:00:00 AM9/17/98
to
I'm afraid I really put my foot in it this time! I've been running
Win98/YEO successfully now for several months. I found out today that
they are incompatible.

During shutdown last night, my PC laptop froze on "MSGSVR32". This
morning, upon bootup, Norton Utilities prompted me about an "Error on
Disk 1". It said my "bootable partition can't be booted from and that
the partition normally only boots from a partition if the boot record
has valid information."

I clicked "yes" to correct the problem. Norton prompted me for an
"undo" floppy which I inserted. It then prompted me to restart.

Upon bootup, I now get the message "loading boot record from
IDE-0...OK" and then it just hangs with a blinking cursor.

As you might guess, my C:drive reads as 'unknown' in FDISK. I have
used "eunlock" several times to "emergency unlock" my c:drive. It
seems to unlock, and says it was successful, but I'm wondering if it
really has or if the boot data has been corrupted.

I've tried the Win98 bootup disk with CD-ROM support in hopes of
having my Norton Utilities CD-ROM "fix" C:drive, but it always comes
up as "not able to run Norton on c:drive". Similarly, Win98's
RAMDrive with "scandisk" can't "see" the c:drive. The Norton
Emergency floppies aren't able to "see" c:drive either.

Have I really botched it? Has YEO corrupted my boot blocks or system
irreparably? Is it time to call in the zillions per hour "recovery
specialists"? (my local vendor wants $1,500 for retrieval of a 2.1
Gb hard disk!!!

Thanks for any light you can shed on this! I'll take any "last ditch"
procedures you may have on getting this data back. I'll be happy to
try ANYTHING before paying the recovery vulture. Thanks again.

David Lucas (Symantec)

unread,
Sep 17, 1998, 3:00:00 AM9/17/98
to
On 17 Sep 1998 08:03:13 GMT, Garry Goodwin <xggoo...@amgen.com>
wrote:

Hi Garry,

Thank you for posting in our on-line discussion group. It does look
like you have corruption in the boot area of the drive. I have a
suggestion for you to try that may correct the issue. I would
recommend to run NDD /Rebuild. This will attempt to rebuild the
partitions of the drive. If you are able to run the NDD /Rebuild from
the Norton Utilities Emergency disk, this may correct some of the
issue. I extremely recommend to create an UNDO disk when Norton
Utilities asks you to.

If the NDD /Rebuild is able to find the partitions and recover, at the
end of the repair process it asks to restart and would recommend too.

After the Restart, run NDD again without the /rebuild (make a new undo
disk separate from the first one). See if you are able to correct the
errors on the drive now.

If the procedure does not work and you still cannot recover the drive.
I would recommend to run NDD (Disk Doctor) and restore the undo
information starting with the second disk and then the first disk. I
attached our data recovery document as well in case you need it.
http://service1.symantec.com/SUPPORT/nunt.nsf/docid/1997124164654

Please let me know what you find.

David Lucas
Support Analyst
Symantec Corporation

Please continue to post your messages to the public discussion group
as Symantec does not provide support via private e-mail. Thank you.

If you have difficulty getting a response, please read the following
article:

http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/1998527114414

For free technical support newsletters, Knowledge Base support
articles, our Online Support Genie, and FAQs, visit our Norton
AntiVirus support page:

http://www.symantec.com/techsupp/nav.html

Garry Goodwin

unread,
Sep 18, 1998, 3:00:00 AM9/18/98
to
Hi, David and thanks for your response.

I tried running NDD from one of my Norton floppies and got the
message "invalid media type reading drive c:". I then went back to my
Win98 startup disk, and tried running NDD from the E: drive CD, and
basically got the same message. I couldn't find a Rebuild.exe file
and therefore assumed that Rebuild had to run from within NDD.

Any suggestions? Thanks! If I end up going through Eugene, OR for
recovery if we're unable to get this to work, I didn't see a service
for boot block recovery. Does this fall under system repair? Thanks
again.

David Lucas (Symantec)

unread,
Sep 18, 1998, 3:00:00 AM9/18/98
to
On 18 Sep 1998 01:50:44 GMT, Garry Goodwin <xggoo...@amgen.com>
wrote:

>Hi, David and thanks for your response.


>
>I tried running NDD from one of my Norton floppies and got the
>message "invalid media type reading drive c:". I then went back to my
>Win98 startup disk, and tried running NDD from the E: drive CD, and
>basically got the same message. I couldn't find a Rebuild.exe file
>and therefore assumed that Rebuild had to run from within NDD.
>
>Any suggestions? Thanks! If I end up going through Eugene, OR for
>recovery if we're unable to get this to work, I didn't see a service
>for boot block recovery. Does this fall under system repair? Thanks
>again.

Hi Garry,

The rebuild is a switch to use with ndd.exe (Example: NDD /Rebuild).
You may want to try it again with the example above and see if you
have any luck!

Also, you can request the Data Recover information from our fax
retrieval system at 541-984-2490 and the document numbers you want are
911001, 911002.
This would fall under software repair.

Garry Goodwin

unread,
Sep 21, 1998, 3:00:00 AM9/21/98
to
If I'm reading you correctly, I type ndd/Rebuild at the command
prompt, right? If this is right, I've done it and received the
message, "invalid media type reading drive C".

Is this our last option? Thanks.

David Lucas (Symantec)

unread,
Sep 21, 1998, 3:00:00 AM9/21/98
to
On 21 Sep 1998 00:17:19 GMT, Garry Goodwin <xggoo...@amgen.com>
wrote:

>If I'm reading you correctly, I type ndd/Rebuild at the command


>prompt, right? If this is right, I've done it and received the
>message, "invalid media type reading drive C".
>
>Is this our last option? Thanks.

Hello Garry,

Thank you for replying back to our discussion group. It looks like the
DOS boot record or possibly the file allocation tables could be
damaged. I do suggest to try our data recovery service. We have gone
as far as you can online for repairing it without causing more damage.

The Data Recover information can be sent via fax from our fax


retrieval system at 541-984-2490 and the document numbers you want

are:
911001
911002

Please let me know what you find out about this issue.

David Lucas
Symantec

0 new messages