BT causes shutdown hangs in WinXP.

[trenchtown]

Hi there, this is my first post so please be kind!! I have an issue that is totally driving me crazy, it is simply this. I use BitTorrent regularly, without it my life would become pretty mundane, I've mainly used the original client but have recently switched to Azureus. When trying to close down my PC after using either BT client, the shutdown process invariably hangs on the 'saving your settings' screen causing me to reset my machine. I've recently done a reinstall of WinXP SP2 hoping that this might cure the fault but the same thing keeps happening. I know it's kinda clutching at straws but have any of you discovered the same problem or perhaps a cure? Any help would be like gold dust, thanks, Charlie.

[boogiedan]

alrite n welcome 2 zp
ive had probs in past wid bt(sameish probs)
i was using azureus n bittornado(speed on bittornado is why)
now i use BitLord(a mod of BitComet)
try either of above
should help

[Miniver]

Make sure you shut down the client before you try to shut windows down.

[DigitalJunkie]

I think Azureus is written in Java, someone correct me on this.

But anyways, you should update your Java from Sun if you have not anyway!

http://java.sun.com/j2se/1.5.0/download.jsp

[Travis982]

I use Azureus (with all Java updates) and it takes a long time to quit when I shut down. At first I thought it hung my system, but found that it eventually will close and allow Windows to end. I have WinXP w/SP1.

Don't have any clue why it takes so long. Anyone have any ideas?

[DigitalJunkie]

When it comes to resource management, Windows OS is not very efficient!

[cpugeniusmv]

When it comes to resource management, Windows OS is not very efficient!

I think Windows XP is damn good at resource management. But many programs that run under XP are terrible at it.

[trenchtown]

Hi Peeps, many thanks for all the responses to this one, I truly, truly, appreciate it, a few follow ups to all of the above. I will definitely have a look at BitLord although my guess is that as most of these clients are based on the same core the problem will persist. Yes, Azureus is written in Java of which I do have the latest version from Sun, so out of date Java is not the issue. I tried Azureus because it was Java, i.e. a different mechanism to BT original but like I say, the system still hangs on the 'saving your settings' screen. I always close down any BT client before attempting to shutdown, I've even installed an advanced task manager to make sure that no BT related processes are running in the background. This is really doing my brain in, it's not so much of a problem if I just want to turn the computer off, I can do that via the plug in the wall but when a program requires a system restart (PartitionMagic, DriveImage etc) it can create havoc.
I do have ZoneAlarm on my machine, it's version 4.5 so there is no actual conflict with Azureus or any other client but I am beginning to wonder if this program might have something to do with my problems.
Thanks again for your kindness and suggestions, hopefully someone may be able to shed some light on this before I go totally spare, regards, Charlie.

[DigitalJunkie]

Windows doesn't close all the memory even that program has closed (ie. icons, menus, etc.), why is this necssary? I have no ideas, since speed of open & close program(s) is not that big of a issues to me. All I really need, are the icons, etc. on the desktop for the Windows OS at all times.

[cpugeniusmv]

Windows doesn't close all the memory even that program has closed (ie. icons, menus, etc.), why is this necssary? I have no ideas, since speed of open & close program(s) is not that big of a issues to me. All I really need, are the icons, etc. on the desktop for the Windows OS at all times.

It's not Windows' fault. It's the responsibility of individual programs to manage their own memory usage. If they don't release some memory after closing, that's their own fault.

[DigitalJunkie]

There are bad applications, but most are unlike those bad resident memory apps. in the past that would still be running after the application is closed without releasing the memory until you reboot. Since it is Windows to released memory areas to applications, so those applications can run its operations. It is up to Windows to efficiently mange the reservations of memory areas! Keeping more icons, menus, etc., from closed applications so if re-running those applications can be faster, to me it is not a efficient way of managing those resources.

[pkmugg]

I use a program called rambooster to release programs' memory if they don't release it when they close. It's a little old, but it's free and gets the job done.