Uninstalling

12 years, wow, you should be there with FD from the very beginning and among the first squad of adopters. It was then surely very exciting to drive ze jowel in its early dévelopment.

Here, I was a late bloomer I bought it from raxco in april 2007 for US $55.96 !! Quelle aubaine "Your payment will be handled by our payment processor BIBIT. This charge may appear on your statement as "ASKNET-SHOPS.COM" or as "Bibit"... FD-ISR_Workstation_v3.21.202.exe

The scripter story's ending would have surely love, like us all, to write some happier continuing scénarii I don't know Todd that much but the some email exchanges I had proved him as a true classy gentleman.

 

Yes, I use it on my test/play machine for some months now and never gave me any problems.

Panagiotis

 

Hi Panagiotis

I tried twice, following your tutorial. Both times, the FD-ISR manager was not usable (error message "FD manager stopped working. Do you want to close it ?"). And the system (7x64) froze to the point I had no choice but to make a hard reboot and use the AX64 recovery CD. Too bad...

 

Strange.
Could be related to the security settings (ownership) of the "System Volume Information\AXTrack*****.dat" file...

Panagiotis

 

Ruinebabine, did you have FDISR installed at the same time with AX64? There is a way to make them work together, pandlouk has described it somewhere, but otherwise they are incompatible. Maybe their conflict (if indeed you had them both installed) is what caused your problem.

Acadia

 

Hi Acadia, I followed the instructions given by pandlouk at
https://www.wilderssecurity.com/showpost.php?p=2272981&postcount=23

I will try again and check the AX64 tracking dat-file's ownership and report back here.

 

I am running this system as admin. Should not have any file's ownership in this situation, isn't it ? Or am I wrong ?

edit
I tried again. And checking the "AXTrack{*}.dat" file ownership, there was only a "system" account (with all being allowed). I added an admin account with all the boxes ticked, but don't know if it was necessary or not. But anyways nothing changed: FD-ISR Manager can't start, only the FD's console was available then. ISR services were running though.

 

Did you already have a secondary FD_ISR snapshot?
Was AX64 running at the time?
Did you reboot afterwords?

Post a screenshot of the error that you receive and a log of FD-ISR.

Panagiotis

 

Ok, I shall try again later this week and I will report back.

 

Still here..
Watching, watching ...

Going through same uncertainties as well...
OS needs update soon ..
HW needs update soon ..
Very hard to grok no FDISR
Panagiotis you rule

 

I tried again (twice). FD-ISR and the system were not freezing this time.

No and when I tried to build one from the primary I receive this error message
http://img11.hostingpics.net/pics/489641Snap2013112109h50m08s003.png
So I had to import an older one.

No, I make my backups manually (only AXtrack service was on).

Yes.

For the screenshot see above, and here is FD-ISR's log:

 

Ok, thanks.

error 1117 usually is referred to an I/O read error. Seems like FD-ISR encounters an error when trying to list the files and crashes and should not be related with the coexistence with AX64. Should not be a bad cluster, if your imaging apps (e.g. AX64) do not give any problems... more likely a file table problem.

Perform check-disk of your system partition try again.

Panagiotis

 

Thanks for your reply.

AX64 doesn't give any problem when FD-ISR is installed on the system.
I performed a checkdisk (using Puran's DiskFresh) on the partition and it gave on it a healthy clean bill.
Btw, FD-ISR always stops and spits the error message at the very end of the files listing, when it will try to start the process of copy files.

 

You are welcome.
Diskfresh won't help if there is a problem with the file table. You should perform a
chkdsk /f
on your system partition.

Panagiotis

 

Ok, I run CHKDSK /f /r.
I think it didn't find or correct any significant error but I know about zilch in this area...
Or do you think this scan result can imply a possible improvement for FD-ISR ?

Being there, I first used WD's Data Lifeguard Diagnostic to perform an Extended Scan on the drive but it found nothing, giving it a "PASS".

Anyway, I will probably try another install this week, hoping I'll be more lucky this time

 

The errors (3915 unused security descriptors, index entries, and the free space that was allocated) which chkdsk fixed and recovered, could cause the crash of FD-ISR indexing since the file table reported those files but FD-ISR could not index them because they were deleted/missing.

Panagiotis

 

Ok and thanks, but I tried again and FD stop copying the same way as before and gave me the dread error 1117 again.

In fact, I had to quit using FD-ISR because of this weird behavior. And I am working with AX64 since then. Really not the same "comfort" (in its infancy and dev. keeps going) but the more I keep using it the more I like it.

 

The original FirstDefense on an XP system ...

Acadia