Re: Openserver 5.07 and a medical practice



On Thu, 6 Mar 2008, Nico Kadel-Garcia wrote:
On 6 Mar, 19:27, darko <darko.krs...@xxxxxxxxx> wrote:
On Mar 6, 1:04 am, "Martin Rubenstein" <ma...@xxxxxxxxx> wrote:
I have a medical practice with all of our billing, appointments,
etc. running on a proprietary software called Script Systems by
Mysis.  The server is a 4 year old IBM eServer with OS 5.07 as OS..
 I am concerned about the need to replace the server before a
hardware failure creates a crisis, as I figure most hardware is good
for about 5 years and we are near that.  Mysis would prefer
(naturally) that I migrate to a different software they offer that
is GUI instead of character based, although they still support our
product.  The OS on our server is OS 5.07.  How realistic is it that
I stick to our prior method of buying an Intel based server and load
OS 5.07 and our data myself, and have Mysis still do software
support for their product (but not hardware or OS) given Sco's
financial problems.  Our vender's solution is considerably more
expensive, but has the advantaage that they will support the new
hardware and software.  All thoughts appreciated.

The information is given. The OP knows that the SW is only supported on
the SCO OS. He is asking for assistance with a specific problem.

At least one major server vendor, HP, still sells new servers that can
run SCO OpenServer 5.0.7, and are certified for that OS. I am not sure
about other vendors, since all Intel/AMD based servers I've dealt with
recently were HP. For example, task of installing 5.0.7 on ProLiant
DL380 G5 is doable, from my recent personal experience. I had to use
external USB optical drive and floppy (broader described in another
thread in this news group).

The other option is to use virtualization like VMWare Server or
Workstation on some Linux or Windows. That is also doable. You should
just check if it is supported by your vendor(s). I am not sure if
OpenServer is supported on VMWare officially.

OpenServer is not supported by VMWare. So taking it to a virtualized
state causes the SW to become unsupported by the vendor.

Just because a server is "compatible" doesn't mean you can get it to
work. I've been doing hardware evaluations and integrations with various
OS's since BSD 4.1, and I've got to say that SCO configuration harkens
back to the bad old '80's of having to know the answer to everything in
advance. including details of SCSI configuration and driver
installations that any modern OS either auto-detects or has decent probe
tools to detect. The result is that adding peripherals, such as tape
drives, external USB drives, graphics tablets, or slightly unusual
monitors is awkward if not impossible. And it's only going to get worse.

That is why there is OpenServer 6. It does not have the old knowledge is
required to get the devices working. Sadly the market has to provide for
clueless Admins, that do no understand UNIX.

Virtualizing lets you sidestep these problems and leave them with a
current operating system capable of handling contemporary hardware, and
allows trivial transfer of your entire virtualized operating system to
an arbitrary virtualization server. It also installs in a fraction of
the time, because the underlying OS and hardware do the bad block
management for you and that *AMAZINGLY* slow OpenServer disk
configuration tools stays the heck out of your way.

Yes, but it is a non supported configuration by the vendor. And yes I use
virtualization. But to report problems to the vendor you have to follow
their rules. Some out right reject any thing done virtually. Sadly we
have to follow vendor rules to get bugs fixed. What you need to realize
is that there are various target audiences. We have to address them.

The SoftWare Applications chooses the OS. We have to look at what is best
for the OP/business. Not pick a ...


--
Boyd Gerber <gerberb@xxxxxxxxx>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
.



Relevant Pages

  • Re: openSUSE as small bussiness server
    ... hardware support for current systems. ... decade and they have hardware support. ... The other 8.2 server is old-ish Dell ca 2001. ... Most of my customers are small to medium size. ...
    (alt.os.linux.suse)
  • Re: [PATCH] xen: core dom0 support
    ... Despite all the noise made about kvm in kernel circles, ... let's add Xen support to the kernel!" ... Xen manages to use new hardware ... Xen's memory virtualization is pretty neat, ...
    (Linux-Kernel)
  • Re: ? Debian on dual-socket Xeon server hardware
    ... When buying "experienced" hardware I always tell people to ... But I assume you are asking about hardware support. ... requirements are minimal since you won't be running an X server. ... I avoid using an onboard raid controller unless you have a spare one. ...
    (Debian-User)
  • Re: Why upgrade to SBS2008
    ... Just to comment on a minor part of your post - IMO the winding down of SBS 2003 support is a valid consideration in your scenario. ... You're getting ready to put a major time investment into moving to new hardware, and in my opinion, you'll get more mileage out of the installation if you use the currently shipping version. ... I'm not rushing to upgrade my perfectly functioning SBS 2003 before my normal hardware refresh cycle, but if I were replacing hardware anyway, it would never occur to me to stand up the new server with an old platform version. ...
    (microsoft.public.windows.server.sbs)
  • Re: Using Hyper-V with Windows Small Business Server 2008
    ... I can not stress how much I love the MVP support around these parts. ... This idea that SBS is not good for being a virtualization host is one of the ... MS have released 'Windows Hyper-V Server' as a free download. ...
    (microsoft.public.windows.server.sbs)