Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 22 MAY 2002 01:58:16PM James D Adams wrote:

After migrating from Novell to Win2K Server, we are getting an error when we remove the lhipxtsr.exe from the shortcut properties in Win98. We are using the Win2K services for AREV and are no longer running ipx on the network. Page 17 of the NLM15 document shows the subroutine that gets appended to the AREV program when you install the services for Novell. Apparently that code is still loaded and we can't get it out. We removed the lhipxtsr.exe from the server as per the NLMto2000forARev document but still get the error. How do we remove that piece of code from AREV so it no longer asks for it to be loaded?


At 22 MAY 2002 02:03PM James D Adams wrote:

I neglected to mention this is an AREV 2.12 system.


At 22 MAY 2002 04:07PM prabir maulik wrote:

Since you are running Arev on Win2K server you do not need Lhipxtsr. But for performance and avoiding headaches need to install NT Service. Prior to that though you need to go to the network options inside Arev and change the Network Type.

The way I would do it is

1)Change *.bat file (or icon) removing any reference to lhipxtsr.

2)change network type to non-networking

3)remove the revparam file from all directories

4)install NT Service and NPP.

Do a search on documentation and print out the Installation Documentation for NT Service.

Have Fun


At 22 MAY 2002 04:19PM prabir maulik wrote:

guess i did not read the entire subject and jumped the gun. In all probability during the start up of the application you make have a subroutine that checks for ISTSR(). Good place to look would be from the Logon process. BTW you did not mention the error. Is it an error trapping message that has been coded by a programmer of the application?


At 22 MAY 2002 05:33PM Don Miller - C3 Inc. wrote:

Frequently, in order to check whether the files are under control of the NLM, a piece of code similar to:

* SEE IF WE ARE USING THE IPX NETWARE NLM

CALL GETCONFIGURE(ERROR)

* CHECK THE LAN DRIVER

LAN.DRV=ERROR

IF LAN.DRV1,3=IPX' THEN

  DECLARE FUNCTION IsTSR
  • ROUTINE TO CHECK TO SEE IF THE NOVELL NETWARE NLM IS LOADED
  • DON'T DO I/O IF NOT
  IF IsTSR() THEN    /* IF TSR IS LOADED, NO ACTION IS REQUIRED */
  END ELSE
      RESP='
      MSG.TXT=You don't have LHIPXTSR loaded!  Logging off!!!"
      ECHO OFF
      MSG(MSG.TXT,'RI',RESP,'')
      ECHO ON
  • THE CODE BELOW ALLOWS FOR EMERGENCY ACCESS IN THE EVENT OF CATASTROPHIC
  • FAILURE
      IF RESP NE 'PRIV' THEN EXECUTE "OFF"
  END
  • CHECK TO SEE IF NULL @STATION - THIS WILL CAUSE BIG PROBLEMS
  IF @STATION=' THEN
      MSG.TXT=Unable to obtain Workstation ID!  Logging off!!!"
      RESP='
      ECHO OFF
      MSG(MSG.TXT,'RI',RESP,'')
      IF RESP NE 'PRIV' THEN EXECUTE "OFF"
  END
  • CHECK TO SEE IF THE VOC FILE IS UNDER CONTROL OF THE NLM
  • THE FILE HANDLE WITH BE "FFFFFF" IF SO OTHERWISE IT WILL BE A DOS
  • FILE HANDLE
  OPEN "VOC" TO VOC THEN
      IF INDEX(VOC,"FFFFFF",1) ELSE
           MSG.TXT=The VOC file is NOT under the NLM'S Control!|"
           MSG.TXT:=|Please contact the system administrator     '
           MSG.TXT:=|You will now be logged off!!                '
           RESP='
           ECHO OFF
           MSG(MSG.TXT,'RI',RESP,'')
           ECHO ON
  • THE CODE BELOW ALLOWS FOR EMERGENCY ACCESS IN THE EVENT OF CATASTROPHIC
  • FAILURE
           IF RESP NE 'PRIV' THEN EXECUTE "OFF"
      END
  END

END

Might be executed. Check your VOC's Login procedure or the Start program for the application to see if anything like this is loaded. If so, disable it.

Next, change the Lan Driver to Non-Networking.

Next, remove any REVPARAM files from all directories (or rename them)

Next, INSTALL the WIN2000 Service, if necessary on the server

Finally, install the NPP driver .. Oh, you don't have it .. get out your checkbook.

HTH

Don Miller

C3 Inc.


At 22 MAY 2002 07:22PM James D Adams wrote:

The error we get is "You don?t have LHIPXTSR loaded! Logging off!!!" if we don't have the tsr loaded on the client machine. We aren't running Novell or ipx on the network. The istsr() subroutine is still somehow loaded in the programming and we can't figure out how to get rid of it. We'll try the migration procedure again and what you suggested; change to non-networking, delete the revparam, and reinstall the NT services. Thanks.


At 22 MAY 2002 07:27PM James D Adams wrote:

We no longer have Novell or ipx on the network so the NLM shouldn't be loading from anywhere. We'll try as has been suggested to:

Change the Lan Driver to Non-Networking, remove any REVPARAM files from all directories (or rename them), INSTALL the WIN2000 Service, if necessary on the server, and install the NPP driver.

Thanks

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/5838171ca950559988256bc10062b7ff.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1