UNABLE TO OPEN BOOT MEDIA MAP (AREV Specific)
At 15 JUN 1999 05:03:11PM Peter Fisera, Synergy Computer Consulting wrote:
I know this message has come up many times before in this discussion, but it usually seemed to boil down to either Novell access rights, or problems with the NLM, or this mysterious 'Windows frame size' thing.
In our situation we have Windows 95 and Novell 4.x, and no NLM… and I have checked and I have full access to all directories involved. If I type "AREV PFIS" at the command line, where PFIS is a user in the given application, it will not open the application and gives the old "unable to open…" message.
However, if I type "AREV SYSPROG", and then open the application once logged into AREV, then it works!
Any ideas?
Peter Fisera
Synergy Computer Consulting
At 16 JUN 1999 08:27AM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
What happens if you log to the account?
At 19 JUN 1999 07:05PM Peter Fisera wrote:
This is embarrassing to admit, but… how exactly do you LOG TO an account? I know such thing exists but I rarely if ever use it… and in AREV 3.x (which is where this app is, and I am most familiar with AREV 2.x) a lot of the terminology and menus have changed. What is the difference between 'LOG TO' and 'Open Application' (which is what I did), and how do you specify LOG TO from TCL?
Peter Fisera
Synergy Computer Consulting
At 20 JUN 1999 02:31PM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
Logging to an application and opening the application are the same thing. It sounds like something is mismatched on the default volume location, the startup location and the VOC tables.