Thinking it over, I believe the problem is probably that
win4lin can't handle certain vxd's. These want to run
privileged instructions in ring 0 (or access memory they
"shouldn't"). Instructions or memory access not trapped
and handled by win4lin are probably passed back to Windows as errors.
I filed an issue with Netraverse and they replied promptly, saying
their engineers are investigating. They suggest in the meantime
that ncpfs be used to mount the Netware volume to a linux mount
point, and then use winsetup to assign this mount point a DOS
drive letter. I'll give this a try, though I was under the
impression that ncpfs could not handle Netware IP, and also
that ncpfs has problems with file locks. I'll see.
Dan Greenberg
Ann Arbor, MI
On Fri, 15 Jun 2001, Paul Harvey wrote:
> I get the same error (went by fast enough that I couldn't read it very well), but
>haven't found a solution.
>
> I would love to get this working though.
>
> My install is on a Toshiba laptop, so I don't think that it is the hardware bios
>that is the problem. Might be the "virtual" bios that W4L uses?
>
> There was another message talking about some of the limitations of the current bios
>(64 MB max memory to W4L), maybe Netraverse will update to a newer one that will fix
>both problems.
>
> --Paul Harvey
> [EMAIL PROTECTED]
> Network Engineer
> Walla Walla College
>
> >>> [EMAIL PROTECTED] 6/13/2001 7:45:07 AM >>>
> Under Win4lin 3 (with vnet) I've installed the Novell Client for Netware
> in Windows 95. (I think this should work since our Netware servers use IP
> and not IPX.)
>
> When I try to start windows however, I get the following error message:
>
> "While initializing device NIOS:
> Windows protection error. You need to restart your computer."
>
>
> "NIOS" refers to nios.vxd, which is used by the Netware client. If I
> remove ~/win/windows/system/nios.vxd I can get Windows to start, but
> networking is unavailable.
>
> I searched the Novell knowledge base, and found a single article which
> talks about this problem showing up on a Gateway machine with a buggy
> bios. (The fix was a bios upgrade.) I'm using a DELL however and I
> gather the bios is virtualized under win4lin in any case. (This is a
> dual-boot machine and I get no error when I boot directly to windows.)
>
> Anyone have any idea how I can get nios.vxd to load under win4lin 3?
>
> Thanks,
> Dan Greenberg
>
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
>
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
>
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
