FS466, unable to open boot media map (Novell Client 32, ver. 3.1) (AREV Specific)
At 14 SEP 1999 05:22:33PM Maggie Woo wrote:
One of my clients submitted the following. Can anyone help?
Has anyone else had this problem:
we installed a new 98 machine w/ Novell Client32 ver. 3.1 (w/ service
pack 1) and cannot get AREV to run. We are running the Novell NLM ver. 1.1 on our Novell 3.12 server. I am getting the "lhipx drive revmedia open error FS466, unable to open boot media map"
I have been to the Revelation web site and found some info., but the
fixes presented there apply only to versions 2.5 and 3.01 of Client32,
anyway, they didn't seem to work for us.
Any suggestions/fixes/insights are desperately needed; we have 9 more
machines like this to set up, plus we will be migrating to a new Novell 5 network w/in a month requiring the new client.
Thanks!
Maggie Woo
At 14 SEP 1999 05:39PM Stephen S. Revelation wrote:
Maggie,
The error you speak of is a known bug with our NLM's on NetWare 4.x and 5.x and Service Pack 1 for Novell Client32 v.3.10 on Win95/98 workstations. We are currently dealing with Novell on the issue and for now recommend staying with the initial Client32 v.3.10 (without the Service Pack).
-Stephen
At 15 SEP 1999 10:25AM Maggie Woo wrote:
My client seems to be under the impression that they must use the new client when they go to Novell 5 next month. Do you know of a work-around to this? Will you be sending out a notice when a solution is found?
Thanks for your reply!
Maggie
At 15 SEP 1999 02:18PM Stephen S. Revelation wrote:
Maggie,
I don't know for what reason your client needs the latest client from Novell when they upgrade to NetWare 5 server, but I do know that, as yet, we do not have a workaround for that particular client running our software with the NLMs. We are actively working on the problem and will undoubtedly let it be known (on this site) when we have found a workaround/fix for the problem.
-Stephen
At 19 OCT 1999 10:41AM William McIntire wrote:
We have same problem, Novell 4.11, Client 3.10. One reason to use newest Novell Client is troubleshooting other software problems, Novell will inevitably suggest one migrate to latest Client version. We took suggestion of earlier post & typed in a manual map to a drive in Dos, even though we're already mapped. This works as a workaround. Will try & see if this can be done in our batch file executing Arev.
At 26 JAN 2000 08:09AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Another of our clients is now experiencing this problem with Client32 3.1 sp1 and sp2.
Can anybody at Revelation tell us if this issue has been resolved yet?
Thanks
World Leaders in all things RevSoft
