🚀 go-pugleaf

Are you able to view the directory structure on the hard drive with the dir
command? Do you get the error when the bios checks the drive or when windows
starts?


Michael Morenberg <michaelm@fcc.net> wrote in message
news:39931279.9C824A81@fcc.net...
>
> I turned on my computer and instead of getting my usual Windows 98, I
> got a "read error".
> Tried many times, but only got read error.  I was eventually able to get
> a C prompt.  from
> the C prompt I could execute DOS commands.  When I try to get into
> windows I still
> get the read error.
>
> I tried to reload windows, but I still get a "read error".  Seagate is
> no help, they gave me
> several companies that could extract the data.
>
> I have no idea of how to solve this problem.  Is there any software outs
> there that can
> help me extract the data on my drive (9.1 gig seagate).  I have
> purchased a new 30.6 gig
> seagate drive.
>
> Are there any other newsgroups more appropriate then the ones I have
> addressed.
>
> PLEASE HELP ME.
>
> Fred.
>
>
>

I assume you are now using the new hard drive, have you tried to slave your old
one to the new one and see if you can access anything on it?   I'm only
guessing, but the old drive may possibly have a boot sector virus.  If you don't
have to boot from it, you may be able to access the data from it.  There are
programs like Ghost available from Norton that can copy all your data from one
disk to another and I believe it works in DOS mode.  But be careful in case that
old drive has an infection.

--
Stephen Pehrson <Inglo>
ICQ:  65545522
(remove your eternal soul to reply by e-mail)

It all coheres...



"Michael Morenberg" <michaelm@fcc.net> wrote in message
news:39931279.9C824A81@fcc.net...
|
| I turned on my computer and instead of getting my usual Windows 98, I
| got a "read error".
| Tried many times, but only got read error.  I was eventually able to get
| a C prompt.  from
| the C prompt I could execute DOS commands.  When I try to get into
| windows I still
| get the read error.
|
| I tried to reload windows, but I still get a "read error".  Seagate is
| no help, they gave me
| several companies that could extract the data.
|
| I have no idea of how to solve this problem.  Is there any software outs
| there that can
| help me extract the data on my drive (9.1 gig seagate).  I have
| purchased a new 30.6 gig
| seagate drive.
|
| Are there any other newsgroups more appropriate then the ones I have
| addressed.
|
| PLEASE HELP ME.
|
| Fred.
|
|
|

Hi:

I can execute a Dir command.  I believe it is when windows attempts to
execute.  I have since removed the drive.  I could reinstall, or install
both my new drive & the old drive.

Thanks for your help,

FRED
******************************************8

Paradoxical wrote:

> Are you able to view the directory structure on the hard drive with the dir
> command? Do you get the error when the bios checks the drive or when windows
> starts?
>
> Michael Morenberg <michaelm@fcc.net> wrote in message
> news:39931279.9C824A81@fcc.net...
> >
> > I turned on my computer and instead of getting my usual Windows 98, I
> > got a "read error".
> > Tried many times, but only got read error.  I was eventually able to get
> > a C prompt.  from
> > the C prompt I could execute DOS commands.  When I try to get into
> > windows I still
> > get the read error.
> >
> > I tried to reload windows, but I still get a "read error".  Seagate is
> > no help, they gave me
> > several companies that could extract the data.
> >
> > I have no idea of how to solve this problem.  Is there any software outs
> > there that can
> > help me extract the data on my drive (9.1 gig seagate).  I have
> > purchased a new 30.6 gig
> > seagate drive.
> >
> > Are there any other newsgroups more appropriate then the ones I have
> > addressed.
> >
> > PLEASE HELP ME.
> >
> > Fred.
> >
> >
> >

On Thursday, in article <39931279.9C824A81@fcc.net>
     michaelm@fcc.net "Michael Morenberg" wrote:

> Are there any other newsgroups more appropriate then the ones I have
> addressed.

demon.ip.support.pc is not a newsgroup for which pc hardware problems 
are on topic.

But if you can get to a c: prompt, it looks more like a bad sector in a 
critical Windows file than a total loss.  Run scandisk, and see what 
happens when you do a surface test.


-- 
David G. Bell -- Farmer, SF Fan, Filker, and Punslinger.

Copyright 2000 David G. Bell
The right to insert advertising material in the above text is reserved
to the author.  The author did not use any form of HTML in the above text.
Any text following this line was added without the author's permission.

In article <3993198E.A975702@fcc.net>
           michaelm@fcc.net "Michael Morenberg" writes:

> Hi:
> 
> I can execute a Dir command.  I believe it is when windows attempts to
> execute.  I have since removed the drive.  I could reinstall, or install
> both my new drive & the old drive.

Why the fuck are all you numbskulls posting this crap into
demon.ip.support.pc?  It has nothing to do with Demon (an ISP based in
the UK), nor with using Internet Protocols.  Moreover, it has nothing to
do with the group's charter, which is concerned purely with those using
DOS (ie *not* Windoze) to make IP connections to Demon.

Moreover, are you actually entitled to post from the domain fcc.net?

(Hmm, perhaps I should do a WHOIS?)

Follow-ups set.

-- 
Brian {Hamilton Kelly}                                          bhk@dsl.co.uk
    "We have gone from a world of concentrated knowledge and wisdom to one of
    distributed ignorance.  And we know and understand less while being incr-
    easingly capable."                          Prof. Peter Cochrane, BT Labs

[The origianl article was posted (by error) in d.i.s.pc, where it got
 some answers but not of the sort it would have got from the proper
 fraternity, d.t.pc, so I am including the whole text with my answer.]

On Thursday, in article <39931279.9C824A81@fcc.net>
     michaelm@fcc.net "Michael Morenberg" wrote:

"I turned on my computer and instead of getting my usual Windows 98, I
"got a "read error".
"Tried many times, but only got read error.  I was eventually able to get
"a C prompt.  from
"the C prompt I could execute DOS commands.  When I try to get into
"windows I still
"get the read error.
"
"I tried to reload windows, but I still get a "read error".  Seagate is
"no help, they gave me
"several companies that could extract the data.
"
"I have no idea of how to solve this problem.  Is there any software outs
"there that can
"help me extract the data on my drive (9.1 gig seagate).  I have
"purchased a new 30.6 gig
"seagate drive.
"
"Are there any other newsgroups more appropriate then the ones I have
"addressed.
"
"PLEASE HELP ME.
"
"Fred.
"

Michael:

    You had a few responses - some not too complimentary!  - in
 d.i.s.pc, but perhaps one should go a little deeper.  There are a
 surprising number of highly computerate and highly helpful people in
 this NG (d.t.pc); many more expert than I.  But here's 2p worth.

    Everyone running Win9x (and presumably also Win2K) should have
 a boot floppy.  This is also known as a rescue disk.  With it (and
 provided you have set your PC's BIOS to try booting from floppy
 before booting from HDD) you can get at your HDD without booting
 from it.  Win9x has an option (in 'Windows Setup') to create such a
 disk, as do many of the utility packages such as Norton.  Personally
 I have my own carefully crafted one (which I'll snail you a copy of
 if you e-mail me your address, if you like).  This disk will only boot
 to DOS, of course; but it has the same effect as the F8 option
 "Command prompt only".

    There are many things you can do at the DOS-prompt (which will
 now be "A:>") to investigate the C-drive.  And to repair it.  There
 exist a raft of utilities designed to do this.  I use Norton.  But
 FDISK will give you quite a bit of information; and Partition Magic
 will do some remarkable things; and Spinrite will often fix HDD
 problems which are semi-software, ie things written wrongly on the
 disk rather than real I/O errors.

    You will get lots of advice in these NGs about what to do next.
 Most of it will be sound.  But when posting a request for help,
 always say exactly what happened.  If you get an error message,
 quote it fully and explain how far you had got into the booting (or
 other) process before the error occurred.

    In your particular case, you have solved the problem by replacing
 the HDD.  This was probably unnecessary.  But at least you ought now
 to do a full post-mortem on the old disk, (slaved to the new), to find
 out what was wrong.

    As suggested, you may have a virus.  Get and run the latest copy
 of F-Prot (from www.complex.is).  Or one of several other good
 scanners.  If you find that you had one, then you will need to test
 ALL of your floppies (and CD or other backups); which is a fine old
 hassle.  But viruses have to be exterminated, not tolerated.

    There are other angles to all this, such as how to interpret
 partition-info from FDISK etc, how to rewrite the Master Boot
 record, and what happens if you have Ontrack Disk Manager (or
 similar) installed.  Hang around in this newsgroup and you will find
 out.  (I am e-mailing you to tell you to do this, in case this
 posting doesn't reach you.)

                                        Chris K.
-- 
Chris Kennington in anti-spam news-posting mode.
  If e-mailing replies, please use name "chris@".