Where is "Internet Connectivity Evaluation Tool"?

I just looked up the modem that is I chose for my XP desktop, and my Zoom PCI plus 56k (2920) hardware based modem is not windows 7 compatible! all their other modems that are either softmodems or are controllerless are still compatible tho. that is really messe up. I am planning building a new PC soon, and am planning on reusing several components (the MB I have lined up has 3x PCI slots). There seems to be a trend of the both M$ and the hardware industry trying to push consumers away from hardware based PC components. I prefer to have my different parts of my PC (sound, video, networking) do their own work, and not rely on the CPU to do their work for them before passing it back to the different components (video, sound, networking). there is really no reason what so ever why my modem should not be able to work under win7. the only limiting factor that I see is the lack of drivers for zoom. I know for a fact that the modem does work under win7 as I had the modem working while running the last win7 beta when it was released on my Athlon XP desktop (where the modem resides). there 32-bit vista drivers for the modem. maybe someone can provide a reason (other than speculation) as to why there are not any 64-bit drivers for hardware based cards.

This is offhand, I'm actually looking to fix an Easy Connect issue (That I wasn't having before.)  What seems to work sometimes is using a Vista Driver for Win 7.  Vista seems to be the unsung hero (and maybe more useful) as an upgrade tool when migrating from XP to Win 7.  I have so far done 2 upgrades on 2 very different systems.  Had problems with both, but enough of Vista loaded that when I did "clean" installs of 7 without formatting, Win 7 pulled all of the hardware drivers from the Windows.old folder.  This came in handy, since these were custom build machines, built by someone else.

---

Since the tool is no longer available, does anyone know how I can enable Peer-to-Peer service so my network which is running two computers both with Windows 7, will work with Homegroup?

Can't you go into the services screen and turn it on?

I.e. click on start and in the search box in win7, type 'services', and see if something called "windows services management" comes up.

There are a few services related to peer-to-peer networking.  Unfortunately, I've never used them (I use an old PC running linux to run a local domain and enable sharing that way).

But some services I see are 'HomeGroup Provider', 'HomeGroup Listener', 'Peer Name Resolution Protocol', 'Peer Networking Grouping', Peer Networking Identity Manager',  and  'PNRP Machine Name Publication Service'.  Might try enabling those and see what happens... Also if you bring up "Help and Support" from the start menu, and search for peer networking, you might find some topics of interest or help.

@Cybot: There is a reason why your custom modem is not compatible with Win7 -- the maker of the modem is not supporting it.  This isn't Microsoft's fault.

If you need a safe modem that will be OS and hardware independent and do its own work, go for an external modem that plugs into your computer's serial port.

As long as it is embedded in the computer, it is dependent on both the hardware and the OS.

External modems aren't controller-less -- they have the controller in the modem and aren't dependent on your computer, whereas the one you have is dependent on the computer for all it's resources -- so if you want to have HW that does it's wown work for a modem -- go external.

Like you, I also go for "component" PC-design.  With separate cards for video and networking.   It would be nice to have an external option for video, since I can't upgrade my video card due to newer (faster) cards requiring a new version of PCI-Express.  I have mostly settled with an external sound system using my video card's HDMI output.  But interestingly enough, I use MS's audio drivers, instead of the vendor (Nvidia) audio drivers, because the Vendor's driver files have a bug that won't allow audio output unless you have it associated with another screen.    The MS driver doesn't require me to keep a 2nd monitor (a flat screen TV, really), turned on -- and can drive HDMI sound independently as HDMI was designed.  If you use the Nvidia audio drivers that come with their driver package, it will shut off the sound if it doesn't detect a video monitor.  Big waste of money/electricity. 

So if you want to go with independent stuff, it looks like separate, stand-alone hardware is becoming the way to go and ditching your PC-HW dependent modem for a standalone-external modem would be the way to go.

Remember, if your modem was purchased for XP, that was year 2000.  This is 14 years later.  How many things in your life are usable for >10 years?

I just looked up the modem that is I chose for my XP desktop, and my Zoom PCI plus 56k (2920) hardware based modem is not windows 7 compatible! all their other modems that are either softmodems or are controllerless are still compatible tho. that is really messe up. I am planning building a new PC soon, and am planning on reusing several components (the MB I have lined up has 3x PCI slots). There seems to be a trend of the both M$ and the hardware industry trying to push consumers away from hardware based PC components. I prefer to have my different parts of my PC (sound, video, networking) do their own work, and not rely on the CPU to do their work for them before passing it back to the different components (video, sound, networking). there is really no reason what so ever why my modem should not be able to work under win7. the only limiting factor that I see is the lack of drivers for zoom. I know for a fact that the modem does work under win7 as I had the modem working while running the last win7 beta when it was released on my Athlon XP desktop (where the modem resides). there 32-bit vista drivers for the modem. maybe someone can provide a reason (other than speculation) as to why there are not any 64-bit drivers for hardware based cards.

With modems that may or may not work, I have tried older OS drivers that will usually work.  Sometimes 32 bit drivers will work when 64 bit will not, or 64 bit drivers not available.