joshace

Established Members
  • Content Count

    103
  • Joined

  • Last visited

  • Days Won

    2

joshace last won the day on December 2 2017

joshace had the most liked content!

Community Reputation

3 Neutral

About joshace

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. As I'm sure we all know, there is 32 bit and 64 bit A 64 bit device can run 32 bit software (except for some very strange situations in which bad programmers check to see if the cpu is 32 bit or 16 bit. and if it's not 32 bit the program won't work.. they failed to consider that people would be using a 64 bit computer). 32 bit and 64 bit programs run at pretty much the same speed, because programmers are not smart enough to use the 64 bit commands properly. However, 32 bit programs can only address a maximum of 4GB (actually less, because things like the video and other functions steal some of that memory) 64 bit programs can address more memory than anybody could dream of ever having. I get hit with errors such as seen below almost every day with uTorrent. If uTorrent were compiled with a 64 bit compiler, I think that problem would go away. I don't know that they even manufacture 32 bit cpus anymore.. so why is anybody compiling their software to be 32 bit? I recall that many many years ago, there was one version of uTorrent that was 64 bit, but it was discontinued. I have no idea why. Probably the same reason a lot of boneheads still use uTorrent version 2.21 The Amish might not have electricity, but even they use uTorrent 3.5.x
  2. What doesn't make sense about that is.. I never even come close to running out of memory. It SAYS I have run out of memory, but it has not. I think I have sort of a solution for this... 32 bit can only address 4GB of RAM If uTorrent were compiled to be a 64 bit program, I think the memory issues would vanish.
  3. My laptop has an incredible amount of memory.. 128GB I should never run out of memory under ANY circumstances, however, about once a day, uTorrent 3.5.5 45311 crashes on me with errors such as "run out of memory" or "unable to allocate memory" I have tried to downgrade to previous versions.. but it won't let me.
  4. My new computer has 128GB of RAM.. no I'm not kidding. I just had uTorrent crash with a message that the computer ran out of memory! How is that possible?
  5. These are my current cache settings. The three that are highlighted in yellow used to be the opposite. Are my current settings the best choices?
  6. joshace

    3.5.x Beta

    a long time ago.. utorrent came bundled with a load of embedded games. I didn't mind that, but most other people hated it. The only other torrent client that I would suggest people use is Bittorrent, which is made by the same company and 100% clone of Utorrent, but is coded differently. I use bittorrent to download / leech files, then autosave the torrent files to a directory which utorrent automatically loads the completed torrents.. and utorrent uploads / seeds the files.
  7. joshace

    3.5.x Beta

    My guess is that an html video player was removed? I'm just guessing.
  8. joshace

    3.5.x Beta

    3.6.6.4481? Where did you get that? It must be an alpha? I'm now running beta 3.5.4.44809 My updates.dat file is only 1,861 in size. What is that file for? Would there be any reason not to delete it? From what I can see.. it's just a log of installs with no function at all.
  9. My Utorrent pane suddently went from 2 panes to one.. and I did every trick in the book to fix it, including deleting the settings.dat file and regenerating the default.  That didn't fix it. 

    What DID fix it was downloading Rafi's settings. dat file.   That fixed the problem and also improved other things quite a bit.  I am now tweaking Rafis settings to suit my own needs. 

    What puzzles me is.. I have no idea what settings are in Rafi's settings.dat file that make it work right.  I don't see anything about pane controls.  I have seen dozens of people posting about the same problem for years.  

    I would like to know how to fix that problem instead of having to replace my settings with a transfusion of Rafi's settings. 

    1. rafi

      rafi

      Glad to hear it helped you. Screenshot (including menu->options)? Usually F4->F7 control the panes. Two monitors setup can sometimes be an issue...

    2. joshace

      joshace

      Thanks for the tips, but it wasn't any of that.  

      One of these days I will compare the defective settings.dat file with the one you posted.  You made some other improvements in the appearance that I can't find in the settings.  I backed up the defective one.  I think my cat screwed up the settings when he was stomping on my keyboard.  

      One setting you have set, which I did not like is that torrents don't start downloading automatically.  

    3. rafi

      rafi

      >One setting you have set, which I did not like is that torrents don't start downloading automatically.  

      I like that  since I start them automatically using RSS downloader or using Medusa TV app . But I think you might be right, it is better to set to auto-run for other users. I'll make a note to change it on that file... 

       

  10. joshace

    3.5.x Beta

    The problem with the ads in the free-ad version is fixed again in 3.5 build 43534.. which is curious.. because it's the same build. The program didn't change, but the ads stopped popping up. I love utorrent.. and the charge to get the ad-free version is well worth it (when it works)... however, that ad engine makes the "free" version essentially "crippleware". There is no reason why those ads should take up 57% of my cpu and 700 megs of memory. It should be less than 1% of cpu.. and at most 1 meg of memory.
  11. joshace

    3.5.x Beta

    I'm running Utorrent Ad-Free 3.5 build 43534 32-bit.. and the ads have returned again.. Webhelper (utorrentie.exe) is the ad generator, and I've seen it take up to 57% of the CPU and 800 megs of memory. That is outrageous. See attached snip.