Hi folks,

I have a pal who who has a small biz who just switched over her Novell network to OS/2 Warp.

Before: Novell ver 3.12, workstations Win95 and OS/2, AREV ver 1.15 for DOS.

After: OS/2 Warp 4 Advance, workstations OS2 Warp 4, AREV ver 1.15 for DOS.

She is now getting all sorts of GFEs (mostly on her indexed files).

I would like to help her, but I know ZERO about OS/2 Warp.

Anybody have any ideas?

My questions:

Will AREV-for-DOS run on an OS/2 Warp network?

If so, do I upgrade to a newer version, pick a different drive, both of these?

Or, will this old AREV-for-DOS never run happily on OS/2 Warp?

Do I need to scare up a copy of AREV-for-OS2 - and will Revtech sell me one?

Any help would be truly appreciated! I've a new baby and this thrice-darned network migration could not have come at a worse time!

Best,

Lisa Grundy

310-665-6318

Lisa_Grundy@spe.sony.com

Lisa,

We run AREV 3.12 on OS/2 machines here with no problem. I believe we are running Warp 3. I do know that the network is Novell IPX, and the AREV network driver is set accordingly.

HTH,

Matt Sorrell

msorrell@movgal.com

What networking protocol is being used? You may have to bind ARev to the LAN Manager Network drivers.

Confirm that record locking is working: Edit the same record on two different workstations, you should get the record in use warning on the second workstation. If not, try a different network driver.

DOS sessions have to be set to be able to run in the background. Idle Sensitivity will probably need to be tweaked (set low ⇐ 3 and monitor CPU usage with Pulse).

Is this the Lisa Grundy?

Anyway, ARev 3.12 was written on OS/2 warp, for what it's worth. By 1.15, the LH structures were already rewritten in C and the opcodes had be finialized long before. Only real changes were some bug fixes and some tweaks here and there.

Can't say I've ever used Warp 4 before, and I'm trying to remember what settings I changed for Warp 3, but last time I used this was mid 1995.

For the most part, I recommend the basics, opportunistic locking and caching. They're the big causes of GFEs. Check for locking and try and increase file handles some. I remember there were a bunch of settings that had to be done in the DOS specific environment for the session. Also, make sure you're using the DOS 3.1 network driver, though back then as long as it's not Novell or Banyan, it shouldn't make a difference.

akaplan@sprezzatura.com

Sprezzatura Group

Thanks Mark, Warren and Aaron -

Just to clarify so that I do not make a muddle of this:

My pal has old version of AREV - 1.15 or 1.16 -

Here are some more questions:

1) Will this old AREV ver run on OS2 Warp 4 Advanced server?

2) Does anybody know if that old AREV ver has the DOS 3.1 network driver Aaron mentioned?

3) If not, can I pop the list of network drivers from a more modern app over to This Old App (apologies to PBS!)?

4) Mention has been made of various settings required for the OS2 workstation - all I know of OS is how to spell it - is there something I can look up or can somebody tell me what the ideal settings are for old AREV under OS2? Or failing that, modern AREV under OS2?

5) How does one prevent network folk from migrating apps without first testing them on the target environment - yeah, I know - if I solve this I will have the (software deveopment/support) world by the tail!

Thanks to respondants; all help is appreciated -

Lisa Grundy

Lisa_Grundy@spe.sony.com

]1) Will this old AREV ver run on OS2 Warp 4 Advanced server?

No reason why it shouldn't. I haven't run across a DOS app that won't run under OS/2, unless it requires some wierd drivers and it can still by run in a virtual dos session.

]2) Does anybody know if that old AREV ver has the DOS 3.1 network ver Aaron mentioned?

Should be included in versions ARev 1.12 and higher, I believe. If the ARev is at 1.15, the upgrade to 1.16 should include it anyway.

]3) If not, can I pop the list of network drivers from a more modern app over to This Old App (apologies to PBS!)?

This ones for Aaron, I don't know the internals enough to say since this requires binding the drivers to REVBOOT which in turn is version specific to the EXE.

]4) Mention has been made of various settings required for the OS2 workstation - all I know of OS is how to spell it - is there something I can look up or can somebody tell me what the ideal settings are for old AREV under OS2? Or failing that, modern AREV under OS2?

When you create the desktop object it gives you the option to fiddle with the settings. At any time after this you can right click the desktop object for ARev and fiddle around with the DOS settings. Main things are to give it as much conventional memory as possible, load as much stuff into HMA as possible, give it expanded memory (4MB), allow to run in background, lower idle sensitivity to 5) How does one prevent network folk from migrating apps without first testing them on the target environment - yeah, I know - if I solve this I will have the (software deveopment/support) world by the tail!

If it is an outside company require them to have several hundred thousand dollars in liability insurance to make up for lost revenue and damages if the conversion doesn't work before signing them on. Also make final payment contingent on the functionality of all (gasp! that phrase…) mission critical applications.

If it is an internal department, there's not much you can do other than the old CYA memos.

Warren was spot on. As for the network drivers, when the change, they change, and usually hook into EXE and RTP57 R/BASIC code changes so they're useless in other versions.

Just to add to his message slightly, I want to stress that an upgrade to 1.16 would be most helpfull.

akaplan@sprezzatura.com

Sprezzatura Group

View this thread on the forum...