MBR is out of date

[Antarctica]

Hello,
Sometimes I get this message from FD ISR saying I should update the MBR. Any idea why and how to do that?

[tradetime]

No sorry, that's a new one on me. Which version of fd-isr is that?

[Eldar]

{QUOTE-> Sometimes I get this message from FD ISR saying I should update the MBR. Any idea why and how to do that? <-QUOTE}Wondering about that myself ???
Using the latest version 3.20 build 202.

[Antarctica]

{QUOTE-> No sorry, that's a new one on me. Which version of fd-isr is that? <-QUOTE}

Using the latest version.

Eldar, this is the exact same message I get. Glad to know I am not the only one.

[tradetime]

ok, that surprises me (but then many things about computers do :) ) since Fd-isr doesn't bother with mbr anymore, or so I thought. It seems a bit like telling you ur AV is out of date, afraid I can't help, but will be interesting to see what one of the experts has to say.

[Antarctica]

This is really strange because when I go in the Start Menu from FD ISR, as suggested by the message I don't see anything to "Create a new MBR"???

[tradetime]

{QUOTE-> This is really strange because when I go in the Start Menu from FD ISR, as suggested by the message I don't see anything to "Create a new MBR"??? <-QUOTE}
No I just looked throgh all the options myself, and see no reference to the MBR. As I sad b4 it was my uderstanding that fd-isr stopped messing with the MBR in this or a previous version, so I'm puzzled.

the command fdisk -u will update the mbr keeping all partitions.....I think....but have someone who knows what they are talking about confirm this before using it.

[Acadia]

Wonder if it could be a remnant of an older version left on our systems if we upgraded the newer version on top of the old version?

Acadia

[Antarctica]

{QUOTE-> Wonder if it could be a remnant of an older version left on our systems if we upgraded the newer version on top of the old version?

Acadia <-QUOTE}

Hi Acadia, as for myself I always do a clean install for any Software I upgrade.:)

[Acadia]

Then maybe they forgot to remove the coding for that feature when they made the latest version? :-\

Acadia

[Eldar]

{QUOTE-> Eldar, this is the exact same message I get. Glad to know I am not the only one. <-QUOTE}Yep, really strange since it doesn't use MBR anymore. ??? {QUOTE-> ok, that surprises me (but then many things about computers do :) ) since Fd-isr doesn't bother with mbr anymore, or so I thought. It seems a bit like telling you ur AV is out of date, afraid I can't help, but will be interesting to see what one of the experts has to say. <-QUOTE}No AV out of date, so that's not it.
Will try your other suggestion when confirmed by someone who knows it a bit better. Not doubting it may help, but better make sure before performing that command.
Anyway thanks for your help. ;){QUOTE-> Wonder if it could be a remnant of an older version left on our systems if we upgraded the newer version on top of the old version? <-QUOTE}Nope, uninstalled the previous version on my laptop running Windows MCE and upgraded to Vista.
Installed the latest FDISR-version, although it's always possible something was left behind. The question is what :-\

[tradetime]

{QUOTE-> Will try your other suggestion when confirmed by someone who knows it a bit better. <-QUOTE}Absolutely, be sure and get confirmation from someone who actually knows, someone like Peter, will be along in due course, and since he both uses fd-isr and understands computers vastly more than I do he likely can say whether that command would be of use or a seriously bad idea.

[Eldar]

{QUOTE-> the command fdisk -u will update the mbr keeping all partitions..... <-QUOTE}Just tried it for the fun ;D
It's an unknown command.

[Antarctica]

{QUOTE-> Just tried it for the fun ;D
It's an unknown command. <-QUOTE}

Gee, your'e brave man.;D

[Eldar]

{QUOTE-> Absolutely, be sure and get confirmation from someone who actually knows, someone like Peter, will be along in due course, and since he both uses fd-isr and understands computers vastly more than I do he likely can say whether that command would be of use or a seriously bad idea. <-QUOTE}Too late. ;D ;)
Will wait until Peter or someone else responds to this problem.
It's annoying, that's all, but for the rest FD-ISR works great. :)

[Eldar]

{QUOTE-> Gee, your'e brave man.;D <-QUOTE}No big deal, got my images to fall back on, in case it corrupts my system. :D 8)

[snapdragin]

Hi Antarctica,

The message that Elder posted above in Post 3 is referring to the option to update the MBR Backup floppy. In FD's menu, look under Help -> FirstDefence-ISR Manual -> Options -> MBR Backup Options, and it will explain about using the MBR Backup Wizard to make a copy of the MBR for safekeeping.

A reminder to occasionally make a new backup can be scheduled too.

Hope that helps,

Snap

[tradetime]

{QUOTE-> Hi Antarctica,

The message that Elder posted above in Post 3 is referring to the option to update the MBR Backup floppy. In FD's menu, look under Help -> FirstDefence-ISR Manual -> Options -> MBR Backup Options, and it will explain about using the MBR Backup Wizard to make a copy of the MBR for safekeeping.

A reminder to occasionally make a new backup can be scheduled too.

Hope that helps,

Snap <-QUOTE}
No can't see anything like that in my manual. I suspect that was a feature of the old fd-isr when it used to play with MBR.
Here's what's in my manual.

[stapp]

It is not mentioned anywhere, it only gave those instructions for the last build where you had to make a floppy.

[Eldar]

{QUOTE-> I suspect that was a feature of the old fd-isr when it used to play with MBR <-QUOTE}Yes, that was a feature in the previous version.
Can't find anything here. :-\

[Antarctica]

{QUOTE-> It is not mentioned anywhere, it only gave those instructions for the last build where you had to make a floppy. <-QUOTE}

Yeah, this is quite strange because I always do a "clean install" when I install new build.

@snapdragin, thanks for your help but as the others I can't see anything about the MBR in the Help Menu.

[ErikAlbert]

Sorry guys, I know FDISR pretty good, except when there are technical problems.
I hesitate to recommend "fixmbr", because I don't know anything about it.
Do at least some research on this command before you really use it and make sure you have a backup of your system.

The latest build has no MBR functions anymore, because you don't need them anymore.

[snapdragin]

Yes, it appears that the option to make a copy of the MBR was only available in the earlier version; not the latest one. Under "Tools -> Options" there was a tab called "MBR backup" which also gave you the option to schedule a reminder to make another backup of the MBR. That tab isn't available in the newer versions of FD. :-\

I'm not sure (it's been awhile) but I think a scheduled reminder was checked by default. It could be that even though you uninstalled the earlier version, the scheduled reminder might still be active from that previous version?

[tradetime]

Looking at the warning again, it says:
Your FirstDefence-ISR MBR Backup is out of date, so I would be wary of using any commands to alter your actual MBR. So since fd-isr no longer does MBR backups, or takes much interest in the MBR, could it be, if you had an older version of fd-isr on your system that there is an old MBR backup somewhere that it is detecting, or any other software that creates backups of your MBR that it can see?
Though from the image posted it clearly thinks it can still backupthe MBR, has to be something from an older version still interacting.

[stapp]

I kept the old MBR backup I made, with the instructions etc but as yet I haven't had a message like yours. I did uninstall previous version completely along with snapshots as I had a problem at the time with the copy engine, but I kept the MBR thing (don't know why!)

[Peter2150]

Snapdragin has it right. Used to be that you made a back floppy of the MBR, incase something went wrong, and you get back the original system mbr.

Since it was recommended that you refresh the floppy every six months the reminder. Really doesn't apply with the latest version. I bet they just forgot to take the reminder code out.

Not really issue for most of anyway, as quite a few of us use imaging software that gives the option to restore with either the image mbr or a standard windows mbr.

In any case if you are using the lastest version of FDISR, you can ignore that warning.

Pete

[Antarctica]

{QUOTE-> In any case if you are using the lastest version of FDISR, you can ignore that warning.

Pete <-QUOTE}

Thanks Pete. That's what I've been doing so far, ignoring the warning. It's just annoying.:o

[Eldar]

{QUOTE-> I bet they just forgot to take the reminder code out. <-QUOTE}That's what I've been thinking too. ;D {QUOTE-> Not really issue for most of anyway, as quite a few of us use imaging software that gives the option to restore with either the image mbr or a standard windows mbr. <-QUOTE}No issue here, so I'll wait for the next update to get that fixed.

Thanks Pete & everyone who responded. :)

P.s.: I know it's annoying Antarctica, but FD-ISR works, so that's what counts.
A minor bug. ;)

[Peter2150]

Latest option doesn't have the option to even make the MBR floppy. Are you folks seeing this warning using the latest version??

[Antarctica]

{QUOTE-> Latest option doesn't have the option to even make the MBR floppy. Are you folks seeing this warning using the latest version?? <-QUOTE}

Yes, latest version and clean install.

[lucas1985]

Does this reminder use the Windows' built-in task scheduler? I'd check there.

[Eldar]

{QUOTE-> Are you folks seeing this warning using the latest version?? <-QUOTE}Yes, the latest version and it was a clean install after removing the previous version from my previous OS. ::)

[Eldar]

{QUOTE-> Does this reminder use the Windows' built-in task scheduler? I'd check there. <-QUOTE}Going to check it later on, although I doubt it.
Otherwise sending a request to Support may probably give a definite answer to what we're seeing. :)

[ErikAlbert]

{QUOTE-> Yes, the latest version and it was a clean install after removing the previous version from my previous OS. ::) <-QUOTE}
I did the same thing :
1. Uninstalled the old version without removing the snapshots.
2. Installed the new version, with a full installation file.
I never saw that weird MBR-message.
The main reason why I installed the latest version so quickly : I wanted to see the new "Splash Screen".

[EASTER]

{QUOTE-> I wanted to see the new "Splash Screen". <-QUOTE}

Take your chances.

If any of this membership knows me, and some i have worked with on other forums as a HijackThis Specialist, i am strictly old-fashioned. If something works and works perfectly, i keep it just as-is and don't venture into subsequent releases unless absolutely neccessary.

The same applies to FD-ISR. I still use the old 166 version and since i will NEVER fall for the phony Longhorn/Vista craze, there is been no need whatsoever to ask for problems with a program that is proven itself as admirable/dependable as RAMSES, Pharoah of Ancient Egypt, and thats the way it's going to stay.

I still use Kerio 2.15, a real relic from the past that is NEVER ONCE given me the issues Zone Alarm, COMODO, Jetico and others have made and theres no reason to turn to any others.

Same with System Safety Monitor v.568, i stopped right there and then because it works to perfection plus theres no need for the network addition (DSA can fill in), or relearning the new settings and GUI all over again in that registry module.

I see clearly from all sections of these forums, users stumble over themselves to get on-board the latest and claimed greatest, new releases, but i managed to avoid a multitude of frustrations by keeping to what works even if it's years old, and thats the way things will stay in this camp.

I just tried the new CyberHawk-->PCTools ThreatFire and now i have to reformat for the first time in years due to a software program badly coded.

[Eldar]

{QUOTE-> Does this reminder use the Windows' built-in task scheduler? I'd check there. <-QUOTE}Just checked, nothing to be found there. :-\ {QUOTE-> The main reason why I installed the latest version so quickly : I wanted to see the new "Splash Screen". <-QUOTE}LOL, I'm not that curious about how it looks. The most important thing is that it works as it should. :thumb: :thumbd:
I only had to use the latest version, since it works on Vista, the other one NOT. {QUOTE-> The same applies to FD-ISR. I still use the old 166 version and since i will NEVER fall for the phony Longhorn/Vista craze <-QUOTE}Your decision, but Vista works fine here. :)
I always like to try out new things and Vista is one of them.
Also received my Vista upgrade for about 20 euro, so I would be a fool to let that go by. 8)

As long as it works for you, that's OK, but remember that whenever you've to buy a new computer it will only be available with the latest OS and nothing else.

With HIPS or any other security software, you always have to take your precautions. Had to delete a snapshot because of it, since my PC wouldn't start up anymore. :(

As for the problem at hand I'll send an email to their support, so they can have a look at it. There's nothing more we can do about it.

Thanks all. ;)

[lucas1985]

{QUOTE-> I still use Kerio 2.15, a real relic from the past that is NEVER ONCE given me the issues Zone Alarm, COMODO, Jetico and others have made and theres no reason to turn to any others. <-QUOTE}
Kerio 2.1.5 is a proven app, but it has some bugs in certain configurations. I'd like to know which bugs/issues Jetico (which version?) gave to you :)
{QUOTE-> Just checked, nothing to be found there. :-\ <-QUOTE}
I'm out of ideas now, will return later :)

[ronjor]

{QUOTE-> I'd like to know which bugs/issues Jetico (which version?) gave to you <-QUOTE}Please discuss that question in the other firewalls forum.

The "MBR is out of date" is the topic of this thread and it will be interesting to find the cause of the problem.

[Eldar]

Email has been sent to their support, so I'll keep you informed on their answer. ;)

[Antarctica]

{QUOTE-> Email has been sent to their support, so I'll keep you informed on their answer. ;) <-QUOTE}

Thanks Eldar.:)

[Huupi]

Thats strange i am on a older version .173 and never saw the message and refreshed never !

[Eldar]

{QUOTE-> Thanks Eldar.:) <-QUOTE}My pleasure Antarctica. ;)
My first email to supportdesk AT horizon-datasys.com came back as undeliverable after 5 tries, so instead I opened a ticket, although I couldn't select FDISR from the dropdown menu. I included the screenshot and a link to this topic.

Hope I'll get a response though. ::) {QUOTE-> Thats strange i am on a older version .173 and never saw the message and refreshed never ! <-QUOTE}That's strange, always got that message after some time.

BTW that message now appears on every restart of my system. :-\

[flimbag]

{QUOTE-> Thanks Pete. That's what I've been doing so far, ignoring the warning. It's just annoying.:o <-QUOTE}>

Especially when you see it umpteen times every day, as I do.

>:(

[tradetime]

{QUOTE-> BTW that message now appears on every restart of my system. <-QUOTE}
Hmmnn, now that would be annoying. May I ask how long after installation of fd-isr did it start, just wondering have I got it to look forward to :(

[Eldar]

{QUOTE-> Hmmnn, now that would be annoying. May I ask how long after installation of fd-isr did it start, just wondering have I got it to look forward to :( <-QUOTE}It just started last week, never seen it before. ::)

[tradetime]

{QUOTE-> It just started last week, never seen it before. ::) <-QUOTE}
....but when did you install this version of fd-isr?

[Acadia]

Good grief, this is something that possibly could start happening to ALL OF US eventually. :-\

Acadia

[Antarctica]

{QUOTE-> ....but when did you install this version of fd-isr? <-QUOTE}

As for myself this problem just started last week as Eldar and I did install the latest FD ISR version sometimes in April or May.

[Peter2150]

To the guys having an on going problem. Which vendor did you buy it from. If Raxco email them. I can give you a contact(please PM me) You will get a response.

Pete

[Eldar]

{QUOTE-> ....but when did you install this version of fd-isr? <-QUOTE}I installed the Vista compatible version in May 2007, so it seems to be a common factor as Antarctica mentionned. ???

I received the download link from Raxco Support after I asked for this new version. Maybe it's a bit the same version as the one you can download now.
Just guessing here. :-\

[Eldar]

{QUOTE-> To the guys having an on going problem. Which vendor did you buy it from. If Raxco email them. <-QUOTE}Pete, I bought the version from Raxco, but emailing won't help.
Just sent it to Mark from Raxco and he pointed out to address the issue to LeapFrog/Horizon-Datasys, so that's what I did.

Raxco no longer sells it, so they don't offer support for it anymore. :-\

[Huupi]

Just ignore,minor impact,have a good image at hand in case......,in latest version
MBR is untouched,so makes no sense to worry about.

[tradetime]

{QUOTE-> As for myself this problem just started last week as Eldar and I did install the latest FD ISR version sometimes in April or May. <-QUOTE}
{QUOTE-> I installed the Vista compatible version in May 2007, so it seems to be a common factor as Antarctica mentionned. <-QUOTE}
Thanx, guys, I installed on April 29th and so far have not seen this message.

[Peter2150]

{QUOTE-> Pete, I bought the version from Raxco, but emailing won't help.
Just sent it to Mark from Raxco and he pointed out to address the issue to LeapFrog/Horizon-Datasys, so that's what I did.

Raxco no longer sells it, so they don't offer support for it anymore. :-\ <-QUOTE}

Thats nonsense. See PM

[Eldar]

Thanks for the PM Pete. :)
Email has been sent, so I'll let you know.

Wonder why the other person redirected me to LeapFrog. ::)

[Leapfrog Software]

Greetings All,

This is a bug in the current x.202 versions. As many have guessed it is an annoying reminder message from a legacy feature. It has been fixed for future releases, but here is the solution for x.202:

1. Open the ..."ISR Control" CLI (There is a shortcut in the Start/Programs area for your *flavor* of the product.
2. Type in the following command: config erdage 0
3. That's it! You should get a return prompt saying "Forever". This will keep ISR from bugging you about the legacy MBR reminder.

-Todd

[EASTER]

Todd. You and your wonderfully thoughful and Xtremely talented Team AFAIK are nothing short of Legendary in this development of FD-ISR.

There are simply not enough compliments that could possibly match what your creation is meant to the computing/working world like you guys/gals have so finely fashioned.

The timing of your first releases onward have set an earmark for the world and is placed this SUPER rollback program at the very pinnacle of reliability and is done wonders for confidence on a level never before imagined.

I know many share in my wholehearted thanks to you AND your associates for making the impossible very possible and bringing a newfound design to light for this entire world to trust.

You guys and your product deserves more than but simple brief compliments, you are all so much well deserving of an award for the highest achievement that is worthy of the record books and is LEGENDARY. P.E.R.I.O.D.

Thank You and may the light of All good things always fall to your favor as a result of this generosity along with all those efforts you worked hard at that has made it all a reality worth noting.

EASTER

[Leapfrog Software]

Wow EASTER, you completely took me off-guard. I could cry; well almost ;)
Such kind comments. I am glad to see you enjoy the product. btw: I am emailing my development team your comments. I may even frame it!

It is us that bows to you. Without you guys, ISR would be, well, not-ISR. 10,000 thanks!

We are very busy at LSI wilth all sort of new development taking place. We are keeping the ISR flame going with new features and capabilities, but *hopefully* without the common problem of product bloat(simple is best).

Take care all

[EASTER]

Your Welcome. And that sentiment still stands. Your Team and yourself have done a gret service for the Windows computing world and all of you deserve the very BEST of compliment and appreciation.

It is 100% fact and a well-deserved credit to your own generosity (and development Team) for bringing something this magnificiently creative about for all the world to confidently turn to for confidence and reliability above ALL others.

EASTER

[Acadia]

Leapfrog, Easter speaks for all of us, he just knows how to word things. 8)

And if you can make FD even better WITHOUT bloat, we bow down to you! ;D

Acadia

[kennyboy]

Todd.

I second everything EASTER says, only he says it so beautifully I couldnt hope to compete.
Seriously, you are the sort of company that us users dream about to deal with, and thank heavens we found you.

You are a role model for customer service and support, and only wish others would follow your example.

Many Thanks.

[Peter2150]

AMEN!!!!

[Antarctica]

Thanks Todd for the very fast reply regarding this little annoying problem.I'm sure it will fix i.:)

[Eldar]

Many thanks Todd for your quick response to this annoying problem. :)
Not at home for the moment, but will try it later on.
Thanks again & keep up the good work. :thumb:

[stapp]

Is the same MBR fix required even if you uninstalled the last build along with all snapshots?

I haven't had the reminder yet by the way with the latest build.

[ErikAlbert]

I copied Leapfrogs post in my installation file of FDISR. I never had a "MBR is out of date" situation, but you never know.
Frankly, I never had any technical problems with FDISR and if I had a problem it was always caused by my own stupidity.
In such case, I used a smart image to overwrite my stupidity.

[stapp]

{QUOTE-> I copied Leapfrogs post in my installation file of FDISR. <-QUOTE}

Good idea Erik, I will do the same.

[Eldar]

{QUOTE-> Is the same MBR fix required even if you uninstalled the last build along with all snapshots? <-QUOTE}I guess it wouldn't hurt to apply the fix to your installation, so you won't receive that message. :)

[Eldar]

I just applied the fix, so I'm relieved to finally getting rid of that message. ;D

At the same time I received a response from Raxco with about the same explanation as above.

Thanks Pete, LeapFrog & Raxco & anyone else who participated to this thread. :D ;)

Case closed. :P

[flimbag]

That's been driving me mad for months now. Since updating to the latest version pretty well.

Thanks for the fix.