The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: OT: IIS Control Panel in ASP.NET?


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: My first XP SP2 crash issue!


  • Subject: RE: My first XP SP2 crash issue!
  • From: "Paul Gale" <groups@xxxxxxxxxxxxxxxx>
  • Date: Sat, 4 Sep 2004 11:52:38 +0100

I've had a similar thing when sometimes viewing a folder with DivX videos
in - don't have Dr DivX but I think it's something to do with the CODEC.
The DivX website suggests running XP SP2 with the following switch:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional COMPATIBLE" /fastdetect /Execute

rather than:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect /NoExecute=OptIn

Paul.


> -----Original Message-----
> From: big_red_frog [mailto:anthony.tod@xxxxxxx]
> Sent: 04 September 2004 08:01
> To: ukha_d@xxxxxxx
> Subject: [ukha_d] My first XP SP2 crash issue!
>
> Hi All,
>
> Just to save some of you some time, if you have the same issue.
>
> I suddenly noticed that both my main machines were crashing explorer
> out if I tried to right click context menu any icons on the desktop
> or in explorer.
>
> All this since installing XP SP2
>
> After some digging around I found it was the Dr. Divx installed
> context menu entries. Something to do with the way they do it, ( and
> the same for spy sweeper ) that SP2 doesn't like.
>
> They are supposedly working on a fix.
>
> Meanwhile remove the reg key via regedit.
>
> search for "EncodeDivXExt"
>
> And delete the entry.
>
> Sorted both my machines out.
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>




UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.