From: Tripathi, Ashutosh (
Date: Fri Feb 22 2019 - 16:28:37 CST

Shall I just then download

The package PBCtools<> (v1.1 or later) from the VMD script library..?

Earlier I downloaded the pbctools from

Many thanks!


From: Vermaas, Joshua <>
Sent: Friday, February 22, 2019 4:15:14 PM
To:; Tripathi, Ashutosh
Subject: RE: [EXTERNAL] RE: pbctools installation error

Hi Ashutosh,

Yeah, that happens because .so is the default file extension for compiled shared object libraries on unix-derived operating systems (Linux & Mac). Those files have zero meaning on windows systems, which instead uses .dll files for the same purpose. The immeadiate solution to your problem is to go back to the version of pbctools distributed with VMD that only depends on tcl and forget this ever happened. Was there a particular feature you were looking for that wasn't in the standard build?


On 2019-02-22 15:10:36-07:00 Tripathi, Ashutosh wrote:
It mentioned:>

“C:/Softwares/VMD/pbctools couldn’t load library “C:/Softwares/VMD/pbctools/”: this library or a dependent library could not be found in library path 3.0”

I tried looking up for file but couldn't find it anywhere.

Thank you so much


From: "Vermaas, Joshua" <>
Date: Friday, February 22, 2019 at 4:05 PM
To: "" <>, "Tripathi, Ashutosh" <>
Subject: [EXTERNAL] RE: pbctools installation error

A .so file on windows shouldn't be required. What did it specifically say?


On 2019-02-22 14:36:43-07:00 wrote:

I recently installed VMD version 1.9.3 on my Window's workstation (Windows 7). I am now trying to install PBCtools plugin which I downloaded from github. I have made modifications to the vmd.rc file.

set dir C:/Softwares/VMD/pbctools

source $dir/pkgIndex.tcl

package require pbctools

However, VMD cannot load library files. it specifically says