joea64
10-10-2001, 08:36 PM
(I had originally posted this on the Peripherals Troubleshooting forum this morning, but as I haven't gotten a response I decided to repost on a busier forum and see if anyone could help. Apologies for the duplication.)
I have recently set up a mini-network at home between a Windows 95B
machine, acting as host, and a Windows 98 SE machine, acting as guest. The
Win95 box is a Dell PII333 (Overdrive), BIOS version A06, 64 MB RAM, with a 56K
ISA modem; the Win98 machine has an AMD Duron 800, 512 MB RAM, Award
BIOS version 6.00 PG, no modem (Internet connections are to be made from the
host and transferred to the guest via DCC).
In order to get Internet Connection Sharing working on the Win95 box (I am
using WinRoute Lite 4.1 as the ICS software), I had to install Dial-Up Networking
1.3 for Virtual Private Networking (VPN) support, then install the RMM patch
when I found that Windows stopped on bootup with a "Windows protection
error" message.
As of now, DCC (I am using a port parallel cable connection) and ICS are
working properly. However, when I close the DCC connection from the guest
machine, the host machine (the Win95 computer) spontaneously (and
improperly) reboots, thus causing Norton Disk Doctor to have to be run to make
sure no damage was done. If I close DCC from the _host_, the system doesn't
spontaneously reboot; however, when I try to shut down the machine, the
computer shuts down before the process completes properly.
I don't know what the problem is, but the Win95 box is older than the Win98
box, which has more modern power management features. Those power
management features (on the Win98 machine) are currently turned off, but I
wonder if somehow the host machine is not interpreting the DCC shutdown
command from the guest machine as a command to reset the machine
(analogous to when the reset button is pressed). Has anyone encountered a
problem similar to this?
-Joe-
P.S. I should note that I installed basic DCC support on both machines about a week before I installed VPN and DUN 1.3; _before_ I installed those, there was no problem with spontaneous reboot. This problem has only occurred since those updates were installed on the Win95B box.
I have recently set up a mini-network at home between a Windows 95B
machine, acting as host, and a Windows 98 SE machine, acting as guest. The
Win95 box is a Dell PII333 (Overdrive), BIOS version A06, 64 MB RAM, with a 56K
ISA modem; the Win98 machine has an AMD Duron 800, 512 MB RAM, Award
BIOS version 6.00 PG, no modem (Internet connections are to be made from the
host and transferred to the guest via DCC).
In order to get Internet Connection Sharing working on the Win95 box (I am
using WinRoute Lite 4.1 as the ICS software), I had to install Dial-Up Networking
1.3 for Virtual Private Networking (VPN) support, then install the RMM patch
when I found that Windows stopped on bootup with a "Windows protection
error" message.
As of now, DCC (I am using a port parallel cable connection) and ICS are
working properly. However, when I close the DCC connection from the guest
machine, the host machine (the Win95 computer) spontaneously (and
improperly) reboots, thus causing Norton Disk Doctor to have to be run to make
sure no damage was done. If I close DCC from the _host_, the system doesn't
spontaneously reboot; however, when I try to shut down the machine, the
computer shuts down before the process completes properly.
I don't know what the problem is, but the Win95 box is older than the Win98
box, which has more modern power management features. Those power
management features (on the Win98 machine) are currently turned off, but I
wonder if somehow the host machine is not interpreting the DCC shutdown
command from the guest machine as a command to reset the machine
(analogous to when the reset button is pressed). Has anyone encountered a
problem similar to this?
-Joe-
P.S. I should note that I installed basic DCC support on both machines about a week before I installed VPN and DUN 1.3; _before_ I installed those, there was no problem with spontaneous reboot. This problem has only occurred since those updates were installed on the Win95B box.