Re: Setnet yet again

In article <5vpdki$hd0@cssun.mathcs.emory.edu> marioestrada@guate.net (Mario Estrada) writes: >Peter, > > >I reproduced your problem, when I changed the computer name >in the NetWork option in the Win95 machine just after >installed the product. I have Informix-CLI. > >Try to re-install the Informix Connect or CLI ( Whatever you have, >may be someone rename your computer :-) , In the SETNET >utility don't set INFORMIXSQLHOSTS to any value, that means >that your local machine will be responsible of administering >the sqlhosts files. I've de-installed & reinstalled. Still no joy. This computer once had NewEra 1.1 installed on it and it never deinstalled properly either. It's a Win95 box, not WinNT so there (as far as I know) is no differentiation of users into users & administrators as there is in NT. Just users. I logged in as Informix, same password as on the unix machine. That made no difference either. The computer hasn't been renamed at any time since I installed Win95. At one stage, I killed Intersolv too. It couldn't run its own ODBC admin utility. The MS one in Control Panel configured a data source fine. Then the Intersolv one worked again. Go figure. INFORMIXDIR is set. PATH is set. LOts of general wierdness in this stuff. Testing the Intersolv data connection with Openlink's cppdemo32 works fine. Running the Apptivity forms based builder against an Intersolv/Informix data source, I can connect to & query the tables & columns. When I run the applet, I get an error 'can't find sql.iem' - which is where it's supposed to be. Same with Vis Basic - well, it errors and gives a useless error number anyway. By dint of editing informix.ini I eventually fix this only to have Intersolv say I'm sending an incorrect password. When it didn't ask me for one. And the Deebee log shows the correct password. I went & installed everything on my laptop which had never had any Informix client stuff on it previously. What I ended up with was *2* Informix directories - c:\\informix and cwin32app\\informix. This is real helpful, too. Intuitive. Esp for us unix people who've been warned many times that all Informix tools have to go in the one tree. Anyway, the win32app one has a setnet/ilogin that looks old - 2D and tries to access stores5. And worked. The other one is 3D and doesn't. By looking at the ini settings, I eventually got a sensible error message -956. Since I'm also sysadmin, I could fix this. Put an entry in hosts.equiv (note that I do *not* like this as a solution). Then Ilogin demo works. Does the other stuff - the GUI admin tools?? No. Why? Registry still. Go figure. If I use Openlink's ODBC drivers, the Java stuff works perfectly, every time. So does VB. There's gotta be a moral here. I am *tired* of dealing with this shit. 2 years ago, this might just have been forgivable. Not now. I expect client database drivers to install correctly and work first time. Openlink can do it. Why can't Informix? No wonder MS SQL server is eating up the low end client market. It may not be in the same league, but at least it can be made to work. The joke of it all is - I'd never have bothered with the client side stuff if Informix hadn't removed the unix side tools like onmonitor. Removing that makes as much sense as removing dbaccess. Hmmm....better shut up before we get an all singing client side GUI replacement for it, too. Which also can't be configured in less than a week. Peter Wiley PS: Last minute playing on the laptop - Space Explorer works at least sufficient to see the db server, databases & tables. Command Centre doesn't admit any servers exist. Wunnerful. Registry still, I'd say. Anyone know how to hack the goddam thing MANUALLY?