ARev PIF Problems (AREV Specific)
At 08 JAN 2001 02:30:16PM Matt Sorrell wrote:
I'm having a problem configuring the PIF to run ARev on a windows 95 box.
We are using the NLM, but when I try to set the batch file parameter of the PIF, I receive an error message saying that arev.exe cannot be located. If I remove the batch file setting, the arev.exe launches, but I receive an error message because LHIPXTSR is not running.
If I open a dos box and manually load the tsr and then launch ARev, everything works just fine.
Does anyone have any ideas?
At 08 JAN 2001 03:48PM Joe Doscher wrote:
Matt
I'm not sure you are not already doing this but try putting the load commands for the TSR in its own bat file and put the name of that bat file on the batch line of the short cut for the AREV app.
Or put the whole thing - load the TSR, call the AREV app., then unload the TSR - into one bat file and put that bat on the command line of the short cut.
I have had luck with both
Hope it helps
JoeD
At 08 JAN 2001 04:38PM Don Miller - C3 Inc. wrote:
I recommend a stand-alone Batch File (I usually put mine in the AREV subdirectory) Lines look like this
@ECHO OFF
* you can put drive mapping commands here
MAP R:=SYS/AREV…
* if your capture commands are needed, you can put them here also
LHIPXTSR /P /M4096X ← start the app with EMS enabled
Make sure in the properties, you set Close On Exit to checked.
Other Tabs …
Memory:
AUTO
EMS 4096
XMS None
Uses HMA Unchecked
Rest .. don't care
Misc Tab:
Uncheck Screen Saver and Print Screen Key
What I often do is to then copy this shortcut into the AREV subdirectory. Then when I need to set up a new AREV user, just copy/paste using explorer to the desktop
Hope it's useful
Don Miller
C3 Inc.
At 08 JAN 2001 05:10PM matt sorrell wrote:
I tried that, both placing the TSR load in its own bat file, and the whole deal in a batch file.
When I do that, I get an error about not being able to find command.com. I checked the SET variables, and COMSPEC is set to "C:COMMAND.COM". Notice that there is not a backslash in that. I think this might have something to do with the problem, but I could not find anywhere on the machine to change the comspec setting.
Any ideas?
At 09 JAN 2001 10:40AM Don Miller - C3 Inc. wrote:
Matt ..
Is there a COMMAND.COM located in the root directory of the C: drive? There should be. Copy it there if it's not.
Alternatively, you can put a COMSPEC line in the AUTOEXEC.BAT file to point to the right place.
Don Miller
C3 Inc.
At 09 JAN 2001 05:39PM dale walker wrote:
Matt,
Is the comspec first when you type SET?
If not check all the usual suspects - autoexec.bat, login scripts, etc. and get rid of them.
Dale