I have this problem with our app where one machine cannot run it at all. When the app starts, our entry window does not get executed. On this machine it cannot run either a local copy or the one on the network. On another machine, it can run it's local copy but not the network one. Other machines in the office run the app fine, even mapping the offending machines drive and running their local copy. What seems strange is the startup engine calls. Here are the last ones:

RUN START_WINDOW RUN REPOSITORY 'EXECUTE','NIS*OIWINEX…. RUN GET_SYSINFO RUN SETAPPID 'NIS' RUN SWAP_DATABASE 'NIS' RUN BCHECKLEGALUSER 'NIS','NIS','ASF',… RUN GET_APP_INFO 'NIS' Any sugestions? Thanks, Bryan </QUOTE> —- === At 18 DEC 1997 03:24AM Aaron Kaplan wrote: === <QUOTE>There was a problem with START_WINDOW doing strange things in older versions. I think this had to do with some system DLLs. You might want to compare them with others. Cam'll probably post a proper solution though…. apk@sprezzatura.com Sprezzatura Ltd </QUOTE> —- === At 18 DEC 1997 08:27AM Cameron Revelation wrote: === <QUOTE>Bryan, I have this problem with our app where one machine cannot run it at all. When the app starts, our entry window does not get executed …. Other machines in the office run the app fine … What seems strange is the startup engine calls. Here are the last ones: RUN START_WINDOW …[/i] When you see one or more <code> Start_Window '' </code> in the System Monitor, it means that IsEventContext is failing. This is a very serious problem which is apparently caused by changes in Microsoft's latest Windows system files, perhaps related to software updates like IE40 or Win98. The good news is that we resolved the problem in the 3.5 release (which Works customers should have received by now). The bad news is that there is no way to provide a patch to previous versions because it required changes to the engine. My suggestion is this: If you have received 3.5, make a temporary test copy of the customer system and upgrade it to 3.5 to see if this resolves the problem. If it does work, you will need to upgrade the application to 3.5. I hope this helps, Cameron Purdy info@revelation.com </QUOTE> —- === At 18 DEC 1997 09:44AM Bryan Feddish wrote: === <QUOTE>Thanks for the reply. As for the PC that would not load any copy I'm currently re-installing windows 98 as it was having other problems too and we need this machine for demos. The other PC can load local copies that are not 3.5 but cannot load the network version that is 3.5. Are there some DLL's in the Windows/System directory that I should be looking for? I'm also worried that maybe a DLL from my NT 5.0 machine may have slipped into the Oinsight directory on the network but it is working on the rest of the 95, 98, 4.0 and 5.0 machines. Thanks! Bryan </QUOTE> View this thread on the forum...