VREDIR.VXD Problem

Does this only happen on machine A or does it also happen on machine B?

You might want to try hitting Ctrl-Alt-Delete once and remove everything except for things like Explorer, Systray, Rundll, and Em_exec (that's from my computer - I have a compaq presario as well)

1. Have you verified that the network settings between the two systems are identical?

2. Does it matter which of the two machines playing descent starts the game and which one joins the existing game?

3. Have you tried any other games?

4. Have you tried any other network access, other than Descent and file sharing?

5. I'm assuming that you are using Microsoft networking on both machines (Client for microsoft networking is the primary logon, and file and printer sharing for microsoft networks is listed on both network control panel), and no trace of netware networking (not listed in either network control panel)

Also, you might want to try re-installing the VREDIR.VXD driver. It could be corrupted. Slim chance, but it might work.

I have tried three different versions of VREDIR.VXD:
1) The original one shipped with Win95.
2) The updated one shipped with service pack 1.
3) A patched version which was supposed to solve a buffering
problem between Win95 and Win NT.

I appreciate your attempt at an answer. Thanks.

I have come across similar problems with network cards and found it was cause by memory range conflicts.
Seriously, not on the local machines but across the networks (dont ask how). Changing the memory range on one of the cards solved the problem. (eg C0000-D0000 changed to E0000-F0000)
If this fixes it, let me know & I will re-submit as an answer.

Are you trying to used SHARE.EXE ?

Re: Comment from Ikon
There are no settings on the LinkSys Ether16 LAN Card for
memory.

Re: Comment from smeebud
No I don't think I'm using share.exe
I do the following: (1) Double click on Notwork neighborhood.
(2) Double click on a shared drive from the other machine.
(3) Watch my system crash!

If you put EmmExclude=A000-FFFF in the [386Enh] section of your system.ini on both machines what happens??

Have you got any different network cards you can try (all you need is probably one).

fossey
read the share.exe relationship. Sometimes you have to trick you system because certain *hardware* sharing requires share.exe but 95 does not lile it. See if this mertod would apply.
-------------------------------

Well the guy has two choices.
1- If he has version 950 of windows 95, OS2 will
run the network program under windows 95. He needs
to install the  program from setup in
windows 95 and make sure that no network is
installed or running. After the installation check
Autoexec.bat for added share. if not there add
the following : to the bat file @C:\windows\command\share.exe.
Before verify, that a share.exe file exist under
that directory.
That should be enough for it to work, if not you need
the error messages.
2.He can install two differents setup on his computer.
A-Create a new partition on the hard drive "Fdisk".
B-Install Dos and Win 3.1 on that partition.
C-modify autoexec.bat to load either windows 95 setup
or win31.
Type Help under Dos command for Info on how to modify
autoexec.bat for several different setup or how to use
Fdisk.
Once this is done. Install the netware on the new partition.
That should make the system run it without problem.
He is going to have to provide more informations about the
netware he is using, the cards and the version of windows
95. And also on the systems that are already on the
system, I assumed that they at least run win 3.1.

sorry, I didn't mean to mark that as an answer. But pleas read anyway

From the MS Knowledge Base:
13 (0Dh): General Protection Fault

  Any condition which is not covered by any of the other processor exceptions will result in a general protection fault. The exception indicates that this program has been corrupted in memory usually resulting in immediate termination of the application.

There is another program that is stepping on the memory that is allocated for the VREDIR.VXD.  If you have already reinstalled the network (overwritting the files) then look for other things in your config.sys autoexec.bat system.ini registry and windows directories that could be different.

I had a similar problem opening *.doc files from a NFS drive it turned out to be an error in the NFS software.

Just FYI

From the MS Knowledge Base:
13 (0Dh): General Protection Fault

  Any condition which is not covered by any of the other processor exceptions will result in a general protection fault. The exception indicates that this program has been corrupted in memory usually resulting in immediate termination of the application.