We are currently undertaking a project to provide remote access to a Ceridian payroll database. Ceridian is running on Arev 3.12, which in turn is running on a Netware 5.0 (SP6a) server. We are using the Revelation NLM version 5.0.

My local Ceridian contact recommends that we use Metaframe to facilitate this remote access, but unfortunately has not provided any documentation on how best to accomplish this. I've seen references to the older Citrix Winframe product on this site, but have yet to stumble upon any Metaframe references. Has anyone out there successfully used Metaframe to provide access to Arev? If so, any links to documentation or pointers would be welcome. Thanks.

Patrick

Nothing hard and fast.

You might want to read the Comprehensive Application Tuning Document provided by Citrix.

Metaframe is actually older since it was the OS/2 based product they originally shipped. Seems to be they resurected the name or product since it's being used for their XP offering.

The Sprezzatura Group

World Leaders in all things RevSoft

You also might want to read the Citrix WinFrame: Software Configuration Requirements document.

The Sprezzatura Group

World Leaders in all things RevSoft

The version of Metaframe we have is 1.8, which apparently is designed to run on Windows NT 4.0 Terminal Server Edition (TSE). However, I just realized I may be getting ahead of myself here.

I have installed NT 4.0 TSE on an HP NetServer LC2000r, and applied SP6 for TSE (equivalent to NT 4.0 SP6a). I have also installed Novell Client32 v4.71 so that I can log in to the Netware 5.0 server where Arev resides. When I try to launch Arev via a shortcut to the mapped drive, I get the Linear Hash IPX Driver - REVMEDIA Open Error: FS477 Revparam file specifies server only access mode. Unable to open boot media map. I did a quick test by renaming the Revparam file so that Arev would bypass it. While this fix got rid of my error, Revelation's documentation is fairly clear about the risk of data corruption that can occur while running Arev without the Revparam file. I renamed the file back to Revparam and am stuck again with my error.

I have checked all of the usual suspects for this error: IPX frame type, protocl order with the Novell client properties, mapping the drive to the directory above the one where Arev resides, etc. to no avail. We have 80 or so Win98 workstations running Client32 v2.2 that access Arev without a problem. This is our first attempt trying to run it from an NT 4.0 box. Is there an undocumented trick to making this work? From what I've read, the 4.71 client running on NT 4.0 Workstation has been proven to work with Arev. I would assume the same would be true for NT 4.0 Server (or TSE).

I believe after getting this issue resolved, the Metaframe part of this project should be relatively uneventful (I hope).

Patrick

At very least you'll need a copy of Steve Smith's CPUPLUS.

At worst, AREVFIX.COM (TSR supplied from Citrix) should be

loaded ahead of AREV.

In Australia this config sustains 20+ users no problems.

The Sprezzatura Group

World Leaders in all things RevSoft

I have been encountering this problem with OI quite a bit, and stumbled upon something which has corrected the problem for me. I had a user that consistently got this error under a Citrix connection, when other users did not. I discovered that by changing the primary connection to either the tree or the server which runs the NLM, the problem disappeared. To do this, right-click on the red N in the tray, choose Netware Connections, then highlight the server and click on Set Primary. HTH

View this thread on the forum...