from50sand60s

Ralink D-Link DWA-547 RangeBooster N650 Desktop Adapter Free Driver Download File List Also Supports: RT2860 / RT2870, AirLink101 300N Wireless PCI Adapter, AirLink101 300N Wireless CardBus Adapter, http://www.driverguide.com/driver/detail.php?driverid=1721707&action=filfo

Can you help me sort out the information you provided in this thread? "I went back to trying the utility that's on the AWLC6080 cd and it worked on second install. The cd has a win98 inf. but not the 9x sys file..." So are we to understand that you added this driver... "Ralink made a driver for it named rt28609x.sys." ...and that this provided the missing 9x.sys file for the CD-install to work under Win98/SE? or that "Sitecom wl-180-software.exe has a utility (install and run in w2k mode) if missing stub is added to Kstub822 netapi32.dll section. ie DsGetDcNameA=" provided the missing 9x.sys file? or was this uninstalled prior to attempting the second factory CD-install? Or is nothing sorted out? and everything you attempted needs to be repeated? Was the second factory CD-install performed with additional compatibility selected (ie. Win2K)? Did you install the TI cardbus updates from the MDgX website that you were referred to by jaclaz prior to installing this card... "At http://www.mdgx.com/web.htm there are 2 related bugfixes listed, and after installing them, the original bugfix would not cause nubs 3.3 to hang the system anymore: a ) "Microsoft Windows 98 SE PCMCIA Adapter Code 10 Device Manager Error MSHDC.INF, IOS.VXD 4.10.2224 + PCI.VXD 4.10.2227 Fix:" b ) "Microsoft Windows 98 SE Laptop PCs PCI.VXD 4.10.2228 Fix: MUST install PCMCIA Adapter Code 10 Fix above FIRST!" ...along with microsoftTI.inf from 9/02/2002? Can you provide a link for this last update too? Thanks

Cool... I'm curious about how the wireless-N is accomplished under Win98SE. May I ask what are the adapter specs and the client utility employed?

My laptop is a HP Omnibook 800CT with P1 166MHz processor and 32mb RAM. (2)Type II Cardbus slots, no mini-PCI. No USB. If I'm lucky, someone I know may have a XP laptop gathering dust in their garage or I might find one at a garage sale.

In all the KernelEx development work done to date in the current 4.5.2015.x (or the Kexstub package), is there any resolution for this function call, 'SETUPAPI.DLL:CM_Locate_DevNodeA', to work under Win98SE? Wine has a stub that appears to address something around this... http://code.metager.de/source/xref/wine/dlls/setupapi/stubs.c

Installed newer, WinMe setupapi.dll from the MDgX website... Installed the latest bcmwl5.dll made available. Thanks again... Ran WSCv4. Thanks again... The WL-100G card failed. No WPA support, which I suspected because the card isn't flashed with drivers during the ASUS install. Apparently those with Windows Me experience the same problems getting WPA support on this card. Not surprising since the .inf file for installing the .sys file is the same one for this card. Apparently need a Win2000 or Windows XP laptop to plug this card into and install just so the card would get flashed with the Win 2000 or XP driver bits - the cards you have are setup for Win XP WPA and WPA2 and still could connect using the WSCv4 client under Win98SE (albeit your machine probably has additional drivers/files/settings that may have made your success possible - dunno). That is actually quite a breakthrough in the WPA knowledge base arena. Congrats! Just to round out the parameters, are your cards connecting using AES and/or TKIP encryption?

I found in the discussion of the newer _2015 KernelEx release, http://www.msfn.org/board/topic/173233-kernelex-4520159-updates-apihook/page-5 That this .dll can function under Win98SE. The member has your SP3 installed so he probably has other dependencies covered. I can't go with SP3 because Teamviewer employs IE6 in some manner and I only have 32mb memory on this laptop (Omnibook 800CT). So would the strategy be to place setupapi.dll in the C:\Windows\System directory and install the newer _2015.8 KernelEx release?

Okay, thanks. Does me little good. haha Are you aware if Kexstubs provides a solution? Wine stubs: http://code.metager.de/source/xref/wine/dlls/setupapi/stubs.c Pretty sure this is where the installation fails for Win98SE. Other user tried the Funk Odyssey client to no avail... The McAfee WSC client failed for me when I tried it before... If Kexstubs doesn't provide a setupapi.dll stub, I will try the WSCv4 client...

I know. WSC is WPA only. WSC is my backup plan for WPA, in case the ASUS WPA2 update can't install properly (for the umpteenth time). The ASUS WPA2 install folder includes winflash.exe but it doesn't execute during the installation. There is also an app called 'Resume'. The actual purpose for this app is unknown because, when I click on it, it stalls at a NT-dependent function call. Weird that this is present in a Win98 install. I'm under the impression that this 'Resume' app is responsible for flashing the Broadcom chip with the Broadcom driver bits needed for WPA2. I do not know if the Kexstubs package would help and there are possibly/probably other NT dependencies behind the initial one. It's 'SETUPAPI.DLL:CM_Locate_DevNodeA'... My router is a Belkin N600. A Netgear card I have with WPA can only connect to the internet if the router is set for WPA encryption only, not WPA+WPA2. Problem with this card is that with a Teamviewer remote desktop feature running, the connection drops every time (even on an open connection with encryption disabled) though I can transfer files without problems. That's where the ASUS WL-100G comes into play... Teamviewer remote desktop is rock-solid using the ASUS WL-100G card on an open connection but open connections through the Belkin router are not permitted to make LAN connections to other devices, which is the most secure way to use Teamviewer - behind the router's firewall. This is where WPA (or WPA2) comes in - to run Teamviewer securely within the LAN to access cyberspace from the host computer with secure modern browsers (never mind using the modern MS Office apps on the host computer, etc.). Obviously, I don't know how stable a WPA or WPA2 connection will be while using Teamviewer with this card, yet... My current circumstances force me to connect to Teamviewer on the host computer over the internet using the Belkin router's unencrypted guest account (password required) using a PPTP vpn tunnel. Teamviewer uses it's own encryption simultaneously, so it's a fairly secure approach. I don't seem to be able to connect to L2TP vpn servers from home, likely unable to accomplish NAT transversal, so PPTP is the limit in this regard.

I won't be attempting it until tomorrow.. I'm 99% near the conclusion that the ASUS update cannot install the firmware onto the broadcom chip in this card (at least under my current laptop configuration) and apparently installation aborts before the card is flashed. I'm going to uninstall the native L2TP client to free up TCP/IP connections - my ASUS utility complains that the card adapter is not binding to TCP/IP protocol (it's there and I can connect to the internet but not 'binding' and I can't save configurations). After that, I will try uninstalling and reinstalling the ASUS WPA2 support one last time. According to what I've read, the WL-100G card supports WPA but the ASUS utility interface doesn't which is why I need to try the WSC client if WPA2 is the dead end that it appears to be.

Now what's your take on the bcm43xxa.cat file included in the download you provided? The one that I currently have for my WL-100G card (from the ASUSTEK download that I mentioned earlier) is newer...

You da man!!! Thanks for giving me another shot at WPA

Okay, thanks for the clarification. Possible for you to make that WSC Guard version available to me? The only version available on the internet is the McAfee version and that didn't work for me.

"...They are all Broadcom wireless cards using BCMWL5.SYS 3.90.38.0 which is the last version to work on Windows 98." There is an ASUSTEK 3/2006 download for Win98SE to update ASUS WL-100G wireless PCMCIA cards for wpa2 that includes a BCMWL5.SYS file v 3.90.70 if you want to get a bit further beyond your existing sys files available in your collection... http://www.asus.com/support/Download/11/1/0/2/19/ Select Win98SE OS and check for English version under the utilities available. "...Anything over 3.9x will not work... The Mcafee version gave me nothing but problems. Users should use version 4.0, the one before Mcafee branding..." I'm confused. Statements are seemingly contradictory and unclear to me... The McAfee version of what? WSC Guard? a BCMWL5.SYS file included in the McAfee download? You recommend using 'version 4.0' after stating nothing above version 3.9x will work under Win98SE. Or is there a 4.0 version of WSC Guard out there other than the McAfee version that you can point to or provide? For me, the WSC client recognizes my WL-100G card but cannot connect using WPA. Connects to the guest account connection provided by my router using an open, unencrypted connection. I assumed that the router/card combination wasn't supported. But your experience gives me a sliver of hope that a file substitution can be tried...

Thanks for all the support, folks! Looking for Kexstub installation info, I found the full recommendations list and I will be installing these files before proceeding any further. Reading through the individual updates' information, I need to verify: 1. that I'm supposed to rename "Kstub88.dll" to 'Kexstub.dll' by the time I finish this install? 2. According to the SP3 homepage, SP3 isn't supposed to be installed on systems with IE6 (required for Teamviewer app on my system). Anyone know anything to the contrary? The link on the recommendations page takes you straight to the SP3 download and should be warning of conflicts with IE6, though it may be in a Readme file... I do plan on installing Kexstubs to support the DNSAPI.dll called for by CloudMe. I discovered some pertinent information regarding this dependency in the post referred to for usage of the iphlpapi4.dll. In the 'Without Kexstubs' section, under the 'Kstub_KnownDLLs' subsection, it shows a RegEdit entry forwarding calls for DNSAPI.dll (among others) to LZ32.dll, as if some registry changes may be a fallback solution. @loblo Regarding Kstub88 definitions, "You also need to add a definition for DnsRecordListFree..." For instance? @loblo Thanks for the actual .dll file If I require the other dependency .dll files indicated by Drugwash, do they (and DNSAPI.dll) need to be registered? Can they be registered when they are dummy files or designed for other operating systems?

Installed the dummy DNSAPI.dll. Apparently, the real thing is required. Leads to error "QT5NETWORK.DLL file is linked to missing export DNSAPI.DLL:DnsQuery_W". Any insight, Drugwash?

Thank you, loblo. Swapping msvcr70.dll for msvcrt.dll does resolve the issue with LIBSTDC++-6 as I discovered while running version.7, but there's no special fix regarding the dependency in CloudMe 1.8.8 for DNSAPI.dll included in version 4.5.3.1 - still get the error that this file is missing. I cannot substantiate Drugwash's success running this app in Win98SE. After finding your 2010 post regarding your creation of a dummy DNSAPI.dll, it still seems possible to get this app up and running...

Okay. Installed v4.5.3.1 and installed CloudMe 1.8.8 under default mode (with extensions; no advanced compatibility mode selected). Opened program and received error "LIBSTDC++-6.DLL file is linked to missing export MSVCRT.DLL:_fstat64", the same error I first received under version.7 before swapping msvcr70.dll for msvcrt. So there appears to be no special fix in v4.5.3.1. Unable to duplicate the success of the author without further advice...

I see that loblo did something interesting back in Jan 2012 with a dummy dnsapi.dll under the topic of "finding and fixing dependency problems". Otherwise, this dependency on dnsapi.dll cannot be resolved with Win98 SP3 - not provided in that distribution. So, is this dependency managed somehow in KernelEx 4.5.3.1?

I feel fortunate to have come across this work being done to extend KernelEx capabilities... Running version.7 on a Win98SE machine - no SP3, Revolution Pack, 98SEtoMe... Installing CloudMe 1.8.8 version (said to work with KernelEx 4.5.3.1). Installing in default mode (with extensions). First installation attempts seemed to require installing msvcr70 as msvcrt.dll in C:\Windows\System for the program to run, so I did that. The original error message is gone. Now receive error that DNSAPI.dll is missing when I attempt to run CloudMe. This is not a native .dll file in Win98SE. In this post, there was no mention of additional specific (Win2000/XP) drivers required and I doubt that they were included in the Firefox installation associated with the mentioned success of the CloudMe installation (though the author did mention, vaguely, that "drivers" were installed when Win98SE was installed). So the question is, are there additional drivers in v. 4.5.3.1 (including DNSAPI.dll) not present in version.7 (kinda doubt it) or is SP3 required even though that isn't mentioned (much more likely)? If/when I have the required files, what compatibility mode should I install/operate in? Best regards to you all