Hi all,

I posted this in the Works section on Friday afternoon and I haven't received any responses, so I thought I would try it here as well.

I am trying to deploy my first runtime application and I have run into some problems. Initially, I didn't have an Oengine.run; Revelation Software sent me one called Cunning403R.exe. I saved this into my development system and renamed it Oengine.run. I hope that was the right thing to do! I then deleted the previous deployment's folders from my customer's computer and tried the deployment again; this time it deployed successfully. When I tried to launch the deployed app, I received an error stating that Revshe32.dll was missing. I installed the most recent version of the OI Client that I could find (oiwg35cl, which worried me as it looks like it is for OI 3.5) and I copied Revshe.dll to my customer's computer. I tried launching again, this time Revcap32.dll was missing! I found a list of DLLs that are often missing (in a previous posting), copied them all over, launched again and got an error that Imgman32.dll was missing, which I copied it over as well. Now when I try to launch OI, I briefly get an hourglass which disappears and nothing happens…no error, no OI, nothing. Any ideas?

I am using OI 4.0.3 and the customer's system is a Windows 2000 Server with the 2000 Service v2.1 running with named pipes-]TCP/IP, using Windows XP workstations. They are currently running a 10-user Arev 3.12 system which I intend to eventually convert to OI. I have installed a 5-user SDP for the new OI application.

Surely I can't be the only one that has encountered problems such as these during deployment, it seems like some work should be done to make deploying apps a little more seamless…after all, isn't that the final goal for everyone who is writing an application?

Thanks in advance,

Gray Cunningham

Gray,

I didn't respond because in previous threads on the RDK it appears that you are committed to getting a Full System deployment to work. This is a topic with some history where you will find some of us who are successfull with Full System deployments and some of us who have chosen to handle it a different way due to the common problems (like yours) that come up.

FWIW, we keep a clean copy of OI around just for this purpose. When we are ready to deploy an application we use the Upgrade/Module deployment type to extract all of our components. We then load these into our clean OI, copy over the datatables, remove the developer tools, and then put in the runtime engine. There might be a few minor steps that I overlooked but that is essentially all there is.

[email protected]

SRP Computer Solutions, Inc.

Don,

Thanks for your response. The reason that I am so committed (translation: stubborn) to getting a full deployment to work is that I have a fundamental problem with paying (and continuing to pay) for something that doesn't work.

Would your concept of keeping a "clean" copy of OI for initial deployment purposes be essentially the same as my copying my development version to my customer's system, then dropping a runtime engine overtop of my development Oengine.exe? I have considered this approach as I have already applied a 5-user SDP to my customer's runtime engine. I assume this procedure is legal from a licensing standpoint.

Gray

Gray,

Thanks for your response. The reason that I am so committed (translation: stubborn) to getting a full deployment to work is that I have a fundamental problem with paying (and continuing to pay) for something that doesn't work.

No argument here. However, keep in mind there are plenty of things that don't work 100% if you look hard enough. All of us could continue in our committment (ahem…stubborness) for a pure product and overlook the many things that do work just fine (or the workarounds that exist.)

IMHO, the RDK has not be a critical tool to get to 100% because we can work around it. Like you and DSig, I presume the Full System and Application deployments will eventually get cleaned up. Also, like I said before, there are some who seem to use these deployments successfully but only after a rigorous verification that everything is "just right".

Would your concept of keeping a "clean" copy of OI for initial deployment purposes be essentially the same as my copying my development version to my customer's system, then dropping a runtime engine overtop of my development Oengine.exe? I have considered this approach as I have already applied a 5-user SDP to my customer's runtime engine. I assume this procedure is legal from a licensing standpoint.

Yes, it's essentially the same. It's a valid way to deploy as long as you don't leave behind your development engine and tools.

[email protected]

SRP Computer Solutions, Inc.

View this thread on the forum...