Re: Can't Connect to Internet - Driver?

[Paul]

Boris wrote:
> I'm attempting to resurrect a Dell Inspiron 8600 laptop, which ran XP
> Home, SP1a, purchased 5/21/2004.
>
> Good news, the charger worked fine, and the battery actually holds a
> charge. I have all the OEM software on CD/DVD that shipped with the
> system.
>
> Bad news, the 40 GB hard drive was dead. Neither Disk Management nor
> DiskPart could fix. I purchased another (60 GB) refurbished hard drive
> ($15) and it installed fine. Windows XP SP1a also loaded ok from the OEM
> CD.
>
> I knew I had to install the drivers from the OEM CD, but first I checked
> Device Manager to see where the yellow question marks were. Here's a list
> of them, next to which is the driver type that eliminated each yellow
> mark. I rebooted after each driver install.
>
> (Under Network adapters there was only one entry, 1394 Net Adapter. It
> had no yellow mark, and was there after completing the OS install, and
> before installing any missing drivers.)
>
> Here's what had yellow question marks. All were under Other Devices:
>
> Other Devices
> 1) Ethernet controller, fixed with Broadcom 440 10/100 Integrated
> Controller
> 2) Multimedia Audio Controller, fixed with Sigmatel Stac etc
> 3) PCI Modem, fixed with Broadcom V92 MDC Modem Rev. A02
> 4) Video Controller, fixed with nVidia GeForce Go5200 Rev. A02
>
> Like I said, I rebooted after each drive install. At this point all was
> working fine.
>
> 5) Network Controller, fixed with Intel PRO/Wireless 2200BG Network
> Connection Rev. A00
>
> I rebooted, and got a BSOD:
>
> https://postimg.cc/gallery/3ivpzsqm4/
>
> If I turned off Wireless in the BIOS, started Windows in Safe Mode without
> networking, or uninstalled the Intel PRO/Wireless driver, BSOD went away
> whenever rebooting.
>
> I then installed the most recent Intel PRO/Wireless driver I could find.
> It was from a Dell Inspiron 6400 purchsed 1/21/2007, and had the OEM
> CD/dvd. It was named the same but Rev. A10. This made the BSOD go away,
> but I could not get on to the internet. The connection to my router said
> excellent, but I couldn't get on wired or wirelessly. I tried connecting
> directly to my Comcast modem, but still no luck.
>
> When I click on the IE desktop icon, I get
> The page cannot be displayed
> Cannot find server or DNS error
>
> This is IE6, Update version SP1, Cipher Strength 128-bit.
>
> SSL, TSL, all seem to be set correctly.
>
> I do have other old Windows OSs; 95, 98, 2000, ME, Vista, all retired, all
> Dell. I wonder if trying them would work. But the drivers may not play
> well with the chipset required on this machine.
>
> Any ideas?

I would have done:

1) WinXP Sp1a (the no-Java service pack, as Sp1 had MSJava)
2) Install SP3 service pack right after.
3) Install drivers.

The theory being, that a more modern driver might
be expecting the services of SP3 (KB936929). This might be
where I got SP3 in a Jan2017 download.

http://download.windowsupdate.com/msdownload/update/software/svpk/2008/04/windowsxp-kb936929-sp3-x86-enu_c81472f7eeea2eca421e116cd4c03e2300ebfde4.exe

Name: WindowsXP-KB936929-SP3-x86-ENU.exe
Size: 331805736 bytes (316 MB)
SHA1: C81472F7EEEA2ECA421E116CD4C03E2300EBFDE4
https://www.virustotal.com/#/file/62e524a552db9f6fd22d469010ea4d7e28ee06fa615a1c34362129f808916654/details

Even though, you could still have troubles. Looks like this
2200BG involves a lot of praying.

https://social.technet.microsoft.com/Forums/lync/en-US/9c31a34c-ab74-4019-8c60-a23afb143d84/sp3-updateddisabled-intel-r-prowireless-2200bg-connection?forum=itproxpsp

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=1637&DwnldID=16617&strOSs=44&OSFullName=Windows*%20XP%20Professional&lang=eng

WZC (Wireless Zero Config) was integrated into SP3. But that
should have been a change above the physical layer and driver bits.

https://en.wikipedia.org/wiki/Wireless_Zero_Configuration

Paul

[J. P. Gilliver (John)]

In message <XnsA9A1901F67700n...@144.76.35.198>, Boris
<nos...@nospam.invalid> writes:
[]

>(Under Network adapters there was only one entry, 1394 Net Adapter. It
>had no yellow mark, and was there after completing the OS install, and
>before installing any missing drivers.)

IIRR, IEEE1394 is the old FireWire. Does the machine have a Firewire
connector (bit like this:

_____
| \
|_____/, about the width of a USB one but thicker)?
[]

>but I could not get on to the internet. The connection to my router said
>excellent, but I couldn't get on wired or wirelessly. I tried connecting
>directly to my Comcast modem, but still no luck.

[]
Could you connect to the router/MoDem's HTML interface (usually
something like http://192.168.0.1, http://10.0.0.2, or similar), either
wired or wirelessly?
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Have you ever heard about a petition, disagreed with it, but been frustrated
that there's no way you can *show* that you disagree? If so, have a look at
https://petition.parliament.uk/petitions/232770 - and please pass it on if you
agree, especially to twitter, facebook, gransnet/mumsnet, or any such forum.

A waist is a terrible thing to mind.

[J. P. Gilliver (John)]

In message <XnsA9A1BEC893E6Bn...@144.76.35.198>, Boris
<nos...@nospam.invalid> writes:
>"J. P. Gilliver (John)" <G6JP...@255soft.uk> wrote in
>news:hU6oCRvo...@255soft.uk:

[]
>> Could you connect to the router/MoDem's HTML interface (usually
>> something like http://192.168.0.1, http://10.0.0.2, or similar), either
>> wired or wirelessly?
>

>Oh, I never thought of trying to log on via ethernet connection to either
>the modem or router.
>
>Comcast Arris CM820 Modem, 192.168.100.1, gets me connected and I can see
>statistics and settings. Nothing is editable.
>
>Dl-524 router, 802.11g/2.4gHz, 192.168.0.1, gets me connected and I can
>see all and change all.
>
>Both of the above actions were done with the Intel PRO/Wireless 2000 BG
>unnstalled. If installed it, I'd get a BSOD and couldn't boot into
>Windows to perform the above.
>
>(I may soon swap out both modem and router. There's enough new technology
>in the house that could benefit.)
>
>What's the signifigance of being able to reach modem/router? Shows that
>network card works? I did replace the network card with the same Dell P/N
>card taken from another Dell, same vintage. I didn't think it would make
>a difference, and it didn't.
>
I'm not sure, but hope it will help others advise (-:!

--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Have you ever heard about a petition, disagreed with it, but been frustrated
that there's no way you can *show* that you disagree? If so, have a look at
https://petition.parliament.uk/petitions/232770 - and please pass it on if you
agree, especially to twitter, facebook, gransnet/mumsnet, or any such forum.

How do you govern a country that seems to have decided that facts are the work
of the devil? - Andy Hamilton on HIGNFY, 2010

[Paul]

Boris wrote:
> Paul <nos...@needed.invalid> wrote in news:pt4rin$utd$1...@dont-email.me:

> IE, FF, and SRIWare Iron browsers all land on
> https://downloadcenter.intel.com/download/16617
> and give me Page Not Found
>
> no matter how careful I am to enter the proper, entire URL.

>
>> WZC (Wireless Zero Config) was integrated into SP3. But that
>> should have been a change above the physical layer and driver bits.
>>
>> https://en.wikipedia.org/wiki/Wireless_Zero_Configuration
>>
>> Paul
>>
>

> I do have SP3 on CD that I downloaded back in May 2008. I did think about
> trying it here, now I will. I just checked and it is indeed the same file in
> the link you provide. I saved it to CD because I wanted to install it on
> many XP machines and using the update method was just too agonizing. I don't
> remember if back then I installed SP3 on this Dell 8600. The machine may
> have been away and unavailable to me.
>
> I do remember that after installing it on another Dell laptop, which
> originally came with XP SP2(?), the network was alway jumping between
> Wireless Zero Configuration and Intel PRO. It was nutty.
>
>

https://web.archive.org/web/20081104145312/http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=1637&DwnldID=16617&strOSs=44&OSFullName=Windows*%20XP%20Professional&lang=eng

Which gives the dead link

http://downloadcenter.intel.com/T8Clearance.aspx?sType=&agr=Y&ProductID=1637&DwnldID=16617&url=/16617/eng/12.0.4.0_X_Drivers.zip&PrdMap=&strOSs=44&OSFullName=Windows* XP Professional&lang=eng

We can try, but this was also protected and not archived.

http://downloadmirror.intel.com/16617/eng/12.0.4.0_X_Drivers.zip

*******

We climb into this here dumpster.

http://downloadwindowsdrivers.info/pci/ven_8086/dev_423a/subsys_10218086/

And are offered a link like this.

ftp://ftp.hp.com/ftp1/pub/softlib/software10/COL24717/gs-63761-1/Intel_Wireless_Drivers_12.0.4.0.exe

Re-craft. Finally, a download.

ftp://ftp.hp.com/pub/softlib/software10/COL24717/gs-63761-1/Intel_Wireless_Drivers_12.0.4.0.exe

But the file doesn't particularly impress me.
It might not be the right tool for the job.
But that's the best I can do for finding something
that "looks like" the link above. 2200BG is mentioned
in the INF file.

These files seem to be identical, so that won't help.

ftp://ftp.hp.com/pub/softlib/software10/COL24711/gs-63687-1/Intel_Wireless_Drivers_12.0.4.0.exe

ftp://ftp.hp.com/pub/softlib/software10/COL24712/gs-63698-1/Intel_Wireless_Drivers_12.0.4.0.exe

Paul

[Paul]

Boris wrote:
> "J. P. Gilliver (John)" <G6JP...@255soft.uk> wrote in
> news:hU6oCRvo...@255soft.uk:
>

>> In message <XnsA9A1901F67700n...@144.76.35.198>, Boris
>> <nos...@nospam.invalid> writes:
>> []
>>> (Under Network adapters there was only one entry, 1394 Net Adapter. It
>>> had no yellow mark, and was there after completing the OS install, and
>>> before installing any missing drivers.)
>> IIRR, IEEE1394 is the old FireWire. Does the machine have a Firewire
>> connector (bit like this:
>>
>> _____
>> | \
>> |_____/, about the width of a USB one but thicker)?
>

> Yes, it is FireWire and it does have a FireWire port. I just found it odd
> that in Device Manager it was under Network Adapter. I never paid much
> attention to the fleeting FireWire technology, but I didn't consider it
> anymore a network thingy than I did USB.

>> []
>>> but I could not get on to the internet. The connection to my router
>>> said excellent, but I couldn't get on wired or wirelessly. I tried
>>> connecting directly to my Comcast modem, but still no luck.
>> []
>> Could you connect to the router/MoDem's HTML interface (usually
>> something like http://192.168.0.1, http://10.0.0.2, or similar), either
>> wired or wirelessly?
>

> Oh, I never thought of trying to log on via ethernet connection to either
> the modem or router.
>
> Comcast Arris CM820 Modem, 192.168.100.1, gets me connected and I can see
> statistics and settings. Nothing is editable.
>
> Dl-524 router, 802.11g/2.4gHz, 192.168.0.1, gets me connected and I can
> see all and change all.
>
> Both of the above actions were done with the Intel PRO/Wireless 2000 BG
> unnstalled. If installed it, I'd get a BSOD and couldn't boot into
> Windows to perform the above.
>
> (I may soon swap out both modem and router. There's enough new technology
> in the house that could benefit.)
>
> What's the signifigance of being able to reach modem/router? Shows that
> network card works? I did replace the network card with the same Dell P/N
> card taken from another Dell, same vintage. I didn't think it would make
> a difference, and it didn't.
>

Firewire supports multiple protocols. 61883 was one of them.
And you might have seen a 61883.sys or similar at one time.

https://docs.microsoft.com/en-us/windows-hardware/drivers/ieee/the-ieee-1394-driver-stack

*******

Networking is one of them.

Typically, a person might use it between two PCs, and using
Internet Connection Sharing.

NIC FW 192.168.1.2
broadband_modem ------ PC#1 --------------- PC#2
ICS Firewire cable
6 to 4 adapter
preferred so no
power is transferred
or power on the connector.
Hopefully, fewer sparks.

The cable still has shield ground, and this may be an
issue if ground potentials are offset.

I don't particularly like connecting Firewires together where
PCs are involved, because the powering strategy might not
be as the standard intended (ground referenced VBUS?). If I
was doing it today, I'd try to use adapters that prevent
VBUS and GND connections, by using 4 pin adapters with only
TX+/TX- RX+/RX- wiring. Using four wire connections to
camcorders is definitely recommended, so nothing gets blown out.
A few people have lost the Firewire port on their $1000 camcorder.

*******

Texas Instruments made a "Firewire box" which
functioned as a hub for Firewire networking. I don't
think anyone bought one. I was never able to find
comments about it, whether sparks came out, or whatever :-)

TI was one of the companies, that attempted to put
capacitive coupling between the MAC and PHY, in an
attempt to avoid a DC path. At one time, people
would state brand preferences for the various
Firewire implementations. Other brands, the MAC and
PHY were one in the same chip, which made it rather
difficult to implement some sort of DC path strategy.

*******

One nice thing about Firewire is RDMA. You can suck the
entire memory contents out of a PC via Firewire. If you're
in the forensics department of the police, this
might allow snapshotting a PC where the perp left
the Firewire port enabled. Who knows what passwords
you might extract, etc.

https://en.wikipedia.org/wiki/DMA_attack

Certain features of Firewire are disabled in Win10.
I don't think the networking stack is there in Win10.
Not sure what other OSes are hobbled on this.

*******

The only thing you should be using that for today,
is camcorder downloads. Firewire is too much of
a PITA (the stiff cable...) to bother with. It's
from the "vacuum tube era".

Paul

[Bill in Co]

Boris wrote:
> Paul <nos...@needed.invalid> wrote in news:pt5rns$cdf$1...@dont-email.me:

>> Which gives the dead link
>>
>> http://downloadcenter.intel.com/T8Clearance.aspx?sType=&agr=Y&ProductID=1
>> 637&DwnldID=16617&url=/16617/eng/12.0.4.0_X_Drivers.zip&PrdMap=&strOSs=44
>> &OSFullName=Windows* XP Professional&lang=eng
>>
>> We can try, but this was also protected and not archived.
>>
>> http://downloadmirror.intel.com/16617/eng/12.0.4.0_X_Drivers.zip
>

> Yep,those go nowhere.

>>
>> *******
>>
>> We climb into this here dumpster.
>>
>> http://downloadwindowsdrivers.info/pci/ven_8086/dev_423a/subsys_10218086/
>>
>> And are offered a link like this.
>>
>> ftp://ftp.hp.com/ftp1/pub/softlib/software10/COL24717/gs-63761-1/Intel_Wi
>> reless_Drivers_12.0.4.0.exe
>>
>> Re-craft. Finally, a download.
>>
>> ftp://ftp.hp.com/pub/softlib/software10/COL24717/gs-63761-1/Intel_Wireles
>> s_Drivers_12.0.4.0.exe
>>
>> But the file doesn't particularly impress me.
>> It might not be the right tool for the job.
>> But that's the best I can do for finding something
>> that "looks like" the link above. 2200BG is mentioned
>> in the INF file.
>>
>> These files seem to be identical, so that won't help.
>>
>> ftp://ftp.hp.com/pub/softlib/software10/COL24711/gs-63687-1/Intel_Wireles
>> s_Drivers_12.0.4.0.exe
>>

>> C
>
> Yes, I downloaded both*, and they are identical from what I can tell. How
> did you get to the .ini file to see it mentioned 2200BG?
>
>
> Anyway, I did get this mess fixed. Here's what I did.
>
> I was still running the 2200BG driver that I loaded from a Dell Inspiron
> 6400 driver CD, Rev. A10, as opposed to the driver that came with this
> Dell Inspiron 8600, which was Rev. A00. Rev. A00 kept BSODing the machine
> unless I turned WiFi off.
>
> *I did download
> ftp://ftp.hp.com/pub/softlib/software10/COL24717/gs-63761-1/Intel_Wireless_
> Drivers_12.0.4.0.exe. I clicked it off, and it said it installed, but
> there was no grand finale, like "Finish", or "Restart". The green (or was
> it blue) install bar just proceeded from left to right, and that was it.
> It then disappeared. I couldn't find where it installed, if it did. So
> what driver was I now using? A10 or this gs-63761 friver.?
>
> But still, I couldn't get connected. All symptoms were the same as
> before, except for one. I could get to google and anything on the google
> domain, like images. I could even get to a few links presented by google
> images, for instances, I googled Marian Carey, got a bunch of images with
> links, and I could go to some of the image links, but not all.
>
> I tried to go to msnbc, no luck. I tried yahoo, no luck.
>
> I went to oldversion.com on another machine, and download IE8 (I was
> currently on IE6). The install on the 8600 went nicely, and opened to the
> settings page. I was encourage. but once configured (to defaults), still
> no luck getting any farther than above, but I could now get to
> Moxilla.org.
>
> From the 8600, I downloaded the last supported FireFox browser compatible
> with XP x32-bit. This was ESR 52.9.0 (32-bit). The install went fine.
>
> I could now cruise the internet both on wifi and ethernet connections.
> (The wifi was being managed by Microsoft, per the funnel shapped system
> tray icon.)
>
> I still wonder what driver is in use. Per Device Manager,

> Intel PRO/Wireless 2200BG Network Connection

> Provider Intel, .
> Date 12/19/07
> Version 9.0.4.39
> Driver Files:
> C:\windows\system32\drivers\w29n51.sys
> C:\windows\system32\netw2c32.dll
> C:\windows\system32\netw2r32.dll
>
> By thte way, updating the driver in Device Manager finds nothing.
>
> I haven't turned on Windows Update. I may, to see what it hands out, but
> not think I should leave well enough alone.
>
> I can't tell anything about the
> ftp://ftp.hp.com/pub/softlib/software10/COL24717/gs-63761-1/Intel_Wireless_
> Drivers_12.0.4.0.exe.
>
> It could be FireFox which got me online, or it could be one of those two
> drivers.
>
> I was ready to move this laptop from the service department to the spare
> parts department, but I'm going to play some more.
>
> Thanks.

Probably safest to leave well enough alone, unless you have a good system
backup. And incidentally, IE6, and to a bit lesser degree, IE8, are
essentially useless now on most sites. So if you're a windows XP user, your
only sane choices left are Firefox and Chrome, IMHO. And Chrome covers the
cases where FF doesn't quite cut it on some sites.

[Paul]

Boris wrote:
> Paul <nos...@needed.invalid> wrote in news:pt5rns$cdf$1...@dont-email.me:

>> Which gives the dead link
>>
>> http://downloadcenter.intel.com/T8Clearance.aspx?sType=&agr=Y&ProductID=1
>> 637&DwnldID=16617&url=/16617/eng/12.0.4.0_X_Drivers.zip&PrdMap=&strOSs=44
>> &OSFullName=Windows* XP Professional&lang=eng
>>
>> We can try, but this was also protected and not archived.
>>
>> http://downloadmirror.intel.com/16617/eng/12.0.4.0_X_Drivers.zip
>

> Yep,those go nowhere.

>> *******
>>
>> We climb into this here dumpster.
>>
>> http://downloadwindowsdrivers.info/pci/ven_8086/dev_423a/subsys_10218086/
>>
>> And are offered a link like this.
>>
>> ftp://ftp.hp.com/ftp1/pub/softlib/software10/COL24717/gs-63761-1/Intel_Wi
>> reless_Drivers_12.0.4.0.exe
>>
>> Re-craft. Finally, a download.
>>
>> ftp://ftp.hp.com/pub/softlib/software10/COL24717/gs-63761-1/Intel_Wireles
>> s_Drivers_12.0.4.0.exe
>>
>> But the file doesn't particularly impress me.
>> It might not be the right tool for the job.
>> But that's the best I can do for finding something
>> that "looks like" the link above. 2200BG is mentioned
>> in the INF file.
>>
>> These files seem to be identical, so that won't help.
>>

> Intel PRO/Wireless 2200BG Network Connection

> Provider Intel, .
> Date 12/19/07
> Version 9.0.4.39
> Driver Files:
> C:\windows\system32\drivers\w29n51.sys
> C:\windows\system32\netw2c32.dll
> C:\windows\system32\netw2r32.dll
>
> By thte way, updating the driver in Device Manager finds nothing.
>
> I haven't turned on Windows Update. I may, to see what it hands out, but
> not think I should leave well enough alone.
>
> I can't tell anything about the
> ftp://ftp.hp.com/pub/softlib/software10/COL24717/gs-63761-1/Intel_Wireless_
> Drivers_12.0.4.0.exe.
>
> It could be FireFox which got me online, or it could be one of those two
> drivers.
>
> I was ready to move this laptop from the service department to the spare
> parts department, but I'm going to play some more.
>
> Thanks.

Looking in "Intel_Wireless_Drivers_12.0.4.0.exe.", the w29n51.sys
in there is version 9.0.4.39 , so that could be where it came from.

Even though the EXE file has the Installshield icon, 7ZIP doesn't
have any trouble accessing the files folder inside the EXE. I can
extract the w29n51.sys for a look, without a problem.

Some driver searches do take a while, especially with "kwality"
drivers where a number of drivers have various bugs, and you
have to play the "best driver" game :-)

Paul


Paul

[Paul]

Boris wrote:

>
> So because the "Intel_Wireless_Drivers_12.0.4.0.exe.", which you led me
> to, and which 7ZIP, when applied to this file, shows version 9.0.4.39
> *and* w29n51.sys, it seems like this is the driver in use. I'd like to
> know for sure, for imaging/backup purposes. If not too much trouble, how
> did you use 7ZIP to interrogate the file?
>
> Many thanks.

When you install 7ZIP, it puts a number of entries in the
right-click context menu.

If you right-click an EXE file, then select "Open archive"
from the 7ZIP sub-menu, you can look inside the EXE. Examples
where this won't work, is if the EXE uses a packer (UPX, Armadillo,
there are more than 20 others). For lots of other formulations,
you can have a look around. I use these techniques, multiple
times per day. It's habit-forming :-)

Things like the more modern versions of InstallShield can
be a problem. You may be able to find a third party tool
for unpacking at least some InstallShield formats. I run
installers in Linux WINE if I need some of those unpacked.
Which is a lot more work (fire up VM, clean up afterwards).

Some softwares detect that you're using WINE and
they refuse to run. I've run into one software, that
"knows all the hacker tricks" and it won't be fooled.
If only the developer had put that much effort into
the actual program he was protecting :-\ The program
itself was crap, and not worth protecting. The installer
on the other hand, was amazing, and could have been
sold to other developers.

Paul

[Ron Hardin]

When one of my wifi's fail I just use a USB wifi
connector and skip everything native to the
machine. They're down to $9.99 or so for XP.

Netgear N300 has always worked. Belkin seems to
have a similar thing.
--
rhha...@mindspring.com

On the internet, nobody knows you're a jerk.

[Bill in Co]

Really? (I think people can tell if you are or are not, and possibly just
as easily as in RL).

[MikeS]

On 24/11/2018 00:55, Boris wrote:
>
Snipped

> I can't tell anything about the
> ftp://ftp.hp.com/pub/softlib/software10/COL24717/gs-63761-1/Intel_Wireless_
> Drivers_12.0.4.0.exe.
>
> It could be FireFox which got me online, or it could be one of those two
> drivers.
>
> I was ready to move this laptop from the service department to the spare
> parts department, but I'm going to play some more.
>

> I just noticed this thread but two observations may still be of interest.

The final version of Internet Explorer that runs on XP (IE8) will no
longer connect to the Internet. Firefox and other browsers are OK but
the IE8 problem is not linked to the driver. I have several real and
virtual XP machines and all are the same. This is well documented if you
search.

I have the final XP (x32) 2200BG drivers which I downloaded from Intel
long ago. The OP is using the correct versions. Here are the Intel
details (choice of exe or zip) if anyone wants to search for the Intel
download files rather than OEM bundles.

Wi-Fi Driver Versions:
-Intel® PRO/Wireless 2200BG Network Connection: 9.0.4.39
-Intel® PRO/Wireless 2915ABG Network Connection: 9.0.4.39
ICS_Dx32.exe 9.0.4.39
12/10/2009 Latest
4.46 MB English
ICS_Dx32.zip 9.0.4.39
12/10/2009 Latest
4.17 MB English
Windows XP *, Windows XP Home Edition*, Windows XP Media Center
Edition*, Windows XP Professional*, Windows
XP Starter Edition*, Windows XP Tablet PC Edition*

[Boris]

MikeS <Mi...@fred.com> wrote in news:pu61hb$c5b$1...@dont-email.me:

Hi, MikeS,

Appreciate your reply. Your observations are of interest, and make
sense. I did give up on IE8 using those drivers, and now I know it was a
losing battle.

Firefox ESR 52.9.0 works fine.

It was just fun getting this old laptop up and running again. Without
all the bloatware on it, it runs decently. It holds a charge, but it
sure is a brick of a laptop. I'm thinking about getting another hard
drive for it and installing Win95, Win98, or Win2000. Of course, I have
to make some boot floppies (chucked all of mine years ago, damn), and see
if they will be recognized by an external USB floppy drive. I need more
spare time.

[Bill in Co]

You might also consider adding Chrome (ver 49.0) as an addition to Firefox,
for those sites that FF doesn't work well enough on. That's happened to me
on a few occasions. And I think having Chrome on there gives us the longest
possible future connectivity for the Internet (for us Windows XP and below
users), even though we're using the last versions possible of those browsers
(for Windows XP).

[R.Wieser]

Boris,

> Firefox ESR 52.9.0 works fine.

Its a bit of a blabbermouth though (calls home to multiple servers, for
"location services" and the like). If you want to reign it in you'll need
to do quite a bit of about:config editing (apart from the ones that you can
access by the menu I mean) .

> Of course, I have to make some boot floppies (chucked all of
> mine years ago, damn), and see if they will be recognized by
> an external USB floppy drive.

USB thumbdrives will mostly do as well.

As for the disk images themselves ? You can find a few here :
https://www.bootdisk.com/bootdisk.htm

Regards,
Rudy Wieser