I have literally spent all week on one issue after another with deploying an OI application. My client is getting VERY VERY VERY impatient. His application runs great on my system but I can not deploy it.

I feel there must be a "secret" about using the RDK that no one let me in on. I am now able to get to the point where the RDK announces 'Extraction completed.' Great. WRONG! I logout of my development copy and attempt to log in to the runtime version using the OInsight.exe there. I am told that I am attempting to log in too many users. No other OI system is running and it is my only attempt to log in. I am using ONLY the RDK program built in to the development copy of OI 7. Do I need anything else or need to do anything else? I know there is a RDK related installer on the WORKS CD but I assume that is not my problem. I have tried creating the runtime from SYSPROG and from the application. At one time I think a DLL exchange was required from Revelation Software. Do I need a separate runtime license? I must need something that I do not have or do not have installed. Do I need to do anything special to run a runtime? I am simply double-clicking on its OInsight.exe and failing. PLEASE HELP!

Also, if I double click on NETDRV.EXE, I am given an error that rcl4.dll was not found.

Did you ever get the OENGINE.run file from Revelation?

BTW, from what I've read it appears that you have been trying to do a Full System deployment. Many here on the board don't recommend using that option of the RDK. It is often easier to just make a copy of your system, remove the source code, remove the development engine, and put in the singler-user runtime engine (after you get it from Revelation.)

dbakke@srpcs.com

SRP Computer Solutions, Inc.

Thanks for your reply.

No, I never received the OENGINE.run file from Revelation. This is the first I hear of it. That sounds like it may be the missing link. Is that requirement documented somewhere?

In the meanwhile, I copied over the missing dll to the runtime directory and the NETDRV.EXE window will now open and shows the wrong network driver and 0 maximum users. I developed with the Universal Driver 3.0 after discussing the differences with tech support but NETDRV shows only 2 older drivers available now. I am hoping the OENGINE.RUN will do the total trick.

THANKS AGAIN.

Oengine.run actually does exist in my 7.0 folder without asking Revelation Software for it. Am I correct in attempting to run OInsight.exe in the folder created by the RDK? Must I maually copy over Oengine.run and change the extension?

First thing I would do is rename it to OENGINE.dll (back up your other one first) and then run OENGINE.exe to see if it runs. Check the version and serial number to make sure all is correct.

If so then you ought to be able to keep this as OENGINE.run in your development folder so it will get extracted correctly during a Full Install RDK. If you simply want to get the runtime engine in place then just copy it over to your deployment folder and test run the application.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

It seems like the generic OENGINE.RUN supplied with 7.0 is useless. I sent Revelation Software my OENGINE.DLL and hopefully the return file will work. The 7.0 OENGINE.RUN sets my maximum users to 0 when I rename it OENGINE.DLL

There is an easier way to deploy your OI application.

Make a copy of the entire application folder, clear out your source code, then delete all the dev executables, such as System Editor, Form Designer etc.

Rename Oengine.run to Oengine.exe

Away you go.

It will be bigger than an RDK deployed app, but at least its all there and will work.

Colin

That is standard post OI WG3.x. The doc says that you MUST contact Rev Soft for the initial single user runtime Oengine.dll.

Having said that I do encourage you to follow the advice of Donald and Colin and prepare a clean 'Master' runtime system. Temporarily use a development engine (Oengine.dll) to open up and create / establish your application start point. Depending on the method you select that may be suffice for your your master runtime system so replace the development dll with the runtime dll supplied by RevSoft and proceed with the RDKInstall process.

A comment about the driver. When you execute Netdrv.exe you are presented with and choose from network drivers as are located in the Revboot directory (ie LH3, LHNPP, LHNLM32 etc).

Richard Bright

BrightIdeas New Zealand

That's what we do.

We also wrote custom code to handle upgrades.

However I all so delete all the following, is this required?

del FORMDES.EXE

del TESTRUN.DLL

del TOOLBAR.DLL

del ACCESS.EXE

del BRFHELP.*

del README.WRI

del TMU.EXE

del DWB.EXE

del BRFHELP.HLP

del NTHELP.HLP

del OINSIGHT.HLP

del OIPI.HLP

del RDKHELP.HLP

del RDKWEB.HLP

DEL *.ISU

View this thread on the Works forum...