I decided to give Apache and 'mono' http://www.mono-project.com a shot trying
to get VistAWeb to run on my linux laptop box that runs VistA no joy
yet. I have mono installed and Apache configured correctly, the .NET/ASP
test applications that come with mono run just fine. so I know it
I received an off-line e-mail suggesting that I had not fully responded
to questions about Greek support in GT.M today.
The answer is to use a UI (terminal or terminal emulator) with the 8
bit character set ISO 8859-7 (e.g., see
http://czyborra.com/charsets/iso8859.html#ISO-8859-7 or
http://w
This is hows Fileman sets screens on pointers. Rather than edit the
input transform, you should modify the screen.
Gregory Woodhouse
[EMAIL PROTECTED]
On Apr 23, 2005, at 6:46 PM, Kevin Toppenberg wrote:
I need help understanding an input transform
In file 50.7/PHARMACY ORDERABLE ITEM, in fi
I need help understanding an input transform
In file 50.7/PHARMACY ORDERABLE ITEM, in field MED
ROUTE (.06), I am being limited in the choices
available to me. I want to be able to put in ORAL or
PO for a drug route.
Here is a screen log:
INPUT TO WHAT FILE: PHARMACY ORDERABLE ITEM//
EDIT WHIC
Drs Kevin & Bones (alias Rosanne
Rosanneadanna, alias Emily Litella)
Yes, the line must have been staticky.
WorldVistA will definitely be putting an open source license on OpenVistA.
Which license it will be is under discussion. GPL has both fans and
critics, and in the fine print, it's n
But doesn't that require a license like the LPGL?
Gregory Woodhouse
[EMAIL PROTECTED]
On Apr 23, 2005, at 3:27 PM, Kevin Toppenberg wrote:
The understanding I got was that we wanted to allow companies to be
able to develop modules that work with VistA, and have them be
propriatary. Even on
It is called context Mano. maybe it was lost in translation and nuance.
public domain software is different than open source software which is
different than free software. Open Source is thrown around very loosely
these days.
There are a lot of licenses out there, the license is what mat
The understanding I got was that we wanted to allow companies to be able to develop modules that work with VistA, and have them be propriatary. Even on Linux, one can make a commercial program that makes use of open source technology.
Kevin Doctor Bones <[EMAIL PROTECTED]> wrote:
I realize, th
I realize, that I am doing nothing but muckraking at the moment...
and, I know that I am NOT by any means a core vista person or
personality. BUT...
I am offended that we call openvista, openvista... it isn't covered by
the GPL or another license that ensures development happens in the open.
There are only a few changes, so no need to start all over. Look at 38 and
39, and fix the mode of Taskman and see what happens. If that doesn't work,
comment out the lines in ZU and see if that does it.
On Saturday 23 April 2005 04:33 pm, Butch Jones wrote:
> No,
> I am using a version that
No,
I am using a version that might be a little older.
I guess it would be a good thing to download and start from scratch.
Sorry for the silly question.
Butch
--- Nancy Anthracite <[EMAIL PROTECTED]> wrote:
> Are you using the current set of instructions that is online at
> Hardhats?
> Th
Now here's an interesting paragraph from the link
below:
Although VistA is not open-source software, at least
one vendor, Medsphere Systems Corp., is marketing an
open-source version of it. However, the Aliso Viejo,
Calif., company is selling its product only to
hospitals at this time, said Scott
Nancy,
Could you post that directory with the source that I
compiled from somewhere? I would like to get a copy
of what I did.
Thanks
Kevin
--- Nancy Anthracite <[EMAIL PROTECTED]> wrote:
> That was 1.0.23.15 that was modified, and we are
> circling the wagons on the
> problem that we had wi
;The next line keeps sign-on users from taking the last slot
;It can be commented out if not needed.
JOBCHK I $$AVJ^%ZOSV()<3 W $C(7),!!,"** TROUBLE ** - ** CALL IRM NOW! **"
G HALT
The JOBCHK of the routine commented about in #39 of the Cache install
instructions is/was the same problem. Sti
I believe that he is referring to the "theoretical" idea that it will work
with GTM, but they are not going to put out a GTM version and will not have
tested it. There is no reason, from what I have heard, to think it should be
any more difficult to port to GTM than prior versions of the VistA
I don't think I'm speaking out of turn by saying the following:
1. You'll have to do less "tweaking" of the cache.dat which will be released
as the VistA-Office EHR than has to be done with the cache.dat VA VistA FOIA
release. E.g. Device file entries will likely be defined for clinic offices
to
http://www.ama-assn.org/amednews/2005/04/11/bisa0411.htm
Is his last statement valid?
Will or can we get an early peak at the codebase for VistA-Office? Any
resources for what is going in and what is being taken out?
>The VA is modifying its VistA software for physician offices, and that
>ver
Here is what my ZU routine looks like. Do I need to edit something in
this routine to prevent the error or is it another parameter someplace
else. I see the error code that is being displayed too fast to read:
** TROUBLE ** - ** CALL IRM NOW! **
==
Are you using the current set of instructions that is online at Hardhats?
There have been some changes in steps 38 and 39 and one other place that I
think were made to deal with this. I am thinking that this may be the
problem with the number of users on Cache again, or maybe that you need to
It may be as simple as needing a space between the D and the ^ZU.
It should be D ^ZU, not D^ZU. If you actually did type D ^ZU, then
use FileMan (D P^DI) to check that you have an entry in the Device file
appropriate for the device you are on.
Butch Jones wrote:
I have just gotten back into com
I have just gotten back into community and am again trying to set up a new
installation of CACHE. I have been pretty successful in following the
instructions on setting up a system.
When I sing onto Cache terminal and change the namespace to VISTA, I am
getting an error message that displays ev
That was Aric Stewart from Codeweavers.
On Saturday 23 April 2005 10:02 am, Maury Pepper wrote:
> - Original Message -
> From: "Jim Self" <[EMAIL PROTECTED]>
> To:
> Sent: Saturday, April 23, 2005 2:30 AM
> Subject: Re: [Hardhats-members] VistA Community Call - TODAY
>
> > Could someone
That was 1.0.23.15 that was modified, and we are circling the wagons on the
problem that we had with my server, so before we spend the time fixing
another version, why don't we get this one fixed.
However, I wanted to see the messaging with Ismet's to give us a head start on
the next one and
[warmth without flame]
One of my favourite slogans that I learned the "Underground Railway"
coined and used is "committing portability". What I think Nancy is
passionate about is portability and affordability ...by making VistA
portable and affordable we stand a good chance of making it
ubiquit
> Is this generally the case with CPRS versions following the particular
> Vista server release? Can the same juju be applied to CPRS 1.0.25.28? Or
> does the Codeweavers product give me the "fix" for any version of CPRS?
The version of CPRS has to be the right one for the server...wine
doesn't "f
- Original Message -
From: "Jim Self" <[EMAIL PROTECTED]>
To:
Sent: Saturday, April 23, 2005 2:30 AM
Subject: Re: [Hardhats-members] VistA Community Call - TODAY
> Could someone post highlights or a summary from these calls to this list for
> those of us
> who can't join the calls?
>
Ismet,
Comments below:
--- "Ismet Kursunoglu, MD" <[EMAIL PROTECTED]>
wrote:
> I did a fresh install/config using Bhaskar's
> VistAFOIA20050227 to a
> server/demo laptop and tried to connect over a local
> switch here with
> CPRS 1.0.25.28 (another laptop running
> Debian/Sarge)- it presents t
The binary Ethereal file is at
http://www.alaskaclinic.com/worldvista/cprs/cprsboston-ethereal
as captured from running Ethereal version 0.10.10 on the server side
192.168.1.101, the client being 192.168.1.100
Thanks Nancy.
Ismet, would you please run a Ethereal in the promiscuous mode capturing
OK David, you are on. I will try it fully patched and Norton running full
blast and see what happens.
So were the CodeRed writers really Chinese?
On Saturday 23 April 2005 02:14 am, David Sommers wrote:
> Well Nancy - you were most likely hit with CodeRed.
>
> [anti-flame war hat on]
>
> I li
Ismet, would you please run a Ethereal in the promiscuous mode capturing the
connection traffic between the two machines and send me a copy of the output?
For you or anyone else that wants to send a capture of you connection, just
install Ethereal, start it up right before you connect by choosin
Could someone post highlights or a summary from these calls to this list for
those of us
who can't join the calls?
Rick wrote:
>Dear friends,
>
>On next week's call, we will discuss:
>
>1) plans for the Seattle R&D meeting May 12th-15th,
>
>2) OpenVistA version 4, which will be released at the e
31 matches
Mail list logo