Tuesday, July 21, 2009

Windows XP doesn't play the autorun

Autorun in Windows XP is not working. Here is the solution.

 clipped from winhlp.com

Autoplay after inserting a CD or DVD


General

The two most common complaints about autoplay are that it works when it shouldn't and that it doesn't work when it should.

I want to shut it off

To shut it off globally for all CD and DVD drives, use Start, Run ..., regedit to navigate to the following key:

HKEY_LOCAL_MACHINE
 \SYSTEM
  \CurrentControlSet
   \Services
    \Cdrom
REG_DWORD value: Autorun

Change this value from 1 to 0.

Of course, changing it back to 1 will re-enable autorun.

To change Autorun for a particular CD or DVD drive, right-click on the drive in Windows Explorer and use the Autorun tab.

There is a second registry key that affects the autorun function in Windows Vista and possibly also in Windows XP. It can occur twice, once for each user and once for the entire machine.

HKEY_CURRENT_USER
 \Software
  \Microsoft
   \Windows
    \CurrentVersion
     \Policies
      \Explorer
REG_DWORD value: NoDriveTypeAutoRun

HKEY_LOCAL_MACHINE
 \Software
  \Microsoft
   \Windows
    \CurrentVersion
     \Policies
      \Explorer
REG_DWORD value: NoDriveTypeAutoRun

Hexadecimal B5 or decimal 181 indicates that Autorun is off, while hexadecimal 91 or decimal 145 indicates that Autorun is active.

The meaning of these values is:

Value Meaning
0x1 Disables Autoplay on drives of unknown type.
0x4 Disables Autoplay on removable drives.
0x8 Disables Autoplay on fixed drives.
0x10 Disables Autoplay on network drives.
0x20 Disables Autoplay on CD-ROM drives.
0x40 Disables Autoplay on RAM drives.
0x80 Disables Autoplay on drives of unknown type.
0xFF Disables Autoplay on all types of drives.

The actual value is the sum of the selected values. The default value is 0x95.


Autorun, Autoplay

Tue, 2007-07-17 19:41 by admin · Forum/category:

General

There are two different kinds of autorun, also called autoplay, that are technically quite distinct. One is that some programs run on their own after your computer is booted and a user logs on. This is sometimes called autostart or autorun.

The other is that some programs are automatically loaded when you insert removable drive media like a DVD or some other removable storage. This is usually called autoplay or sometimes confusingly also autorun. Let's deal with this first.

Autoplay after inserting a CD or DVD

General

The two most common complaints about autoplay are that it works when it shouldn't and that it doesn't work when it should.

I want to shut it off

To shut it off globally for all CD and DVD drives, use Start, Run ..., regedit to navigate to the following key:

HKEY_LOCAL_MACHINE
 \SYSTEM
  \CurrentControlSet
   \Services
    \Cdrom
REG_DWORD value: Autorun

Change this value from 1 to 0.

Of course, changing it back to 1 will re-enable autorun.

To change Autorun for a particular CD or DVD drive, right-click on the drive in Windows Explorer and use the Autorun tab.

There is a second registry key that affects the autorun function in Windows Vista and possibly also in Windows XP. It can occur twice, once for each user and once for the entire machine.

HKEY_CURRENT_USER
 \Software
  \Microsoft
   \Windows
    \CurrentVersion
     \Policies
      \Explorer
REG_DWORD value: NoDriveTypeAutoRun

HKEY_LOCAL_MACHINE
 \Software
  \Microsoft
   \Windows
    \CurrentVersion
     \Policies
      \Explorer
REG_DWORD value: NoDriveTypeAutoRun

Hexadecimal B5 or decimal 181 indicates that Autorun is off, while hexadecimal 91 or decimal 145 indicates that Autorun is active.

The meaning of these values is:

Value Meaning
0x1 Disables Autoplay on drives of unknown type.
0x4 Disables Autoplay on removable drives.
0x8 Disables Autoplay on fixed drives.
0x10 Disables Autoplay on network drives.
0x20 Disables Autoplay on CD-ROM drives.
0x40 Disables Autoplay on RAM drives.
0x80 Disables Autoplay on drives of unknown type.
0xFF Disables Autoplay on all types of drives.

The actual value is the sum of the selected values. The default value is 0x95.

More information on annoyances.org

Get Clipmarks - The easiest way to email text, images and videos you find on the web.
Sent with Clipmarks

Tuesday, July 14, 2009

SysInternals Process Explorer Crash Resolved

 clipped from forum.sysinternals.com

Problems with PE ...


How do I see my Task Manager again???

Please read How do I see my Task Manager again???.

(In short, delete the key [HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\taskmgr.exe].)

Well.... I deleted the key you told me but still as i want to start PE

"Sysinternals Process Explorer has occurred a problem and has to be closed. We are sorry about the inconvenience. "   (I have another lang O/S

Check the Application and System event logs in the Event Viewer (start -> run -> eventvwr -> OK).




0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 70 72 6f   ure  pro
0018: 63 65 78 70 2e 65 78 65   cexp.exe
0020: 20 31 31 2e 32 31 2e 30    11.21.0
0028: 2e 30 20 69 6e 20 70 72   .0 in pr
0030: 6f 63 65 78 70 2e 65 78   ocexp.ex
0038: 65 20 31 31 2e 32 31 2e   e 11.21.
0040: 30 2e 30 20 61 74 20 6f   0.0 at o
0048: 66 66 73 65 74 20 30 30   ffset 00
0050: 30 31 37 35 64 30 0d 0a   0175d0..

and it tells me that the error is an application error and the adress is

0x000175d0‏...


0x000175d0

That's helpful.

First, exit PE, and then try executing the following commands from a CMD prompt:

unlodctr .NETFramework
lodctr c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\corperfmonsymbols.ini
 
unlodctr .NETFramework
lodctr c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\corperfmonsymbols.ini

Thank you very much!!! Smile
 
Now PE finally works! :) I suggest putting this topic in the F.A.Q so it can help other people with this strange error
 
Again, Thank you very much for your help I really appreciate that


Parts of the problem are in the FAQ.  The particular crash address that is related to the problem will generally change for each version of procexp.exe.  And this specific solution is not always guaranteed to solve the problem; sometimes, one must resort to uninstalling / reinstalling / repairing installations of the .NET Framework.  But yes - the particular FAQ item relating to this certainly could use some augmentation.

Get Clipmarks - The easiest way to email text, images and videos you find on the web.
Sent with Clipmarks