I have no idea why the turkish hackers had to crash my Vault-OS site after I had worked on it for three weeks getting ready to debut. They didn't just ruin my site, they crashed my entire server host. They have actually been sold to get rid of the support headaches.
I have moved everything but this Vault-Co blog to a new server.
I have almost finished rebuilding the site and will launch it again this weekend. It will have a wiki, a gallery and a forum for Vault-OS. The software itself is looking and running pretty good. The closest thing to a release candidate that I have is the Win32 version - it is working really good on Windows NT Workstation, Win 98SE and Windows XP. I know I said the DOS 16 bit version was going to come out first but I have run into a lot of problems with it, particularly communicating with the data server seamlessly via IPX. I know I will get the simpler version integrated but the likeliest thing to have in your hand this year is going to be a Win32 application.
I have broken up my Win32 build from being a monolithic desktop into a series of modules, of which the most important is the VOSCODER. This is essentially the control, alert and monitoring program which is visually represented by a marquee. I have the inventory standing alone, the personnel module standing alone, the calendar and scheduling apps standing alone. They all use the same data server which runs in the background and they use IPC to communicate locally or over TCP-IP to each other.
The sooner I get this version out and running on site in my shelter, the sooner I can wrap up my first book on Vault-OS and Vault-Co best practices for shelter management. Instead of hawking it here (this blog is reserved always for non-commercial interests) I will probably be selling it off the new site, which means I will stop blathering about it on the blog once and for all. That should make some visitors pretty happy if they were sick of hearing about it.
P.S. My test version of the Win32 VOSCODER has run up to 19 days 24/7 continuously without any interruptions, crashes or even unexpected behaviour. The only reason it finally got turned off was that I accidentally unplugged it when working on another setup. Windows NT is a very, very stable platform and 15 years ago it was regarded as superbly suited for embedded, industrial applications that had to run around the clock with zero maintenance.