<HR>
anabus_maximus
a) I try to implement the K.I.S.S principle wherever possible. So in a nutshell - at this point I have no plans to implement a content filtering system, it's not the objective of Odyssey.
b) It's not watered down IE - it is IE, using a standard control, any VB application can display a web browser window and customise it to their heart's content. No, it won't include favourites, as you can see the menu/status/tool bars are all disabled and invisible.
Any favourites you do want - will need to be on your start page - which you design in good ol html.
<HR>
peachey
1) you will learn that these days, pretty much anything is networkable one way or another. Odyssey will function network-wise in the same fashion as DHPOS. You are responsible for having the databases on any hard drive on the network, as long as all the client machines can access the folder that contains them. You must then tell each client what the path is. And before anyone does ask, yes you could have the databases on one of the client machines and map to that folder, however the machine may run slower depending on your network configuration. I told ya it was networkable in the same fashion as DHPOS.
2) That's what I expect the users to tell me, I really won't know the system specs until I finish, but as with DHPOS - the hard drive space etc required will depend on the size of your databases once they start filling with data. As for windows versions - I would say Win95 (preferably 98 ) upwards should be usable, as it is a VB app - the VB runtime files will need to be installed as well.
