Mail Archives: djgpp/2006/05/18/06:04:54
"decker" <bdeck AT lycos DOT co DOT uk> wrote in message
news:1147932565 DOT 364009 DOT 291470 AT 38g2000cwa DOT googlegroups DOT com...
> XP only asks for a reboot when I deactivate swsvpkt from my 3Com 3C920.
>
> It seems that the Watt-32 apps try to use the first connection that was
> used previously. Here is a scenario:
>
> I go to the office and attach the ethernet cable but cannot watt-32
> ping network addresses until I deactivate swsvpkt from the wireless.
> But I still have to reboot before watt-32 apps start to work.
The 'Software Systems virtual packet driver' is unbound from an adapter as
soon as the checkbox next to it is cleared (in the NCPA) and the dialog
dismissed. From that point on the adapter is not accessible via SwsVpkt.
If there is an active SwsVpkt session when the driver is disabled then XP
will prompt you to reboot since it can't unbind the driver until all open
handles are closed.
> Then I move to anothjer location with no ethernet but Wifi. Watt-32
> stops working again. I now disable swsvpkt from the ethernet. At that
> moment XP consistently says it requires a reboot.
To avoid the reboot you should either close the SwsVpkt/Watt-32 session or
exit your Watt-32 app and execute SwsVpkt -u, before changing the driver
bindings.
> I activate swsvpkt on
> the wireless, but Watt-32 will not work again until anotther reboot.
> Then I move back to the office and go through the whole thing again.
Ditto above.
> Watt-32 is not storing any access_type setting, so the reason that the
> connection seems to 'default' to the first prior available swsvpkt
> interface must be somewhere in the NDIS registry.
I suspect that Watt-32 doesn't support more than 1 interface per packet
driver and hence is always opening the 1st. The logical numbering
interfaces is based upon the order in which NDIS binds the 'Software Systems
virtual packet driver' to adapters.
> The rebooting is very inconvienient. Is it possible to request an
> enhancement, that the DOS stub have such command line options to 1)
> list available interfaces or 2) switch swsvpkt to use a specific
> interface globally; i.e for all DOS apps run thereafter in the cmd.exe
> session (similar to ndis3pkt stub)??
1) Listing the number of available interfaces is certainly possible, but
it's not currently possible to provide the 'friendly name' i.e. the name of
the adapter shown in the NCPA. This is a limitation of versions of NDIS
prior to 5.0. Adding this feature would prevent the driver running on
Windows 95/98/Me and NT4, which is currently required.
2) Adding an interface number preference to the SwsVpkt command line is
straightforward.
I'll bear these requests in mind but it's unlikely that they'll be any work
on SwsVpkt in the near future. Earning a crust has a much higher
precedence.
In truth it would suit you better if the Watt-32 stack attached to both
interfaces, each with a different IP address. The only change required when
moving locations would be to update the routing table, which should be
automatic if dead gateway detection is implemented.
Given that these discussions are OT for this newsgroup then e-mail any
follow-up to sales AT softsystem DOT co DOT uk
- Lawrence Rust, Software Systems, www.softsystem.co.uk
- Raw text -