I will be upgrading a runtime engine to 32-bit. My current LAN

is using NT Service 1.5 and I understand I need to update this to 2.1, which I am waiting for. If I understand correctly, I should NOT run 32-bit OI with the older NT 1.5 because I will get some corruption. Can I load NT 2.1 on our LAN and continue using OI-16 bit for a while befored I update to OI-32.

In other words.. duh… is OI-16 bit compatible with the new NT 2.1 service??? or do I need to upgrade NT Service 2.1 and OI-32 at the same time.

Thanks…

Steve Carlson

Steve,

It is not necessary to update to the Windows 2000 Service 2.1 in order to run OI32. All versions of the W2K (or NT) Service can be run against OI16 and OI32 data.

Sean

Sean-

I thought there was something about the 64k record size that NT 5.1

wouldn't handle… so if I was using OI-32bit and was saving a ]64k

record on the older NT 5.1 service I could have problems…NO???

TIA

Steve Carlson

I mean NT 1.5 , not 5.1

SC

Steve,

Yes there is a 64K limit when using the Windows 2000 Service ver 1.5. Sorry, for the misleading information. If you are below the 64k limit then the 1.5 will work fine on both OI16 and OI32. If you are going above the 64k limit use the W2K 2.1.

Sean

Sean/Revelation,

What's the best way to downgrade from 2.1 to 1.5. The reason I ask is that we just discovered that AREV cannot be ran if the workstations are Win98SE or lower. We haven't migrated completely off of Win98SE (and we might not do so for a while for support reasons) so this has become an issue that we'll have to deal with.

Thanks,

dbakke@srpcs.com

SRP Computer Solutions, Inc.

Don,

We have our network here configured so that our OpenInsight is running Named Pipes -] TCP/IP and all of our Arev apps run Named Pipes. It is a NT 4.0 SP6a Server running the NT/2000 Service 2.1 We have no problem running our Arev apps on a Windows 95 workstation. What kind of trouble are you experiencing? What driver do you have selected to run in Arev?

If you still need to back down to the NT/2000 Service 1.5 for Arev:

In Arev, to get to the All Networks Driver 1.5, just copy the REVBOOT.OLD over the REVBOOT.

On the Server Side, you will need the 1.5 Server side disk. First, stop the LH Service. Then in the NT/2000 Service directory, type LHSRVC REMOVE. Next delete the NT/2000 Service directory. Lastly, go into the registry:

My Computer -] HKEY_LOCAL_MACHINE -]SOFTWARE -] REVSOFT

Here you should see either/or/both Nt/2000 Service 1.5 and 2.1 folders. Delete them all.

At this point, it is like the Service has never been installed.

Then you can reinstall.

I would also suggest renaming the revparam file in the main Arev directory before you begin.

Hope this Helps,

Kevin

Not unimportant, perhaps…

If you are running OI32 (which accepts ]64k) plus NT Service 1.5 (which apparently doesn't) and a string gets over 64k, what happens?

Crash? Embarrassment for developer/supplier/programmer?

Should OI32 program check string length if NT Service 1.5 in use? If so, how can one detect programmatically if NT Service 1.5 is in use? If so what a nightmare!

Also, what happens with things like indexing? OI32 thinks it can exceed 64k and feeds ]64k to NT Service??

Sounds like (a) a "can of worms" to me - or maybe (b) I'm missing something. If (a) true and (b) untrue then its sound like we shouldn't upgrade to OI32 with NT Service unless latter upgraded to 2.1. If so, where did RTI warn us clearly of this?

Clarification please

Hi Kevin,

We haven't experienced any problems yet. I just read the section in the Upgrade Instructions booklet about using the "pure TCP/IP functionality on Windows NT, 2000, and XP" only for AREV. I had not considered allowing Named Pipes to co-exist.

Thanks,

dbakke@srpcs.com

SRP Computer Solutions, Inc.

Is there any advantage in updating to W2000 service 2.1 in a OI16 & Arev3.12 environment. Speed?

There will be a future upgrade path to OI32 and decommision of Arev3.12

Barry

View this thread on the forum...