'Flatten and Rebuild' concerns

'Flatten and Rebuild' concerns

Secure Home | Search | About
 Microsoft Applications Security    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content add this group's latest topics to your Google content
Subject Author Date
'Flatten and Rebuild' concerns ~BD~ 09-14-2008
  |   ---> Re: A new beginning? PA Bear [MS MVP...12-31-2008
  |   | ---> Re: A new beginning? PA Bear [MS MVP...01-01-2009
  |--> Re: A new beginning? Tom [Pepper] Wi...01-02-2009
Posted by ~BD~ on September 14, 2008, 8:26 am
If you were  Registered and logged in, you could reply and use other advanced thread options


Earlier this year I started a thread expressing concern about the MBR virus. I
had many replies and
again thank everyone for their contributions.

The thread is still available on Google, here:-

http://groups.google.co.uk/group/microsoft.public.security.virus/browse_thread/thread/5779fa422ba9af96/ee5f99b403a1e451?hl=en&lnk=gst&q=I've+done+both+of+these+'silly+things'!+#ee5f99b403a1e451

The final post in that thread was from '-jen' . I noted with dismay that I
failed to acknowledge
his/her advice and apologise now for my oversight!

This was the advice given:-

The OP's OS is XP. He should instead boot from the Recovery Console and

type: fixmbr.
Fixmbr Command Syntax:

fixmbr (device_name):

device_name = This is where you designate the exact drive location that
a master boot record will be written to. If no device is specified, the
master boot record will be written to the primary boot drive.
Fixmbr Command Examples:

fixmbr \Device\HardDisk0

In the above example, the master boot record is written to the drive
located at \Device\HardDisk0.

fixmbr:

In this example, the master boot record is written to the device that
your primary system is loaded onto. If you have a single installation of
Windows installed, which is normally the case, running the fixmbr
command in this way is usually the right way to go.
Fixmbr Command Availability:

The fixmbr command is only available from within the Recovery Console in
Windows 2000 and Windows XP.

-jen
*************************************

I've now asked for specific advice on the Malwarebytes forum, here:
http://www.malwarebytes.org/forums/index.php?showtopic=6302

If anyone reading here feels they can add to the discussion, I'd welcome their
views. TIA

Dave

--



Posted by Paul Adare - MVP on September 14, 2008, 8:33 am
If you were  Registered and logged in, you could reply and use other advanced thread options


On Sun, 14 Sep 2008 13:26:43 +0100, ~BD~ wrote:

> I've now asked for specific advice on the Malwarebytes forum, here:
> http://www.malwarebytes.org/forums/index.php?showtopic=6302
>
> If anyone reading here feels they can add to the discussion, I'd welcome their
views. TIA

Please stop referencing threads from external web forums here. If you want
to participate here, great, post your question here, please don't use this
group as a referral to outside forums.

--
Paul Adare
MVP - Identity Lifecycle Manager
http://www.identit.ca
Code: Virus lasting about three to five days, accompanied by sore throat,
runny nose and fever.

Posted by BoaterDave on September 14, 2008, 10:32 am
If you were  Registered and logged in, you could reply and use other advanced thread options


> On Sun, 14 Sep 2008 13:26:43 +0100, ~BD~ wrote:
> > I've now asked for specific advice on the Malwarebytes forum, here:
> >http://www.malwarebytes.org/forums/index.php?showtopic=6302
>
> > If anyone reading here feels they can add to the discussion, I'd welcome
their views. TIA
>
> Please stop referencing threads from external web forums here. If you want
> to participate here, great, post your question here, please don't use this
> group as a referral to outside forums.
>
> --
> Paul Adare

I hear what you say, Mr Paul Adare, but you don't moderate the posts
here.

The Google thread *was* a Microsoft thread but has lapsed, no doubt
due to the 90 day retention rule, of which I'm sure you will be aware.
Rather than re-invent the wheel, I deemed it appropriate to refer back
to it.

Perhaps you should read it and then, based on your no-doubt superior
knowledge of computing and security matters, you might make a useful
contribution to the debate.

I mention the Malwarebytes forum because I have found the folk there
helpful and knowledgeable. They will answer questions on any subject.
When I first came to the MS Communities newsgroups I had thought that
they were run and staffed by Microsoft. Choosing which group to post
in proved to be very hit-and-miss; I'm quite sure many of those
posting their problems can never find the answers given! Perhaps
Microsoft ought to consider setting up a Web Forum which IS staffed by
its own people - or even by MVP's - they *could* then moderate it!

As you have said please, though, I will endeavour to comply with your
request! <smile>

Dave

--

Posted by What's in a Name? on September 14, 2008, 2:35 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


BoaterDave@nospam.invalid after much thought, came up with this jewel:

> Earlier this year I started a thread expressing concern about the MBR
> virus. I had many replies and again thank everyone for their
> contributions.
>
> The thread is still available on Google, here:-
>
> http://groups.google.co.uk/group/microsoft.public.security.virus/brows
> e_thread/thread/5779fa422ba9af96/ee5f99b403a1e451?hl=en&lnk=gst&q=I've
> +done+both+of+these+'silly+things'!+#ee5f99b403a1e451
>
> The final post in that thread was from '-jen' . I noted with dismay
> that I failed to acknowledge his/her advice and apologise now for my
> oversight!
>
> This was the advice given:-
>
> The OP's OS is XP. He should instead boot from the Recovery Console
> and
>
> type: fixmbr.
> Fixmbr Command Syntax:
>
> fixmbr (device_name):
>
> device_name = This is where you designate the exact drive location
> that a master boot record will be written to. If no device is
> specified, the master boot record will be written to the primary boot
> drive. Fixmbr Command Examples:
>
> fixmbr \Device\HardDisk0
>
> In the above example, the master boot record is written to the drive
> located at \Device\HardDisk0.
>
> fixmbr:
>
> In this example, the master boot record is written to the device that
> your primary system is loaded onto. If you have a single installation
> of Windows installed, which is normally the case, running the fixmbr
> command in this way is usually the right way to go.
> Fixmbr Command Availability:
>
> The fixmbr command is only available from within the Recovery Console
> in Windows 2000 and Windows XP.
>
> -jen
> *************************************
>
> I've now asked for specific advice on the Malwarebytes forum, here:
> http://www.malwarebytes.org/forums/index.php?showtopic=6302
>
> If anyone reading here feels they can add to the discussion, I'd
> welcome their views. TIA
>
> Dave

I have used the fixmbr on a dual boot w2k/linux setup-worked well to
restore the w2k bootup after removal of linux.
max
--
Virus Removal http://max.shplink.com/removal.html
Keep Clean http://max.shplink.com/keepingclean.html
Change nomail.afraid.org to gmail.com to reply by email.
nomail.afraid.org is for use in USENET-feel free to use it yourself.

Posted by BoaterDave on September 14, 2008, 5:58 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


wrote:
> BoaterD...@nospam.invalid after much thought, came up with this jewel:
>
>
>
>
>
> > Earlier this year I started a thread expressing concern about the MBR
> > virus. I had many replies and again thank everyone for their
> > contributions.
>
> > The thread is still available on Google, here:-
>
> >http://groups.google.co.uk/group/microsoft.public.security.virus/brows
> > e_thread/thread/5779fa422ba9af96/ee5f99b403a1e451?hl=3Den&lnk=3Dgst&q=
=3DI've
> > +done+both+of+these+'silly+things'!+#ee5f99b403a1e451
>
> > The final post in that thread was from '-jen' . I noted with dismay
> > that I failed to acknowledge his/her advice and apologise now for my
> > oversight!
>
> > This was the advice given:-
>
> > The OP's OS is XP. =EF=BF=BDHe should instead boot from the Recovery Co=
nsole
> > and
>
> > type: =EF=BF=BDfixmbr.
> > Fixmbr Command Syntax:
>
> > fixmbr (device_name):
>
> > device_name =3D This is where you designate the exact drive location
> > that a master boot record will be written to. If no device is
> > specified, the master boot record will be written to the primary boot
> > drive. =EF=BF=BDFixmbr Command Examples:
>
> > fixmbr \Device\HardDisk0
>
> > In the above example, the master boot record is written to the drive
> > located at \Device\HardDisk0.
>
> > fixmbr:
>
> > In this example, the master boot record is written to the device that
> > your primary system is loaded onto. If you have a single installation
> > of Windows installed, which is normally the case, running the fixmbr
> > command in this way is usually the right way to go.
> > Fixmbr Command Availability:
>
> > The fixmbr command is only available from within the Recovery Console
> > in Windows 2000 and Windows XP.
>
> > -jen
> > *************************************
>
> > I've now asked for specific advice on the Malwarebytes forum, here:
> >http://www.malwarebytes.org/forums/index.php?showtopic=3D6302
>
> > If anyone reading here feels they can add to the discussion, I'd
> > welcome their views. TIA
>
> > Dave
>
> I have used the fixmbr on a dual boot w2k/linux setup-worked well to
> restore the w2k bootup after removal of linux.
> max
> --
> Virus Removalhttp://max.shplink.com/removal.html
> Keep Cleanhttp://max.shplink.com/keepingclean.html
> Change nomail.afraid.org to gmail.com to reply by email.
> nomail.afraid.org is for use in USENET-feel free to use it yourself.- Hid=
e quoted text -
>
> - Show quoted text -

That's good to know! Thanks, Max

Dave

--

Similar ThreadsPosted
Concerns on Port Listening and Microsoft XBox Link October 4, 2006, 11:49 am

The site map in XML format XML site map

Contact Us | Privacy Policy