I have been attempting to network the following two machines with only partial success.
I'm out of ideas......H E L P.....

Machine A:
486DX66 Clone, 16M, WIN95
LINKSYS 16 Bit Ethernet card using 10BaseT connection.

Machine B: (My New COMPAQ)
Compaq Presario (P120, 16M), WIN95
LINKSYS 16 Bit Ethernet card using 10BaseT connection.

Here is what works:
a) From machine A, I can access all shared drives on machine B.
b) From machine A, I can capture the printer on machine B, and print OK.
c) Descent2 runs IPX/SPX network games between the two machines.

Here is is what's driving me crazy!!!!!
About 9 out of ten times, when attempting to access a shared drive on
machine a from machine b,
the redirector (VREDIR.VXD) rewards me with the blue screen of death.

(exception 0D in VREDIR.VXD...followed by the usual register dump,

At this point the system is toast!!!

1) There are no IRQ, DMA, or PORT ADDRESS conflicts.
2) I have tried removing all other network software and starting from scratch.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

fosseyAuthor Commented:
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 ?
fosseyAuthor Commented:
Re: Comment from Ikon
There are no settings on the LinkSys Ether16 LAN Card for

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).
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
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.

please read this and see the articles that it refers to, they will tell you much about your problem.
Get back to me if you don't understand anything.
We'll put this VREDIR.VXD issue away for good.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.