Just some tidbits of information that I thought should be thrown in... The life-cycle of Windows 2000 is coming to an end in less than a year (March of next year)
Windows XP is about a year and a half beyond that Dec. `06. http://www.microsoft.com/windows/lifecycle/default.mspx Now the above link shows "license availability roadmap", but mainstream support for is due to stop on June `05 for 2000 and Dec `06 for XP. http://support.microsoft.com/default.aspx?scid=fh;[ln];LifeWin --Vic ----- Original Message ----- From: "Randy Groves" <randy.gro...@boeing.com> To: <ag-t...@mcs.anl.gov> Sent: Friday, September 10, 2004 3:53 PM Subject: RE: [AG-TECH] Possible enhancement for Toolkit > I totally understand about the Win2K support issue. But I don't think that > I'm the only one in the position of wanting to proselytize in an > environment where XP is just now becoming an 'officially supported' > OS. Unfortunately, AG is not yet a 'driver' package ;-) - you can't > justify putting XP on a box just because you want to run AG. > > I see Win2K essentially in a similar position with the many Linux > distributions. Hopefully, until such time as something comes along that > totally breaks AG on Win2K, I'm hoping that there will be some accumulated > wisdom available that will condense the needed tweaks. I'm willing to > contribute any findings that I have to that wisdom, but I'm not in a > position to coordinate that effort. > > -randy > > At 07:57 PM 9/9/2004, Ivan R. Judson wrote: > > >One other thing to mention; the reason we don't support win2k is that we > >don't run win2k anywhere. We're writing the toolkit in a way that we hope > >ensures no backward problems, but we are also leveraging the nice new > >features of the latest OS's. > > > >At some point it's likely we'll introduce a feature or bug that will disable > >the "accidental" backward compatibility that exists for platforms like win2k > >(this already happens on linux where old os's, ahem, RH7.X don't have python > >2.3.3+). > > > >We're more than happy for someone else to tinker with this and see if > >there's a reasonable solution, but we're not going to start adding support > >for legacy OS's; not unless someone wants to start paying us to do that -- > >we've got enough interesting research moving forward. > > > >Cheers, > > > >--Ivan > > > > > -----Original Message----- > > > From: owner-ag-t...@mcs.anl.gov > > > [mailto:owner-ag-t...@mcs.anl.gov] On Behalf Of Ivan R. Judson > > > Sent: Thursday, September 09, 2004 9:01 PM > > > To: 'Randy Groves'; ag-t...@mcs.anl.gov > > > Subject: RE: [AG-TECH] Possible enhancement for Toolkit > > > > > > > > > The toolkit is already handling the case where the machine > > > has multiple network adapters; indeed almost all laptops have > > > both wireless and wired connections, mine which I use for > > > development has the following: > > > > > > NetWork Card(s): 3 NIC(s) Installed. > > > [01]: Intel(R) PRO/100 VE Network > > > Connection > > > Connection Name: Fast Ethernet > > > Status: Media disconnected > > > [02]: Intel(R) PRO/Wireless 2100 > > > LAN 3B Mini PCI Adapter > > > Connection Name: Wireless > > > Network Connection > > > DHCP Enabled: Yes > > > DHCP Server: 10.0.1.65 > > > IP address(es) > > > [01]: 10.0.1.17 > > > [03]: Cisco Systems VPN Adapter > > > Connection Name: MCS VPN > > > DHCP Enabled: No > > > IP address(es) > > > [01]: 140.221.18.114 > > > > > > Plus, add the vmware interfaces, MS's fancy ipv4/ipv6 > > > tunnels, teredo, et al and you'll find that on XP the toolkit > > > is doing quite a good job of working in the face of *many* > > > network interfaces ;) > > > > > > Here's my development desktop net interfaces: > > > > > > NetWork Card(s): 4 NIC(s) Installed. > > > [01]: 3Com 3C920 Integrated Fast > > > Ethernet Controller (3C905C-TX Compatible) > > > Connection Name: Wired > > > DHCP Enabled: Yes > > > DHCP Server: 140.221.11.6 > > > IP address(es) > > > [01]: 140.221.34.71 > > > [02]: VMware Virtual Ethernet > > > Adapter for VMnet1 > > > Connection Name: VMware > > > Network Adapter > > > VMnet1 > > > [03]: VMware Virtual Ethernet > > > Adapter for VMnet8 > > > Connection Name: VMware > > > Network Adapter > > > VMnet8 > > > [04]: 1394 Net Adapter > > > Connection Name: 1394 Connection 2 > > > DHCP Enabled: Yes > > > DHCP Server: N/A > > > IP address(es) > > > > > > What kind of a feature are you looking for? What's the use > > > case you're experiencing? What problem are you trying to solve? > > > > > > --Ivan > > > > > > > -----Original Message----- > > > > From: owner-ag-t...@mcs.anl.gov > > > > [mailto:owner-ag-t...@mcs.anl.gov] On Behalf Of Randy Groves > > > > Sent: Thursday, September 09, 2004 8:38 PM > > > > To: ag-t...@mcs.anl.gov > > > > Subject: [AG-TECH] Possible enhancement for Toolkit > > > > > > > > My recent experience with the 'Microsoft TV/Video' network > > > connection > > > > brings to mind an enhancement. It would be nice if, during the > > > > install (and maybe accessible later via a python script), if the > > > > Toolkit finds more than one network adaptor installed on > > > the machine, > > > > it would ask the installer which one it should use. This > > > would have > > > > made it obvious in my case, but also would handle the case > > > where there > > > > REALLY is more than one network adaptor in a machine. I know that > > > > I've also seen a 1394 network adaptor installed on various machines > > > > with FireWire adaptors. > > > > > > > > I will enter this in Bugzilla if it sounds like a good idea. > > > > > > > > -randy > > > > > > > > > > > > > > >
