Fatal Dedicated Indexor (AREV Specific)
At 17 NOV 2002 02:18:47PM Jim Dierking wrote:
Running Arev 3.11, NLM1.5, Novell 4.11, win98se2
Our dedicated indexor is getting an error "Fatal
error in expanded memory, error 210 detected in module g while
executing v119." I found a thread talking about some code to call indexing for one table at a time as a means of isolating where the problem might be. Anyone out there have any other insights or suggestions. TIA, Jim Dierking, Liberty Natural Products, Inc.
At 17 NOV 2002 10:50PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Jim,
Check you have set a max of 4096 K of Expanded memory both on the Windows shortcut and on the AREV.EXE command line (/XM4096).
Also ensure you run AREV in full screen mode.
Steve
World Leaders in all things RevSoft
At 18 NOV 2002 06:22AM Hippo wrote:
What can happen if AREV is not run in full screen?
At 18 NOV 2002 08:25AM Don Miller - C3 Inc. wrote:
When running in windowed mode, then there is overhead in doing video translation which can sometimes interfere with the processing speed required to process an index (particularly on a busy network). Sometimes the process then times out or goes into infinite-retry mode (which is the same thing, in effect).
Don M.
At 18 NOV 2002 06:49PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
I have seen cases where buggy video drivers overflow the video buffer and write into adjacent Expanded Memory buffers. I've even seen faulty mouse drivers (inexplicably) cause grief.
By running in full screen you minimize the chance of an intersection -the 4000 byte video array in video mode 3 (CGA MODE) is less likely to intersect the expanded memory buffer(s) than a full-res screen (in xVGA mode) would.
I agree the chance is slim, but that was the thinking.
Steve
World Leaders in all things RevSoft
At 19 NOV 2002 08:04AM Hippo wrote:
Thanks for answers.
Why I was asking … we run our batch closings usually in windowed mode.
Last closing when operator came to check the closing status she was surprised that it was in "almost start" of the closing, but as she touches mouse the screen changed so rapidly that she saw "almost end".
Does it mean we should run closings in full screen?
Or even run AREV mostly in full screen?
P.S.: Sorry in one of last submits I forgot the word "not" in I am not good at this. It was not intention.
At 19 NOV 2002 08:40AM Don Miller - C3 Inc. wrote:
If I were you, I'd tend to run AREV in full-screen mode, particularly for critical batch-processing operations. Also, be sure to check the startup parms of the shortcut .. especially make sure that background operation is selected. I'd also disable all screen savers and allow for Print Screen (if a printer is available to DOS). Make sure that the workstation is configured properly for EMS operation and that the memory settings are set properly. 4096, no HMA, no XMS, etc. Also make sure that the Idle Sensitivity is set properly if you are using AREV 3.1x. Enable yield-time to windows, etc. In one of my sites which does regular batch postings to accounting, I have an MS-DOS 6.22 machine that connects to their Novell Netware server and does all of this. It has never failed in 7 years (except when the network itself went down). Also, if your batch process creates a lot of new transaction records that are indexed, it is worth using the BATCH INDEXING routines .. see Knowledge Base for more info.
Don M.
At 19 NOV 2002 11:50PM Ted Archibald wrote:
I agree that using DOS only AREV for batch processing is a valid way of operating.
I have a client that has a bank of 8 DOS 6.22 machines running AREV 2.12 that do all the batch processing for the company. This way there are NO problems with MS Windows. PERIOD. The operations room has 2 staff, 1 with a Windows + AREV computer, 1 with 2 windows + AREV systems. Behind them is a rack of 8 monitors with keyboards. The computers themselves are in another room about 30 feet away. Works great. The heat and noise is kept away from staff.
Cheers
Ted
At 20 NOV 2002 08:37AM Don Miller - C3 Inc. wrote:
Ted ..
I have a very similar customer. They use a KVM smart-switch to toggle among the machines to 2 Monitors / Keyboards. I was very impressed when they showed it to me. We wrote a "dispatching" process that allows batch processing to be auto-run from any of the DOS workstations. It logs which workstation grabbed the job, when it started, # of records processed, new items created, etc. Has run flawlessly for many years.
Don M.