Problem starting windows

Hi,

After installing two programs then rebooting WindowsME will not start.
Safemode will not start either. I then run scandisk and the problem was
identified 'Scandisk detected an invalid long filename entry on this drive
but was unable to fix it' and 'To fix this problem run scandisk for windows'

The problem is I am unable to run scandisk for windows because windows will
not load.

I also ran scanreg/restore as suggested in help, again the problem is still
there.

Anyone come across this problem before? I do not want to do a system
restore as I have current files not yet backed up.

Much appreciate any help!

Do you have a System Restore point to just before the install of the problem
causing apps?....if so, I would recommend Restoring to that point and
installing only one of the apps and then checking your machine before
installing the other (since you don't know which app is causing the issue or
if it is a combination of the two).

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be scanreg
/restore.....note the space between the "g" and the "/" and don't use the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about 5
choices of reg dates to choose from....dates from successful boots).
Heirloom, old and hope that helps


"Pat" wrote in message
...
Hi,

After installing two programs then rebooting WindowsME will not start.
Safemode will not start either. I then run scandisk and the problem was
identified 'Scandisk detected an invalid long filename entry on this drive
but was unable to fix it' and 'To fix this problem run scandisk for
windows'

The problem is I am unable to run scandisk for windows because windows
will
not load.

I also ran scanreg/restore as suggested in help, again the problem is
still
there.

Anyone come across this problem before? I do not want to do a system
restore as I have current files not yet backed up.

Much appreciate any help!

If, after following HL's excellent advice, you still can't make any
progress, then you could try running scandisk in Real Mode DOS. But be aware
that you *might* just have a faulty hard drive and therefore you *might* be
putting your data at risk.

Boot, using the WinMe Startup (floppy) Disk and select 'With CD-ROM Support'
then at the A:\ prompt, type "scandisk c:" (no quotes and note the colon)
then press Return.

Follow the screen prompts - and for the first time at least, (unless you are
happy that either the disk is OK, or you can sacrifice your data) tell it
NOT to do a Surface Scan. See what it reports and keep a check on its
progress.

If it reports major problems, copy your important data to another drive (or
CD-R) before attempting to write (surface scan) to the disk.

Mart


"heirloom" wrote in message
...
Do you have a System Restore point to just before the install of the
problem
causing apps?....if so, I would recommend Restoring to that point and
installing only one of the apps and then checking your machine before
installing the other (since you don't know which app is causing the issue
or
if it is a combination of the two).

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be scanreg
/restore.....note the space between the "g" and the "/" and don't use the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about 5
choices of reg dates to choose from....dates from successful boots).
Heirloom, old and hope that helps


"Pat" wrote in message
...
Hi,

After installing two programs then rebooting WindowsME will not start.
Safemode will not start either. I then run scandisk and the problem was
identified 'Scandisk detected an invalid long filename entry on this
drive
but was unable to fix it' and 'To fix this problem run scandisk for
windows'

The problem is I am unable to run scandisk for windows because windows
will
not load.

I also ran scanreg/restore as suggested in help, again the problem is
still
there.

Anyone come across this problem before? I do not want to do a system
restore as I have current files not yet backed up.

Much appreciate any help!

Hi gentlemen,

Do you have a System Restore point to just before the install of the
problem
causing apps?....if so, I would recommend Restoring to that point and
installing only one of the apps and then checking your machine before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).
To try this out will mean taking a big risk as to whether I can control the
ability to restore in a limited basis. When I loaded System Restore disk I
was afraid of selecting to restore as this action may be refersable once
selected. If I new there is a custom restore I could select I would be
confident to try it out.

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be scanreg
/restore.....note the space between the "g" and the "/" and don't use
the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about 5
choices of reg dates to choose from....dates from successful boots).

Sorry I omited the space between "g" and the "/" in my last post. I did
indeed have 5 choices of reg dates to choose from.

If it reports major problems, copy your important data to another drive
(or
CD-R) before attempting to write (surface scan) to the disk.

How can I do this? when I am unable to get into windows to carry this out.

Pat


"Mart" wrote in message
...
If, after following HL's excellent advice, you still can't make any
progress, then you could try running scandisk in Real Mode DOS. But be
aware
that you *might* just have a faulty hard drive and therefore you *might*
be
putting your data at risk.

Boot, using the WinMe Startup (floppy) Disk and select 'With CD-ROM
Support'
then at the A:\ prompt, type "scandisk c:" (no quotes and note the colon)
then press Return.

Follow the screen prompts - and for the first time at least, (unless you
are
happy that either the disk is OK, or you can sacrifice your data) tell it
NOT to do a Surface Scan. See what it reports and keep a check on its
progress.

If it reports major problems, copy your important data to another drive
(or
CD-R) before attempting to write (surface scan) to the disk.

Mart


"heirloom" wrote in message
...
Do you have a System Restore point to just before the install of the
problem
causing apps?....if so, I would recommend Restoring to that point and
installing only one of the apps and then checking your machine before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be scanreg
/restore.....note the space between the "g" and the "/" and don't use
the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about 5
choices of reg dates to choose from....dates from successful boots).
Heirloom, old and hope that helps


"Pat" wrote in message
...
Hi,

After installing two programs then rebooting WindowsME will not start.
Safemode will not start either. I then run scandisk and the problem was
identified 'Scandisk detected an invalid long filename entry on this
drive
but was unable to fix it' and 'To fix this problem run scandisk for
windows'

The problem is I am unable to run scandisk for windows because windows
will
not load.

I also ran scanreg/restore as suggested in help, again the problem is
still
there.

Anyone come across this problem before? I do not want to do a system
restore as I have current files not yet backed up.

Much appreciate any help!

Pat wrote :-

Sorry I omited the space between "g" and the "/" in my last
post.

Easily done!

I did indeed have 5 choices of reg dates to choose from.

So, presumably, they didn't resolve the problem - nor running scandisk
(excluding surface scan) in Real Mode DOS?

And so I guess that it therefore :-
.... reports major problems,

....... copy your important data to another drive (or CD-R)
before attempting to write (surface scan) to the disk.

How can I do this? when I am unable to get into windows to carry this out.

Either, using the copy and/or xcopy commands in Real Mode DOS (or better
still xxcopy from www.xxcopy.com), copying your important un-backed-up files
to a second (D:?) harddrive - or even floppies!!

Or, physically removing the 'suspect' drive and installing it as a second
drive in another PC (with a burner) and copying your files to a CD-R using
Windows.

N.B. You won't be able to get your burner (assuming you have one on your
existing PC) to burn in DOS - no burning software/drivers for DOS !

But hopefully, the data should still be 'recoverable' before you attempt to
write to or troubleshoot the disk. Only you can decide how important your
data is, compared to the effort involved g

HTH and good luck

Mart


"Pat" wrote in message
...
Hi gentlemen,

Do you have a System Restore point to just before the install of the
problem
causing apps?....if so, I would recommend Restoring to that point and
installing only one of the apps and then checking your machine before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).
To try this out will mean taking a big risk as to whether I can control
the
ability to restore in a limited basis. When I loaded System Restore disk I
was afraid of selecting to restore as this action may be refersable once
selected. If I new there is a custom restore I could select I would be
confident to try it out.

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be scanreg
/restore.....note the space between the "g" and the "/" and don't use
the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about 5
choices of reg dates to choose from....dates from successful boots).

Sorry I omited the space between "g" and the "/" in my last post. I did
indeed have 5 choices of reg dates to choose from.

If it reports major problems, copy your important data to another drive
(or
CD-R) before attempting to write (surface scan) to the disk.

How can I do this? when I am unable to get into windows to carry this out.

Pat


"Mart" wrote in message
...
If, after following HL's excellent advice, you still can't make any
progress, then you could try running scandisk in Real Mode DOS. But be
aware
that you *might* just have a faulty hard drive and therefore you *might*
be
putting your data at risk.

Boot, using the WinMe Startup (floppy) Disk and select 'With CD-ROM
Support'
then at the A:\ prompt, type "scandisk c:" (no quotes and note the
colon)
then press Return.

Follow the screen prompts - and for the first time at least, (unless you
are
happy that either the disk is OK, or you can sacrifice your data) tell it
NOT to do a Surface Scan. See what it reports and keep a check on its
progress.

If it reports major problems, copy your important data to another drive
(or
CD-R) before attempting to write (surface scan) to the disk.

Mart


"heirloom" wrote in message
...
Do you have a System Restore point to just before the install of the
problem
causing apps?....if so, I would recommend Restoring to that point and
installing only one of the apps and then checking your machine before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be scanreg
/restore.....note the space between the "g" and the "/" and don't use
the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about 5
choices of reg dates to choose from....dates from successful boots).
Heirloom, old and hope that helps


"Pat" wrote in message
...
Hi,

After installing two programs then rebooting WindowsME will not start.
Safemode will not start either. I then run scandisk and the problem
was
identified 'Scandisk detected an invalid long filename entry on this
drive
but was unable to fix it' and 'To fix this problem run scandisk for
windows'

The problem is I am unable to run scandisk for windows because windows
will
not load.

I also ran scanreg/restore as suggested in help, again the problem is
still
there.

Anyone come across this problem before? I do not want to do a system
restore as I have current files not yet backed up.

Much appreciate any help!

Actually, I was referring to System Restore (Start, Programs, Accessories,
System Tools, System Restore), NOT your OEM Restoration disks....these will
put your machine back to the state it was when you bought it. A System
Restore point just before you installed the two offending apps would
(should) not impact any of your data.
Heirloom, old and must get breakfast


"Mart" wrote in message
...
Pat wrote :-

Sorry I omited the space between "g" and the "/" in my last
post.

Easily done!

I did indeed have 5 choices of reg dates to choose from.

So, presumably, they didn't resolve the problem - nor running scandisk
(excluding surface scan) in Real Mode DOS?

And so I guess that it therefore :-
.... reports major problems,

....... copy your important data to another drive (or CD-R)
before attempting to write (surface scan) to the disk.

How can I do this? when I am unable to get into windows to carry this
out.

Either, using the copy and/or xcopy commands in Real Mode DOS (or better
still xxcopy from www.xxcopy.com), copying your important un-backed-up
files
to a second (D:?) harddrive - or even floppies!!

Or, physically removing the 'suspect' drive and installing it as a second
drive in another PC (with a burner) and copying your files to a CD-R using
Windows.

N.B. You won't be able to get your burner (assuming you have one on your
existing PC) to burn in DOS - no burning software/drivers for DOS !

But hopefully, the data should still be 'recoverable' before you attempt
to
write to or troubleshoot the disk. Only you can decide how important your
data is, compared to the effort involved g

HTH and good luck

Mart


"Pat" wrote in message
...
Hi gentlemen,

Do you have a System Restore point to just before the install of the
problem
causing apps?....if so, I would recommend Restoring to that point and
installing only one of the apps and then checking your machine before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).
To try this out will mean taking a big risk as to whether I can control
the
ability to restore in a limited basis. When I loaded System Restore disk
I
was afraid of selecting to restore as this action may be refersable once
selected. If I new there is a custom restore I could select I would be
confident to try it out.

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be
scanreg
/restore.....note the space between the "g" and the "/" and don't
use
the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about
5
choices of reg dates to choose from....dates from successful boots).

Sorry I omited the space between "g" and the "/" in my last post. I did
indeed have 5 choices of reg dates to choose from.

If it reports major problems, copy your important data to another drive
(or
CD-R) before attempting to write (surface scan) to the disk.

How can I do this? when I am unable to get into windows to carry this
out.

Pat


"Mart" wrote in message
...
If, after following HL's excellent advice, you still can't make any
progress, then you could try running scandisk in Real Mode DOS. But be
aware
that you *might* just have a faulty hard drive and therefore you
*might*
be
putting your data at risk.

Boot, using the WinMe Startup (floppy) Disk and select 'With CD-ROM
Support'
then at the A:\ prompt, type "scandisk c:" (no quotes and note the
colon)
then press Return.

Follow the screen prompts - and for the first time at least, (unless
you
are
happy that either the disk is OK, or you can sacrifice your data) tell
it
NOT to do a Surface Scan. See what it reports and keep a check on its
progress.

If it reports major problems, copy your important data to another drive
(or
CD-R) before attempting to write (surface scan) to the disk.

Mart


"heirloom" wrote in message
...
Do you have a System Restore point to just before the install of the
problem
causing apps?....if so, I would recommend Restoring to that point and
installing only one of the apps and then checking your machine before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be
scanreg
/restore.....note the space between the "g" and the "/" and don't
use
the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about
5
choices of reg dates to choose from....dates from successful boots).
Heirloom, old and hope that helps


"Pat" wrote in message
...
Hi,

After installing two programs then rebooting WindowsME will not
start.
Safemode will not start either. I then run scandisk and the problem
was
identified 'Scandisk detected an invalid long filename entry on this
drive
but was unable to fix it' and 'To fix this problem run scandisk for
windows'

The problem is I am unable to run scandisk for windows because
windows
will
not load.

I also ran scanreg/restore as suggested in help, again the problem
is
still
there.

Anyone come across this problem before? I do not want to do a
system
restore as I have current files not yet backed up.

Much appreciate any help!

Hi HL - good point!

I have to admit that I missed that paragraph in Pat's third post - too many
chevrons g or a case of seeing only what I wanted to? bg

must get breakfast Full English I trust g

Dinner (or Supper) time here of course.

Mart


"heirloom" wrote in message
...
Actually, I was referring to System Restore (Start, Programs, Accessories,
System Tools, System Restore), NOT your OEM Restoration disks....these
will
put your machine back to the state it was when you bought it. A System
Restore point just before you installed the two offending apps would
(should) not impact any of your data.
Heirloom, old and must get breakfast


"Mart" wrote in message
...
Pat wrote :-

Sorry I omited the space between "g" and the "/" in my last
post.

Easily done!

I did indeed have 5 choices of reg dates to choose from.

So, presumably, they didn't resolve the problem - nor running scandisk
(excluding surface scan) in Real Mode DOS?

And so I guess that it therefore :-
.... reports major problems,

....... copy your important data to another drive (or CD-R)
before attempting to write (surface scan) to the disk.

How can I do this? when I am unable to get into windows to carry this
out.

Either, using the copy and/or xcopy commands in Real Mode DOS (or better
still xxcopy from www.xxcopy.com), copying your important un-backed-up
files
to a second (D:?) harddrive - or even floppies!!

Or, physically removing the 'suspect' drive and installing it as a second
drive in another PC (with a burner) and copying your files to a CD-R
using
Windows.

N.B. You won't be able to get your burner (assuming you have one on your
existing PC) to burn in DOS - no burning software/drivers for DOS !

But hopefully, the data should still be 'recoverable' before you attempt
to
write to or troubleshoot the disk. Only you can decide how important your
data is, compared to the effort involved g

HTH and good luck

Mart


"Pat" wrote in message
...
Hi gentlemen,

Do you have a System Restore point to just before the install of the
problem
causing apps?....if so, I would recommend Restoring to that point
and
installing only one of the apps and then checking your machine
before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).
To try this out will mean taking a big risk as to whether I can control
the
ability to restore in a limited basis. When I loaded System Restore
disk
I
was afraid of selecting to restore as this action may be refersable
once
selected. If I new there is a custom restore I could select I would be
confident to try it out.

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be
scanreg
/restore.....note the space between the "g" and the "/" and don't
use
the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about
5
choices of reg dates to choose from....dates from successful boots).

Sorry I omited the space between "g" and the "/" in my last post. I did
indeed have 5 choices of reg dates to choose from.

If it reports major problems, copy your important data to another
drive
(or
CD-R) before attempting to write (surface scan) to the disk.

How can I do this? when I am unable to get into windows to carry this
out.

Pat


"Mart" wrote in message
...
If, after following HL's excellent advice, you still can't make any
progress, then you could try running scandisk in Real Mode DOS. But be
aware
that you *might* just have a faulty hard drive and therefore you
*might*
be
putting your data at risk.

Boot, using the WinMe Startup (floppy) Disk and select 'With CD-ROM
Support'
then at the A:\ prompt, type "scandisk c:" (no quotes and note the
colon)
then press Return.

Follow the screen prompts - and for the first time at least, (unless
you
are
happy that either the disk is OK, or you can sacrifice your data) tell
it
NOT to do a Surface Scan. See what it reports and keep a check on its
progress.

If it reports major problems, copy your important data to another
drive
(or
CD-R) before attempting to write (surface scan) to the disk.

Mart


"heirloom" wrote in message
...
Do you have a System Restore point to just before the install of the
problem
causing apps?....if so, I would recommend Restoring to that point
and
installing only one of the apps and then checking your machine
before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be
scanreg
/restore.....note the space between the "g" and the "/" and don't
use
the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about
5
choices of reg dates to choose from....dates from successful boots).
Heirloom, old and hope that helps


"Pat" wrote in message
...
Hi,

After installing two programs then rebooting WindowsME will not
start.
Safemode will not start either. I then run scandisk and the problem
was
identified 'Scandisk detected an invalid long filename entry on
this
drive
but was unable to fix it' and 'To fix this problem run scandisk for
windows'

The problem is I am unable to run scandisk for windows because
windows
will
not load.

I also ran scanreg/restore as suggested in help, again the problem
is
still
there.

Anyone come across this problem before? I do not want to do a
system
restore as I have current files not yet backed up.

Much appreciate any help!

Actually, I was referring to System Restore (Start, Programs, Accessories,
System Tools, System Restore)

That is good advise but its not possible in my case, because the computer
will not boot to windows.

Pat

"heirloom" wrote in message
...
Actually, I was referring to System Restore (Start, Programs, Accessories,
System Tools, System Restore), NOT your OEM Restoration disks....these
will
put your machine back to the state it was when you bought it. A System
Restore point just before you installed the two offending apps would
(should) not impact any of your data.
Heirloom, old and must get breakfast


"Mart" wrote in message
...
Pat wrote :-

Sorry I omited the space between "g" and the "/" in my last
post.

Easily done!

I did indeed have 5 choices of reg dates to choose from.

So, presumably, they didn't resolve the problem - nor running scandisk
(excluding surface scan) in Real Mode DOS?

And so I guess that it therefore :-
.... reports major problems,

....... copy your important data to another drive (or CD-R)
before attempting to write (surface scan) to the disk.

How can I do this? when I am unable to get into windows to carry this
out.

Either, using the copy and/or xcopy commands in Real Mode DOS (or better
still xxcopy from www.xxcopy.com), copying your important un-backed-up
files
to a second (D:?) harddrive - or even floppies!!

Or, physically removing the 'suspect' drive and installing it as a
second
drive in another PC (with a burner) and copying your files to a CD-R
using
Windows.

N.B. You won't be able to get your burner (assuming you have one on your
existing PC) to burn in DOS - no burning software/drivers for DOS !

But hopefully, the data should still be 'recoverable' before you attempt
to
write to or troubleshoot the disk. Only you can decide how important
your
data is, compared to the effort involved g

HTH and good luck

Mart


"Pat" wrote in message
...
Hi gentlemen,

Do you have a System Restore point to just before the install of
the
problem
causing apps?....if so, I would recommend Restoring to that point
and
installing only one of the apps and then checking your machine
before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).
To try this out will mean taking a big risk as to whether I can
control
the
ability to restore in a limited basis. When I loaded System Restore
disk
I
was afraid of selecting to restore as this action may be refersable
once
selected. If I new there is a custom restore I could select I would be
confident to try it out.

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be
scanreg
/restore.....note the space between the "g" and the "/" and don't
use
the
"", of course. Threw that in just because you didn't mention
any
particulars, just that it didn't work. You should have gotten
about
5
choices of reg dates to choose from....dates from successful
boots).

Sorry I omited the space between "g" and the "/" in my last post. I
did
indeed have 5 choices of reg dates to choose from.

If it reports major problems, copy your important data to another
drive
(or
CD-R) before attempting to write (surface scan) to the disk.

How can I do this? when I am unable to get into windows to carry this
out.

Pat


"Mart" wrote in message
...
If, after following HL's excellent advice, you still can't make any
progress, then you could try running scandisk in Real Mode DOS. But
be
aware
that you *might* just have a faulty hard drive and therefore you
*might*
be
putting your data at risk.

Boot, using the WinMe Startup (floppy) Disk and select 'With CD-ROM
Support'
then at the A:\ prompt, type "scandisk c:" (no quotes and note the
colon)
then press Return.

Follow the screen prompts - and for the first time at least, (unless
you
are
happy that either the disk is OK, or you can sacrifice your data)
tell
it
NOT to do a Surface Scan. See what it reports and keep a check on its
progress.

If it reports major problems, copy your important data to another
drive
(or
CD-R) before attempting to write (surface scan) to the disk.

Mart


"heirloom" wrote in message
...
Do you have a System Restore point to just before the install of
the
problem
causing apps?....if so, I would recommend Restoring to that point
and
installing only one of the apps and then checking your machine
before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be
scanreg
/restore.....note the space between the "g" and the "/" and don't
use
the
"", of course. Threw that in just because you didn't mention
any
particulars, just that it didn't work. You should have gotten
about
5
choices of reg dates to choose from....dates from successful
boots).
Heirloom, old and hope that helps


"Pat" wrote in message
...
Hi,

After installing two programs then rebooting WindowsME will not
start.
Safemode will not start either. I then run scandisk and the
problem
was
identified 'Scandisk detected an invalid long filename entry on
this
drive
but was unable to fix it' and 'To fix this problem run scandisk
for
windows'

The problem is I am unable to run scandisk for windows because
windows
will
not load.

I also ran scanreg/restore as suggested in help, again the problem
is
still
there.

Anyone come across this problem before? I do not want to do a
system
restore as I have current files not yet backed up.

Much appreciate any help!

Either, using the copy and/or xcopy commands in Real Mode DOS (or better
still xxcopy from www.xxcopy.com), copying your important un-backed-up
files
to a second (D:?) harddrive - or even floppies!!

This is an interesting suggestion, only I think I would need to have xxcopy
installed on the computer first of all. Transfering xxcopy from another
computer by floppy is not possible as there is no floppy drive available.

Or, physically removing the 'suspect' drive and installing it as a second
drive in another PC (with a burner) and copying your files to a CD-R using
Windows

I think this is the way I should go, only I think I will need professional
help to carry this out.

Pat

"Mart" wrote in message
...
Pat wrote :-

Sorry I omited the space between "g" and the "/" in my last
post.

Easily done!

I did indeed have 5 choices of reg dates to choose from.

So, presumably, they didn't resolve the problem - nor running scandisk
(excluding surface scan) in Real Mode DOS?

And so I guess that it therefore :-
.... reports major problems,

....... copy your important data to another drive (or CD-R)
before attempting to write (surface scan) to the disk.

How can I do this? when I am unable to get into windows to carry this
out.

Either, using the copy and/or xcopy commands in Real Mode DOS (or better
still xxcopy from www.xxcopy.com), copying your important un-backed-up
files
to a second (D:?) harddrive - or even floppies!!

Or, physically removing the 'suspect' drive and installing it as a second
drive in another PC (with a burner) and copying your files to a CD-R using
Windows.

N.B. You won't be able to get your burner (assuming you have one on your
existing PC) to burn in DOS - no burning software/drivers for DOS !

But hopefully, the data should still be 'recoverable' before you attempt
to
write to or troubleshoot the disk. Only you can decide how important your
data is, compared to the effort involved g

HTH and good luck

Mart


"Pat" wrote in message
...
Hi gentlemen,

Do you have a System Restore point to just before the install of the
problem
causing apps?....if so, I would recommend Restoring to that point and
installing only one of the apps and then checking your machine before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).
To try this out will mean taking a big risk as to whether I can control
the
ability to restore in a limited basis. When I loaded System Restore disk
I
was afraid of selecting to restore as this action may be refersable once
selected. If I new there is a custom restore I could select I would be
confident to try it out.

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be
scanreg
/restore.....note the space between the "g" and the "/" and don't
use
the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about
5
choices of reg dates to choose from....dates from successful boots).

Sorry I omited the space between "g" and the "/" in my last post. I did
indeed have 5 choices of reg dates to choose from.

If it reports major problems, copy your important data to another drive
(or
CD-R) before attempting to write (surface scan) to the disk.

How can I do this? when I am unable to get into windows to carry this
out.

Pat


"Mart" wrote in message
...
If, after following HL's excellent advice, you still can't make any
progress, then you could try running scandisk in Real Mode DOS. But be
aware
that you *might* just have a faulty hard drive and therefore you
*might*
be
putting your data at risk.

Boot, using the WinMe Startup (floppy) Disk and select 'With CD-ROM
Support'
then at the A:\ prompt, type "scandisk c:" (no quotes and note the
colon)
then press Return.

Follow the screen prompts - and for the first time at least, (unless
you
are
happy that either the disk is OK, or you can sacrifice your data) tell
it
NOT to do a Surface Scan. See what it reports and keep a check on its
progress.

If it reports major problems, copy your important data to another drive
(or
CD-R) before attempting to write (surface scan) to the disk.

Mart


"heirloom" wrote in message
...
Do you have a System Restore point to just before the install of the
problem
causing apps?....if so, I would recommend Restoring to that point and
installing only one of the apps and then checking your machine before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be
scanreg
/restore.....note the space between the "g" and the "/" and don't
use
the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about
5
choices of reg dates to choose from....dates from successful boots).
Heirloom, old and hope that helps


"Pat" wrote in message
...
Hi,

After installing two programs then rebooting WindowsME will not
start.
Safemode will not start either. I then run scandisk and the problem
was
identified 'Scandisk detected an invalid long filename entry on this
drive
but was unable to fix it' and 'To fix this problem run scandisk for
windows'

The problem is I am unable to run scandisk for windows because
windows
will
not load.

I also ran scanreg/restore as suggested in help, again the problem
is
still
there.

Anyone come across this problem before? I do not want to do a
system
restore as I have current files not yet backed up.

Much appreciate any help!

.... I think I will need professional
help to carry this out.

Probably so, unless you've got a 'computer geek' neighbour - usually the
spotty 14 year-old kid from next door g

... there is no floppy drive available. ?? On your faulty PC???

In which case, my previous advice Startup floppy Disk and Real Mode DOS
was irrelevant g

I strongly recommend you consider that now might be a good time to fit a
floppy drive, they are only a few US $'s - Ah! you're from the UK - a few
£'s. - £6.99 at Dabs.com or £12.99 at Maplins

Mart


"Pat" wrote in message
...
Either, using the copy and/or xcopy commands in Real Mode DOS (or better
still xxcopy from www.xxcopy.com), copying your important un-backed-up
files
to a second (D:?) harddrive - or even floppies!!

This is an interesting suggestion, only I think I would need to have
xxcopy
installed on the computer first of all. Transfering xxcopy from another
computer by floppy is not possible as there is no floppy drive available.

Or, physically removing the 'suspect' drive and installing it as a second
drive in another PC (with a burner) and copying your files to a CD-R
using
Windows

I think this is the way I should go, only I think I will need professional
help to carry this out.

Pat

"Mart" wrote in message
...
Pat wrote :-

Sorry I omited the space between "g" and the "/" in my last
post.

Easily done!

I did indeed have 5 choices of reg dates to choose from.

So, presumably, they didn't resolve the problem - nor running scandisk
(excluding surface scan) in Real Mode DOS?

And so I guess that it therefore :-
.... reports major problems,

....... copy your important data to another drive (or CD-R)
before attempting to write (surface scan) to the disk.

How can I do this? when I am unable to get into windows to carry this
out.

Either, using the copy and/or xcopy commands in Real Mode DOS (or better
still xxcopy from www.xxcopy.com), copying your important un-backed-up
files
to a second (D:?) harddrive - or even floppies!!

Or, physically removing the 'suspect' drive and installing it as a second
drive in another PC (with a burner) and copying your files to a CD-R
using
Windows.

N.B. You won't be able to get your burner (assuming you have one on your
existing PC) to burn in DOS - no burning software/drivers for DOS !

But hopefully, the data should still be 'recoverable' before you attempt
to
write to or troubleshoot the disk. Only you can decide how important your
data is, compared to the effort involved g

HTH and good luck

Mart


"Pat" wrote in message
...
Hi gentlemen,

Do you have a System Restore point to just before the install of the
problem
causing apps?....if so, I would recommend Restoring to that point
and
installing only one of the apps and then checking your machine
before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).
To try this out will mean taking a big risk as to whether I can control
the
ability to restore in a limited basis. When I loaded System Restore
disk
I
was afraid of selecting to restore as this action may be refersable
once
selected. If I new there is a custom restore I could select I would be
confident to try it out.

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be
scanreg
/restore.....note the space between the "g" and the "/" and don't
use
the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about
5
choices of reg dates to choose from....dates from successful boots).

Sorry I omited the space between "g" and the "/" in my last post. I did
indeed have 5 choices of reg dates to choose from.

If it reports major problems, copy your important data to another
drive
(or
CD-R) before attempting to write (surface scan) to the disk.

How can I do this? when I am unable to get into windows to carry this
out.

Pat


"Mart" wrote in message
...
If, after following HL's excellent advice, you still can't make any
progress, then you could try running scandisk in Real Mode DOS. But be
aware
that you *might* just have a faulty hard drive and therefore you
*might*
be
putting your data at risk.

Boot, using the WinMe Startup (floppy) Disk and select 'With CD-ROM
Support'
then at the A:\ prompt, type "scandisk c:" (no quotes and note the
colon)
then press Return.

Follow the screen prompts - and for the first time at least, (unless
you
are
happy that either the disk is OK, or you can sacrifice your data) tell
it
NOT to do a Surface Scan. See what it reports and keep a check on its
progress.

If it reports major problems, copy your important data to another
drive
(or
CD-R) before attempting to write (surface scan) to the disk.

Mart


"heirloom" wrote in message
...
Do you have a System Restore point to just before the install of the
problem
causing apps?....if so, I would recommend Restoring to that point
and
installing only one of the apps and then checking your machine
before
installing the other (since you don't know which app is causing the
issue
or
if it is a combination of the two).

Also, if you, indeed, tried scanreg/restore as stated in your
post.....that is an incorrect syntax.....the command should be
scanreg
/restore.....note the space between the "g" and the "/" and don't
use
the
"", of course. Threw that in just because you didn't mention any
particulars, just that it didn't work. You should have gotten about
5
choices of reg dates to choose from....dates from successful boots).
Heirloom, old and hope that helps


"Pat" wrote in message
...
Hi,

After installing two programs then rebooting WindowsME will not
start.
Safemode will not start either. I then run scandisk and the problem
was
identified 'Scandisk detected an invalid long filename entry on
this
drive
but was unable to fix it' and 'To fix this problem run scandisk for
windows'

The problem is I am unable to run scandisk for windows because
windows
will
not load.

I also ran scanreg/restore as suggested in help, again the problem
is
still
there.

Anyone come across this problem before? I do not want to do a
system
restore as I have current files not yet backed up.

Much appreciate any help!