CBers

Glad you're all sorted now.

@oj88 Once you release the licence on your old server, the pool will stay online until you reboot, and even then, it may still run for 60 days, as that is how long the evaluation licence is for. When you install DB on the new server, you will again have 60 days evaluation until you have to apply the full licence. So really, you could set up your new server, move the disks and utilise the 60 days, without having to release the licence on your old server, just in case you need to move back. When all is OK on the new server, then release the key, wait for the support people to release it and then apply to the new server.

You can force remove it once you've pulled it from your server.

Nice to see another Emby user here 😀 You would need to have ANVIL installed on each PC in the chain and only permit certain programs access to certain folders. You can run ANVIL without DriveBender, they are separate products, but DriveBender does have a Folderwall built-in now, so you probably don't need Anvil on the PC running DB. Hope this helps a little, otherwise it might be worth raising a Support Ticket. Could you not consolidate the process onto one PC ? Just a thought.

I have asked Anthony to respond to your comments/questions.

I'm sorry you feel that way. It's not a mess, just issues that can't be fully tested in a development environment, especially when new enhancements are being added. Whatever the issues have been, Anthony has worked night and day to fix them. You're on v3.2, so you're not that far behind. I am now running v3.6 on 5 different servers, all running without any issues. Anthony has posted about the "Recent issues with releases". I see you have posted elsewhere about Cloud Xtender, so I won't answer here.

v3.6 has just been released.

https://www.drivebender.com/downloads.html

Not sure how, or why, that would happen. I have upgraded to v3.5, so you could try that. If still read-only, raise a Support Ticket.

I have raised a Support Ticket with Anthony, as I am having issues when playing content with EMBY that needs transcoding with DB v3.4. When transcoding occurs, temporary files are written to a folder in the pool, but playback fails and I get the following message in the EMBY server log: "System.UnauthorizedAccessException: System.UnauthorizedAccessException: Access to the path 'X:\Videos\transcoding-temp\B12932.m3u8' is denied." It appears that with the latest version, although writes appear to occur successfully, reads seem to be a problem. If I delete the 'transcoding-temp' folder from 'X:\Videos' and let EMBY re-create it and then play something, loads of files are created in the folder as expected, but I get the "access denied" message in the EMBY server logs. When the playback ends, EMBY tidies the folder, so it cannot be permissions. I have regressed from v3.4 to v3.1 and transcoding and playback works fine, using the same folder in the pool. I believe a friend of mine has seen a similar occurrence with v3.4 but with a different service. I just thought I'd put this out there in case others see similar issues.

Have you considered upgrading from Windows XP to Windows 10? According to this page, DriveBender supports Windows XP, but you could raise a Support Ticket just to confirm. FYI, v3.4.0.0 has just been released.

I would upgrade, as there are many more features and bug fixes. I would suggest that you raise a Support Ticket first though, just to check that there wouldn't be any issues upgrading from V2.3 to v3.4. I don't think there would be, but better to be forewarned.

Version 3.4.0.0 has been released. No release Notes as yet, but it can be downloaded from here: https://files.division-m.com/DriveBender v3400.exe

UPDATE: I gave Anthony full access to my server to try and resolve the issue, which he has now done after finding what the bug was. Hopefully a newer version of DB will roll out in the next few days/week. Watch this space !!

Calm down merwinsson, there nothing stopping you going back to v3.1 😀 Use this link for v3.1: https://files.division-m.com/DriveBender v3100.exe Make sure you uninstall v3.3, reboot, (**) install v3.1, reboot and go from there. (**) You may need/want to Hard Reset the DriveBender firewall rules before re-installing v3.1: https://support.division-m.com/hc/en-us/articles/360000568955-Hard-resetting-Pool-Firewall-rules If you Hard Reset the rules, you'll have to set them all up again. Never be in a rush to upgrade to the latest release of software, let others (like me and w3wilkes) use it first and report back any issues, as we tend to have develop servers for this reason. The DriveBender developers can only test so much, before a release. Thanks.