Wn111v2 Driver Windows 10

0 views

Skip to first unread message

Alana Fekety

unread,

Aug 3, 2024, 3:14:20 PM8/3/24

to buttjutcompmi

In windows 98 SE ,I am not seeing a lot of options for WPA2-PSK [AES], I have a WG111T, WN111v2 and WNA3100 but only the WG111T has drivers for WIN98SE however the latest drivers (1.2) don't allow for WPA2-PSK [AES] , any idea how to get it working?

I have tried update v1.3(any update after that would not install or work well after intalling Kernel 4.5) for WG111T and it gives me WPA but I couldn't connect, even after creating a guest connection on my DGN2200v4 router which has WPA-PSK [TKIP] + WPA2-PSK [AES] and WPA/WPA2 Enterprise

well, the thing is that, most if not all wifi adapters that support windows 9x doesn't support wpa2 psk because the standard didn't exist or the chip/driver doesn't support that security method.
bear in mind that neither windows 98se, ME or windows 2000 doesn't have native or built in support for any wireless conections (being wifi, bluetooth and so)
it was up to the manufacturer and the drivers to support everything in these OS'es

So, in a proper/old Win 98 machine I have reliable connections without encryption or using WEP, but slow and unreliable connections using WPA. Also, like most wifi chipsets they had issues with their drivers (wireless app not working with the card manufacturer drivers, but working fine with chipset manufacturer drivers). The best thing about that cards was that they supported (had official drivers to do so) being converted into APs.

EDIT: Another option would be using an external wireless to ethernet bridge. I used one in the past to provide wifi connection to a printer that only had ethernet, and you won't have to look for drivers or worry about the card hogging your CPU.

Win98 doesn't natively support WiFi in any form, so you're completely dependent on the drivers of your card/adapter for WPA supplicant. No surprise given that Win98SE was from 1999, and WPA was defined in 802.11.i-2004, so is five years newer.

CPU usage is dependent on both NIC design (does it offload?) and on encryption chosen - TKIP or CCMP(AES). TKIP is computationally lighter, but is almost never accelerated in hardware. AES is harder, but there's more hardware offload. Even Via C3 CPUs (very much Win98-era) had a unit for that. WPA allows both standards, WPA2 is essentially the same as WPA, but mandates the availabilty of CCMP-AES, where it was optional in WPA. It's worth playing around with these settings if you encounter problems. Note that WPA1/TKIP is theoretically insecure, but - unlike WEP, which in some ways is worse than no encryption at all - in practice it's no major risk unless you're doing something sensitive, in which case you shouldn't be messing around with old crap on that network anyway.

The biggest disadvantage to allowing TKIP is that 802.11-2012 mandates that all High Throughput performance enhancements (i.e. the stuff that makes WiFi-n faster than WiFi-a/g) should be disabled if a station connects using TKIP. That not only nerfs your old stuff, but potentially newer devices associating on the same network might select TKIP instead of AES and be impacted too. For optimal performance you should run WPA2-only/CCMP(AES)-only - but when you're talking about getting Win98 online, you might need to compromise for the sake of compatibility. If your AP supports multiple SSIDs with separate security settings, you could potentially get the best of both worlds by broadcasting separate WPA2/AES and WPA1/TKIP SSIDs. Only issue here is that you increase overhead with multiple SSIDs, although each SSID is 'only' about 3% of airtime in 2.4GHz - but with multiple APs that adds up fast.

I'm trying to help a friend with a virus issue. He seems to have fake virus software called "System Check" installed. It has hidden all of his desktop icons, blocked access to the task manager and crippled his antivirus software. When he contacted me about the problem I advised him to disconnect his system from the internet and it has not been reconnected since.

He booted in safe mode and installed MBAM from a CD. Malwarebytes found and fixed three issues in safe mode but upon reboot the virus was still there. He rebooted back into safe mode and ran MBAM again but it found nothing this time. Also, he was able to run his Norton software from his ISP in safe mode but if didn't find anything either.

3/7/2012 8:03:35 PM, Error: Service Control Manager [7000] - The Parallel port driver service failed to start due to the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

3/7/2012 7:12:17 PM, Error: Service Control Manager [7001] - The Network List Service service depends on the Network Location Awareness service which failed to start because of the following error: The dependency service or group failed to start.

3/7/2012 7:12:12 PM, Error: Service Control Manager [7001] - The Workstation service depends on the Network Store Interface Service service which failed to start because of the following error: The dependency service or group failed to start.

3/7/2012 7:12:12 PM, Error: Service Control Manager [7001] - The WebDav Client Redirector Driver service depends on the Redirected Buffering Sub Sysytem service which failed to start because of the following error: A device attached to the system is not functioning.

3/7/2012 7:12:12 PM, Error: Service Control Manager [7001] - The WebClient service depends on the WebDav Client Redirector Driver service which failed to start because of the following error: The dependency service or group failed to start.

3/7/2012 7:12:12 PM, Error: Service Control Manager [7001] - The TCP/IP NetBIOS Helper service depends on the Ancilliary Function Driver for Winsock service which failed to start because of the following error: A device attached to the system is not functioning.

3/7/2012 7:12:12 PM, Error: Service Control Manager [7001] - The SMB MiniRedirector Wrapper and Engine service depends on the Redirected Buffering Sub Sysytem service which failed to start because of the following error: A device attached to the system is not functioning.

3/7/2012 7:12:12 PM, Error: Service Control Manager [7001] - The SMB 2.0 MiniRedirector service depends on the SMB MiniRedirector Wrapper and Engine service which failed to start because of the following error: The dependency service or group failed to start.

3/7/2012 7:12:12 PM, Error: Service Control Manager [7001] - The SMB 1.x MiniRedirector service depends on the SMB MiniRedirector Wrapper and Engine service which failed to start because of the following error: The dependency service or group failed to start.

3/7/2012 7:12:12 PM, Error: Service Control Manager [7001] - The Network Store Interface Service service depends on the NSI proxy service service which failed to start because of the following error: A device attached to the system is not functioning.

3/7/2012 7:12:12 PM, Error: Service Control Manager [7001] - The Network Location Awareness service depends on the Network Store Interface Service service which failed to start because of the following error: The dependency service or group failed to start.

3/7/2012 7:12:12 PM, Error: Service Control Manager [7001] - The IP Helper service depends on the Network Store Interface Service service which failed to start because of the following error: The dependency service or group failed to start.

3/7/2012 7:12:12 PM, Error: Service Control Manager [7001] - The DNS Client service depends on the NetIO Legacy TDI Support Driver service which failed to start because of the following error: A device attached to the system is not functioning.

3/7/2012 7:12:12 PM, Error: Service Control Manager [7001] - The DHCP Client service depends on the Ancilliary Function Driver for Winsock service which failed to start because of the following error: A device attached to the system is not functioning.

3/7/2012 7:12:12 PM, Error: Service Control Manager [7001] - The Computer Browser service depends on the Server service which failed to start because of the following error: The dependency service or group failed to start.

Viewpoint Manager is considered as foistware instead of malware since it is installed without users approval but doesn't spy or do anything "bad". This will change from what we know in 2006 read this article:

After MBAM ran it required a restart to complete the removal process. However, the system hung while shutting down, (I gave it over 30 minutes displaying the shutdown screen before I manually shut it down.)

I attempted to run DDS again but while it was running I got a blue screen and the system restarted. (Not sure if this was related to the process, but I thought I should let you know what happened.) It flashed too fast for me to see the error before the restart.

3/8/2012 9:35:08 PM, Error: Service Control Manager [7000] - The Parallel port driver service failed to start due to the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

3/8/2012 7:59:10 PM, Error: Service Control Manager [7001] - The Network List Service service depends on the Network Location Awareness service which failed to start because of the following error: The dependency service or group failed to start.

3/8/2012 7:57:24 PM, Error: Service Control Manager [7001] - The Workstation service depends on the Network Store Interface Service service which failed to start because of the following error: The dependency service or group failed to start.

3/8/2012 7:57:24 PM, Error: Service Control Manager [7001] - The WebDav Client Redirector Driver service depends on the Redirected Buffering Sub Sysytem service which failed to start because of the following error: A device attached to the system is not functioning.

3/8/2012 7:57:24 PM, Error: Service Control Manager [7001] - The WebClient service depends on the WebDav Client Redirector Driver service which failed to start because of the following error: The dependency service or group failed to start.