Ron,

Do you have any update on this problem?

Gary S. Terhune
MS MVP Shell/User

"Gary S. Terhune" wrote in message
...
I don't know, precisely, the answer to your question. I'll have to look
into it.
In the mean time, look in the BIOS settings to make sure it's all proper.
I
suspect the problem starts there. Next, I'd go into Safe Mode, Device
Manager,
and see what's what. Looking for references to an LS-120, and also for
other
entries that might be obsolete, and/or duplicated entries -- some are
expected,
others aren't. We want to know which items are duplicated (exact
duplicates) and
how many of each instance. I'd probably delete the floppy controller and
floppy
drive (plus anything that smacks of the LS-120) and then restart to
reinstall.

I remember little about LS-120s, so I'll study up. But I won't be back
here for
another 24 hours, just so you know. At this time, I'd recommend against
editing
the Registry directly.

--
Gary S. Terhune
MS-MVP Shell/User

"Ron Estes" wrote in message
...
In checking Registry it appears floppy "thinks" it is a Superdisk LS-120
which was previously installed in computer and now replaced with
original
1.4 MB floppy. I find all kind of references to this when I search
"LS-120"
in registry. This seems to be the problem. What is the best way to
remove
these references and restore registry to standard floppy drive ? ? ?
Can I
just delete them ? ? ? TIA


--------------------------------------------------------------------------
--

--------------------------------------------------------------------------
--
----------

"Gary S. Terhune" wrote in message
...
All I can think is that the original installation somehow "installed"
one
or
more components to the A:\ drive--or thinks it did. It's looking for
components
or instructions from the FD and when they're not found, it just keeps
trying.
Or, perhaps, some kind of redirection is involved, some kind of
drive-letter
substitution app? Very strange, and I'm sorry but I don't see anything
I
can
further help with.

I'm not saying I could fix it if I were on the scene, but I'd probably
be
looking at a set of "deep clean" procedures, maybe installing
Retrospect
to a
test system in order to take before and after snapshots of the system
so I
could
track down the possible error, or at least remove all traces and try
again. I
think that's your critical hint, he You need to make sure *all*
traces
of
previous installations of Retrospect have been erased, since it is
typical
of
uninstallers to leave old configuration data behind. We've covered the
Registry
in so far as gross references to the FD are concerned (though more
subtle
references may still exist), so I'd also be looking for INI or other
configuration files that belong to Retrospect, like in the Application
Data or,
perhaps, Common Files sections.

One or more of the Process Viewer type utilities might also help.
Figure
out
what's being called when this thrashing is going on, but it's been a
while
since
I did that kind of detective work, so I don't have any good
instructions
for you
to follow. My favorite place for such diagnostic utilities is
http://www.sysinternals.com/Utilities.html

--
Gary S. Terhune
MS-MVP Shell/User


"Ron Estes" wrote in message
...
Here is the latest I have tried:

Disabled FD Drive in BIOS.

When FD Drive is disabled Retrospect 6.5 seems to load
properly
from
CD BUT after reboot the computer freezes on trying to "Configure
Retrospect"
. Ctl-Alt-Del does not work and I have to turn off power and come up
again.

When FD Drive is disabled and Retrospect 6.5 is opened,
initial
screen comes up but computer "freezes" and Ctl-Alt-Del shows
"Retrospect
Not
Responding".

When FD Drive is disabled it is impossible to remove
Retrospect
using Add/Remove Programs from under Control Panel. Program removal
"freezes" part way through and Ctl-Alt-Del does not work. Only
solution
to
get out of this one is to turn off power and come up again
?????????????????????????????

All other programs load properly and computer functions very
well
EXCEPT for trying to use Retrospect. The FD Drive continues to
"hunt"
when
trying to run Retrospect. If it is disabled, Retrospect doesn't like
it
. .
.

Any other ideas will be greatly apprciated ! ! !





-------------------------------------------------------------------------
-
--


-------------------------------------------------------------------------
-
--
---
"Ron Estes" wrote in message
...
I have tried uninstalling Retrospect Express 6.5 numerous times
after
trying
various options. So far it still causes the floppy drive to hunt
with
a
big
"grunt" or just run intermittently when a blank disk is inserted . .
..

"Gary S. Terhune" wrote in message
...
Have you tried completely removing Retrospect and then
reinstalling?
I
have
assumed so, but it never hurts to ask.

--
Gary S. Terhune
MS-MVP Shell/User

"Ron Estes" wrote in message
...
Removed all references to "a" as indicated - Didn't solve
problem.
Floopy runs intermittently with a blank disk in drive - 3
seconds
ON, 1
second OFF.
Disabled all of Find Fast - Didn't help.
Ran MRU Blaster - Didn't work.

I anyone has any more ideas they will be greatly
appreciaated.
TIA


"Gary S. Terhune" wrote in message
...
Ron,

Sorry, I meant to get back to you sooner, but I got lost on the
way.

First thing I think you should try is to delete all references
to
the
A:\
drive
in the Registry using REGEDIT (StartRunREGEDIT). Go to Edit
menu,
Find,
and
search only for Data and enter "a:\" (a-colon-backslash).
Delete
any
Registry
values you find with data that starts with "a:\"

If that doesn't do it, then I'll load Retrospect to see what I
can
see.
Oh, and
what happens if you put a blank floppy into the drive before
opening
Retrospect?

--
Gary S. Terhune
MS-MVP Shell/User

"Ron Estes" wrote in message
...

Floppy starts seeking as soon as Retrospect Express 6.5 is
opened.
I've
been round & round with dantz software on this one and they
have
been
no
help.
TIA