Weird AREV problems (AREV Specific)
At 28 MAY 1999 07:57:40PM Don Bakke wrote:
Hi there. Here's another one that's stumping me (two in two weeks…that can't be a good sign.)
Situation
Existing AREV 3.12 app running just fine for some time on Novell 3.2 server and workstations running DOS 6.22/Win 3.1/VLM's/NLM 1.50
We installed new workstations running Win98 and we upgraded all previous workstations to Win98. We then installed Novell Client 3.10.
We are getting two different unusual anomalies -
1) AREV launches fine from a shortcut on the desktop. However, once any other program (DOS or Windows) is launched afterwards and the user goes back to AREV, it is always crashed to the debugger. The message and system routine is always different.
2) As mentioned above, AREV will launch fine in a desktop shortcut. However, if we go through a DOS prompt and attempt to manually launch AREV (after successfully manually loading the LHIPXTSR) it always says "Unable to open boot media map". That's all it says. There are no additional messages like FS477 or anything else. I can set my ServerOnly parameters to 0 and this will get me in, but that defeats the purpose.
So what's going on here? Why would a shortcut be successful and not a manual launch? Are the two problems related? BTW, these problems happen on every workstation - new or upgraded - so I can't believe it's a configuration issue. We have also downed the file server without any problems. Everything else is as clean as I can make it and we've had great success with exact configurations elsewhere.
Any help would be much appreciated.
dbakke@srpcs.com
At 28 MAY 1999 08:34PM Steve Smith wrote:
Don, FWIW,
The first problem sounds like the second loaded
program is changing the working root drive/directory
"behind AREV's back", and the attach volume conditions
are somehow violated (try setting the drive letter in
the SETATTACHes). You may have to disable Alt-Tab
on the Win 98 shortcut. I'd try messing with the
shell= statment in config.sys, and checking that
there aren't multiple copies of command.com floating
about. The comspec= may be set to the Novell
server copy, so check that the OS version resolves
OK under Novell's login and is mapping to the correct
copy of command.com
Uncertain about your second problem.
Steve
At 28 MAY 1999 11:38PM Bill Titus wrote:
Copied from posting dated 2/18/99, if of use to you.
This seems to be the problem with novells client32 (ver 2.5 +) and how it maps drives to the novell server. You can solve the problem by remapping the revelation data drive in a dos batch file like:
map root v:=Server\Drive:\path
v:
LHIPXTSR /P /C:200 /R:60
AREV /X /M4096
LHIPXTSR /U
I havent had any problem after doing so, so its worth a try.
Good luck.
/ Jörgen Nydahl, Sandvikenhus
I got the same "Unable to open boot media map" message after upgrading to Client32 3.1 and this did the trick. Hope it helps.
Bill
At 02 JUN 1999 04:09PM Don Bakke wrote:
Thanks, Steve and Bill, for your input.
In the end we had to uninstall Novell Client 3.10 and install Novell Client 2.2. We tried all of your suggestions with 3.10 but nothing quite worked right.
While I'm glad we've got the system stable, I am concerned that 3.10 wouldn't perform right. We are using 3.10 quite well at other sights and I would like to standardize on one client if possible.
One other interesting, but logical, observation. Only those programs that reside on the server would cause crashing in AREV. Local programs would have no effect. This just point me to the network client being the culprit.
dbakke@srpcs.com