1. You should *not* set Scandisk to automatically fix anything. There are
certain types of problems that Scandisk will only make worse. Much worse.
For this reason, you should also locate SCANDISK.INI and make the
appropriate changes so that any autorun of Scandisk at startup also does not
automatically fix anything. The INI file is fully documented, so it should
be no problem for you to figure out what to change.
2. If Scandisk in Windows seems to be behaving oddly, especially if it
fails, aborts prematurely or runs forever without progressing, you should
restart in Command Prompt Only mode and runs Scandisk there, with a full
surface scan. Again, DO NOT autofix anything. Report back here with the
results.
In general, the only two scandisk fixes I habitually OK when reported are
Date/Time inconsistencies and Free Space reporting errors. If I'm aware that
there was a "dirty" shutdown or other program failures, things that can
cause files to be "broken", then I will OK the "repair" of lost clusters and
cross-linked files, but I don't do this on the first round. I make sure to
mentally take careful stock of any other recent systems, first. If the hard
drive is going bad, or there's a low-level virus, or some other serious
problem, it can look like file-table corruption when it's really not. If you
let Scandisk fix files and file tables in these situations, it will be based
upon faulty data. I liken the effect to the flu, where it is the human
auto-immune system's over-reacting that causes the worst symptoms, and even
death, not the virus itself. If you want more details on this, ask Chris
Quirke. He'll be describe the death throes of a system eaten by its own
immune system with an enthusiasm that would make Jack Klugman blush.
Have you read my article on Windows 98 maintenance?
"Clean Boot -- What is and why you need it."
http://grystmill.com/articles/cleanboot.htm
--
Gary S. Terhune
MS MVP Shell/User
"tim" <tim.RemoveThis@discussions.microsoft.com> wrote in message
news:56E94383-D203-42F9-BB2E-EF7A883C2244@microsoft.com...
> Many thanks for all the suggestions and the one that does the trick is the
> memory modules. I can boot up to desktop. Deleted all the TIF and do a
> Window Scan Disk. It does not seems to 'work'. Normally, I set it to
> automatic Fix and you will expect Scan Disk to check folders, folders and
> files, allocation tables and give you a running figure. Now, it never
seems
> to give me that number abd looks like it stuck in a loop. However, I can
do
> defrag and complete it.
> How can I rectify the problem?
>
>
>
> "Ben Myers" wrote:
>
> > Open the case and remove and reseat the memory modules.
> > If possible, replace them with known good ones or find some
> > way of testing the existing ones.
> >
> > Ben
> >
> > "tim" <tim.RemoveThis@discussions.microsoft.com> wrote in message
news:EE6D87AD-F5D9-49E6-BD38-233CC39D5634@microsoft.com...
> > > I will repost with more details . My w98se cannot boot up. It will
freeze
> > > after "Memory testing: 131072k ok"
> > > and the cursor is no where to be seen.
> > >
> > > At the bottom of the screen, there are 3 commands
> > > Press F8-to enable System Configuration
> > > Press F9- to select Boot Device after POST
> > > Press DEL to enter SETUP
> > > and none of these commandsget me anywhere.
> > >
> > > The best I can go is when I press DEL upon start up, its says
'Emtering
> > > SETUP and just freeze there. Please advice what can I do next? Thanks
> > >
> > >
> > >
> > > What can I do next? Can I use another
> > > pc win 98 boot floppy? (pc used by young ones playing internet games,
NAV2005
> > > updated regularly). Many thanks for uour assistance
> > >> Stay informed about: Cannot boot up