Downloaded 4 more times, from four different mirrors, same result, same
md5sum:
linux:~ # md5sum /Distrib/VistA/FOIAVistASemiVivA20060113.tgz
714b75b4b3f560c43ab5aeb2ca3e444d
/Distrib/VistA/FOIAVistASemiVivA20060113.tgz
linux:~ # md5sum /Distrib/VistA/FOIAVistASemiVivA20060113.tgz
While creating the forthcoming FOIAVistA VivitA 20060113 (based on the
latest FOIA), I noticed that there are two globals ^rINDEX and
^rINDEXCLASS that appear to violate the standards.
My understanding is that all variables (as well as labels and routines)
must be upper case letters only, and a
I uploaded in a two step process, first to my shell account at Source
Forge and then from there to the File release system. The checksum is
fine on my shell account, so it must have been damaged while uploading
from my shell account at Source Forge to the file release system at
Source Forge!
I
As I understand it, those will be Cache specific and can be removed.
I'll am sure Cameron will weigh in here later and let us know.
On Sunday 29 January 2006 10:32, Bhaskar, KS wrote:
While creating the forthcoming FOIAVistA VivitA 20060113 (based on the
latest FOIA), I noticed that there are
I would like to point out, as Bhaskar has pointed out in the past, but not in
the emails about this release to my knowledge, that the CPRSChart that
Bhaskar has included is not fully functional on the Linux platform and the
functionality that is there is probably OK, but has not been tested to
Based on the January 13, 2006 release of FOIA VistA, FOIAVistA VivitA
20060113 has been released and is available at the WorldVistA project at
Source Forge (http://sourceforge.net/projects/worldvista). This is the
smallest VistA live CD download to date, and is built on Damn Small
Linux 2.1b (DSL
On Sun, 2006-01-29 at 09:37 -0600, Bhaskar, KS wrote:
I uploaded in a two step process, first to my shell account at Source
Forge and then from there to the File release system. The checksum
is
fine on my shell account, so it must have been damaged while
uploading
from my shell account
Any client application (even those running with a green-screen interface)
can have errors and leave the globals in an incomplete state in VistA. The
more robust applications in VistA take such things into account and buffer
information and check it before it's filed, have post-filing coded that
