i dont want to try the longhorn alpha version but 1 question to all that installed the newsest 4015 version....

can u explain alittle about the kill button for explorer??


thanks

Well even in released versions of Windows operating system, Explorer has a tendency to stop responding and therefore needs to be killed and restarted.

Most likely the alpha is as at such point where this has become so commonplace that made a button to do just that.

I haven't installed 4015, but this has been the theory thus far.

i knew that but maybe i wasnt clear enough...i was wondering if like there is anything special about it except that what u said?


thanks taco supremo

After all those boot problems, I finally got 4015 installed, but didn't see this button to kill Explorer. I even looked through all the sidebar options.

I've also tracked the down the original article, but I don't see it explicity pointed out in any of the screenshots.

The only thing I can think of is that they're referring to the lightning bolt portrayed in the 5th screenshot, but all it does is display a list of the Quick Launch entries.

here's the kill button:

http://www.winbeta.org/images/4015/kill.jpg

Right and winbeta screwed up in saying that it kills explorer. It doesn't! It kills that application that u right click on on the taskbar. Now that we cleared that up

Ah, that explains why I didn't see it. Thanks for clearing that up wI-OSMAN-2.

so it's jsut a quick way of using ctrl alt and del?

Exactly

An exploxer kill switch would be good though, as it re-sets your soft reg-edits.

yer that would be good, and also what would be good is just under the kill button should be shut down computer

Yeah, but sometimes your computer is on such a high load that it takes a while to enter task manager and can crash your computer in the process. Kill is a wonderful method of preventing constant crashes in slow cpu/memory machines.

i supose, but why the bloddy hell did ms remove java support from xp, and did they do it to longhorn?

Talk about off topic. You're good at that devildan!

It was part of the whole court order that Sun filed against Microsoft for violating the terms of their agreement. Hence SP1a for XP which pulled Microsoft's rendition of Java runtime and SP1b & SP2 which will put Sun's rendition in its place. The same will eventually hold true for Longhorn if they haven't done so already.

Sun's version of Java sucks tho. Its A LOT and i mean A LOT more resource heavy and not to mention SLOW.

yer i know. thats why i went mozilla

soz about off topic

If you're saying that you went to Mozilla because Sun's version of Java is slow, that doesn't make any sense because Mozilla uses Sun's version. It's IE which uses the faster one by Microsoft.

However, you can still download Microsoft's version or just not apply SP1a to prevent it from being removed in the first place.

Sorry to keep this topic off topic but I just want to add my voice to the tide of displeasure about the Java situation. WTF gives Sun the right to bitch because they make a competitive product that nobody wants? I remember a quote a while back about this situation being like Coke having to include three cans of Pepsi in every case... Maybe I'm missing something about the whole battle but it doesn't really seem worth the trouble. Is Symantec suing MS for putting System Restore in XP? Are firewall makers suing MS for including a firewall in XP? And what is Sun gaining out of all this? A whole lot of nothing, if you ask me.

The jist of the lawsuit was that, under the original terms, MS had agreed to NOT modify Java's normal behavior. In return MS could make use of Java's technology and API. However Microsoft violated that with both J++ and their Java Virtual Machine which is why they were held at fault.

Interesting... although I still don't see how it makes any difference... the only people making money off it are lawyers!