PRE_Packaged Posted May 21, 2011 Share Posted May 21, 2011 First things first... Hello to all Bitcomet coders and support staff, thank you all for your hard work.... We shifted from 1.26 to 1.27 and have had a difficult time on all of our computers at all of our locations. I will focus on one-system to try and help you to help us. Workstation hardware Red Fox 880 G+ X2-250e AMD Processor 2-GB DDR-3 640 GB 7200 RPM Samsung HDD BIOS setting changed to ACP-3 BIOS setting changed to LAN-Wake EDIMAX Router DHCP server disabled Workstation software XP-SP3 Pro currently updated MS Windows Firewall We setup the UPnP User Interface. Internet Connection Properties/Advanced Settings are setup for BitComet TCP and UDP services, as well as services for ED2K. JAVA Adobe reader Adobe plugins and Active-X components MS 2007 ACAD 2010 Mozilla Firefox Café Joe - Session manager BitComet 1.27, plus the current E-Mule adder Garrena messenger for DOTA players Yahoo messenger Skype Approximately 500 plus links, game links to our servers, the games are LAN/Online and standalone and are ran from the server disks and workstation cached files. Each workstation is setup with a manual IP This one in this discussion was setup as follows’ IP Address 192.168.1.1 Mask 255.255.255.0 Default gateway 192.168.1.254 DNS1 192.168.1.254 We created a set of registry Codifier keys that are merged to protect the Run from paths and to restrict the ability for any installers to unpack. We have never had a malicious program run on any of our machines since Windows 95, we also use a driver that allows us to enable Disk Protection so when our systems are restarted nothing of the Users activates remain, this driver is controlled by our Session timing manager, a workstation cannot be placed into Disk Commit update mode if a user session has ran. We have never installed virus or malicious software on any of our systems. We have never needed that redundant protection. On this specific workstation we pulled the HDD out and scanned it from a separate system designed for 3rd party trouble shooting, no issues were found, excluding the false positive related to P2P. From our point of view we cannot see any issues with this machine or any of our other machines, when we removed our Disk protection and uninstalled 1.27 and reinstalled 1.26 and commit the changes to our Disk everything works great. As of now we must run 1.26 but hope that you can code out the issue(s) with version 1.27, we have thousands of users many have asked us why we rolled back to 1.26. Please advice when resolved. PRE_Packaged Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.