I was given an Arev DB into which I need to gain access (Arev is version 2.9n) I have all the passwords. The problem is that I am working on a stand-alone machine. I took the AREV directory that was given to me on a CD and put it on my hard drive. I use the command

c:\arev\arev ap to run the application.

At first I was getting an error that only the server could access the DB so I deleted the Server Only=True in file Revparam. Now I got an error which said that NetWare is not responding and that I should only open local tables. Opening just the local tables would suit me just fine since I have all the tables locally. The question is, how do I only open the local tables?

I ran "arev lanpack" which let me change the network type (I selected it to be non networking). Now I no longer get the looking for NetWare popup. Instead, I get to the blue main program screen, and a popup appears that tells me "Your computer does not have the NLM TSR, please contact support."

I don't know what the NLM TSR is, but from what I've been able to gather from the revelation knowledge base, I need it to communicate with the NetWare server. I checked and I have the TSR files, but not the NLM (I used the user lanpack and saw that the SYSOBJ field in SYSTABLES table contains a code without any F's in it).

Can I get around the NLM somehow or do I need to install it on my computer?

It sounds like the TSR watchdog was added to login/startup process for the application.

If you can get into SYSPROG, from the menu pick Options -] Application or User (depends on the login name you're using) - enter the name -] F10 -] Advanced -] note what the startup command and shell settings are - Clear startup (control X). F9 changes.

Log into the user/application you just modified and edit VOC name_of_startup_command. This will either be a TCL item or a catalog program pointer which will tell you which file and the name of the program that is being called. Edit this item and comment out the tsr watchdog stuff.

Go back into SYSPROG and add the startup command back into the user/application.

If SYSPROG is doing the the tsr check also, you can type "RUNMENU STARTUP" from TCL in LANPACK to get to the SYSPROG menu.

There is probably a backdoor account/user which will bypass the tsr watchdog check in the startup command. Try looking at the items in the SYSENV file with F1 or TYPE EQ "USER""ACCOUNT""APPLICATION". You should be able to do this from LANPACK.

Note: Do not edited these items in the SYSENV fiile because they have a checksum in them and you can corrupt them so they are no longer usable.

I couldnt log into Sysprog, so I used "RUNMENU STARTUP" from Lanpack like you advised.

I selected Application AP, went to Advanced, the settings were as follows:

Startup Command - LOGON

Environment - AP

Restriction Level -

Shell

Code - X Command - LOGON

I cleared Startup Command and logged out of the application. Now when I try to log into AP by running "Arev ap" i still get the screen that informs me that my computer doesnt have NLM TSR and I am unable to log in and edit anything.

Sincerely,

Andrei

The original application developer has chosen to prevent access to the application if the NLM is not loaded. Normally an easy way around this if it has not been proscribed by the original author is simply to press F5 when the NLM TSR message displays.

Are you able to do this and get a command window?

Is your ultimate intent to export this data?

The Sprezzatura Group

World Leaders in all things RevSoft

If the Sprezzie trick doesn't work, remove the X LOGON from the shell code and command parameters in the user/application collector.

Then edit LOGON from the VOC file. This will either be a TCL record (F1=TCL) or a catalog program pointer (F1=RBASIC). If it's a TCL record their maybe several commands being executed but most likely the first one will be the TSR check.

Thanks a lot Warren and Sprezzatura. I am able to get access to the tables now.

~Andrei

Excellent - any more problems just shout.

The Sprezzatura Group

World Leaders in all things RevSoft

View this thread on the forum...