"You cannot see the list of users . . . "

Above message displays in Win98 / Drive / Properties / Sharing
window and seems to prevent networking . . .

General setup for wireless network of two PCs:
Upstairs WinXP PC with Wireless G PCI card;
Downstairs Win98/Linux PC with Wireless G router;
this is because the wireless modem to my ISP gets
an OK signal downstairs but not upstairs. (I suspect
the farmhouse-type TV antenna tower spoils the signal
upstairs.)

1. Upstairs WinXP sees and shares all downstairs directories
when downstairs PC is booted in Linux.
2. Downstairs Win98 PC sees all (shared) upstairs WinXP
directories.
Case 3 is incomplete. I cannot yet get the upstairs WinXP
to access the downstairs PC when it is running under Win98.
The WinXP wizard balks and I do not know if the cause is:

A -- Weak wireless signal (showing only 2 strength units out
of 5 in the Belkin wireless card utility.) I doubt this because
## 1 and 2 are OK as above via the same wireless cards.

B -- Win98 sharing routines are incomplete, cf. error
message above. Any drive accepts the sharing command
but balks at the next step, listing permitted users: "You
cannot see the list of users at this time. Try later . . . "

Is this a standard Win98 problem with a standard cure?

--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)





Don Phillipson

In article <(E-Mail Removed)>, "Don Phillipson"
<(E-Mail Removed)> wrote:
>Above message displays in Win98 / Drive / Properties / Sharing
>window and seems to prevent networking . . .
>
>General setup for wireless network of two PCs:
> Upstairs WinXP PC with Wireless G PCI card;
> Downstairs Win98/Linux PC with Wireless G router;
> this is because the wireless modem to my ISP gets
> an OK signal downstairs but not upstairs. (I suspect
> the farmhouse-type TV antenna tower spoils the signal
> upstairs.)
>
>1. Upstairs WinXP sees and shares all downstairs directories
>when downstairs PC is booted in Linux.
>2. Downstairs Win98 PC sees all (shared) upstairs WinXP
>directories.
>Case 3 is incomplete. I cannot yet get the upstairs WinXP
>to access the downstairs PC when it is running under Win98.
>The WinXP wizard balks and I do not know if the cause is:
>
>A -- Weak wireless signal (showing only 2 strength units out
>of 5 in the Belkin wireless card utility.) I doubt this because
>## 1 and 2 are OK as above via the same wireless cards.
>
>B -- Win98 sharing routines are incomplete, cf. error
>message above. Any drive accepts the sharing command
>but balks at the next step, listing permitted users: "You
>cannot see the list of users at this time. Try later . . . "
>
>Is this a standard Win98 problem with a standard cure?

In Win98, go to Control Panel > Network > Access Control and specify
share-level access control. User-level access control requires a
server network and isn't available in a workgroup network like yours.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

"Steve Winograd [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...

> In article <(E-Mail Removed)>, "Don Phillipson"
> <(E-Mail Removed)> wrote:
> >Above message displays in Win98 / Drive / Properties / Sharing
> >window and seems to prevent networking . . .
> >Is this a standard Win98 problem with a standard cure?
>
> In Win98, go to Control Panel > Network > Access Control and specify
> share-level access control. User-level access control requires a
> server network and isn't available in a workgroup network like yours.

Aha -- an undocumented feature (?) but easily fixed: only
this made the system unstable, reporting at reboot unable to find
NDIS.VXD
NDIS2SUP.VXD -- not on disk
VNETBIOS.VXD -- not on disk.
NDIS.VXD was in c:/windows/vcm thus easily copied to c:\windows\system
and this enabled reboot -- with complaints the other two VXD files were
not found. Hence supplementary questions:

1. There were earlier problems installing Win98SE on this
2.8 GHz PC, eventually solved by repetition. (At the 6th
or 8th attempt at installation, the second reboot occurred
OK i.e. did no encounter the NDIS error.) I have the MS
NDIS fix, which reported it did not run on this PC. This
has made me reluctant to attempt any later reinstallation
of the OS (previously done every 18 months or so.) Only
when this month I tried to network did problems appear.
Helpful comments?

2. Aiming (#1) to restore a rock solid OS and then (#2)
to network via wireless card as in the OP, I could simply
remove with REGEDIT the keys calling the other two VXD
files which are
NDIS2SUP.VXD
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\InstalledFiles
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\NDIS
VNETBIOS.VXD
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\InstalledFiles
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\VNETBIOS
and then rebuild the network from scratch. (The Livingston and Straub
"Secrets" manual got the network started, but I don't think it mentioned
the difference between user sharing and server shariing: so I shall read
http://www.bcmaven.com/networking/faq.htm carefully.)
For task #1 (OS) is REGEDIT a practical idea or should I try first
to get the network active and stable?

Many thanks again
--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)

In article <#(E-Mail Removed)>, "Don Phillipson"
<(E-Mail Removed)> wrote:
>> >Above message displays in Win98 / Drive / Properties / Sharing
>> >window and seems to prevent networking . . .
>> >Is this a standard Win98 problem with a standard cure?
>>
>> In Win98, go to Control Panel > Network > Access Control and specify
>> share-level access control. User-level access control requires a
>> server network and isn't available in a workgroup network like yours.
>
>Aha -- an undocumented feature (?) but easily fixed: only
>this made the system unstable, reporting at reboot unable to find
> NDIS.VXD
> NDIS2SUP.VXD -- not on disk
> VNETBIOS.VXD -- not on disk.
>NDIS.VXD was in c:/windows/vcm thus easily copied to c:\windows\system
>and this enabled reboot -- with complaints the other two VXD files were
>not found. Hence supplementary questions:
>
>1. There were earlier problems installing Win98SE on this
>2.8 GHz PC, eventually solved by repetition. (At the 6th
>or 8th attempt at installation, the second reboot occurred
>OK i.e. did no encounter the NDIS error.) I have the MS
>NDIS fix, which reported it did not run on this PC. This
>has made me reluctant to attempt any later reinstallation
>of the OS (previously done every 18 months or so.) Only
>when this month I tried to network did problems appear.
>Helpful comments?
>
>2. Aiming (#1) to restore a rock solid OS and then (#2)
>to network via wireless card as in the OP, I could simply
>remove with REGEDIT the keys calling the other two VXD
>files which are
>NDIS2SUP.VXD
>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contr ol\InstalledFiles
>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servi ces\VxD\NDIS
>VNETBIOS.VXD
>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contr ol\InstalledFiles
>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servi ces\VxD\VNETBIOS
>and then rebuild the network from scratch. (The Livingston and Straub
>"Secrets" manual got the network started, but I don't think it mentioned
>the difference between user sharing and server shariing: so I shall read
>http://www.bcmaven.com/networking/faq.htm carefully.)
>For task #1 (OS) is REGEDIT a practical idea or should I try first
>to get the network active and stable?
>
>Many thanks again

Installing Win98SE on a 2.8 GHz PC??? There are many pitfalls to
that, including:

Windows Protection Error in NDIS with CPU Faster Than 2.1 GHz
http://support.microsoft.com/?kbid=312108

How much memory can Windows 95/98/Me handle?
http://onlinehelp.bc.ca/tips.htm#64mb

For the problem with NDIS.VXD, NDIS2SUP.VXD, and VNETBIOS.VXD,
un-install Client for Microsoft Networks, reboot, and re-install it.
If that doesn't fix the problem, run System File Checker. If that
doesn't fix it, see this site:

Err Msg: Cannot Find a Device File That May Be Needed to Run...
http://support.microsoft.com/kb/166832

I'm sorry, but I'm not familiar with the keys that you list in #2
above.

I don't know of any wireless network adapter that works reliably with
Windows 98. Do you? If a consulting client of mine wants to use
wireless networking with Windows 98, I get a wireless gaming adapter
and connect it to the computer's wired Ethernet port. For example:

http://catalog.belkin.com/IWCatProdu...duct_Id=154416
http://catalog.belkin.com/IWCatProdu...duct_Id=154416
http://games.dlink.com/products/?pid=383&#DGL-3420
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

"Steve Winograd [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...

> Installing Win98SE on a 2.8 GHz PC??? There are many pitfalls to
> that, including:
>
> Windows Protection Error in NDIS with CPU Faster Than 2.1 GHz
> http://support.microsoft.com/?kbid=312108

Got it: thanks anyway.

> For the problem with NDIS.VXD, NDIS2SUP.VXD, and VNETBIOS.VXD,
> un-install Client for Microsoft Networks, reboot, and re-install it.
> If that doesn't fix the problem, run System File Checker. If that
> doesn't fix it, see this site:

Done OK (network successfully created, linking fast Win98
with slow WinXP PC via wireless) by other means . . . when
I discovered / Network / Ethernet dev / Props / Advanced
was blank for "Network address." I added this manually
(last figure reset as 101 instead of 1, because my two PCs
apppear to be .101 and .102) -- and the network popped
into existence (pending configuration of numerous drives
to be Shared or not.)

> I don't know of any wireless network adapter that works reliably with
> Windows 98. Do you? If a consulting client of mine wants to use
> wireless networking with Windows 98, I get a wireless gaming adapter
> and connect it to the computer's wired Ethernet port. For example:
>
> http://catalog.belkin.com/IWCatProdu...duct_Id=154416
> http://catalog.belkin.com/IWCatProdu...duct_Id=154416
> http://games.dlink.com/products/?pid=383&#DGL-3420

Network now works OK, its links being
-- Belkin Wireless G card on upstairs WinXP
-- Trendnet wireless router between downstairs
Win98 PC and ISP's wireless modem. (Originally
installed just as a hardware firewall. No broadband
where I live!) The router required manual configuration
and inputting Belkin-generated data (e.g. encryption
code) into Trendnet menus did the trick OK -- but
only after you explained Share routines (and I input
that home address) for which many thanks.
--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)

In article <(E-Mail Removed)>, "Don Phillipson"
<(E-Mail Removed)> wrote:
>"Steve Winograd [MVP]" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>
>> Installing Win98SE on a 2.8 GHz PC??? There are many pitfalls to
>> that, including:
>>
>> Windows Protection Error in NDIS with CPU Faster Than 2.1 GHz
>> http://support.microsoft.com/?kbid=312108
>
>Got it: thanks anyway.
>
>> For the problem with NDIS.VXD, NDIS2SUP.VXD, and VNETBIOS.VXD,
>> un-install Client for Microsoft Networks, reboot, and re-install it.
>> If that doesn't fix the problem, run System File Checker. If that
>> doesn't fix it, see this site:
>
>Done OK (network successfully created, linking fast Win98
>with slow WinXP PC via wireless) by other means . . . when
>I discovered / Network / Ethernet dev / Props / Advanced
>was blank for "Network address." I added this manually
>(last figure reset as 101 instead of 1, because my two PCs
>apppear to be .101 and .102) -- and the network popped
>into existence (pending configuration of numerous drives
>to be Shared or not.)
>
>> I don't know of any wireless network adapter that works reliably with
>> Windows 98. Do you? If a consulting client of mine wants to use
>> wireless networking with Windows 98, I get a wireless gaming adapter
>> and connect it to the computer's wired Ethernet port. For example:
>>
>> http://catalog.belkin.com/IWCatProdu...duct_Id=154416
>> http://catalog.belkin.com/IWCatProdu...duct_Id=154416
>> http://games.dlink.com/products/?pid=383&#DGL-3420
>
>Network now works OK, its links being
>-- Belkin Wireless G card on upstairs WinXP
>-- Trendnet wireless router between downstairs
>Win98 PC and ISP's wireless modem. (Originally
>installed just as a hardware firewall. No broadband
>where I live!) The router required manual configuration
>and inputting Belkin-generated data (e.g. encryption
>code) into Trendnet menus did the trick OK -- but
>only after you explained Share routines (and I input
>that home address) for which many thanks.

You're welcome! I'm glad that I was able to help you get everything
to work.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm