Jump to content
Division-M Community

merwinsson

Members
  • Content Count

    7
  • Joined

  • Last visited

  • Days Won

    1

merwinsson last won the day on January 11

merwinsson had the most liked content!

About merwinsson

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I upgraded a PC that had a DriveBender pool to the new Windows version 2004 and accessing the pool is like 100x slower. For instance, if I try to load BattleNet it takes 3-5 minutes to come up and then the app is very unresponsive for another minute or so, after which time I can finally enter my login credentials, and then the app goes into Not-Responding state for awhile. Opening Explorer and actually trying to access a file also goes into the unresponsive state. I had DB 3.6 so I went ahead and installed 3.7, but that did not make any difference.
  2. After doing some research for the support ticket, I am posting my observations here so others can see. This is what I found out. In 3.4.0.0 my pool still doesn't work correctly, BUT I can now turn off the FolderWall (as opposed to 3.3.0.0 which wouldn't let me), and doing so solves my problem. Also in 3.4.0.0 I can't seem to see any logging. Don't know why, but the log appears empty at all times. I've asked support to get my FolderWall working, and will report how that goes.
  3. Still busted. I'm not seeing that FolderWall error anymore, but things on the DB drive still don't work. Ran 3.1 installer to go back. Creating a support ticket.
  4. Watching. Looking forward to an update because I would like to start using the FolderWall to protect against malware, especially encrypting malware.
  5. For me it's different. All of the software I have installed there (Steam games, Origin games, Blizzard games) give various errors when loading. Only after reverting back to 3.1 did things return to normal. FYI I have 4 500GB SSDs in my pool.
  6. I am also experiencing this same issue. You guys have got to get your act together. I upgraded from 3.1 to 3.3 and my pool is unusable because of this "cannot read rules" error. Nothing I do (uninstall, etc) fixes the problem and disabling the FolderWall for me just results in the UI saying it's disabled, but next time I view the setting it's ON again. This is disgraceful. I basically upgraded and destroyed access to my pool. Yes, I know no files are damaged, but I can't effectively run any software installed on that pool. Great job guys. I'm hoping I can just find a version 3.
  7. For me, I have a 10 drive enclosure with 2 port multipliers that connect to 2 eSATA ports (each on a separate controller) on my file server. To ensure optimal performance, a file and its duplicate should be on drives that connect to a different port multiplier / controller. Without a way to mark a drive as "can contain primary files only" or "can contain duplicate files only" or (not for me) "can contain either primary or duplicate files", there is no way to ensure this. I was looking at StableBit DrivePool to do this and it can't really do this either; in fact DrivePool doesn't eve
×
×
  • Create New...