Jump to content

evilmonkey

Members
  • Content Count

    7
  • Joined

  • Last visited

About evilmonkey

  • Rank
    Newbie
  1. I have found that the current version seems to just close? I can open the application click data disk and then leave it for 5-10mins come back and the appliction has closed itself? This happens on any machine I install it on on our network. I have tried runnining it as a local admin and still have the same issue. This also seems to happen when burning. I can set it burning a disc and look across and notice the burning window has dissapeared and that the disk is knackard because it hadn't finnished burning? I've checked event viewer but there are no error messages. Is there somewhere else I should be looking or a way of turning on extra logging so I can provide you with more info?
  2. Excellent that's brilliant! Are we talking weeks or months for that release?
  3. Any luck getting a response?
  4. I've just tested this in the new version but still receiving the error, just wondering if you thought you had resolved this or if it will be resolved in a future release?
  5. Excellent thanks for that!
  6. NoDrives is a windows policy restriction commonly used on networks as apart of restrictions to limit users access to the C:\. Basically by adding HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoDrives and NoViewOnDrives as apart of a GPO it hides the drive specified in the key, from view in explorer and common dialog boxes. Most apps common dialog box's respect these policies but on odd occasions some don't and yours appears to be one. You can replicate this issue by Log in to a user Add the following dwords HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoDrives HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoViewOnDrives Then to hide a drive letter use the following key fingd the number needed to be set in these reg keys to hide the required drive. If you want to block multiples to add the numbers together A= 1 B=2 C=4 D=8 E=16 F=32 G=64 and so on Reboot and open explorer the drives will not appear. Open notepad or IE and they will show these the drive letters you hide. More info can be found at http://support.microsoft.com/?kbid=555438 http://support.microsoft.com/kb/231289 http://www.worldstart.com/tips/tips.php/1638 When done locally it the drives can be access by typing in their drive letter but when done through a GPO as we do 99% of apps return a access denied message.
  7. We run a large network with around 1500 machines and are looking at implementing your product. We have run into an issue though. We redirect our users mydocuments folder to point to the UNC path of their home drive which is something like \\File-Server\Staff Account Area$\Username. When you first open the application and create a CD there is no issue you can happly navigate their mydocuments folder without any issue. The problem happens when you close and then reopen CDBurnerXP and go to create a new data disk. When you open it for the second time it obviously stores the last folder it accessed in user.config, and therefore it attempts to reconnect to this UNC path \\File-Server\Staff Account Area$\Username. When it does it displays the following error FolderView1 \\File-Server\Staff Account Area$ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Now you will notice that the error doesn't show the full path, I think I know what is causing it. Contained in each of our \\File-Server\Staff Account Area$ are around 500 accounts, so for security reasons users have share permissions at this level but cannot list the folder directory, to stop them listing all user accounts intentionally or accidentally. I presume the error is that your software is attempting to folder list \\File-Server\Staff Account Area$\ before it gets to \\File-Server\Staff Account Area\Username and therefore failing as no user has permission to access this area. Could this be adjusted or have an option for us to enfore the default folder that it navigates to so that users don't receive this error. This is easily replicated 1) Create a Folder on a machine called user 2) Create a folder inside called test 3) Share the user folder to allow an account access 4) Change file(NotShare) permission, remove all permissions from this user 5) on the Test folder change the File permissions to allow your user full access to it and its sub folders 6) Copy a couple files in here. From another machine Open CD Burner XP - create DATA disk- Type the full path \\machinename\user\test in to the dropdown box above the top left hand window and press enter This will display the folder listing on the other machine. Close the app Reopen the app and the error will be displayed. If there isn't away to quickly fix the alternative would be away to force the startup directory to a specified drive letter.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.