BitComet is designed to be userfriendly and offers many abilities not found in any other client, but being a free product, there are limited resources and developing multiple versions for different platforms would involve a lot of work. Perhaps someday our development team will feel ambitious and begin development on Linux and/or Mac versions, but I don’t see it happening any time soon.

TuuS

You found the problem, Sir.

However, expecting BitComet to also have a release for other OSes was a mistake from my part. It seems to be a Windows only application.

I can tell you that I run Vista and Seven x64 and all my 32bit apps run flawlessly.

What the author of that article did was very similar. Basically it would use physical ram chips to serve as a sort of “ramdrive” that would then hold “pagefile” data. A pagefile is harddrive space that is used like ram, but is naturally slower because harddrives are very slow when compared to ram. A really simple way to do this would be to install a solidstate harddrive and use a pagefile on that drive for your virtual memory. This would create something similar to having more then 4gB of ram while using a 32bit chip and OS, but it’s nothing more then a work around and a poor substitute for doing things right.

The author of that article even admitted that his system became unstable as soon as he installed video drivers, and that this was not a viable method of running a 32bit OS with more then 4gB of ram.

Even if you designed an OS from the ground up with intentions on having it translate alternate memory address space to where applications could access it, it wouldn’t be the best alternative, no, not even close.

You could build an outbuilding on your property containing two bedrooms for your children to live in since your house only has one bedroom, then attempt to have your brain rewired to make you believe you have a 3bedroom house, and assuming we had the technology to do that, you might even be happy with it, but the rest of the world is going to look at it and say WTF? why not just build a 3br home?

The only logical way to move beyond 4gB of ram is to increase our processors beyond 32bit.

Also, I think who ever used the words “licensing” to describe the ram limits wasn’t referring to a piece of paper giving permission, they were referring to the code within the chip that lists (licenses) address space.

Sure you can try to reassign address space, translate the size (similar to what was needed to get harddrive sizes larger then 528mB), and do other hacks and patches, but there is no point being that there is a much better and cost efficient way to solve it. It’s called (AMD x86-64 extension to intel x86 architecture).

All the major Bittorrent clients now include a disc cache for good reason. A simple analogy is that Windows Operating system isn’t smart enough to understand bittorrent protocol and know what data will need to be continuously read/write on the harddrive. When BitComet caches the read/writes, it disables windows caching of the files and holds them in cache as long as the task requires them.

Windows disc cache wasn’t designed with artificial intelligence, it just sees a write in progress and caches it until complete, as with a read, but it doesn’t know that new requests for that data are to be expected.

It would be nice if it did, but having bitcomet use a disc cache stops need for repeated read/writes on the harddrive, freeing it up for other tasks and preventing wear/tear on the device, however if you prefer to use windows disc caching, then you can easily disable the disc cache in bitcomet in advanced options.

TuuS