"BlueSuedeDeer" wrote:
>
>
> "Rock" wrote:
>
> > BlueSuedeDeer wrote:
> >
> > > I'm not sure whether this has anything to do with the recent Service Pack 2
> > > update or not, but I have just now noticed that my computer lacks any of the
> > > tools needed to allow me to use the SET command in Recovery Console. None of
> > > the things listed in the Microsoft Knowledge base are on my computer. Can
> > > anyone tell me if this was because of the Service Pack 2 Update if they took
> > > some things out or what may have caused this and a possible solution? Also, I
> > > make videos through my webcam of my playing the guitar for my friends and I
> > > also recently noticed that one of my files is there, but not there, according
> > > to windows. It says it's 11.1 MB but when you try to play it in Windows Media
> > > Player it is just a black screen. It does not even attempt to play at all or
> > > give an error message and the play button never enables only on this
> > > particular file. Also, the normal menu you get when you right click on a file
> > > is different on this one, just has options to play, open with burn to cd,
> > > etc... There is no option to delete rename or any of the other normal "right
> > > click" options as on on the other files. If I choose open with, and try to
> > > play the file with Real Player, it plays another file, the first file in the
> > > directory. I cannot delete or even drag and drop this file. It is just
> > > sitting there taking up space which is one reason I'm trying to get to
> > > recovery console to see if I can delete it from there. Does anyone have any
> > > answer or idea about any of this?
> > >
> > > Thanks.
> >
> > What tools? There are only three set commands allowed in recovery
> > console. All you do is type set and the command, such as
> >
> > Sell AllowAllPaths = true
> >
> > What exactly are you missing or do you mean by, "none of the things
> > listed in the ...are on my computer."
> >
> >
>
> When I attempt to use the set command as you described above I get the error:
>
> "The SET command is currently disabled. The SET command is an optional
> Recovery Console command that can only be enabled by using the Security
> Configuration and Analysis snap-in."
>
> This is addressed in Microsoft Knowledge Base Article - 235364 (since I'm
> new at this I don't know if I'm allowed to post links in here or not or I
> would copy the link.)
>
> Right under that it says:
>
> "Before you can change any of the environment variables to TRUE, you must
> enable the set command option using one of the following Windows security
> tools:
>
> The Security Configuration and Analysis snap-in in Microsoft Management
> Console(MMC)
> The Domain Controller Security Policy in Administrative Tools.
> The Domain Security Policy in Administrative Tools.
> The Local Security Policy in Administrative Tools.
>
> After you start one of these security tools (as applicable to your
> computer's environment), look under the Local Policies, Security Options
> heading and locate the following two security policies pertaining to Recovery
> Console.
>
> Recovery Console: Allow Automatic Administrative Logon.
> Recovery Console: Allow floppy copy and access to all drives and all folders.
>
> These are the tools I am referring to that are not on my computer. Not a
> single one of them.
>
> Also, I'm using Windows XP Home Edition with SP 2 installed if that helps
> any and I am the owner of the computer so I have all administrative rights
> and access. Noone else uses the computer, no other accounts have even been
> created so...I'm stumped.
>
> There are lots of snap ins listed in MMC, but not the Security Configuration
> and Analysis snap-in and all I have in my Administrative Tools is Component
> Services, Computer Management, Data Sources(ODBC), Event Viewer,
> Microsoft.NET Framework Configuration, Microsoft.NET Framework 1.1 Wizards,
> Performance and finally Services. That is all that is listed in there.
>
> Thanks for responding and in advance for any further help.
One other thing, I also noticed at the bottom of the article it says:
The information in this article applies to:
Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Professional
Microsoft Windows 2000 Datacenter Server
However I'm running into this issue on Windows XP Home Edition with SP 2
installed as I said. I haven't been able to find any articles that apply to
XP pertaining to this issue.
|