What's the dang deal!

I am currently using a Win95 computer, with AREV 3.12, NLM 1.12, Novell 3.12. We use two different AREV applications, one accounting and one underwriting. If I use the underwriting application and toggle out to use another Windows application (Word, Excel, etc) for several minutes or an hour, with AREV in the background, and then toggle back to AREV, the whole system locks up.

I do the same while running the accounting application, when I toggle back everythings is fine. I tried to compare the configurations of the two applications and they appear to be the same.

We also have Windows 3.1 machines that do not experience any problems at all on either application.

Any ideas?? I desperately need to resolve this issue as I intend to install Win95 on the remaining computers, but need the bugs worked out first.

I appreciate any and all help.

Brian Gregory

Trident Marine Managers

[email protected]

Ensure that the Always Suspend item is NOT checked. It is in the Background section under the Misc tab when you check the properties of the shortcut.

Also, ensure you have yield time to windows enabled in the 3.12 session.

If you're running code in the background, inside the occasional processing loop, add your own call to yield().

[email protected]

Sprezzatura, Inc.

Okay, I viewed the "Always Suspend" box and both applications were unchecked already. I also made sure the "yield time to windows" said "yes" on both applications, and they did.

When I toggle, I am not really running any code in AREV. Usually the application is just in an input screen or sitting at a menu.

Any other ideas?

Brian Gregory

Brian-

If you try starting the AREV app from a DOS prompt ( also ensuring that the ALWAYS Suspend is NOT checked for that command.com session ) does it lock up as well?

I am basically trying to determine if there is a difference from starting the app this way versus starting the app from a shortcut. If so, maybe there is an old pif lying around somewhere??

Tracy Revelation

Thanks Tracy.

Okay. Here's what I did.

I opened a DOS session from the MS-DOS prompt. I then launched AREV from the command line in the appropriate directory. I toggled back to Excel, played around a little, and the left for lunch with my screen still in Excel.

When I returned from lunch and toggled back to AREV…oh my goodness…it actually worked! No frozen screen, no locked up computer!

Now for the big question. Why? Why does using the DOS prompt work and the shortcut not work?

Brian Gregory

I few months ago I had a user that was locking up for no good reason. No amount of phone supporst resolved the problem, so I went to her workstation and tried a bunch of things. With two shortcuts set up identically, down to every jot and tittle (I guess that doesn't really apply for computers, but you know what I mean), one worked and the other did not. I concluded that the original shortcut had become corrupted internally somehow. I suggest creating a new shortcut from scratch. You may have run into the same problem.

Here we go again.

I stated yesterday that launching AREV from a DOS prompt seemed to work. Well, today it didn't. I launched AREV from DOS, toggled to Excel, and went to lunch. When I returned and toggled back…the computer locked up.

Now I am back to where I started.

Any other suggestions?

Brian Gregory

Victor,

Tried creating a new shortcut to no avail. Anymore ideas?

I downloaded the NLM1.5 but have not installed it yet. Do you think this could possibly help?

Thanks,

Brian Gregory

Are you running the TSR with the /P param? What is the TSR params? What about the params of the NLM? Did you change SYSTEM.INI as specified in the manuals?

[email protected]

Sprezzatura, Inc.

Aaron:

I am using the lhipxtsr.exe /p in my shortcut.

I did determine that my system.ini was not updated on this particular computer. I thought that was my answer because it seemed to work yesterday, after updating system.ini, but is locking up today.

I'm not sure where to check the params for the NLM, but I did load the NLM 1.5 upgrade yesterday. I also installed the most recent AREV 3.12 maintenance release this morning.

The upgrades seemed to go well but didn't resolve my problem. Could it be just this computer, or do you think it is a network problem?

Let me know what you think.

Brian Gregory

Trident Marine Managers, Inc.

[email protected]

These's might have been posted already, but try looking at these articles in the Knowledgebase:

Advanced Revelation under Windows 95

Advanced Revelation FAQ

Windows 95 Shortcut for Advanced Revelation

The entire Network KnowlegeBase

Something in there might be able to help.

Viewing parameters for the NLM would be on the server during the load. If you didn't change them yourself, then they're probably at the defaults. You might want to look the through all the on-line information and see if anything makes a difference.

Things to look for are timeout settings, network frame type settings and protocols.

[email protected]

Sprezzatura, Inc.

Aaron,

 Thanks for the suggestions.  I am going through them now.  But in the mean time I have another question.

 I spoke with our AREV programer regarding this problem and he suggested switching to Windows NT Server and NT Workstation instead of Windows 95.  He said NT was more stable and less 'buggy'.  You you think this approach has merit?  I hate to go that route unless I am sure it will work.

Thanks again,

Brian Gregory

View this thread on the forum...