 |
|
| ViewTouch is a Multi-User
System; such systems are fundamentally different from and superior
to single-user desktops such as Windows or Macintosh. Here's why..
If ten people are working together with stand-alone desktop computers, each one needs a copy of the OS, of each utility and of each program. Anything which goes wrong in any copy of the OS, program, driver or configuration file on any computer will create problems for everyone. Each program must continually share files with the other copies of the program to inform every other program of everything it is doing. It must rely on each of the other nine programs to likewise send files so that they, too, can share everything they are doing. There are ten computers trying to share access to peripherals, too. It's a very busy system, but not because it's being used. It's busy because it is not designed for multiuser computing and it's trying to simulate a true multiuser system. There is nothing inherent in the OS or in Windows which even recognizes that this is all going on, much less supports it! The software on each computer has to make many assumptions about what is going on within each of the other computers and has a lot to do making up for the fact that the OS isn't really aware of what the big picture is! People writing software for such systems really have their work cut out for them. Lots of CRASHES, Lots of LOCKUPS, Lots of ADMINISTRATIVE OVERHEAD, Lots of COST. It would be unacceptable to have ten managers, ten chefs or ten strong-minded owners.. it is also unacceptable to have ten computers and ten copies of all that software. Here's how it should bftware.
Here's how it should be done... Ten people working together in a Multi-User environment need only ONE server, ONE copy of an OS, one mirrored copy of the data, and ONE copy of a program! Best of all, there is no need for file sharing, so the network is much calmer without all the busywork! A multiuser OS has built-in protocol layers which, among other things, provide each of the ten users with their own display and application window. The OS is designed to permit all the users to work together upon their own 'networked' window. Application programming in this scenario is MUCH SIMPLER. With a multiuser OS and networking user interface doing so much to support users working together there is no need for any assumptions in the program about what might be going on in other copies of the program and other nine copies of the OS at every moment. A multiuser OS is fully managing what each user is doing, leaving the people who write the software free to focus on the real issues - the application ! Just Imagine - one copy of the OS and program dancing elegantly for all to use, perfectly controlling every data file and hardware resource for all! |
|
| Astoundingly,
some POS vendors require you to purchase a license to create
a somewhat customized version of your own application! Take a
deep breath and check out this abbreviated, tortuous description of one
vendor's system installation gauntlet:
First, determine and select each device necessary in the Local Area Network to accomplish the defined solution. Then identify each and every device, assign it the correct hardware configuration resources (i.e. an interrupt request level). Next, configure all the appropriate device drivers software, assemble the correct peripherals and connecting cables, load the necessary underlying system resource software (i.e. DOS, Network OS, Windows, database, etc.). Now configure the appropriate software drivers for each system resource and test the operating system integrity of the configuration combinations. Load the application software and third party modules (i.e. Caller ID, Modem Communications, etc.). Now test the interoperability and total combined application compatibility. OK, prepare the boot routines, make your backups and document the system.Do this for EACH computer at the site,! (Ooops, new patch for the OS and, hopefully, new drivers on the way! Go back and ivers on the way! Go back and do it all over AGAIN on every box. Lordy! Don't you feel like it would be easier to pass some kidney stones?
|