I am getting an error on module load using both Gallery 3.0.10 and .11 running on a 3.2.0 portal

The exception is logged as:
"DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to ContentPane ---> System.IO.DirectoryNotFoundException: Could not find a part of the path "c:\database\portals\psychohamster.com\Portals\0\Gallery\381\_metadata.resources". at System.IO.__Error.WinIOError(Int32 errorCode, String str) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean useAsync, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) at System.Xml.XmlDocument.Save(String filename) at DotNetNuke.Modules.Gallery.GalleryXML.CreateMetaDataFile(String Directory) at DotNetNuke.Modules.Gallery.GalleryXML..ctor(String Directory) at DotNetNuke.Modules.Gallery.GalleryFolder.Populate() at DotNetNuke.Modules.Gallery.Utils.PopulateAllFolders(GalleryFolder rootFolder) at DotNetNuke.Modules.Gallery.Config..ctor(Int32 ModuleID) at DotNetNuke.Modules.Gallery.Config.GetGalleryConfig(Int32 ModuleID) at DotNetNuke.Modules.Gallery.Container.Initialize() at DotNetNuke.Modules.Gallery.Container.Page_Init(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.UserControl.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---"

The problem is that the path doesn't exist, because the portal is running from a UNC path at \\database\portals\..., not c:\

Is the code making some sort of explicit assumption about the underlying file system? Or is the server returning bad information from a system call? Has any of the dev team used this module on a portal running at a unc location (helpful for dfs or other fault-tolerant configurations)?

Any insight would be much appreciated.

The Gallery module (both the 3.0.xx alpha release from several years ago and the new 4.03.00 version which will soon have its beta release) is designed to work only with files located in the local file system of the host server. At several points in the code, the Server.MapPath method is called to convert the relative path of image files, etc. to a physical file path.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner