[Info-vax] bootcamp ?

[Bill Gunshannon]

In article <klcn70$l3a$2 at dont-email.me>,
	David Froble <davef at tsoft-inc.com> writes:
> Keith Parris wrote:
>> On 4/25/2013 4:13 AM, Jan-Erik Soderholm wrote:
>>> 5. Port to Linux
>>> 6. Port to Windows
>>> 7. Port to an open source OpenVMS compatible OS, if developed
>>>
>>> At least for us, there is another option that I think
>>> is the most likely:
>>>
>>> 8. Scrap the VMS apps all together and use something else.
>> 
>> Perhaps if I had used the word "Move" or "Migrate" instead of "Port" in 
>> options 5 and 6 your option would have been covered in one of the two of 
>> those?
>> 
> 
> You don't "port" VMS applications to weendoze.  You re-write.  Been 
> there, done that.  Didn't look the same afterward either.

That would be the fault of the developer.  I once wrote a Unix Shell that
mimiced the UCSD-Pascal Menu System.  Looked just like it externally and
worked for the user base.  I also wrote an application that moved online
(on a Univac-11) data entry to a micro-computer (LSI-11 based Terak). No
change in appearance or functionality for the users.  Only change was at
the end of the day the supervisor collected the disks and ran a program
(also written by me) that transfered all the data to the Univac-1100.
The result was instead of tying up 10 scarce and valuable serial terminal
lines to the Univac for the entire day it only took about an our of
total terminal time to input the same data.  Trust me, these programs had
to exactly mimic what they replaced because re-training those people
was out of the question!!

bill

-- 
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
billg999 at cs.scranton.edu |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>