Write disk file to raw floppy diskette
Enter disk image source file name: bd030112.bin
Enter target diskette drive: a
Remaining Update Soon Keep watch !!!
Sunday, April 20, 2008
Disable Error Reporting
| Disable Error Reporting 1. Open Control Panel 2. Click on Performance and Maintenance. 3. Click on System. 4. Then click on the Advanced tab 5. Click on the error-reporting button on the bottom of the windows. 6. Select Disable error reporting. 7. Click OK 8. Click OK |
Win XP Won’t Completely Shutdown
Win XP Won’t Completely Shutdown
- Goto Control Panel, then goto Power Options.
- Click on the APM Tab, then check the "Enable Advanced Power Management support."
- Shut down your PC. It should now successfully complete the Shut Down process.
- Goto Control Panel, then goto Power Options.
- Click on the APM Tab, then check the "Enable Advanced Power Management support."
- Shut down your PC. It should now successfully complete the Shut Down process.
Remove Shared Documents
Remove Shared Documents
Open Regedit(Start- Run- Regedit) and navigate to HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersion Explorer My Computer NameSpace DelegateFolders
There will see a sub-key named {59031a47-3f72-44a7-89c5-5595fe6b30ee}. By Deleting this you can remove the 'Other Files stored on This Computer' group.
Open Regedit(Start- Run- Regedit) and navigate to HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersion Explorer My Computer NameSpace DelegateFolders
There will see a sub-key named {59031a47-3f72-44a7-89c5-5595fe6b30ee}. By Deleting this you can remove the 'Other Files stored on This Computer' group.
Force users to press Ctrl-Alt-Delete to Logon
Force users to press Ctrl-Alt-Delete to Logon
(XPPro only)
Go to start/run,
and type control userpasswords2
(XPPro only)
Go to start/run,
and type control userpasswords2
How to Convert FAT to NTFS file system
How to Convert FAT to NTFS file system
To convert a FAT partition to NTFS, perform the following steps.
Click Start, click Programs, and then click Command Prompt.
In Windows XP, click Start, click Run, type cmd and then click OK.
At the command prompt, type CONVERT [driveletter]: /FS:NTFS.
Convert.exe will attempt to convert the partition to NTFS.
NOTE: Although the chance of corruption or data loss during the conversion from FAT to NTFS is minimal, it is best to perform a full backup of the data on the drive that it is to be converted prior to executing the convert command. It is also recommended to verify the integrity of the backup before proceeding, as well as to run RDISK and update the emergency repair disk (ERD).
To convert a FAT partition to NTFS, perform the following steps.
Click Start, click Programs, and then click Command Prompt.
In Windows XP, click Start, click Run, type cmd and then click OK.
At the command prompt, type CONVERT [driveletter]: /FS:NTFS.
Convert.exe will attempt to convert the partition to NTFS.
NOTE: Although the chance of corruption or data loss during the conversion from FAT to NTFS is minimal, it is best to perform a full backup of the data on the drive that it is to be converted prior to executing the convert command. It is also recommended to verify the integrity of the backup before proceeding, as well as to run RDISK and update the emergency repair disk (ERD).
Monday, April 7, 2008
Windows Update's silent patches
Microsoft updates Windows without users' consent By Scott Dunn
Microsoft has begun patching files on Windows XP and Vista without users' knowledge, even when the users have turned off auto-updates.
Many companies require testing of patches before they are widely installed, and businesses in this situation are objecting to the stealth patching.
Files changed with no notice to users
In recent days, Windows Update (WU) started altering files on users' systems without displaying any dialog box to request permission. The only files that have been reportedly altered to date are nine small executables on XP and nine on Vista that are used by WU itself. Microsoft is patching these files silently, even if auto-updates have been disabled on a particular PC.
It's surprising that these files can be changed without the user's knowledge. The Automatic Updates dialog box in the Control Panel can be set to prevent updates from being installed automatically. However, with Microsoft's latest stealth move, updates to the WU executables seem to be installed regardless of the settings — without notifying users.
When users launch Windows Update, Microsoft's online service can check the version of its executables on the PC and update them if necessary. What's unusual is that people are reporting changes in these files although WU wasn't authorized to install anything.
This isn't the first time Microsoft has pushed updates out to users who prefer to test and install their updates manually. Not long ago, another Windows component, svchost.exe, was causing problems with Windows Update, as last reported on June 21 in the Windows Secrets Newsletter. In that case, however, the Windows Update site notified users that updated software had to be installed before the patching process could proceed. This time, such a notice never appears.
For users who elect not to have updates installed automatically, the issue of consent is crucial. Microsoft has apparently decided, however, that it doesn't need permission to patch Windows Updates files, even if you've set your preferences to require it.
Microsoft provides no tech information — yet
To make matters even stranger, a search on Microsoft's Web site reveals no information at all on the stealth updates. Let's say you wished to voluntarily download and install the new WU executable files when you were, for example, reinstalling a system. You'd be hard-pressed to find the updated files in order to download them. At this writing, you either get a stealth install or nothing.
A few Web forums have already started to discuss the updated files, which bear the version number 7.0.6000.381. The only explanation found at Microsoft's site comes from a user identified as Dean-Dean on a Microsoft Communities forum. In reply to a question, he states:
"Windows Update Software 7.0.6000.381 is an update to Windows Update itself. It is an update for both Windows XP and Windows Vista. Unless the update is installed, Windows Update won't work, at least in terms of searching for further updates. Normal use of Windows Update, in other words, is blocked until this update is installed."
Windows Secrets contributing editor Susan Bradley contacted Microsoft Partner Support about the update and received this short reply:
"7.0.6000.381 is a consumer only release that addresses some specific issues found after .374 was released. It will not be available via WSUS [Windows Server Update Services]. A standalone installer and the redist will be available soon, I will keep an eye on it and notify you when it is available."
Unfortunately, this reply does not explain why the stealth patching began with so little information provided to customers. Nor does it provide any details on the "specific issues" that the update supposedly addresses.
System logs confirm stealth installs
In his forum post, Dean-Dean names several files that are changed on XP and Vista. The patching process updates several Windows\System32 executables (with the extensions .exe, .dll, and .cpl) to version 7.0.6000.381, according to the post.
In Vista, the following files are updated:
1. wuapi.dll
2. wuapp.exe
3. wuauclt.exe
4. wuaueng.dll
5. wucltux.dll
6. wudriver.dll
7. wups.dll
8. wups2.dll
9. wuwebv.dll
In XP, the following files are updated:
1. cdm.dll
2. wuapi.dll
3. wuauclt.exe
4. wuaucpl.cpl
5. wuaueng.dll
6. wucltui.dll
7. wups.dll
8. wups2.dll
9. wuweb.dll
These files are by no means viruses, and Microsoft appears to have no malicious intent in patching them. However, writing files to a user's PC without notice (when auto-updating has been turned off) is behavior that's usually associated with hacker Web sites. The question being raised in discussion forums is, "Why is Microsoft operating in this way?"
How to check which version your PC has
If a system has been patched in the past few months, the nine executables in Windows\System32 will either show an earlier version number, 7.0.6000.374, or the stealth patch: 7.0.6000.381. (The version numbers can be seen by right-clicking a file and choosing Properties. In XP, click the Version tab and then select File Version. In Vista, click the Details tab.)
In addition, PCs that received the update will have new executables in subfolders named 7.0.6000.381 under the following folders:
c:\Windows\System32\SoftwareDistribution\Setup\ServiceStartup\wups.dll
c:\Windows\System32\SoftwareDistribution\Setup\ServiceStartup\wups2.dll
Users can also verify whether patching occurred by checking Windows' Event Log:
Step 1. In XP, click Start, Run.
Step 2. Type eventvwr.msc and press Enter.
Step 3. In the tree pane on the left, select System.
Step 4. The right pane displays events and several details about them. Event types such as "Installation" are labeled in the Category column. "Windows Update Agent" is the event typically listed in the Source column for system patches.
On systems that were checked recently by Windows Secrets readers, the Event Log shows two installation events on Aug. 24. The files were stealth-updated in the early morning hours. (The time stamp will vary, of course, on machines that received the patch on other dates.)
To investigate further, you can open the Event Log's properties for each event. Normally, when a Windows update event occurs, the properties dialog box shows an associated KB number, enabling you to find more information at Microsoft's Web site. Mysteriously, no KB number is given for the WU updates that began in August. The description merely reads, "Installation Successful: Windows successfully installed the following update: Automatic Updates."
No need to roll back the updated files
Again, it's important to note that there's nothing harmful about the updated files themselves. There are no reports of software conflicts and no reason to remove the files (which WU apparently needs in order to access the latest patches). The only concern is the mechanism Microsoft is using to perform its patching, and how this mechanism might be used by the software giant in the future.
http://WindowsSecrets.com/comp/070913
Microsoft has begun patching files on Windows XP and Vista without users' knowledge, even when the users have turned off auto-updates.
Many companies require testing of patches before they are widely installed, and businesses in this situation are objecting to the stealth patching.
Files changed with no notice to users
In recent days, Windows Update (WU) started altering files on users' systems without displaying any dialog box to request permission. The only files that have been reportedly altered to date are nine small executables on XP and nine on Vista that are used by WU itself. Microsoft is patching these files silently, even if auto-updates have been disabled on a particular PC.
It's surprising that these files can be changed without the user's knowledge. The Automatic Updates dialog box in the Control Panel can be set to prevent updates from being installed automatically. However, with Microsoft's latest stealth move, updates to the WU executables seem to be installed regardless of the settings — without notifying users.
When users launch Windows Update, Microsoft's online service can check the version of its executables on the PC and update them if necessary. What's unusual is that people are reporting changes in these files although WU wasn't authorized to install anything.
This isn't the first time Microsoft has pushed updates out to users who prefer to test and install their updates manually. Not long ago, another Windows component, svchost.exe, was causing problems with Windows Update, as last reported on June 21 in the Windows Secrets Newsletter. In that case, however, the Windows Update site notified users that updated software had to be installed before the patching process could proceed. This time, such a notice never appears.
For users who elect not to have updates installed automatically, the issue of consent is crucial. Microsoft has apparently decided, however, that it doesn't need permission to patch Windows Updates files, even if you've set your preferences to require it.
Microsoft provides no tech information — yet
To make matters even stranger, a search on Microsoft's Web site reveals no information at all on the stealth updates. Let's say you wished to voluntarily download and install the new WU executable files when you were, for example, reinstalling a system. You'd be hard-pressed to find the updated files in order to download them. At this writing, you either get a stealth install or nothing.
A few Web forums have already started to discuss the updated files, which bear the version number 7.0.6000.381. The only explanation found at Microsoft's site comes from a user identified as Dean-Dean on a Microsoft Communities forum. In reply to a question, he states:
"Windows Update Software 7.0.6000.381 is an update to Windows Update itself. It is an update for both Windows XP and Windows Vista. Unless the update is installed, Windows Update won't work, at least in terms of searching for further updates. Normal use of Windows Update, in other words, is blocked until this update is installed."
Windows Secrets contributing editor Susan Bradley contacted Microsoft Partner Support about the update and received this short reply:
"7.0.6000.381 is a consumer only release that addresses some specific issues found after .374 was released. It will not be available via WSUS [Windows Server Update Services]. A standalone installer and the redist will be available soon, I will keep an eye on it and notify you when it is available."
Unfortunately, this reply does not explain why the stealth patching began with so little information provided to customers. Nor does it provide any details on the "specific issues" that the update supposedly addresses.
System logs confirm stealth installs
In his forum post, Dean-Dean names several files that are changed on XP and Vista. The patching process updates several Windows\System32 executables (with the extensions .exe, .dll, and .cpl) to version 7.0.6000.381, according to the post.
In Vista, the following files are updated:
1. wuapi.dll
2. wuapp.exe
3. wuauclt.exe
4. wuaueng.dll
5. wucltux.dll
6. wudriver.dll
7. wups.dll
8. wups2.dll
9. wuwebv.dll
In XP, the following files are updated:
1. cdm.dll
2. wuapi.dll
3. wuauclt.exe
4. wuaucpl.cpl
5. wuaueng.dll
6. wucltui.dll
7. wups.dll
8. wups2.dll
9. wuweb.dll
These files are by no means viruses, and Microsoft appears to have no malicious intent in patching them. However, writing files to a user's PC without notice (when auto-updating has been turned off) is behavior that's usually associated with hacker Web sites. The question being raised in discussion forums is, "Why is Microsoft operating in this way?"
How to check which version your PC has
If a system has been patched in the past few months, the nine executables in Windows\System32 will either show an earlier version number, 7.0.6000.374, or the stealth patch: 7.0.6000.381. (The version numbers can be seen by right-clicking a file and choosing Properties. In XP, click the Version tab and then select File Version. In Vista, click the Details tab.)
In addition, PCs that received the update will have new executables in subfolders named 7.0.6000.381 under the following folders:
c:\Windows\System32\SoftwareDistribution\Setup\ServiceStartup\wups.dll
c:\Windows\System32\SoftwareDistribution\Setup\ServiceStartup\wups2.dll
Users can also verify whether patching occurred by checking Windows' Event Log:
Step 1. In XP, click Start, Run.
Step 2. Type eventvwr.msc and press Enter.
Step 3. In the tree pane on the left, select System.
Step 4. The right pane displays events and several details about them. Event types such as "Installation" are labeled in the Category column. "Windows Update Agent" is the event typically listed in the Source column for system patches.
On systems that were checked recently by Windows Secrets readers, the Event Log shows two installation events on Aug. 24. The files were stealth-updated in the early morning hours. (The time stamp will vary, of course, on machines that received the patch on other dates.)
To investigate further, you can open the Event Log's properties for each event. Normally, when a Windows update event occurs, the properties dialog box shows an associated KB number, enabling you to find more information at Microsoft's Web site. Mysteriously, no KB number is given for the WU updates that began in August. The description merely reads, "Installation Successful: Windows successfully installed the following update: Automatic Updates."
No need to roll back the updated files
Again, it's important to note that there's nothing harmful about the updated files themselves. There are no reports of software conflicts and no reason to remove the files (which WU apparently needs in order to access the latest patches). The only concern is the mechanism Microsoft is using to perform its patching, and how this mechanism might be used by the software giant in the future.
http://WindowsSecrets.com/comp/070913
BEFORE you go VISTA, READ THIS from Microsoft!
Please read this important information before proceeding
• System requirements
View system requirements and information on Windows Vista Capable and Premium Ready PCs.
• Release notes
View the release notes for Windows Vista RC1 (available in English only).
• Upgrade limitations
You may not be able to upgrade your installation of Windows Vista RC1 to the final, commercially available edition of Windows Vista. To upgrade, you will need to acquire the final edition of Windows Vista and you may have to do a clean installation.
• Time-limited software
Windows Vista RC1 is time-limited, pre-release software that will expire on June 1, 2007.
• Beta support policy
This is pre-release (beta) software distributed for trial and testing purposes only.
Microsoft does not provide technical support for beta releases.
Although formal support is not offered for this beta, we have provided newsgroups to help answer questions you may have related to the installation and use of Windows Vista RC1.
To join or read postings in these newsgroups, please visit
http://windowshelp.microsoft.com.
• 2007 Office System Beta 2 compatibility
If you are using 2007 Office system Beta 2 be sure to download the 2007 Microsoft Office system Beta 2 Technical Refresh, the most recent update. (The Technical Refresh is required to use Office Beta 2 with Windows Vista RC1.)
• Installation limitations
There are three installation scenarios for Windows Vista RC1:
1. You can do a clean installation.
This process will overwrite any data that you have on your hard disk or on your installation partition. The overwritten data will be lost and unrecoverable.
2. You can upgrade an existing installation of Windows XP.
3. You can upgrade an existing installation of Windows Vista Beta 2.
No other installation scenarios are supported.
Upgrading to this beta from any other edition of Windows requires a clean installation, as described in option 1.
In addition, once you install Windows Vista RC1, you cannot roll back to the previous operating system installation—you will either have to acquire and install the final released edition of Windows Vista or reinstall a previous edition of Windows.
Before installing Windows Vista RC1 on any computer, please remember to back up all your files.
Upgrading from Windows Vista Beta 2
Please install any Critical Updates from Windows Update before upgrading from Beta 2 to RC1.
Go to Start, All Programs, Windows Update, and click the "Check for Updates" button.
Note: Please close any open applications before beginning an upgrade. During installation, we recommend that you have an active Internet connection and choose Go online to get the latest updates for installation.
• System requirements
View system requirements and information on Windows Vista Capable and Premium Ready PCs.
• Release notes
View the release notes for Windows Vista RC1 (available in English only).
• Upgrade limitations
You may not be able to upgrade your installation of Windows Vista RC1 to the final, commercially available edition of Windows Vista. To upgrade, you will need to acquire the final edition of Windows Vista and you may have to do a clean installation.
• Time-limited software
Windows Vista RC1 is time-limited, pre-release software that will expire on June 1, 2007.
• Beta support policy
This is pre-release (beta) software distributed for trial and testing purposes only.
Microsoft does not provide technical support for beta releases.
Although formal support is not offered for this beta, we have provided newsgroups to help answer questions you may have related to the installation and use of Windows Vista RC1.
To join or read postings in these newsgroups, please visit
http://windowshelp.microsoft.com.
• 2007 Office System Beta 2 compatibility
If you are using 2007 Office system Beta 2 be sure to download the 2007 Microsoft Office system Beta 2 Technical Refresh, the most recent update. (The Technical Refresh is required to use Office Beta 2 with Windows Vista RC1.)
• Installation limitations
There are three installation scenarios for Windows Vista RC1:
1. You can do a clean installation.
This process will overwrite any data that you have on your hard disk or on your installation partition. The overwritten data will be lost and unrecoverable.
2. You can upgrade an existing installation of Windows XP.
3. You can upgrade an existing installation of Windows Vista Beta 2.
No other installation scenarios are supported.
Upgrading to this beta from any other edition of Windows requires a clean installation, as described in option 1.
In addition, once you install Windows Vista RC1, you cannot roll back to the previous operating system installation—you will either have to acquire and install the final released edition of Windows Vista or reinstall a previous edition of Windows.
Before installing Windows Vista RC1 on any computer, please remember to back up all your files.
Upgrading from Windows Vista Beta 2
Please install any Critical Updates from Windows Update before upgrading from Beta 2 to RC1.
Go to Start, All Programs, Windows Update, and click the "Check for Updates" button.
Note: Please close any open applications before beginning an upgrade. During installation, we recommend that you have an active Internet connection and choose Go online to get the latest updates for installation.
Friday, April 4, 2008
start up problem
start up problem
"instruction at 0x00000000 reference memory at 0x00000000 memory could not be readed". click ok to terminate or cancel pop up message showing every time when the system boots.
Solution:
Is any Dump of Memory
Goto Start----> Right click on My Computer ---> Properties----->Advanced--->Performance--->Advanced--->Virtual Memory
---->change value to 756 MB or 1024MB
then Set and click OK ..RESTART THE COMPUTER....
"instruction at 0x00000000 reference memory at 0x00000000 memory could not be readed". click ok to terminate or cancel pop up message showing every time when the system boots.
Solution:
Is any Dump of Memory
Goto Start----> Right click on My Computer ---> Properties----->Advanced--->Performance--->Advanced--->Virtual Memory
---->change value to 756 MB or 1024MB
then Set and click OK ..RESTART THE COMPUTER....
Wednesday, April 2, 2008
Microsoft Surface launching April 17th... with AT&T
Microsoft Surface launching April 17th... with AT&TNo, Microsoft hasn't suddenly transformed its 30-inch, multi-touch Surface into a big-ass cellphone. It has, however, chosen AT&T to launch the world's first Surface into retail. Shoppers in New York, Atlanta, San Antonio, and San Francisco will be treated to what amounts to the novelty (at least initially) of learning about a device (Samsung BlackJack II, pictured) by simply placing it atop the Surface. They'll also have the ability to explore interactive coverage maps. Later, users will be able to drag ringtones, graphics and video and drop it into "the phones." Note their use of "the" and not "your" phone in the press release. Nevertheless, we're happy to see Microsoft get the technology out the door on its long march towards consumerdom.
http://www.engadget.com/2008/04/02/m...h-with-atandt/
Subscribe to:
Posts (Atom)
RAJ SOLUTION'S
