KernSafe Technology

I'm trying out Kernsafe iStorage Server, as it could be a great program for hosting a lot of CD images. I'm running iSS on a Windows XP SP3 guest, in VirtualBox, on Windows XP SP3. When I create a target from drive Z:, which is a mapped network drive, it can not read the ISO file, because it claims the file does not exist. the Windows XP SP3 guest has full access to the mapped network drive, and can access ISO files with other programs. This occurs with both long file names and short file names, also a small ISO in the root of Z: gives the same error. This also occurs when browsing to the ISO file not through Z:, but through \\Servername\Files\isofile.iso

When I copy the small ISO to the local drive of the Windows XP SP3 guest it does recognise the image, and continues with target creation. I suspect this to be an error with iSS.

There are no programs that could interfere with iSS, as I don't use Windows firewall, and no Anti-Virus program is installed on either the guest or the host.

iStorage Server does not support windows shared folder and network drive at this time.
What type of your server mahine is, why not install iStorage Server on to this server machine?

The problem was caused by iStorage Server's core application is running under another user account (local service), so it can't use user related resources.
However, it is also feasible, you can open windows service manager and change the logon user of iStorageServer service to the user who created the network drive.

Charles (Dev) wrote:iStorage Server does not support windows shared folder and network drive at this time.
What type of your server mahine is, why not install iStorage Server on to this server machine?

I want to split the CD/DVD image hosting from the actual fileserver, so I'm now testing with Windows XP SP3. The actual fileserver doesn't run Windows, that's why iSS can't be installed onto the fileserver. It also doesn't have a GUI, and for CD/DVD images it would be nice to use a GUI.

I will install iSS again, and change the user account to a user who does have the network drive. Thanks.