Upgrade? (AREV Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|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]]


==== Upgrade? (AREV Specific) ====
=== At 03 SEP 2003 08:20:35AM Greg Phillips wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
I have inherited an AREV database.  It appears to be using OpenInsight NLM 1.5 and thusly, doesn't print on Windows 2000.  What do I need to upgrade to in order to make it work on both Windows 2000 and Windows 98 (which is what it's running on right now).  The database is actually housed on a Netware 3 server.



Any help would be appreciated.
</QUOTE>
----

=== At 03 SEP 2003 08:36AM Donald Bakke wrote:  ===

<QUOTE>Greg,



Your printing problems are related to how the Windows 2000 print manager communicates with DOS applications. In general, Windows does not know when the print job has completed so it hangs on to the print job almost indefinitely.



If you do a [url=http://www.revelation.com/WEBSITE/DISCUSS.NSF/f12696d31000b22a8525652b00831bb2/$searchForm?SearchView]search[/url] on this list for "printing and 2000" you will find many posts related to this subject and suggested fixes. However, one approach that always seems to work is to issue a PDISK PRN command after every print job. This informs Windows that the print job is complete. However, this might be a difficult approach to implement depending on how many print routines your AREV application has. Many of the suggestions you will find by doing a search are workstation adjustments so you might want to see if those will work first.



dbakke@srpcs.com

[url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]



[img]http://www.srpcs.com/srpicon1.gif[/img]

</QUOTE>

----

=== At 03 SEP 2003 09:43AM Don Miller - C3 Inc. wrote:  ===

<QUOTE>The way I generally handle this with netware is:



SUSPEND EXIT CAPTURE type statements with the app starts or 

a CAPTURE COMMAND in the Batch file that starts the APP.



Make sure, in either case that you set a Timeout (TI=30 or somesuch) in the command line.  This will cause netware to release the print job when a character has not been received within the timeout value.



If the app is started from a batch file, it is a good idea to issue an ENDCAP statement after the app closes.



It is also do-able to do the CAPTURE in the App's startup (asking whether the session will use a Network or Local Printer and then proceeding from there).



One of the problems with PDISK is that it can use up file handles and (despite the fact that it usually works well), can sometimes cause an MS-DOS Stack Overflow error.  I usually recommend a STACKS=256 in CONFIG.SYS if this is going to be done.  



Don M.

</QUOTE>

----

=== At 03 SEP 2003 10:04AM Donald Bakke wrote:  ===

<QUOTE>Don M.,



I was assuming he was printing to a local printer. However, upon reading Greg's post again it could be either one. Good call.



dbakke@srpcs.com

[url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]



[img]http://www.srpcs.com/srpicon1.gif[/img]

</QUOTE>

----

=== At 04 SEP 2003 11:06AM Greg Phillips wrote:  ===

<QUOTE>Here are the contents of the arev.bat file that we are trying to use (wht the recent addition of the capture command).  Is this generally correct, or am I still missing something (it still doesn't work)?



----------



@echo off

capture /s=mcg_gracewood /q=printq_0 /l=1 /ti=30 /au

lhipxtsr /p

arev.exe /x/m4096

capture /endcap



----------



Thanks!

</QUOTE>

----

=== At 06 SEP 2003 01:00PM Warren wrote:  ===

<QUOTE>Are you using the Novell Netware client on the Win2K workstation? If not, you should be. Find the 4.8x version (I tried on Novell just now, it is buried somewhere) as I couldn't get the 4.9 release to work with the NLM.



Set your capture using the Novell Client (click on the tray icon and pick Novell capture). Set it to restore the capture when starting windows.



This was the only way I could get capture to work on Win2K. I'm sure you can get the command line capture to work, but it probably takes a lot of fiddling that isn't worth the time and effort unless you need to change printer queues on the fly.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=11424951B742486B85256D960043CD79|View this thread on the  forum...]]