AREV fails to open in NT 4.0 (AREV Specific)
At 29 OCT 1999 04:54:56PM Andrew Keller wrote:
When I start Arev from a Novel Server using NT 4.0 with Novell 4.5 client the dos session flashes briefly and then shuts down. If the application is moved over to the C drive for this workstation it runs fine… HELP
At 29 OCT 1999 08:33PM Andrew M. Keller wrote:
Correct that - when the application is moved off the network onto the Window NT platform it does NOT run fine - However, when the application is run under dos it runs correctly. Under windows 95 it runs fine. This is with a CLEAN install of Windows NT.. HELP
At 30 OCT 1999 09:12AM Steve Smith wrote:
Several things come to mind
(a) you need to change the network driver to DOS 3.1 byte range (or to no networks) before moving your application.
(b) you have an old Windows 3.1x *.pif present which is being picked up.
© try disabling expanded memory parameters.
Steve
At 01 NOV 1999 02:36PM Andrew Keller wrote:
Steve -
Can't even run arev bump to change to dos drivers, load fails before that.
All pifs were deleted
To disable expanded memory I use arev /o or /x, neither one of which did anything…
Splash screen is only seen for a second, then boom back at DOS prompt… Any other thoughts …
HELP
At 01 NOV 1999 07:55PM Karen Oland wrote:
1) check frame types - we use 802.2. Force this in your netware client. Also, try upgrading. Early versions of the 4.6 (I believe that is right number) client for NT had a bug that prevented AREV from running. If you search the Novell site, AREV is specifically mentioned in the bug fixes. One of these is most likely cause of the problem – I see it about once every other month
2) make sure you have expanded memory support turned ON (not disabled). Check you icon you are using to start AREV. (Actually, EMS is only needed if you want to do something in AREV, such as open a window, run a report, edit a dictionary or compile a program. If you are content to simply view the main menu and log out. EMS is not needed).
3) from the DOS workstation - check the network driver. If necessary, change to to NO NETWORKING. Then copy back to the file server ONLY the AREV.EXE and REVBOOT files. Try to log in again (make backups first, of course). if this works, change back to the netware (or NLM) network driver.
At 02 NOV 1999 01:36PM Warren wrote:
How are you starting ARev?
In a Command Prompt window and typing AREV or some bat file?
or
From a shortcut on the desktop?
Either way the settings for the command prompt or desktop shortcut should include in the memory section: Conventional Memory=640, Expanded Memory (EMS)=4096, Extended (XMS) Memory=none, HMA=true, DPMI=auto, in Misc, Background always suspend=false.
Many times the problems you describe are caused by insufficient conventional memory be supplied to the session. The command prompt can be adjusted from the control panels. The defaults for the command prompt are typically set to auto and is generally too low for ARev to run properly.