I-Net for Windows???

I'm a newbie to TCP/IP client/server apps, most of our stuff runs using terminal emulators on the host. I've been looking through some old(ish) training notes and they only mention I-NET PC. Is it true that this only allows one connection to the UNIX box? Surely this limit will impose problems when users run applications under windows?? We use Microsoft TCP/IP (Wolverine) to connect to our UNIX machine, there is *no* network junk mentioned in the CONFIG.SYS!. Is there a winsock compliant I-NET that would allow us to open multiple connections to the UNIX machine? The reason we *don't* want CONFIG.SYS lines is that we will be also moving towards Win'95 and NT in the future. The TCP/IP stack that comes with '95 is very good, so we will probably be relying on that (it's winsock compliant)... By the way, we are going to use the ODBC driver from Q+E (Intersolv) - is this any good? - are there any problems we should be aware of? The only other alternatives I've heard of are SQL-Retreiver (VisionWare) and Sequelink (Techgnosis), are there better alternatives I should be aware of.. What setups do most people use to connect their windows apps to INFORMIX? On the UNIX end do we have to buy I-NET for SE *AND* I-NET STAR for OnLine? We only use SE at the moment, but there's a good chance that OnLine will be used in the future... Hope someone can advise, I ready to start ordering the stuff.... :) // Chris -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= TASK (Software) Ltd. Unit 4 Antrim Technology Park Belfast Road Co. Antrim BT41 1QS TEL : (01849) 465981 FAX : (01849) 465982