Do you run OIWG on Windows 95 OSR 2? (OpenInsight Specific)
At 08 JAN 1998 08:33:54AM Oystein Reigem wrote:
Have any of you experienced problems running OIWG on Windows 95 OSR 2 (also called Windows 95b)?
Or let me ask the opposite question: Are you running OIWG on Windows 95 OSR 2 *without* problems? You see I have a user who runs a development OIWG 3.3 on a PC with Windows 95 OSR 2 and OIWG appears to be *runtime*!
- Oystein -
At 08 JAN 1998 09:42AM Aaron Kaplan wrote:
Use OSR2 on a few machines. No problems at all. Are you sure it's a development EXE? As they say, sometimes a runtime is really a runtime.
At 09 JAN 1998 10:55AM Oystein Reigem wrote:
Aaron,
]
Well, that was *our* first thought too, but our client is sure it's a development version he runs. He *has* got both development and runtime, but he's very much aware that there *are* two versions of OI. And he's an experienced Windows user and network manager, and has installed and maintained our app for a couple of years. I find it hard to believe he's mixed the two.
(1) Can you think of anything that can make a development OI appear to be runtime? What if some critical files for some reason are unaccessible? (We have had a couple of other curious things happening with OI and OIPI on 32-bit Windows versions, and unaccessible files could have explained the problems.)
(2) Did you ever run OI 3.3 on OSR 2?
- Oystein -
At 09 JAN 1998 01:57PM Cameron Revelation wrote:
Oystein,
our client is sure it's a development version he runs. He *has* got both development and runtime, but he's very much aware that there *are* two versions of OI.
1) What is the serial number?
2) What makes him think that it is a runtime not a dev copy?
Cameron Purdy
Revelation Software
At 11 JAN 1998 10:23AM Aaron Kaplan wrote:
I'm pretty sure all this has been mentioned before, so I'm not posting anything really new. The only difference between runtime and executables is 1 byte. A bit flag is set in that byte that determines if certain items are available. This is what's returned from the RUNTIME() function (which I don't think is available in the normal compiler). So, the paint functions check for the paint bit, the compiler checks for the compiler bit, networks check for the networking bit, demos check for the demo bit, database functions check for the database bit and so forth.
I have never, ever seen this function fail. This is in ARev, OI, RevG, ARev for OS/2 all running on DOS, all Win3.1, all Win95s, all WinNT, OS/2, OS/2 for Windows, under Deskview and even in a Unix DOS emulator.
At this point, I think your best course of action is to get in touch with RTI in the UK on Monday, mail them the OENGINE.EXE in question, and they can read the EXE to verify it.
Yes, I've run OI 3.3 on OSR2. By the time 3.3 was shipped, there was probably some code developed on it.
At 13 JAN 1998 10:08AM Oystein Reigem wrote:
Aaron, Cameron,
Thanks for looking into this.
I now have more information. The OpenInsight for Workgroups window that appears at my clients site looks sort of like a runtime with the App Man grayed out, but not quite. Click here to see the window and its File and Tools menu.
I hope this tells you more.
You tell me you have had no problems with OSR2, and yesterday my colleague installed our app on nine PCs with OSR2 without any problems. So it must perhaps be something else. But I (and certainly my client) still appreciate your help on this!
- Oystein -