A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » Disk Drives
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Floppy runs continuously when Retrospect Express is open



 
 
Thread Tools Display Modes
  #11  
Old September 20th 05, 08:52 AM
Gary S. Terhune
external usenet poster
 
Posts: n/a
Default

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















  #12  
Old September 23rd 05, 10:39 PM
Gary S. Terhune
external usenet poster
 
Posts: n/a
Default

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

















  #13  
Old September 24th 05, 08:45 PM
Ron Estes
external usenet poster
 
Posts: n/a
Default

Gary,
I have tried EVERYTHING suggested to no avail. I believe there is
something in the Retrospect Express 6.5 program that is causing the problem
as no other programs cause the floppy to hunt. It may that the program was
originally released on floppy disk and there is some reference to the "A"
drive ? ? ?
As a last resort I went into the BIOS, "Standard CMOS Features" and
turned drive "A" to None. ( I hate using rubber gloves to fix a leaky
fountain pen).
This, at least, stopped the hunting but I now have no floppy unless I
re-engage it in the BIOS when needed; not a very desirable way to operate.
I double checked the short-cuts to see if anything was referencing the
floppy - NO.
Thank you for all you help. If you think of anything else, please let
me know!
Ron Estes


"Gary S. Terhune" wrote in message
...
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



















  #14  
Old September 24th 05, 10:45 PM
Gary S. Terhune
external usenet poster
 
Posts: n/a
Default

Well, I'm in a bit of a messy situation, myself, right now, and haven't time
to do any experimenting. But I've run Retrospect on several machines and
never encountered this behavior. If I run into anymore ideas, I'll ping you.
I think I can decipher your real email from the below.

--
Gary S. Terhune
MS MVP Shell/User

"Ron Estes" wrote in message
...
Gary,
I have tried EVERYTHING suggested to no avail. I believe there is
something in the Retrospect Express 6.5 program that is causing the

problem
as no other programs cause the floppy to hunt. It may that the program

was
originally released on floppy disk and there is some reference to the "A"
drive ? ? ?
As a last resort I went into the BIOS, "Standard CMOS Features" and
turned drive "A" to None. ( I hate using rubber gloves to fix a leaky
fountain pen).
This, at least, stopped the hunting but I now have no floppy unless I
re-engage it in the BIOS when needed; not a very desirable way to operate.
I double checked the short-cuts to see if anything was referencing the
floppy - NO.
Thank you for all you help. If you think of anything else, please let
me know!
Ron Estes


"Gary S. Terhune" wrote in message
...
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





















  #15  
Old September 26th 05, 06:28 AM
glee
external usenet poster
 
Posts: n/a
Default

Have you looked to see if there is a shortcut in the Windows\Pif folder? If there
is, delete it.
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm


"Ron Estes" wrote in message
...
Gary,
I have tried EVERYTHING suggested to no avail. I believe there is
something in the Retrospect Express 6.5 program that is causing the problem
as no other programs cause the floppy to hunt. It may that the program was
originally released on floppy disk and there is some reference to the "A"
drive ? ? ?
As a last resort I went into the BIOS, "Standard CMOS Features" and
turned drive "A" to None. ( I hate using rubber gloves to fix a leaky
fountain pen).
This, at least, stopped the hunting but I now have no floppy unless I
re-engage it in the BIOS when needed; not a very desirable way to operate.
I double checked the short-cuts to see if anything was referencing the
floppy - NO.
Thank you for all you help. If you think of anything else, please let
me know!
Ron Estes


"Gary S. Terhune" wrote in message
...
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




















  #16  
Old September 26th 05, 09:58 PM
Ron Estes
external usenet poster
 
Posts: n/a
Default

Checked the Windows\Pif folder and found NO shortcuts to the "a" drive.
Again, any ideas GREATLY appreciated. TIA

"glee" wrote in message
...
Have you looked to see if there is a shortcut in the Windows\Pif folder?

If there
is, delete it.
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm


"Ron Estes" wrote in message
...
Gary,
I have tried EVERYTHING suggested to no avail. I believe there is
something in the Retrospect Express 6.5 program that is causing the

problem
as no other programs cause the floppy to hunt. It may that the program

was
originally released on floppy disk and there is some reference to the

"A"
drive ? ? ?
As a last resort I went into the BIOS, "Standard CMOS Features" and
turned drive "A" to None. ( I hate using rubber gloves to fix a leaky
fountain pen).
This, at least, stopped the hunting but I now have no floppy unless I
re-engage it in the BIOS when needed; not a very desirable way to

operate.
I double checked the short-cuts to see if anything was referencing

the
floppy - NO.
Thank you for all you help. If you think of anything else, please

let
me know!
Ron Estes


"Gary S. Terhune" wrote in message
...
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

rive - 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






















  #17  
Old September 27th 05, 12:33 AM
glee
external usenet poster
 
Posts: n/a
Default

Sounds like you have covered all the bases already :-(
To me, it has the sound of a configuration problem in the Retrospect program...being
a backup app, it seems to be checking for the existence of a floppy drive, or of a
disk in a floppy drive. I assume though that you have gone through all the possible
configs and associated registry entries for Retrospect already, and since I don't
have the program, I cannot add much of anything.

In you previous posts, you always say the drive accesses when there is a disk in it.
Does it do so also if there is no diskette in the floppy drive, when you run
Retrospect? That would have me wondering if you have the Registry bit set for
autorun on floppy drives.
http://www.ashzfall.com/products/aut...runfloppy.html
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm


"Ron Estes" wrote in message
...
Checked the Windows\Pif folder and found NO shortcuts to the "a" drive.
Again, any ideas GREATLY appreciated. TIA

"glee" wrote in message
...
Have you looked to see if there is a shortcut in the Windows\Pif folder?

If there
is, delete it.
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm


"Ron Estes" wrote in message
...
Gary,
I have tried EVERYTHING suggested to no avail. I believe there is
something in the Retrospect Express 6.5 program that is causing the

problem
as no other programs cause the floppy to hunt. It may that the program

was
originally released on floppy disk and there is some reference to the

"A"
drive ? ? ?
As a last resort I went into the BIOS, "Standard CMOS Features" and
turned drive "A" to None. ( I hate using rubber gloves to fix a leaky
fountain pen).
This, at least, stopped the hunting but I now have no floppy unless I
re-engage it in the BIOS when needed; not a very desirable way to

operate.
I double checked the short-cuts to see if anything was referencing

the
floppy - NO.
Thank you for all you help. If you think of anything else, please

let
me know!
Ron Estes


"Gary S. Terhune" wrote in message
...
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

rive - 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























  #18  
Old September 27th 05, 02:24 AM
Ron Estes
external usenet poster
 
Posts: n/a
Default

When Retrospect Express 6.5 is loaded the floppy immediately "hunts" or
"grunts" if NO DISKETTE is in the drive, and runs (3 seconds ON - 1 second
OFF) if there IS A DISKETTE in the drive ? ? ? Exiting the program causes
the drive to stop all activity.


"glee" wrote in message
...
Sounds like you have covered all the bases already :-(
To me, it has the sound of a configuration problem in the Retrospect

program...being
a backup app, it seems to be checking for the existence of a floppy drive,

or of a
disk in a floppy drive. I assume though that you have gone through all

the possible
configs and associated registry entries for Retrospect already, and since

I don't
have the program, I cannot add much of anything.

In you previous posts, you always say the drive accesses when there is a

disk in it.
Does it do so also if there is no diskette in the floppy drive, when you

run
Retrospect? That would have me wondering if you have the Registry bit set

for
autorun on floppy drives.
http://www.ashzfall.com/products/aut...runfloppy.html
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm


"Ron Estes" wrote in message
...
Checked the Windows\Pif folder and found NO shortcuts to the "a" drive.
Again, any ideas GREATLY appreciated. TIA

"glee" wrote in message
...
Have you looked to see if there is a shortcut in the Windows\Pif

folder?
If there
is, delete it.
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm


"Ron Estes" wrote in message
...
Gary,
I have tried EVERYTHING suggested to no avail. I believe there

is
something in the Retrospect Express 6.5 program that is causing the

problem
as no other programs cause the floppy to hunt. It may that the

program
was
originally released on floppy disk and there is some reference to

the
"A"
drive ? ? ?
As a last resort I went into the BIOS, "Standard CMOS Features"

and
turned drive "A" to None. ( I hate using rubber gloves to fix a

leaky
fountain pen).
This, at least, stopped the hunting but I now have no floppy unless

I
re-engage it in the BIOS when needed; not a very desirable way to

operate.
I double checked the short-cuts to see if anything was

referencing
the
floppy - NO.
Thank you for all you help. If you think of anything else,

please
let
me know!
Ron Estes


"Gary S. Terhune" wrote in message
...
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

rive - 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

























 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Windows 98 Starting in Dos: Missing Himem.sys elle General 31 May 22nd 05 05:36 PM
What is going on? BAP General 20 March 11th 05 01:25 PM
floppy issues barry martin General 0 December 20th 04 02:48 PM
Microsoft Security Bulletin MS04-018 - Cumulative Security Update for Outlook Express (823353) PA Bear General 5 July 15th 04 05:49 AM
Please help! Display settings !! Mitzi Monitors & Displays 12 July 11th 04 05:19 AM


All times are GMT +1. The time now is 07:58 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.