So the failure of PC 104 as a standard is now resulting in a glut of PC 104 and similar x86 devices with "old hardware" flooding the markets. The world says this is junk, but at Vault-Co we call it our all-purpose high end supercomputer terminal with the right software ...
The prototype is percolating .... screenshots and downloadable alpha test version soon ...
Those of you who have wondered since the first Vault-Co site was launched in 1998, when I was working on Vault OS in Visual Basic, just when if ever this software was going to be released ... I am glad I waited and got a lot of false starts. Somehow I knew this day would come. A world where the x86-32bit-PM is a surplus device for around $20.00 a terminal installation ... that's what I'm talking about. Combined with an I2C standard for realtime sensing and control ... that's a basket I will put all my eggs into and my back into developing.
Of course, you still have to come up with the actual display hardware. I have a couple 12 volt LCDs with VGA input laying around at 640x480 resolution, so I am not worried but if you keep your eyes open I think that you will start to see barebones VGA panels at prices under $40.00 brand new or less as secondhand. The keyboard and mouse have a thousand options available, you can buy a serial mouse for $2.96 new from the bargain shop last time I checked. I saw a mini-keyboard a few weeks back for $12.95. There is also stuff like this floating around the surplus channels.
Because of this strange visual trick I am using, where I overlay one GUI layer onto the desktop transparently, I think it may be some time before I support more than 256 colors. This may entail conversions of incoming true color images into their 256 color counterparts. Basically, I am physically using color index layer zero as the transparency mask for my secondary GUI layer. This is really cool, it works and it is fast. If I try to convert it to 16 bit high color I may experience a significant slowdown on lower end machines (like this Pentium 166 SBC) because that is literally copying 4 times as many bytes with masking onto the bottom layer. So although supporting higher resolutions is a snap (up to 1024x768) I may be locked into the use of an 8 bit palette for a long time for the Vault OS. This will entail the need to convert CCD camera images on the fly, which usually is not too hard if you are using a pregenerated lookup table. I've done a lot of this stuff before in game programming with similar restrictions.
I also think I may roll back Watcom from OpenWatcom 1.4 to the original Watcom 11.5 which I was a registered owner of. My original CD disks have gone bad but it is still legacy code. These idiots maintaining OpenWatcom not only managed to crash all existing makefiles and the linker, they also lost compatibility with the STL (Standard Template Language) port for Watcom. That's a pretty big sore thumb there in terms of productivity. If you don't enjoy debugging custom linked lists for every structure in your program, you use the STL to just say things like ... "list i(INVENTORYITEM)
