windowsnetworking.com/ windows_2003_support_tools.html
http://www.microsoft.com/download/en/details.aspx?id=15326
Saturday, December 3, 2011
Ownership in Windows 2003, Part III
Q919240 - Icacls is available for Windows Server 2003 SP2
Q834721 - Permissions on Folder are incorrectly ordered
Q943043 - Icacls.exe does not support inheritance
Q245031 - Change Registry Permissions (RegIni)
Q220167 - Understanding Container Access Inheritance Flags
Permissions explained
ACL utils: SetACL or FileACL (free)
Equivalent bash command (Linux): chmod / chown - Change file permissions/owner and group
Source SteelWerx (sw)
Bobby Flekmann: Otherwise you can use a program I've written which is an adaptation of the XCACLS.vbs. http://www.xs4all.nl/~fstaal01/swxcacls-us.html
I've even made this particular problem easier with implementing a /RESET switch.
==================
There are a lot of malicious software with the same name swxcacls.exe (dangerous!)
Disable the script host in windows!
swxcacls.vbs
SWReg - freeware implementation of Microsoft's reg.exe
SWSC - freeware implementation of Microsoft's sc.exe
SWWhoAmI - Windows version of the network command
SWCACLS.exe (download the program). - a binary implementation of XCACLS.vbs
Q834721 - Permissions on Folder are incorrectly ordered
Q943043 - Icacls.exe does not support inheritance
Q245031 - Change Registry Permissions (RegIni)
Q220167 - Understanding Container Access Inheritance Flags
Permissions explained
ACL utils: SetACL or FileACL (free)
Equivalent bash command (Linux): chmod / chown - Change file permissions/owner and group
Source SteelWerx (sw)
Bobby Flekmann: Otherwise you can use a program I've written which is an adaptation of the XCACLS.vbs. http://www.xs4all.nl/~fstaal01/swxcacls-us.html
I've even made this particular problem easier with implementing a /RESET switch.
==================
There are a lot of malicious software with the same name swxcacls.exe (dangerous!)
Disable the script host in windows!
swxcacls.vbs
This program is all about managing user's rights to files on a computer, so before we come to an explanation about the program itself, first an historic overview of user rights management.
Every Operating System has to have a way to keep unauthorized computer users out of files. The reason for this is simple, employees have no business with the company's books. A letter from your mom is still her letter, not yours, etc.
The question is: how does Windows do this? This depends on the version of Windows you are talking about. In Windows 95, 98 and Millenium Edition, user rights are a joke. They are non-existent. Programs themselves had to keep confidential information out of your eyes. They did this by changing attributes to make files hidden, or encrypt the contents, etc.
After the Operating Systems from these Win32 platforms came the network version of Windows, Windows NT. This had user management! To be able to use Windows NT you had to login, and a new filesystem (the internal layout of the hard disc) had been devised that supported permissions management. This filesystem, called NTFS
(New Technology File System), was understood and supported by all Operating Systems based on Windows NT.
In Windows 2000 and Windows XP you have to login to use the computer.
This can still be as simple as clicking on a name in the Windows XP Welcome screen, but still...
You are a user to the system. And this user has permissions to access files, and folders. Based on who you are certain parts of the Registry are read-only, or not visible at all.
Same goes for many other parts of Windows, who you are determines whether you can stop and start a service for example.
How does Windows keep track of the permissions? Now we come to a more difficult and abstract part. Even though all the following still appeals to all user objects (Registry keys, files, folders, services, processes, etc.), I will only give examples with files and folders.
To understand how Windows keeps track of permissions, we have to clarify a few keywords in Rights management.
- Windows created a few User groups when it got installed. These User groups are easy ways to finetune accessrights. You can make it so that Administrators have full access, and the rest can only read the file. There are many pre-defined groups, but for us these are the most interesting: Administrators, Users, Power Users and Everyone. Everyone is part of at least one Usergroup, namely Everyone. So, to take our previous example, if you are not part of the Administrators group, you can only read the file.
- Every file is created sometime on the computer, ergo every file has a creator. The creator is the one that has ultimate access to the file. (S)He can decide who has access, and to what level. This person is known as the Owner of the object.
- Permissions are actions you can do on an object, like read a file, stop a service, delete a Registry key. There are two types of permissions, the ones that are specific to the object, like stopping a service, or writing a file. And there are very generic rights. These generic rights are widely used, because they use
simple names, like Read or Execute,to refer to specific sets of permissions to the object.
Whether you want to delete a file, a Registry key or a service, it is still deleting, right? Another thing to understand is that these generic rights can contain different specific rights, you cannot stop a Registry key, or enumerate subkeys on a service. - Almost every file is in a subfolder, so it stands to reason that every file in a folder has the same permissions as the folder, which is in turn in another folder, so it stands to reason it has the same permissions at that folder, which..... You get the point. How do you do this? Beginning with Windows 2000 a new inheritance scheme was devised that automatically propagated all the rights from parents (the folder you are in) to the children (the files and folders in this folder). Before Windows 2000 though, every permission had to be copied down to every file and every folder under it. So if you changed one thing you ran the risk it would not reach the bottom of the chain, making the permissions unstable.
- Even though you are denied certain permissions, some Usergroups still have a possiblilty to do things to an object. Just think of Backup Operators, even though no one but you have access to your files, they can still make a backup of them. These extra rights are called privileges, and are mostly a nice addition to your possible actions. There will be more on privileges later.
- And the last thing to get to know is the Security IDentifier, also known as the SID. A SID is a thing that identifies you uniquely on a system. To Windows you are not a user, you are just a number, and this number is the reason that you can have multiple users on a system with the same name. This is not smart, but it is possible! It is also the reason why people will get locked out of files if they delete an account and make a new one with the same name. They get a different SID. Another thing to remember is that there are these predefined groups I mentioned earlier; they also have predefined SIDs. This way a user can be a part of the Users group in English countries and be a part of Gebruikers in Dutch countries!
Now that we know the basics of permissions, we get down to the how... As I said I will be focusing on files and folders, so let's roll.
In Windows NT you can rightclick on a file and choose "Properties", this will open a new Window with a few tabs, one being "Security".
Huh??? You did just that and you don't see the tab!!! No sweat, let me guess, you are running Windows XP and have Simple File Sharing on. You can check that in "Folder Options" and the tab "View". There is a checkbox checked next to "Use simple file sharing (recommended)". If you uncheck that and click on "Apply" you will see the "Security" tab. XP Pro gives you the choice of disabling this, but for Windows XP Home this is locked. By the way, you'll see this tab page when you are in Safe Mode on Windows XP.
Now that you have the tab open, you can see a list of users and groups, and the permissions belonging to them. These are the generic permissions I talked about earlier. If you click on "Advanced" you can see the specific rights on the Tab page "Permissions", the current owner on the "Owner" page and on the "Auditing" page the actions that will be logged.
You can change all that you want on these pages, even if you kick yourself out. As long as you are the Owner or have access to an account in the Administrators group you can reclaim Ownership and give yourself full control again.
Now that we know all this, we come to these computers that are still on Simple File Sharing. You are confronted with a stubborn file that you cannot do anything with, and want to change the permissions on them. You have several possibilities to do that.
Windows NT comes with a program called CACLS that you can use to change the Access Control Lists with. But this program comes with a few nasty surprises. You cannot use this program to change Ownership, or give specific permissions. What is even worse is that, since it is a legacy program from Windows NT, it doesn't support the "new" inheritance possibilities since Windows 2000. See the part about inheritance earlier in this tutorial.
There is also a program called XCACLS, this is a Microsoft program you can download which will lets you change Ownership and specific permissions, but it still suffers the problem with inheritance. This program is also available as a Visual Basic script, but it is no better.
Also there is a program called SUBINACL that can do the job, but that doesn't even speak of inheritance so I wouldn't trust it not to mess up the inheritance of files and folders.
Now we get to the main program, SWXCACLS. This is a recoding of the SWXCACLS Vbscript I mentioned earlier, though I added a few more options and changed some others.
I will show the differences in bold.
First an explanation of the commandline:
SWXCACLS filename [/P | /E] [[/G user:GUI;Spec/Inh] [/GX:GUI;Spec/Inh] [...]]
[[/D user:GUI;Spec/Inh] [/DX:GUI;Spec/Inh] [...]]
[[/R user] [/RX] [...]] [/I ENABLE|COPY|REMOVE]
[/SPEC A|B|C|D|E|F|G] [/S] [/L filename] [/Q]
[[/O user]| /OA | /OM ] [/RESET ENABLE|COPY|REMOVE] [/VERBOSE]
filename [Required] If used alone, it displays ACLs. Otherwise the given actions will be executed on the file. If you don't give a complete path I expect the file to be in the current directory. Put the filename in double quotes if it contains spaces or special characters such as &, $, #, etc.
If filename is a directory, the given actions will be executed only on the directory, not on the files and subdirectories in the directory. Use /I or /SPEC to tell the program what to do with these.
Wildcards can be used to specify more than one file in a command.The possible wildcards are:
- * - Any string of zero or more characters
- ? - Any single character
Note: To use commands on all files (*.*) , set the permissions on the folder instead of all the files.
/P Replaces permissions. New permissions will be as specified in /G and /D statements.
/E Edits the Access Control List instead of replacing it.
/G User:GUI;Spec/Inh and /GX:GUI;Spec/Inh These grant the specified User or Group the given access rights. Unless
/P is in the command line, this will never touch the rights for other users
| User | If User has spaces in it, surround it in quotes. User can be a string representing the actual SID, but MUST be lead by SID# Example: SID#S-1-5-21-2127521184-160... (SID string shown has been shortened) (If any user has SID# then globaly all matches must match the SID (not name), so if your intention is to apply changes to all accounts that match User then do not specify SID# as one of the users) |
| GUI | Is for standard rights and can be:
|
| Spec | Is for specific rights and can be:
|
| Inh | Inheritance override. For possible choices see /SPEC switch. This is new in comparison to the script. The original script only gave you the opportunity to state an inheritance scheme that would be applied to everyone.This way you can give someone a different inheritance scheme to the rest. |
/GX:GUI;Spec/Inh You can define permissions for predefined groups by using the X variants of the switches. The following switches have been defined:
- A - Administrators
- U - (Limited) Users
- G - Guests
- O - Owner
- P - (Power) Users
- S - Local System
- E - Everyone
- M - Current User
The possible parameters for GUI, Spec and Inh are explained by /G.
/D User:GUI;Spec/Inh and /DX:GUI;Spec/Inh Deny the given user access
/R User and /RX Revoke specified user's access rights. This will remove any Allowed or Denied ACLs for user
/I Switch Inheritance flag, if omitted default is to not touch Inherited ACLs. Switch can be:
- ENABLE - This will turn on the Inheritance Flag if its not on already. The net result is that Inherited ACLs become active on the file/folder
- COPY - This will turn off the Inheritance flag and copy the Inherited ACLs into Effective ACLs
- REMOVE - This will turn off the Inheritance flag and will not copy the Inherited ACLs, this is the opposite of ENABLE
If switch is not present, /I will be ignored and Inherited ACLs will remain untouched.
/RESET [Switch] Resets all permissions to given ones.
Use this sparingly because this switch will keep everyone out if /G and /D switches are specified that way!
Owner will be reset to Administrators group, so it is possible for members of that Group to re-evaluate permissions.
Owner will also receive Full Access permissions, other permissions should be specified in GRANT/DENY statements.
Switch can be the same as with /I. This switch is only used on the root folder. Default of switch is ENABLE
This command can only be used on folders. To change permissions on files use GRANT/DENY statements.
/SPEC Switch Special permission for folder and subfolders only. If this switch is used, and the object is a folder, then one of the switches below would be used instead of the default.
- A - This Folder Only
- B - This Folder, Subfolders and Files (Default)
- C - This Folder and Subfolders
- D - This Folder and Files
- E - Subfolders and Files Only
- F - Subfolders Only
- G - Files Only
/S Execute on subfolders and files as well. This switch only works with wildcards.
/L [Filename] Filename for logging. This can include a path name if the file isn't under the current directory. File will be appended to, or created if it doesn't exist.
Must be Text file if it exists or an error will occur.
If filename is omitted the default name of SWXCACLS.log will be used.
/Q Turn on Quiet mode, it's off by default. If it's turned on, there will be no display to the screen.
/O User Change the Ownership to this user or group.
/OA Change the Ownership to the Administrators group.
/OM Change the Ownership to the Current User.
/VERBOSEDisplay everything there is to know inside the Security Descriptor. Information will be presented using symbols from the Windows Software Development Kit.
You can specify more than one user in a command.
You can combine access rights.
Updated (14 april 2007 v.: 1.0.2.0): Changed the /RESET command a bit as it was possible to use this with a filename.
Updated (26 november 2006): got rid of an Access Violation when for some reason the system could not open the file/folder you requested about.
Now that you've read about the pitfalls and possibilities of this program. Click the download link to download the program.
Commandline utilitiesSWReg - freeware implementation of Microsoft's reg.exe
SWSC - freeware implementation of Microsoft's sc.exe
SWWhoAmI - Windows version of the network command
SWCACLS.exe (download the program). - a binary implementation of XCACLS.vbs
Friday, December 2, 2011
iPAQ (desktop computer) as headless server
A headless system is a computer system or device that has been
configured to operate without a monitor (the missing "head"), keyboard
and mouse. A headless system is typically controlled via a network
connection, although some headless system devices require a connection
to be made via RS232 for administration of the device.
PC BIOS limitations related to headless operation During bootup, some (especially older) PC BIOS
versions will wait indefinitely for a user to press a key before
proceeding if some basic devices are not installed or connected,
effectively halting an unattended system. These can include:
Even in cases where a system has been set up to be managed remotely, a local keyboard and video card may still be needed from time to time, for example to diagnose boot problems that occur before a remote access application is initialized.
Hardware remote control Some servers provide for remote control via an internal network card and hardware that mirrors the console screen. For example, HP offers a solution called Integrated Lights-Out (ILO) that provides this functionality. Remote access to the system is gained using a secure web connection to an IP address assigned to the ILO adapter, and allows for monitoring of the system during start-up before the operating system is loaded.
Another hardware solution is to utilize a KVM-over-IP switch. Such a switch is a traditional Keyboard-Video-Mouse sharing device with the added ability to provide remote control sessions over IP. Connection to the KVM device is gained using a web browser, which allows for remote monitoring of the connected system console port.
Software remote control
In the past systems were typically administered through a text-based interface such as a command line
in Unix. These interfaces were often called 'virtual terminals' or
'terminal emulators', as they attempted to simulate the behavior of
"real" interface terminals like the Digital Equipment Corporation's VT100.
Later on, systems such as X Window System and VNC combined with virtual display drivers allow remote connections to headless machines through ordinary Graphical user interfaces, often runnning over network protocols like the internet's TCP/IP.
================= =================
The iPAQ Desktop Personal Computer in its various incarnations was a Legacy-free PC produced by the Compaq Computer Corporation around the year 2000.
The Compaq iPAQ was primarily designed to be a portable desktop computer that could be used as a simple internet capable computer
Hardware 
The iPAQ had very few limitations on upgradability; hard drives, RAM, CPU and 'Multi-Bay' drives can be readily interchanged, although the iPAQ did not contain sockets for expansion cards.
It featured an interchangeable 'Multi-Bay' slot that could accept a 3.5 inch LS SuperDisk drive (the only way to read a floppy disk - standard Multi-Bay floppy drives do not work), optical drives, or a secondary hard disk device. The slot was the same as those found on many Compaq Armada and many other HP/Compaq laptop computer systems.
By a method of convection for cooling, these computers are commonly found in office environments due to their low noise (dB) output.
The iPAQ ran on either an Intel Pentium III processor or on an Intel Celeron processor; ranging from 500 MHz to 1 GHz processor in a PGA370 socket.
The internal RAM was upgradable to 512 MBs of 100 Mhz 168pin SDR SDRAM. Strangely enough, the BIOS in the iPAQ actually prevents the system from booting if there is more than 512 MBs of RAM installed (a message displays during POST instructing the user to decrease the amount of RAM in the system to no more than 512 MBs). The reason behind this forced RAM limitation is unknown.
The first version came in two different models, "Legacy free" which had no parallel, serial, or PS/2 ports and instead 3 additional USB ports on the back; and the traditional one which included the parallel, serial, and PS/2 ports but only had USB ports on the front. The second version had different styling and had a backpack which added the "legacy" ports. Both models would make good headless servers, except that a bug or oversight in the BIOS requires that a keyboard must be connected in order for the computer to boot. This can be bypassed with a couple of BIOS tweaks [1]
Look for
Running Linux on old hardware
==========================
Windows Seven on old hardware and processor and low mem
- a video card;
- a keyboard.
Even in cases where a system has been set up to be managed remotely, a local keyboard and video card may still be needed from time to time, for example to diagnose boot problems that occur before a remote access application is initialized.
Hardware remote control Some servers provide for remote control via an internal network card and hardware that mirrors the console screen. For example, HP offers a solution called Integrated Lights-Out (ILO) that provides this functionality. Remote access to the system is gained using a secure web connection to an IP address assigned to the ILO adapter, and allows for monitoring of the system during start-up before the operating system is loaded.
Another hardware solution is to utilize a KVM-over-IP switch. Such a switch is a traditional Keyboard-Video-Mouse sharing device with the added ability to provide remote control sessions over IP. Connection to the KVM device is gained using a web browser, which allows for remote monitoring of the connected system console port.
Software remote control
Later on, systems such as X Window System and VNC combined with virtual display drivers allow remote connections to headless machines through ordinary Graphical user interfaces, often runnning over network protocols like the internet's TCP/IP.
================= =================
The iPAQ Desktop Personal Computer in its various incarnations was a Legacy-free PC produced by the Compaq Computer Corporation around the year 2000.
The Compaq iPAQ was primarily designed to be a portable desktop computer that could be used as a simple internet capable computer
The iPAQ had very few limitations on upgradability; hard drives, RAM, CPU and 'Multi-Bay' drives can be readily interchanged, although the iPAQ did not contain sockets for expansion cards.
It featured an interchangeable 'Multi-Bay' slot that could accept a 3.5 inch LS SuperDisk drive (the only way to read a floppy disk - standard Multi-Bay floppy drives do not work), optical drives, or a secondary hard disk device. The slot was the same as those found on many Compaq Armada and many other HP/Compaq laptop computer systems.
By a method of convection for cooling, these computers are commonly found in office environments due to their low noise (dB) output.
The iPAQ ran on either an Intel Pentium III processor or on an Intel Celeron processor; ranging from 500 MHz to 1 GHz processor in a PGA370 socket.
The internal RAM was upgradable to 512 MBs of 100 Mhz 168pin SDR SDRAM. Strangely enough, the BIOS in the iPAQ actually prevents the system from booting if there is more than 512 MBs of RAM installed (a message displays during POST instructing the user to decrease the amount of RAM in the system to no more than 512 MBs). The reason behind this forced RAM limitation is unknown.
The first version came in two different models, "Legacy free" which had no parallel, serial, or PS/2 ports and instead 3 additional USB ports on the back; and the traditional one which included the parallel, serial, and PS/2 ports but only had USB ports on the front. The second version had different styling and had a backpack which added the "legacy" ports. Both models would make good headless servers, except that a bug or oversight in the BIOS requires that a keyboard must be connected in order for the computer to boot. This can be bypassed with a couple of BIOS tweaks [1]
Look for
Running Linux on old hardware
==========================
Windows Seven on old hardware and processor and low mem
Ownership in Windows 2003, Part II
As administrator take ownership of the complete foldertree first.
Start -execute
cmd
(Run As Administrator)
- Change location to the folder you need access to
e.g.:
E:
cd e:\OSL
- Type: takeown /F . /R /A /D Y > NUL
- Type: icacls . /grant Administrator:(OI)(CI)(F) /T /Q
- Type: icacls . /grant oscar:(OI)(CI)(F) /T /Q
Afterwards you will be able to change the access rights using cacls or xcacls.
http://programmerstools.hubpages.com/hub/xcacls
===========================
Unix/linux correspondance to windows
chmod is used to change access rights on files and folders for owner-group-others.
So chmod would correspond more to cacls.
And chown would correspond to takeown.
===========================
CACLS for windows XP
Elevation of privilege per script
Ownership of a file or folder
Denied permission to access folders
- click Start
- Type: cmd
your hard drive is plugged into] to have full access to these files)
---------------------
other version:
iCacls sintax
iCACLS.exe (2003 sp2, Vista)
======================
CACLS: Capacidades de permisos de grupo
Start -execute
cmd
(Run As Administrator)
- Change location to the folder you need access to
e.g.:
E:
cd e:\OSL
- Type: takeown /F . /R /A /D Y > NUL
- Type: icacls . /grant Administrator:(OI)(CI)(F) /T /Q
- Type: icacls . /grant oscar:(OI)(CI)(F) /T /Q
Afterwards you will be able to change the access rights using cacls or xcacls.
http://programmerstools.hubpages.com/hub/xcacls
===========================
Unix/linux correspondance to windows
chmod is used to change access rights on files and folders for owner-group-others.
So chmod would correspond more to cacls.
And chown would correspond to takeown.
===========================
CACLS for windows XP
Elevation of privilege per script
Ownership of a file or folder
Denied permission to access folders
- click Start
- Type: cmd
- Right-click cmd when it appears
- Click Run As Administrator
- Change location to the folder you need access to (e.g. cd e:\folder)
- Type:
takeown /F . /R /A /D Y > NUL
- Type:
icacls . /grant Administrator:(OI)(CI)(F) /L /T /Q
(in other case use instead of Administrator your username - you will only have access from your
XP and Vista machine in this case)
[> is the character greater than without the ; character]
[It should be ""USER : ( O I )..." but without the spaces before and after : ]
(Or, replace USER (Administrator) with Users if you want anyone [on any computeryour hard drive is plugged into] to have full access to these files)
---------------------
other version:
I restored the primary [C:] hard drive from an old computer running
Windows XP to a new one as a secondary/additional hard drive on Windows
Vista, and got a "You have been denied permission to access this folder"
message.
Found this page via Google. Thank you, Jimmy Brush.
Code:
- Click Start
- Type: cmd
- Right-click cmd when it appears and select Run As Administrator.
- Change location to the folder you need access to (e.g. cd e:\folder).
- Type: takeown /F . /R /A /D Y > NUL
- Press the Enter key and wait for the command to complete.
- Type: icacls . /grant users:(OI)(CI)(F) /L /T /Q
- Press the Enter key.
iCACLS.exe (2003 sp2, Vista)
======================
CACLS: Capacidades de permisos de grupo
Ownership in Windows 2003, Part I
There is a Group Policy option that can hide the security tab that would hide it for all files on the computer. Look under user configuration/administrative templates/Windows components/Windows explorer - hide security tab. Set that to disabled in local Group Policy [gpedit.msc] or whatever Group Policy that is applying to the user that you are logging on as. You can use the Resultant Set of Policy mmc snapin on that server to see what Group Policies and what settings are being applied to that computer and user. Also the security tab will not appear if the user does not have read permissions to the Rshx32.dll file in the %systemroot%\system32 folder.
You can also view and manage security permissions with command line utilities such as cacls and xcacls.vbs and my favorite is fileacl. Both xcacls.vbs and fileacl can also change ownership of folders or files.
--Steve
http://www.gbordier.com/gbtools/fileacl.htm --- fileacl
http://support.microsoft.com/?id=825751 --- xcacls.vbs
I have tried using xcacls, but I am getting an access denied message
there as well when I attempt to change the permissions.
http://programmerstools.hubpages.com/hub/xcacls
-------------------------
A program titled NTFSFIX has solved my problems. See below for the link:
NTFSFixPermissions
System Requirements
Product Tour




In the above screenprint two folders were not configured properly. This is because no users exist in the domain with the same name as the folder.
Source
You can use subinacl.exe or fileacl.exe to replace the current owner.
The syntax for fileacl.exe is much easier than for subinacl.exe.
microsoft.com/ FamilyID=723f64ea-34f0-4e6d-9a72-004d35de4e64
Denied message. I omitted the /c option so
"Replace owner on subcontainers and objects"
-------------------------
Got it to work (mostly, haha)
Had to run "fileacl.exe \\server\share /o Administrators /s Administrators /SUB /FILES" twice (for whatever reason the
files don't take the first time around). In theory after that "fileacl.exe //server/share /replace /inherit" should
have worked, but it causes fileacl to fault on large trees.
So SetACL/xcacls/whatever works to reset inheritance after that.
=============================
Source
Set Up and Use Xcacls.vbs
To set up and to use Xcacls.vbs, follow these steps:
You can also view and manage security permissions with command line utilities such as cacls and xcacls.vbs and my favorite is fileacl. Both xcacls.vbs and fileacl can also change ownership of folders or files.
--Steve
http://www.gbordier.com/gbtools/fileacl.htm --- fileacl
http://support.microsoft.com/?id=825751 --- xcacls.vbs
I have tried using xcacls, but I am getting an access denied message
there as well when I attempt to change the permissions.
http://programmerstools.hubpages.com/hub/xcacls
- Home
- Webtools Tutorial
- User Guide
- A quick look at the Windows 2003 support tools
- Setting ownershp and permissions from the command line
- How to use Xcacls.vbs to modify NTFS permissions
- SWXCACLS - a binary implementation of XCACLS.vbs
- HOW TO: Use Xcacls.exe to modify NTFS permissions
- ACL Tutorial
- Using the Command Line to Edit Multiple Subdirectory Permissions
-------------------------
A program titled NTFSFIX has solved my problems. See below for the link:
NTFSFixPermissions
System Requirements
- Windows 2000, XP or 2003 Server
- .NET Framework version 1.1 (Download from Microsoft or Windows Update)
- A user account that has full control permissions on the work areas, or has ownership of the folders.
Product Tour
- Select Mode (Add or Replace)
- Add custom permissions to the work area (Default permissions shown below)
- Select the root folder. (UNC or local path supported) You can also exlude folders here.
- Confirm the selection & start the permissions change.
In the above screenprint two folders were not configured properly. This is because no users exist in the domain with the same name as the folder.
Source
You can use subinacl.exe or fileacl.exe to replace the current owner.
The syntax for fileacl.exe is much easier than for subinacl.exe.
microsoft.com/ FamilyID=723f64ea-34f0-4e6d-9a72-004d35de4e64
Denied message. I omitted the /c option so
"Replace owner on subcontainers and objects"
-------------------------
Got it to work (mostly, haha)
Had to run "fileacl.exe \\server\share /o Administrators /s Administrators /SUB /FILES" twice (for whatever reason the
files don't take the first time around). In theory after that "fileacl.exe //server/share /replace /inherit" should
have worked, but it causes fileacl to fault on large trees.
So SetACL/xcacls/whatever works to reset inheritance after that.
=============================
Source
Set Up and Use Xcacls.vbs
To set up and to use Xcacls.vbs, follow these steps:
- Obtain the latest version of Xcacls.vbs from the following Microsoft Web site:
- Double-click Xcacls_Installer.exe. When you are prompted for a location to place the extracted files, specify a folder that is in your computer's search-path setting, such as C:\Windows.
- Change the default scripting engine from Wscript to
Cscript. (The Xcacls.vbs script works best in Cscript.) To do this,
type the following at a command prompt, and then press ENTER:cscript.exe /h:cscriptNote Changing the default scripting engine to Cscript only affects how scripts write to the screen. Wscript writes each line individually to an OK dialog box. Cscript writes each line to the command window. If you do not want to change the default scripting engine, you must run the script by using the following commandcscript.exe xcacls.vbswhereas if you change the default to Cscript, you can run the script with the following command:xcacls.vbs.
- To see the Xcacls.vbs command syntax, type the following at a command prompt:xcacls.vbs /?
Syntax for the Xcacls.vbs Command
Running Linux on old hardware configuration
http://www.linuxforums.org/forum/per...a64-em64t.html
http://www.linuxforums.org/forum/lin...bit-linux.html
http://www.linuxforums.org/forum/lin...bit-linux.html
Here's a basic link with various options. Choose the DVD with the full install, the CD is very basic and may cause you some frustration.
================
Informacion del equipo
Abre una terminal:
$ su -
--------- root passwd
# dmesg
# dmesg | less
# lshw -short
# lshw -short
# lspci
# cat /proc/cpuinfo
# cat /proc/meminfo
Here the output is in HTML and is redirected to a file which can be viewed in a web browser:
Code:
hardinfo -f html > hardwareinfo.html
Si la version del
kernel usada no soporta el DMA del disco rigido, hay problemas en la
transferencia de datos entre disco y el resto de los componentes:
# hdparm -Tt /dev/hda
===================
The binaries are usually compiled for a specific CPU to gain
increased performance by taking advantage of new architecture and
instruction sets. Every new generation of CPU has some new features
besides just increased clocks.
- i386 - is the old 386/486 intel CPUS
- i586 - intel Pentium/Pro and 100% AMD Compatibles like K5 or Cyrix
- i686 - (Intel Pentium 4) Started with the P II and then the P III and AMD Athlon, Duron
- XPx86_x64 - AMD architecture of Athlon64, intel call it "Intel 64-bit with Extended Memory Technology"
As a general rule, use the one retated to your CPU. Older versions will run on newer CPUs but newer ones might not run on older CPUs.
To give a little more information on that, the X86 processors started
with the Intel 8086 processor way back in 1978. They were incrementally
improved (80186, 80286) and then Intel released the Intel 386 (i386) in
1980. That was then followed by the 486 (i486), the Pentium (i586), and
the Pentium 3/4 (i686) and AMD's Athlon/Duron/T-bird (also i686).
Since all these processors were based on the same architecture (basically they read/wrote 1's and 0's in the same way), and their names all contained "86", the whole family was collectively called "X86". All the X86 processors were 32-bit.
The recent trend has been to move toward 64-bit processors, and several different architectures popped up. DEC's Alpha and Motorola's PPC chips have been 64-bit for a while, but Intel's Itanium and Xeon and AMD's Athlon64 are the new kids on the block.
The difference between the Itanium and PPC versus the Athlon64 is that the Itanium and PPC have completely different architectures (they speak different 1 and 0 languages), whereas the Athlon64 speaks the same language as the 32-bit x86 processors, but adds 64-bit registers. Therefore the name of the Athlon64 in generic terms is "x86_x64".
Intel, not to be outdone, has since redesigned its 64-bit Xeon processors to use the same kind of architecture as the Athlon64, calling it "Intel 64-bit with Extended Memory Technology". Basically they couldn't say they copied AMD without being laughed at in irony (since AMD got its start by simply copying Intel's chips).
Since all these processors were based on the same architecture (basically they read/wrote 1's and 0's in the same way), and their names all contained "86", the whole family was collectively called "X86". All the X86 processors were 32-bit.
The recent trend has been to move toward 64-bit processors, and several different architectures popped up. DEC's Alpha and Motorola's PPC chips have been 64-bit for a while, but Intel's Itanium and Xeon and AMD's Athlon64 are the new kids on the block.
The difference between the Itanium and PPC versus the Athlon64 is that the Itanium and PPC have completely different architectures (they speak different 1 and 0 languages), whereas the Athlon64 speaks the same language as the 32-bit x86 processors, but adds 64-bit registers. Therefore the name of the Athlon64 in generic terms is "x86_x64".
Intel, not to be outdone, has since redesigned its 64-bit Xeon processors to use the same kind of architecture as the Athlon64, calling it "Intel 64-bit with Extended Memory Technology". Basically they couldn't say they copied AMD without being laughed at in irony (since AMD got its start by simply copying Intel's chips).
The bewildering choice and the ever increasing number of Linux
distributions can be confusing for those who are new to Linux. This is
why this page was created. It lists 10 Linux distributions (plus an
honourable mention of FreeBSD, by far the most popular of all of the
BSDs), which are generally considered as most widely-used by Linux users
around the world. There are no figures to back it up and there are many
other distributions that might suit your particular purpose better, but
as a general rule, all of these are popular and have very active forums
or mailing lists where you can ask questions if you get stuck. Ubuntu, Linux Mint and PCLinuxOS
are considered the easiest for new users who want to get productive in
Linux as soon as possible without having to master all its complexities.
On the other end of the spectrum, Slackware Linux, Arch Linux and FreeBSD are more advanced distributions that require plenty of learning before they can be used effectively. openSUSE, Fedora, Debian GNU/Linux and Mageia can be classified as good "middle-road" distributions. CentOS
is an enterprise distribution, suitable for those who prefer stability,
reliability and long-term support over cutting-edge features and
software.
Mint
- Available editions: A "main" edition (with GNOME), a variety
of "secondary" editions (with KDE, Xfce and Fluxbox), Linux Mint
"Debian" edition (rolling-release with GNOME or Xfce)
- Possible alternatives: Ubuntu, Pinguy OS, Zorin OS, SimplyMEPIS, Peppermint OS
Ubuntu
- Available editions: Ubuntu, Kubuntu, Xubuntu, Lubuntu (desktop with LXDE), Edubuntu, Ubuntu Studio and Mythbuntu for 32-bit (i386) and 64-bit (x86_64) processors;
- Suggested Ubuntu-based alternatives: Linux Mint (desktop), Ultimate Edition (desktop), Pinguy OS (desktop), Zorin OS (desktop), Trisquel GNU/Linux (free software), Bodhi Linux (desktop with Enlightenment)
Fedora
- Available editions: Fedora for 32-bit (i386) and 64-bit (x86_64) processors; Red Hat
Enterprise Linux for i386, IA64, PowerPC, s390x and x86_64
architectures; also live CD editions with GNOME, KDE, LXDE or Xfce
desktops
- Suggested Fedora-based alternatives: Kororaa (live DVD with GNOME or KDE), Fuduntu (live DVD with codecs and other user-friendly features), Fusion Linux (live DVD with Mint menu and other user-friendly features)
- Suggested Red Hat-based alternatives: CentOS, Scientific Linux, PUIAS
Debian
- Available editions: Installation CD/DVD and live CD images
for 11 processor architectures, including all 32-bit and 64-bit
processors from Intel, AMD, Power and others
Debian has the 486 kernel on the same disk as the 686 kernel.
- Suggested Debian-based alternatives: Ubuntu, MEPIS Linux (desktop with KDE), KNOPPIX (live CD with LXDE), CrunchBang Linux (desktop with Openbox), aptosid (desktop with KDE or Xfce), Saline OS (desktop with Xfce), Parsix GNU/Linux (desktop with GNOME)
OpenSUSE
- Available editions: openSUSE for 32-bit (i386), 64-bit (x86_64) processors (also installable live CD edition); SUSE Linux Enterprise Desktop/Server for i586, IA64, PowerPC, s390, s390x and x86_64 architectures
Arch
- Available editions: Minimal installation CD and network installation CD images for 32-bit (i686) and 64-bit (x86_64) processors
- Suggested Arch-based and Arch-like alternatives: ArchBang Linux (lightweight with Openbox), Chakra GNU/Linux (live CD with KDE), CTKArch (lightweight with Openbox), ConnochaetOS (for old computers)
CentOS
- Available editions: Installation DVDs and installable live
CDs (with GNOME) for i386 and x86_64 processors; older versions (3.x and
4.x) also available for Alpha, IA64 and IBM z-series (s390, s390x)
processors.
- Other RHEL clones and CentOS-based distributions: Scientific Linux, PUIAS Linux, SME Server, Rocks Cluster Distribution, Oracle Enterprise Linux (commercial)
SlackWare
- Available editions: Installation CDs and DVD for 32-bit (i486) and 64-bit (x86_64) processors
- Suggested Slackware-based alternatives: Kongoni GNU/Linux (desktop, free software), Linvo GNU/Linux (desktop with GNOME), Porteus (live CD with KDE or LXDE), Salix OS (desktop, live CD), VectorLinux (desktop), Zenwalk Linux (desktop)
- Other distributions with similar philosophies: Arch Linux, Frugalware Linux
FreeBSD (not GNU/Linux but GNU)
- Available editions: Installation CDs for AMD64, ARM/ARMEL, i386, IA64, MIPS/MIPSEL, PC98 PowerPC, SPARC64 and Xbox processors
- Suggested FreeBSD-based alternatives: PC-BSD (desktop), GhostBSD (live DVD with GNOME)
- Other BSD alternatives: OpenBSD, NetBSD, DragonFly BSD
===================================
antiX is a fast, lightweight and easy-to-install linux live CD
distribution based on MEPIS and Debian's testing branch for Intel/AMD
x86-compatible systems. antiX offers users the "Magic of MEPIS" in an
environment suitable for old computers. The goal of antiX is to provide a
light, but fully functional and flexible free operating system for both
newcomers and experienced users of Linux. It should run on most
computers, ranging from 64 MB PII systems with a pre-configured 128 MB
swap partition to the latest powerful boxes. 128 MB RAM is the
recommended minimum for antiX while the installer needs a minimum of 2.2
GB hard disk space. antiX can also be used as a fast-booting rescue CD.
| Distribución | antiX |
|---|---|
| Página principal | http://antix.mepis.com/ |
| Listas de correo | -- |
| Foros de usuario | http://antix.freeforums.org/ |
| Documentación | -- |
| Capturas | http://antix.mepis.com/index.php/Main_Page#Screenshots • The Coding Studio |
| Mirrors de descarga | http://antix.mepis.com/index.php/Main_Page#Downloads |
| Bug Tracker | -- |
| Sitios web relacionados | |
| Reviews | 8.x: Desktop Linux Reviews •
Blogspot •
IT Lure 7.x: Blogspot • |
====================================
ark linux, basada en mandriva, KDE 3.5.
Pentium 233mhz con 128mb RAM
--------------------------------------
LXDE (32-bit)
--------------------------------------
Salix
Use the xfce edition or
if language support is needed, download the KDE edition
--------------------------------------
Ark Linux
Ark Linux 2008.1 (Current Stable) Recommended for those with older computers who don't feel comfortable testing.
Use the xfce edition or
if language support is needed, download the KDE edition
--------------------------------------
Ark Linux
Ark Linux 2008.1 (Current Stable) Recommended for those with older computers who don't feel comfortable testing.
===================================
Which operating system to install?
Windows XP and Vista: are too resource intensive,
Windows 95/98/ME: not recommended since these versions are no longer maintained and safety risks are too great,
GNU/Linux: excellent choice because you can choose not only the distribution but also the desktop manager.
Here are some screenshots:
Damn Small Linux running on a machine with 64 MB of RAM ... and there is still room in memory despite Firefox launched:
FeatherLinux:
Fluxbuntu
Photos:courtesy of CCM
On Windows, this is not possible, but on the contrary GNU/Linux allows
you to choose a desktop manager that is not too resource intensive. This
is because, the GNU/Linux distributions all share the same basis, the actual difference in terms of resource consumption is the choice of the Desktop manager.
Desktop stands for the working interface of any user. This
man-machine interface (HMI) uses a window manager, and sometimes an
integrated graphical environment.
But note that desktop solutions in 3D (three dimensional) are unusable on i486 with 512 MB (at best) of memory (RAM).
If you want a "simple" window manager, turn to:
- Blackbox : http://blackboxwm.sourceforge.net/
- FluxBox : http://fluxbox.sourceforge.net/
- FVWM : http://www.fvwm.org/
- IceWM : http://www.icewm.org/
- OpenBox : http://icculus.org/openbox/index.php/Main_Page
If you want a 2D graphics environments (more complete), turn to:
- Enlightenment: http://www.enlightenment.org/
- Xfce: http://www.xfce.org/
... ....
Ready to use Distributions
Note that some distributions may have several desktop managers available:
Feather Linux: Fluxbox and IceWM,
VectorLinux 5.1: Fluxbox, IceWM and Xfce.
The given list considers only those having a desktop manager available by default, but it is always possible to install another thereafter.
Feather Linux: Fluxbox and IceWM,
VectorLinux 5.1: Fluxbox, IceWM and Xfce.
The given list considers only those having a desktop manager available by default, but it is always possible to install another thereafter.
Blackbox
- Damn Small Linux
- Requires a 486 processor, 16MB RAM
- Feather Linux
- Requires a 486 processor, 24 MB RAM
- Fluxbuntu (LiveCD experimental)
- Requires 96 MB of RAM and 2 GB hard disk
- PapugLinux
- Requires 64 MB of RAM
- VectorLinux 5.1
- Requires 32 MB of RAM and 950 MB of hard disk
- Absolute
- Requires a Pentium 200 with 64MB of RAM, a Pentium II with 128 MB of RAM would be better
- DeLi Linux
- Requires a 486, 16 MB RAM and 350 MB of hard disk
- Feather Linux
- Requires a 486, 24 MB RAM
- Morphix
- Requires an i386, 70 MB RAM and 210 MB of hard disk
- Puppy Linux
- Requires a Pentium 166MMX, 128 MB of RAM (but only 64 MB of RAM if there is already a Linux swap partition)
- VectorLinux 5.1
- Requires 32 MB of RAM and 950 MB of hard disk
- CrunchBang
- Requires 128 MB of RAM
- ELive
- Requires a i486 with 100 MHz, 64 MB RAM
- Gentoo
- Requires i486, 64 MB RAM and 1.5 GB hard drive
- SaxenOS
- Requires a Pentium II 350 MHz, 128 MB RAM and 2 GB hard disk
- VectorLinux 5.1
- Requires 32 MB of RAM and 950 MB of hard disk
- Xubuntu
- Requires 64 MB of RAM and 2 GB hard drive
- Zenwalk
- Requires a Pentium III, 128 MB RAM and 2 GB hard disk
You installed a distribution with an office that does not allow a real
graphical boot? If you can log in console mode and you're connected to
the internet,then:
- Log in as root.
- Install one of the windows manager listed above (manipulation varies upon the distribution).
- Enter the startx command
Download version 5.2.8 from ibiblio.org: Get lupu-528.iso or explore the folder.
Download version 5.2.8 from nluug.nl: Get lupu-528.iso or explore the folder.
MD5 Checksum: f04ec9ef3540be8e50d0a24c512e1309
ISO Size: 129MB
NOTE: Update 02 is available - click here to download, then click on the file to install it. Optional multimedia update is here.
Thursday, December 1, 2011
0x0000007b
cebaehren's advice:
Controlar y solucionar la infección de mbr-virus en otro equipo con mbrcheck.exe
============================
Source
Option 1 - Repair Install (recommended)
- Use your Windows Setup CD during startup.
- At the start of Windows Setup, press [Enter] to install Windows.
- Press [R] to repair Windows XP installation.
Or if your running Vista, the option is to upgrade instead of repair.
Option 2 - Recovery Console
This is dependant on if a particular folder resides on the system called "ServicePackFiles"
- Insert your Windows Setup CD during startup.
- At the start of Windows Setup, press [R] for the Recovery Console (if an administrator password has been configured, it will ask you for it at this stage).
- At the recovery console, type in the following commands exactly:
copy c:\windows\servicepackfiles\i386\atapi.sys c:\windows\system32\drivers\atapi.sys
- Restart the PC and tap [F8] during startup.
- At the startup screen, select Last Known Good Configuration to restore the registry.
Option 3 - Remove HDD
- Remove the hard drive, and install it into a working PC that is running the same version and service pack.
- Right click and copy the c:\windows\system32\drivers\atapi.sys file from a working HDD to the newly installed HDD.
- Place the drive back in it's original PC.
- Start the PC and tap [F8] during startup.
- At the startup screen, select Last Known Good Configuration to restore the registry.
Option 4 - Using BartPE
- Download (but do not open) then the following registry file: atapi.reg
- Save it to a USB storage device / memory stick.
- Also copy over the c:\windows\system32\drivers\atapi.sys file to the storage device as well.
- Follow the instruction at UBCD for Windows on how to make a LiveCD of Windows.
- Start the PC with the new LiveCD and connect USB storage device to the PC.
- From the LiveCD Windows environment, go to Start > Program Files > Registry Editors > Regedit (remote). Here you will be asked to select a user from the machine to edit, which should be an account with administrative permissions.
- Go to File > Import, and select the atapi.reg file you saved to the storage device.
- Copy over the atapi.sys file from the storage device to the \windows\system32\drivers folder.
- Restart the PC, and remove the Live CD.
-----------------------------
Lets get your data off first so you dont loose it download PCHF boot cd from
http://www.software4free.org.uk/pchf.rar unrar it and write the iso to a cd then insert the cd and set the pc to boot from cd you will then have a version of windows running off the cd which you can then using a pendrive or cd get your data off before anything else.
Once you have got your data you can then try option 4 in post above.
=================================
Source
Solución de problemas generales
Controlar y solucionar la infección de mbr-virus en otro equipo con mbrcheck.exe
============================
Source
Option 1 - Repair Install (recommended)
- Use your Windows Setup CD during startup.
- At the start of Windows Setup, press [Enter] to install Windows.
- Press [R] to repair Windows XP installation.
Or if your running Vista, the option is to upgrade instead of repair.
Option 2 - Recovery Console
This is dependant on if a particular folder resides on the system called "ServicePackFiles"
- Insert your Windows Setup CD during startup.
- At the start of Windows Setup, press [R] for the Recovery Console (if an administrator password has been configured, it will ask you for it at this stage).
- At the recovery console, type in the following commands exactly:
copy c:\windows\servicepackfiles\i386\atapi.sys c:\windows\system32\drivers\atapi.sys
- Restart the PC and tap [F8] during startup.
- At the startup screen, select Last Known Good Configuration to restore the registry.
Option 3 - Remove HDD
- Remove the hard drive, and install it into a working PC that is running the same version and service pack.
- Right click and copy the c:\windows\system32\drivers\atapi.sys file from a working HDD to the newly installed HDD.
- Place the drive back in it's original PC.
- Start the PC and tap [F8] during startup.
- At the startup screen, select Last Known Good Configuration to restore the registry.
Option 4 - Using BartPE
- Download (but do not open) then the following registry file: atapi.reg
- Save it to a USB storage device / memory stick.
- Also copy over the c:\windows\system32\drivers\atapi.sys file to the storage device as well.
- Follow the instruction at UBCD for Windows on how to make a LiveCD of Windows.
- Start the PC with the new LiveCD and connect USB storage device to the PC.
- From the LiveCD Windows environment, go to Start > Program Files > Registry Editors > Regedit (remote). Here you will be asked to select a user from the machine to edit, which should be an account with administrative permissions.
- Go to File > Import, and select the atapi.reg file you saved to the storage device.
- Copy over the atapi.sys file from the storage device to the \windows\system32\drivers folder.
- Restart the PC, and remove the Live CD.
-----------------------------
Lets get your data off first so you dont loose it download PCHF boot cd from
http://www.software4free.org.uk/pchf.rar unrar it and write the iso to a cd then insert the cd and set the pc to boot from cd you will then have a version of windows running off the cd which you can then using a pendrive or cd get your data off before anything else.
Once you have got your data you can then try option 4 in post above.
=================================
Source
Solución de problemas generales
Antes de solucionar un mensaje de error Stop 0x0000007B,
lea íntegramente este artículo para determinar si se le aplica alguno
de los problemas específicos que se indican en las siguientes secciones.
Si no es el caso, siga estos pasos para la solución de problemas
generales:
Si recibe uno de los mensajes de error que figuran en este artículo durante la instalación de Windows XP, actualice el sistema BIOS del equipo, obtenga los controladores de Windows XP para la controladora del disco duro a través del fabricante del equipo, de la tarjeta de sistema o de la controladora de disco duro, o haga ambas cosas. Para obtener información sobre cómo actualizar el sistema BIOS u obtener los controladores de Windows XP, póngase en contacto con el fabricante de su equipo.
Use la característica Última configuración válida conocida. De este modo, puede que se resuelva el problema si recientemente instaló un controlador de dispositivos incompatible con la controladora de inicio.
Utilice la opción Reparar con el programa de instalación de Windows XP. Para obtener información adicional sobre cómo repararWindows XP mediante el programa de instalación, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 315341 Cómo realizar una actualización en contexto (reinstalación) de Windows XP
Restaure una copia de seguridad del Registro.
Virus en el sector de inicio. Puede que reciba un mensaje de error Stop 0x0000007B si el equipo está infectado con un virus en el sector de inicio. Compruebe si hay virus en el equipo. Si detecta un virus, compruebe también si hay virus en los disquetes antes de volver a usarlos.
Microsoft no proporciona software que pueda detectar o quitar los virus informáticos. Si sospecha o confirma que su equipo está infectado con un virus, obtenga software antivirus actualizado. Para obtener una lista de los proveedores de software antivirus, haga clic en el siguiente número de artículo para verlo en Microsoft Knowledge Base: 49500
Importante: si el equipo fue infectado, puede estar abierto a otras formas de ataque. Microsoft recomienda que se reconstruyan los servidores infectados abiertos a Internet (los servidores que funcionen sin un servidor de seguridad u otra protección), según las indicaciones publicadas en el sitio Web de CERT. Asimismo, se recomienda reconstruir cualquier otro equipo expuesto a riesgos debido a su proximidad a equipos infectados antes de volver a ponerlo en servicio.
Si un virus ha infectado el equipo basado en Windows XP y el programa de detección de virus no puede quitar el virus ni reparar el sistema, tendrá que volver a crear particiones, aplicar formato al disco duro y reinstalar Windows XP.
Para obtener información adicional sobre cómo crear particiones y aplicar formato a un disco duro con Windows XP, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 313348
Para obtener información adicional sobre cómo proteger el sector de inicio contra los virus en Windows XP, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 122221
Si recibe uno de los mensajes de error que figuran en este artículo durante la instalación de Windows XP, actualice el sistema BIOS del equipo, obtenga los controladores de Windows XP para la controladora del disco duro a través del fabricante del equipo, de la tarjeta de sistema o de la controladora de disco duro, o haga ambas cosas. Para obtener información sobre cómo actualizar el sistema BIOS u obtener los controladores de Windows XP, póngase en contacto con el fabricante de su equipo.
Use la característica Última configuración válida conocida. De este modo, puede que se resuelva el problema si recientemente instaló un controlador de dispositivos incompatible con la controladora de inicio.
Utilice la opción Reparar con el programa de instalación de Windows XP. Para obtener información adicional sobre cómo repararWindows XP mediante el programa de instalación, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 315341 Cómo realizar una actualización en contexto (reinstalación) de Windows XP
Restaure una copia de seguridad del Registro.
Virus en el sector de inicio. Puede que reciba un mensaje de error Stop 0x0000007B si el equipo está infectado con un virus en el sector de inicio. Compruebe si hay virus en el equipo. Si detecta un virus, compruebe también si hay virus en los disquetes antes de volver a usarlos.
Microsoft no proporciona software que pueda detectar o quitar los virus informáticos. Si sospecha o confirma que su equipo está infectado con un virus, obtenga software antivirus actualizado. Para obtener una lista de los proveedores de software antivirus, haga clic en el siguiente número de artículo para verlo en Microsoft Knowledge Base: 49500
Importante: si el equipo fue infectado, puede estar abierto a otras formas de ataque. Microsoft recomienda que se reconstruyan los servidores infectados abiertos a Internet (los servidores que funcionen sin un servidor de seguridad u otra protección), según las indicaciones publicadas en el sitio Web de CERT. Asimismo, se recomienda reconstruir cualquier otro equipo expuesto a riesgos debido a su proximidad a equipos infectados antes de volver a ponerlo en servicio.
Si un virus ha infectado el equipo basado en Windows XP y el programa de detección de virus no puede quitar el virus ni reparar el sistema, tendrá que volver a crear particiones, aplicar formato al disco duro y reinstalar Windows XP.
Para obtener información adicional sobre cómo crear particiones y aplicar formato a un disco duro con Windows XP, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 313348
Para obtener información adicional sobre cómo proteger el sector de inicio contra los virus en Windows XP, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 122221
Problemas del controlador de dispositivos
Puede que reciba un mensaje de error Stop 0x0000007B si un controlador de dispositivo que requiere la controladora de inicio del equipo no está configurado para que se inicie durante el proceso de instalación o si está dañado; o bien, si está dañada la información del Registro de Windows XP referente a los controladores de dispositivos que se cargan durante el proceso de instalación.
Windows XP requiere que un controlador de minipuerto se comunique con la controladora de disco duro que se utiliza para iniciar el equipo. SiWindows XP no incluye un controlador de dispositivo para la controladora o usa un controlador dañado o incompatible, deberá reemplazar el controlador con una copia válida que sea compatible con la controladora y Windows XP.
Durante la primera fase de la instalación de Windows XP, el programa de instalación muestra el mensaje siguiente en la parte inferior de la pantalla: Presione F6 si necesita instalar un SCSI oRAID de otro fabricante. Presione F6 y, a continuación, siga las instrucciones para instalar un controlador de dispositivos de almacenamiento masivo del fabricante del equipo OEM.
Para obtener información adicional sobre cómo utilizar F6 para cargar un controlador de dispositivos compatible del fabricante OEM, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 314859
Al presionar la tecla F6 durante la instalación deWindows XP se limita la compatibilidad de controladores OEM. Para determinar si la controladora de disco duro es compatible con Windows XP y obtener información sobre los controladores incluidos en el CD-ROM de Windows XP o que se pueden descargar, vea la versión más reciente de la lista de compatibilidad de hardware de Windows XP (HCL). Para obtener información adicional acerca de la versión más reciente de la lista HCL de Windows XP, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 314062 La versión más reciente de la lista de compatibilidad de hardware de Windows XP
Si su controladora de disco duro no figura en la lista HCL, póngase en contacto con el fabricante del equipo, de la tarjeta de sistema o de la controladora de disco duro para obtener información sobre la disponibilidad de un controlador. Microsoft no garantiza la disponibilidad de una solución para los equipos que no figuren en la lista HCL. Para obtener información adicional, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 315239
Directiva de soporte técnico de Microsoft para el hardware no incluido en la Lista de compatibilidad de hardware HCL de Windows.
Si está dañada la sección del sistema en el Registro de Windows XP, es posible que Windows XP no pueda cargar el controlador de dispositivos de minipuerto que requiere la controladora de inicio. Para resolver este problema, restaure una copia de seguridad del Registro. Para obtener información adicional sobre cómo restaurar una copia de seguridad del Registro, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 307545
Problemas de hardware.
Puede que reciba un mensaje de error Stop 0x0000007B si hay un conflicto de recursos entre la controladora de inicio y otra controladora, o entre dispositivos SCSI, o bien si no se ha realizado o se ha cambiado la conversión de unidades.
Para resolver este problema:
Si existe un conflicto de solicitudes IRQ o de direcciones de puerto de E/S entre la controladora de inicio y otra controladora,Windows XP deja de responder (se bloquea) o muestra un mensaje de error "Stop 0x0000007B". Si ha agregado nuevo hardware recientemente, quítelo o vuélvalo a configurar de modo que no entre en conflicto con los recursos de otras controladoras instaladas.
Si usa un disco duro SCSI, compruebe que la cadena SCSI está terminada correctamente. Quite todos los dispositivos SCSI no usados o asegúrese de que cada identificador SCSI es único.
Asegúrese de que la conversión de unidades está activada (si es preciso) y no se ha modificado. Por ejemplo, si ha cambiado recientemente las controladoras, este problema puede aparecer.Para obtener información adicional acerca de este problema, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 314082
Aparece el mensaje de error Stop 0x0000007B después de mover a otro equipo el disco de sistema de Windows XP
Otros problemas: Entre las demás posibles causas del mensaje de error Stop 0x0000007B figuran las siguientes:
El volumen de inicio está dañado y Windows XP no lo puede montar. Si el sistema de archivos está dañado y Windows XP no puede montar el volumen de inicio durante el proceso de inicio, cambie la unidad a otro equipo con Windows XP y ejecute el comando chkdsk en dicha unidad. O bien, intente crear una instalación paralela de Windows XP en otra carpeta de la unidad. El programa de instalación de Windows XP comprueba la integridad del volumen antes de copiar archivos y puede corregir algunos problemas.
Está instalando en una partición de inicio reflejada que fue creada por Windows NT 4.0. Windows XP no admite los conjuntos de volúmenes Ftdisk de Windows NT 4.0. Si usa Windows 2000, deberá convertir todos los conjuntos de volúmenes Ftdisk a volúmenes dinámicos antes de actualizar a Windows XP. Si usa Windows NT 4.0, deberá eliminar los reflejos existentes y realizar copias de seguridad de todos los datos en los conjuntos de volúmenes con bandas, RAID5 o extendidos antes de actualizar a Windows XP. Quizás no se pueda tener acceso a los conjuntos Ftdisk después de la actualización. Referencias: Para obtener información adicional acerca de los mensajes de error Stop 0x0000007B, haga clic en los números de artículo siguientes para verlos en Microsoft Knowledge Base: 316401
Aparece el mensaje de error STOP 0x0000007B después de reiniciar un equipo basado en Windows XP 303786
La sección [SysprepMassStorage] que falta hace que aparezca el mensaje de error STOP 0x7B en Windows XP al crear imágenes con Sysprep 315031
No es posible realizar la actualización con la versión de Windows XP incluida en MSDN 314082
Aparece el mensaje de error Stop 0x0000007B después de mover a otro equipo el disco de sistema de Windows XP 314859
Al presionar la tecla F6 durante la instalación de Windows XP se limita la compatibilidad de controladores OEM
Puede que reciba un mensaje de error Stop 0x0000007B si un controlador de dispositivo que requiere la controladora de inicio del equipo no está configurado para que se inicie durante el proceso de instalación o si está dañado; o bien, si está dañada la información del Registro de Windows XP referente a los controladores de dispositivos que se cargan durante el proceso de instalación.
Windows XP requiere que un controlador de minipuerto se comunique con la controladora de disco duro que se utiliza para iniciar el equipo. SiWindows XP no incluye un controlador de dispositivo para la controladora o usa un controlador dañado o incompatible, deberá reemplazar el controlador con una copia válida que sea compatible con la controladora y Windows XP.
Durante la primera fase de la instalación de Windows XP, el programa de instalación muestra el mensaje siguiente en la parte inferior de la pantalla: Presione F6 si necesita instalar un SCSI oRAID de otro fabricante. Presione F6 y, a continuación, siga las instrucciones para instalar un controlador de dispositivos de almacenamiento masivo del fabricante del equipo OEM.
Para obtener información adicional sobre cómo utilizar F6 para cargar un controlador de dispositivos compatible del fabricante OEM, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 314859
Al presionar la tecla F6 durante la instalación deWindows XP se limita la compatibilidad de controladores OEM. Para determinar si la controladora de disco duro es compatible con Windows XP y obtener información sobre los controladores incluidos en el CD-ROM de Windows XP o que se pueden descargar, vea la versión más reciente de la lista de compatibilidad de hardware de Windows XP (HCL). Para obtener información adicional acerca de la versión más reciente de la lista HCL de Windows XP, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 314062 La versión más reciente de la lista de compatibilidad de hardware de Windows XP
Si su controladora de disco duro no figura en la lista HCL, póngase en contacto con el fabricante del equipo, de la tarjeta de sistema o de la controladora de disco duro para obtener información sobre la disponibilidad de un controlador. Microsoft no garantiza la disponibilidad de una solución para los equipos que no figuren en la lista HCL. Para obtener información adicional, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 315239
Directiva de soporte técnico de Microsoft para el hardware no incluido en la Lista de compatibilidad de hardware HCL de Windows.
Si está dañada la sección del sistema en el Registro de Windows XP, es posible que Windows XP no pueda cargar el controlador de dispositivos de minipuerto que requiere la controladora de inicio. Para resolver este problema, restaure una copia de seguridad del Registro. Para obtener información adicional sobre cómo restaurar una copia de seguridad del Registro, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 307545
Problemas de hardware.
Puede que reciba un mensaje de error Stop 0x0000007B si hay un conflicto de recursos entre la controladora de inicio y otra controladora, o entre dispositivos SCSI, o bien si no se ha realizado o se ha cambiado la conversión de unidades.
Para resolver este problema:
Si existe un conflicto de solicitudes IRQ o de direcciones de puerto de E/S entre la controladora de inicio y otra controladora,Windows XP deja de responder (se bloquea) o muestra un mensaje de error "Stop 0x0000007B". Si ha agregado nuevo hardware recientemente, quítelo o vuélvalo a configurar de modo que no entre en conflicto con los recursos de otras controladoras instaladas.
Si usa un disco duro SCSI, compruebe que la cadena SCSI está terminada correctamente. Quite todos los dispositivos SCSI no usados o asegúrese de que cada identificador SCSI es único.
Asegúrese de que la conversión de unidades está activada (si es preciso) y no se ha modificado. Por ejemplo, si ha cambiado recientemente las controladoras, este problema puede aparecer.Para obtener información adicional acerca de este problema, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base: 314082
Aparece el mensaje de error Stop 0x0000007B después de mover a otro equipo el disco de sistema de Windows XP
Otros problemas: Entre las demás posibles causas del mensaje de error Stop 0x0000007B figuran las siguientes:
El volumen de inicio está dañado y Windows XP no lo puede montar. Si el sistema de archivos está dañado y Windows XP no puede montar el volumen de inicio durante el proceso de inicio, cambie la unidad a otro equipo con Windows XP y ejecute el comando chkdsk en dicha unidad. O bien, intente crear una instalación paralela de Windows XP en otra carpeta de la unidad. El programa de instalación de Windows XP comprueba la integridad del volumen antes de copiar archivos y puede corregir algunos problemas.
Está instalando en una partición de inicio reflejada que fue creada por Windows NT 4.0. Windows XP no admite los conjuntos de volúmenes Ftdisk de Windows NT 4.0. Si usa Windows 2000, deberá convertir todos los conjuntos de volúmenes Ftdisk a volúmenes dinámicos antes de actualizar a Windows XP. Si usa Windows NT 4.0, deberá eliminar los reflejos existentes y realizar copias de seguridad de todos los datos en los conjuntos de volúmenes con bandas, RAID5 o extendidos antes de actualizar a Windows XP. Quizás no se pueda tener acceso a los conjuntos Ftdisk después de la actualización. Referencias: Para obtener información adicional acerca de los mensajes de error Stop 0x0000007B, haga clic en los números de artículo siguientes para verlos en Microsoft Knowledge Base: 316401
Aparece el mensaje de error STOP 0x0000007B después de reiniciar un equipo basado en Windows XP 303786
La sección [SysprepMassStorage] que falta hace que aparezca el mensaje de error STOP 0x7B en Windows XP al crear imágenes con Sysprep 315031
No es posible realizar la actualización con la versión de Windows XP incluida en MSDN 314082
Aparece el mensaje de error Stop 0x0000007B después de mover a otro equipo el disco de sistema de Windows XP 314859
Al presionar la tecla F6 durante la instalación de Windows XP se limita la compatibilidad de controladores OEM
===============================
Source
Importante
Si el equipo está infectado, puede ser susceptible a otras formas de ataque. Recomendamos que vuelva a crear los servidores expuestos a Internet que estén infectado infectados siguiendo las instrucciones que se publican en el sitio Web CERT (http://www.cert.org/) . Los servidores expuestos a Internet son servidores que funcionan sin un firewall ni ninguna otra protección. Asimismo, se recomienda reconstruir cualquier otro equipo que esté en riesgo por su proximidad con equipos infectados antes de volver a ponerlo en servicio.
Si un virus ha infectado el equipo basado en Windows XP y el programa de detección de virus no puede quitar el virus ni reparar el sistema, tendrá que volver a crear particiones, dar formato al disco duro y reinstalar Windows XP. Para obtener más información sobre cómo crear particiones y dar formato a un disco duro con Windows XP, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base:
Si el equipo está infectado, puede ser susceptible a otras formas de ataque. Recomendamos que vuelva a crear los servidores expuestos a Internet que estén infectado infectados siguiendo las instrucciones que se publican en el sitio Web CERT (http://www.cert.org/) . Los servidores expuestos a Internet son servidores que funcionan sin un firewall ni ninguna otra protección. Asimismo, se recomienda reconstruir cualquier otro equipo que esté en riesgo por su proximidad con equipos infectados antes de volver a ponerlo en servicio.
Si un virus ha infectado el equipo basado en Windows XP y el programa de detección de virus no puede quitar el virus ni reparar el sistema, tendrá que volver a crear particiones, dar formato al disco duro y reinstalar Windows XP. Para obtener más información sobre cómo crear particiones y dar formato a un disco duro con Windows XP, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base:
313348
(http://support.microsoft.com/kb/313348/
)
Cómo hacer la partición de un disco duro y darle formato en Windows XP
Para obtener más información acerca de cómo
proteger el sector de inicio contra virus en Windows XP, haga clic en el número
de artículo siguiente para verlo en Microsoft Knowledge Base:
122221
(http://support.microsoft.com/kb/122221/
)
Cómo proteger el sector de inicio contra virus en Windows
Subscribe to:
Posts (Atom)