Re: aarGH was NO ROM BASIC, System halted

On Mon, 11 Sep 2006 01:22:43 GMT, pmj commented


"Ali" <ali.on.usenet@xxxxxxxxxxxx> wrote in message
news:Xns983ABDA13DC52314159265358@xxxxxxxxxxxxxxxxx
On Sun, 10 Sep 2006 23:47:44 GMT, pmj commented
"Ali" <ali.on.usenet@xxxxxxxxxxxx> wrote in message
news:Xns983AB2B57D5C5314159265358@xxxxxxxxxxxxxxxxx
<snip>
... but I have got a functional system once again.

Good!
:-)
<snip>
... Unfortunately if I let it run it stops at 178,669 clusters,
out of over 2 million, and the Windows version has stopped
there too.

So it sounds like the Disk *is* on its way out?
Or at least has a (or some) Bad Sector(s)?

But this is the new (2yo), 160GB drive, not the old 30GB drive.

AH!
Oh yes!
Sorry I was getting a bit mixed up & Confuzzled over which one was
which & what stage you had reached.

OK, so it may be an idea to leave ScanDisk Running for some time on it?

I did, last night while I was on here, I had started the Windows Scandisk
(since the Dos one never finished), and let it run, and run, but when I
checked, while writing that bit just up there ^, it had stopped, frozen, and
stayed that way while I finished that particular news session.


Are you doing a "(/) Thorough" ScanDisk on it?

Yes

& have you Ticked "[/] Automatically Fix Errors?

Yes


& what about the various other Options in the [Options...] Button?
Scan Sytem and Data areas
All other boxes clear
& also in the [Advanced...] Button?

What have you got them all Set to?

Display Summary: Always
Log file: replage log
cross-linked files: Make copies
Lost file fragments: convert to files
Check files for: invalid file names

other options clear


& what about trying a CHKDSK /f on it?

Though you may find that it won't run CHKDSK from within windoze
& just tells you to use ScanDisk

So it might be an idea to try Running CHKDSK /f when it's Booted
into MSDOS, but apparently, the windoze ScanDisk is more thorough
than the MSDOS CHKDSK

That was one of the first things I tried, from the Win98 boot floppy, on the
30GB drive, and CHKDSK just said Use Scandisk, and quit, so I doubt it will
look at the 160GB drive.


And still to come is re-connecting to old drive, and seeing if
it wants to boot - must change boot sequence again.

& you could make the Partition on that Drive not "Marked as Active"
Still to do that, but that drive is now way down the boot order in BIOS.

Thanks again

No, thank *you* for giving me the opportunity to brush up on & practice
a bit on (& with) some of what I have found out over a period of time!
:-)

A very handy thing, this Virtual PC (& the similar VMWare) thing is!
:-)


Of course since I answered Rabbit, and said it was hapily copying files from
the dodgy drive, it hit a bad sector, when I OK'd the "Cannot read source"
message box, it froze (nearly: Ctrl-Alt-Del brought up a "Busy waiting for
close Program box" blue screen, then another blue screen said "Cannot write
to drive D - Data may be lost" and really froze. I pressed the reset
button, it re-booted, but without the dodgy drive!

I shut down completely, waited a few seconds, then re-started, and everything
came back, and copying is once mre in progress.

--
Ali
.