Almost all of these devices use UHF or microwave frequencies that shouldn't be affected by ionospheric disturbances. You might see some long distance propagation on VHF frequencies (lower TV channels and FM broadcast band).
True... most of these devices hover around that 900Mhz range, which is well below the the gamma range...   But I guess my concern is an increased ionization of some of the heavier particles in the atmosphere that may inturn cause interference, as well as how this will impact our already fragile ozone layer, allowing more stuff to leak through...;-)
"...hardware such as those old 386s can be put to use." Yeah, right. What recent version of Linux will run on a 386 with maybe 8 Meg of RAM (but probably only 4) *and* fit on that under 528M hard drive that's the biggest thing the mobo's BIOS will take? I've got some old hardware I'd like re-use.
There are a bunch of "micro" Linuxes out there that are designed to run entirely on a floppy like Trinux, although they recommend at least 12MB RAM...   There's also the Linux Router Project and FreeSCO for using Linux as a router (which is what alot of the old 386s and 486s are used for).   For a list of full blown distributions, you can go here.   This is pretty cool.
I remember back in the mid-70's when there was a particularly nasty and extended sun spot peak - right in the middle of the "CB" (Citizen Band) radio and "trucker" era... It did some major damage to CB sales then.   And with the proliferation of cell phones, sat phones, global positioning devices, wireless lans, etc., it would be interesting what the radio/x-ray interference will do to folks, especially since we've become so dependent on this technology.
The one industry that has always gotten impacted every time one of these events occurs is short-wave/ham radio...   Those who listen in or manage these media know that they always have to change their broadcast frequencies - particularly during heavy EM bursts such as what's being described as coming - which inturn impacts the listening audience.   'Tis a shame.
Wow... they're kinda doing for video what Aureal has been trying to do with 3-D sound. A shame they didn't post any prices on the page...
I always thought that the latest work with blue lasers and holograms would be the forerunners of this type of 3-D display technology, but I guess I was wrong.
I think you missed the point. There are computers in Africa, believe it or not. It's not entirely unpopulated. S. Africa for example. They feel the same pressures over there regarding this issue, I would imagine. Enough to create the need for open source, apparently.
I would agree.   South Africa is considered by the WTO and most of the world as being a fully industrized (not developing) country (eg., they have nuclear power, nuclear weapons, etc.), no different than most European countries.  I would expect that majority of the use of Linux would occur there first and spread via the OAU to major cities in places like Zimbawe, Egypt, Ghana, Nigeria, and Senegal, Ethiopia,and Kenya.   For example, TUCOWS (a major Linux distributor), has locations in South Africa, Zimbawe, Ivory Coast, Mozambique, Kenya, and Egypt.   And if you go to this link, you will note that there are *9* South African Linux Users groups listed and here you will see that there are 4 LUGs in Egypt.   There are Linux references (link and "counter") for Zimbabwe, Ethiopia, Sierra Leone, Togo, et. al.   I also expect that they are also already big users of the *BSDs right now.
Note that with many of those countries, you have 2 classes - the very wealthy, who have access to everything including the net, and the poor.   The continent is not what Hollywood or the National Geographic has portrayed it as being.   Once the colonial puppets are finally booted out and the continent stablizes a bit, you'll have a near 1 billion person potential market there, and a number of large businesses have already considered this fact and are opening up shop there.
To me, this sounds like they are dropping NT on Alpha and selling NT on Intel instead. The space left void with this move will be filled with those eight-way servers running NT, not Alphas running Linux or that other Unix. This looks more like Alpha loss than NT loss.
I followed that whole issue from start to finish, since we have nothing but Compaq and VAX boxen (except for a few Intel Xpress mistakes) and it became a who will drop who first kind of thing between Compaq and M$ - and with some pretty bad feelings between the two about it.   And why do you suppose?   Because the alpha was the only (and please someone correct me if I'm wrong here) non-Intel box that NT could run on and now M$ is truly limited (support wise) to intel platforms only.   And they expect folks with souped up non-intel legacy hardware to throw it all out so they can run win2K?   And for poor slobs like us with mission critical stuff running NT with those alpha processors, when you read the below rest of the story, you see them offering what?   Their Tru64, OpenVMS, and Linux!   Hell... I'll take one of them thar alphas!
Q: What kind of migration programs and options?
A: If a customer has an Alpha server running NT, we will offer them a free license to Tru64 Unix, OpenVMS or Linux -- where it is validated on Alpha servers. The other thing we will do is offer trade-ins with various discounts depending on how long [customers] have had those systems. There will be different scenarios. In some cases, customers will get free trade-ins.
Actually www.compaq.com is not an alias of compaq.com. According to my DNS cache www.compaq.com has it's own address record
My NT4 server (yes... I run IIS on NT4) has 5 different addresses (and 5 different ANAME records) - all on a single server, not multi-homed , with 1 address assigned to Oracle Web Server and the rest to IIS), so that doesn't tell you much... -)  I can point EVERY link from my static main page on my IIS site to my Apache server running on Red Hat 6.1 and you would never know it.... -)
if it was an alias it would have a cononical name (cname) record. So I really do believe they run NT as their web server.
But both names resolve to the web page...   So I ask again... which is it that they are really using? -)
compaq.com may resolve to a Solaris box but www.compaq.com is NT.
Hmmm.... www.compaq.com is just an alias in DNS like compaq.com.   BOTH take you to the Compaq web site.   So now the question becomes which is it or do they maybe have a farm of servers, some requests going one way, others some place else?????? -)
If you had to reboot NT more than 68 times, you're simply an incompetent moron.
Why is it that everyone who says they had to reboot, reinstall, blah blah any windoze product, they're considered incompetent?
I've been using M$ products since 1988 and NT since 3.51 and it's known (and admitted by uslop) that there is a problem with it and some apps (like Oracle, SQLnet, etc.) and what they term as "memory leaks".   Memory leaks as in when windud won't (or can't) completely REMOVE your app from memory when it is closed and thus pieces of it build up and build up and build up until you run out of RAM and the whole fschking thing gives you BSOD!   This is what happens when you so entangle your apps into your core kernel that they can't be released.   Poor things get lost in a goddamn maze.
I mean come on...   What kind of crap is that????
Oh.... I wish I could find NT Workstation for $150!   Last I paid for it was something like $359 at CompUSA... hee hee hee. Of course my Red Hat 6.1 install over FTP was free as a bird... hee hee hee
Where did you get this? Compaq dropped Aplha NT because Inter NT was much cheaper, and more people were buying it.
Here and there's a press release on Compaq's site, the link to which I can't for the life of me get ahold of at the moment (no surprise - navigating Compaq's site is about as easy as navigating M$'s)...;-)
Bottom line... our main office is right now pulling our critical apps running NT on their Compaq alphas and are putting them on intel boxes due to the loss of support... You'll note that most of the big sites have avoided intel boxes (we have VAXes) and have chosen other hardware platforms.   In fact Compaq itself, based on this link (which is an interview with them) is pushing their own Unix - True64 plus others like Linux for their alphas - the point of my post. -)
Just to serve as a devil's advocate for a moment - and no, I certainly don't advocate MS operating systems - I just have to live with them because people pay me to write software for them - but I've had my NT4.0/sp6a box online (as in connected to the Net) for over 11 days
You're lucky you didn't try SP 6 (or maybe you did?)...   How about that M$-lovers?   Remember the SP6 fiasco (or would you prefer not to?), which inturn brought about SP6a?   We had a BDC go down cold with SP6....   or was that YaF® (Yet another Feature) of windud...??
For those who think that/.ers spend their days trashing uslop because we like to...   it's because much of M$'s hype is true - they do run their OS & NOS in over 90% of corps. & gov't around the world and we poor slobs have to fix, reboot, reinstall, blah blah blah this damn crap day after fschking day after fschking day.   Believe me...   it gets old real quick.
And to add fuel to the fire, here is what Netcraft says about what Compaq is REALLY running as their web server:
compaq.com is running Apache/1.3.1 (Unix) on Solaris
Where the HELL is M$ getting it's stats?   Oh... I know... the FUD-o-matic.   It slices, it dices, it spits out whatever you want...  Ptiouuuuuuu.....*splat*.
Some of the biggest e-businesses and dot coms run on Windows: Dell, the largest e-business on the Internet, runs on Windows. Other major sites include Barnes & Noble, InfoSpace, Data Return, buy.com, monster.com, reel.com, bigcharts.com, Hotbot.com, Nordstrom's, realtor.com, eHome, MarthaStewart.com, cooking.com, and Compaq, to name a few.
So why did Compaq drop support for NT last Octoboer on it's biggest boxen with alpha processors in favor of the *nixes?   Answer, windud can only half work on wintel boxes but is totally unreliable on other, more powerful hardware platforms - the stuff that the *BSDs and Solaris run on.   Windoze is still not ready for primetime and it's sad that alot of those companies will lose money from the downtime...
Compaq's internal network used to be Banyan Vines before Banyan basically went belly up and they switched to M$lop.   Apparently they are having second thoughts...
Even clustering for reliability sucks. We run a pair of big Compaqs, and they both fell over a while back. It took over an hour and a half to reboot and restart, largely because of the complications caused by clustering. We could have simply kept the second box warm, and installed a backup from the failed machine on it, and lit it off in less time.
Same situation happened at one of our sites not a month ago, with 2 Compaq boxen running NT in a cluster... Having had VAX clusters running for YEARS, isn't the point of a cluster the fact that if one box goes down, it doesn't take the whole cluster down with it?   If that's the case, what's the point of the cluster, really?   I have never seen such bizarre behavior like this.   THIS is M$'s so-called enterprise NOS.
Not to mention that the 65,000 number doesn't refer to bugs, but also requested enhancements and optimizations that haven't yet been implemented, even the 28,000 "real bugs" sounds pretty bogus to anyone who's been using Win2K heavily since RC2. Since there are just sooooo many thousands of bugs, I challange ZDnet and Slashdot to name even 200 of them.
According to Microsoft, you should not have a fully qualified DNS computer name with more than 64 characters in Windows 2000. If you do, PKI (public key infrastructure) services will fail, which will cause failures in Enterprise Certificate Authority, domain controller and computer automatic enrollment, and IPSec enrollment.
In Windows 2000, if you upgrade your file system from FAT to NTFS, your CA services will fail with this error message in the Application Log: "Certificate Services did not start: Unable to initialize the database connection for (Your CA Name here). Class not registered 0x80040154." Microsoft says you can fix this by uninstalling the CA service and then re-installing it. Make sure to use the same CA name, key pair, and database that you did before.
An upgrade "feature" that you should be aware of: During an upgrade to Windows 2000, Microsoft officials say that the default security settings you would get if you did a clean install will be applied automatically. This means that if you had tighter security prior to the upgrade, those settings are gone. If you want them back, Microsoft says you need to reapply any custom security settings.
You should delay using EFS (Encrypting File System) on a computer that you have upgraded from Windows 95/98 to Windows 2000 until you are sure that the computer has actually joined the new Windows 2000 domain. If you don't, you may have problems with your EFS recovery and migrating private cryptographic keys.
Microsoft officials say that if you want to use Microsoft Office 95 on a Windows 2000 computer, you need to have the Office 95 Year 2000 update installed, which is at officeupdate.microsoft.com/downloaddetails/o95y2k. htm. Make sure that you have installed the latest patches for all the Office applications.
If you have Microsoft Outlook 2000 installed on your Windows 95/98 computer, and then you upgrade to Windows 2000, you will have to reinstall Outlook 2000 after the upgrade. Microsoft officials say you will be warned during the upgrade process. If Outlook 2000 is in your Startup folder, it will happen automatically. They also say that the Outlook reinstallation is very slow, and the progress bar will reset a number of times. Do not cancel the installation, even if it appears the computer is locked up.
If you have a Windows 95 computer with the Microsoft Proxy client, with Winsock 1.1 and you upgrade to Windows 2000, the Proxy Client will be uninstalled. You will see a message to that effect during the upgrade. Reinstall the Proxy Client after the upgrade.
Microsoft officials say that if you are running Windows 2000 on a multi-homed computer, and if you have two or more interfaces with an APIPA (Automatic Private Internet Protocol Addressing) address, you may end up with inconsistent routing behavior for your computer. Microsoft will have more information in its online Knowledge Base.
If you install Windows Media Services as part of an upgrade to Windows 2000, you may cause some problems if you are trying to use Netscape Navigator 3.04. That browser may not be able to get the URL of the web page that contains an embedded client, which causes a problem in logging the client information-the URL value of the cs(Referrer) field. Microsoft doesn't mention a fix, but they specifically cite this older version of Navigator, so an upgrade of Navigator may be in order.
If you upgrade to Windows 2000 and add the optional Windows Media Services components, you may run into an incompatibility if you also have Microsoft Site Server 3.0 with the Site Server Membership Authentication plug-in. According to Microsoft, there is a boot race problem, which means the plug-in won't load, and clients won't be able to connect to the Windows Media Services. This error won't show up in the Windows 2000 Server Event Log service. But if you use the Windows Media Administrator to connect to Media Services, you will get an error message saying you must restart the Windows Media Unicast service. Microsoft officials say to follow that advice as a workaround.
If you have installed Windows Media Services as part of a Windows 2000 upgrade, and you then enable HTTP streaming in the Windows Media Administrator, Microsoft officials say you need to restart your computer. If you don't, the Windows Media Services Event Log fills up with errors.
According to Microsoft, if you upgrade to the release version of Windows 2000 from a previous (presumably beta) version of Windows 2000, and you have a disk that is part of a fault-tolerant set, it may become orphaned during the GUI setup. However, they say you will not lose any data, and you can rebuild the disk with the Disk Administrator snap-in. If it is a mirror disk, use the Resynchronize Mirror command. If it is a RAID 5 disk, use Regenerate Parity.
Here is a situation to avoid, according to Microsoft. When upgrading from Windows NT 4.0 to Windows 2000, you may not want to create logical drives within extended partitions on basic disks. A drive geometry translation error in the Logical Disk Manager may trigger this error message: "Parameter is incorrect." There is no workaround.
Microsoft points out a problem with the Windows 2000 Backup procedure that is caused by Microsoft Office. Sometimes, applications won't restore because of long file names. The Office components use short 8.3 names when registering component locations in the Registry. After a restore, some of these may point to the wrong place, because short file name generation is based on the order in which the applications are installed. The fix is to reinstall any applications that fail.
If you do a Windows 2000 System State Restore, which is part of Windows 2000 Backup, your network identification may say that your computer is already part of the domain. This is wrong. Microsoft says you must rejoin the domain, otherwise you may see this error message: "Trust relation failure." The workaround is to: 1) Join a workgroup; 2) Restart the computer; 3) Rejoin the domain; 4) Restart the computer again.
If you are going to do a scheduled backup with Windows 2000 Backup, and the wrong kind of media is mounted in the backup drive, the backup operation will not start. There will be no outward notice of the failure, since a scheduled backup runs without a user interface. However, if you look in the backup log, there will be a notice of the failure.
According to Microsoft, it is only a display issue, but in Windows 2000 Backup the elapsed and estimated times will not be correct. For now, Microsoft says to ignore the display.
If you are going to do a Windows 2000 Backup to an Exabyte EXB-220 Changer with 8-mm tape, Microsoft says you need to upgrade your firmware for the changer to 6.4.3. Otherwise, you may see this error message: "write file mark."
The Windows 2000 Backup applet may not be for you, if you have huge data volumes (more than 100 GB) that have file counts in the millions. According to Microsoft officials, you may not be able to restore files at the end of a large backup set. They have two suggested workarounds. Either use third-party backup software without the limitations, or break up your backup procedures into smaller segments.
In Windows 2000, you may get an access error in NTBACKUP.EXE if you have a path name greater than 1000 characters in length. The workaround use shorter path names.
When you upgrade to Windows 2000 from Windows 95/98, you may be told by Windows 2000 that these network adapters will not be supported: 3Com EtherLink III EISA 10/100 (3C597-TX); IBM Etherjet ISA Adapters; Crystal LAN CS8920 ISA Adapter; Olicom Plug and Play Token-Ring ISA 16/4 (OC-3118) Adapters. After installation, you may be pleasantly surprised to find that they work anyway. Microsoft says you might have to reset any static network settings.
Microsoft says that the following adapters will not support Media Sense in Windows 2000: Hewlett Packard HP 27247A PC LAN/16 ISA Adapters; Hewlett Packard HP 27250 PC LAN/8 ISA Adapters; Hewlett Packard HP 27247B PC LAN/16 TP Plus ISA Adapters; Hewlett Packard HP DeskDirect J2973A 10baseT PCI LAN Adapters; Intel Pro/10+ PCI Adapters; SMC EtherEZ 8416; SMC EtherCard Elite 16 Ultra (8216). Because of this, you may be affected by the following errors: display of the wrong connection speed; inability to updated speed after enabling; wrong status of cable connection. There is no workaround.
When you upgrade to Windows 2000 from Windows NT 4.0, you may be told by Windows 2000 that these network adapters will not be supported: 3Com EtherLink 905x 10/100 series of Adapters; Compaq Ethernet or Fast Ethernet PCI Adapters; DEC FDDI Controller PCI (Defpa) Adapters; HP EN1207D-TX PCI 10/100 Fast Ethernet Adapters; Intel EtherExpress PRO/10 Adapters; Intel Pro/100 Intelligent Server Adapters (I960). Yet after installation, you may find that they work anyway. Microsoft officials say you might have to reset any static network settings.
If you are using multiple 3Com 3c509 TPC ISA adapters in EISA mode on a Windows 2000 computer, once you disconnect them using Network and Dialup Connections, you will not be able to reconnect them to the network without rebooting your computer. These adapters also sometimes have problems with Windows 2000 Plug and Play.
If you have a 3Com Fast EtherLink ISA 100BaseTX adapter (3C515-TX) on a Windows 2000 computer, and you disable or enable the adapter through Device Manager, your computer may lock up. There is no fix yet.
On a Windows 2000 computer with a wimpy power supply, an Adaptec ANA62044 64-bit 4-port PCI Fast Ethernet adapter may not be able to automatically negotiate network connection on two of the ports. The only "fix" is to upgrade to a computer with a greater power supply.
Windows 2000 is incompatible with multiple Madge ISA TR adapters. According to Microsoft officials, this will trigger system instability, especially with network connections.
If you have SMC 8216 Ultra, 8216 Ultra Tiger, or 8416 EtherEZ cards installed on a dual processor, ACPI-compliant Windows 2000 computer, you should not have adapter resource settings of IRQ 10, I/O address 300, and RAM address CC00. This will cause a boot failure. You will have to choose adapter resources that don't conflict with other system resources, say Microsoft officials.
Windows 2000 TAPI is incompatible with any ATI video cards that have TV tuners. This would include the ATI-TV, the ATI-TV WONDER, and the ATI All-in-Wonder cards, according to Microsoft officials. They hope to add support later.
The shipping version of Windows 2000 will not have drivers for Kodak USB cameras. However, Microsoft officials say you will be able to get drivers for these cameras from Kodak at http://www.kodak.com.
If you are going to run Windows 2000 on an IBM ThinkPad 760EL, 760XD, or 765D laptop, you probably don't want to use an IBM Ethernet Credit Card adapter. According to Microsoft officials, this adapter will not receive a DHCP address, which means it won't have network connectivity. There is no fix at this time.
If you use a Macronix MX98713 on an ACPI compliant Windows 2000 computer, the adapter may cause the computer to hang. Microsoft officials say you need to check with Macronix for an update for this adapter.
You will have problems updating to Windows 2000 if you have an NE2000 or compatible network adapter in your computer, and it has an input/output (I/O) address at 340h (0x340). According to Microsoft officials, your computer may lock up during installation when you get to text mode. As a workaround, you can remove the card or change its I/O setting. After Windows 2000 is installed, the card will work correctly, even at that address.
If you install Windows 2000 on an ACPI-compliant computer, and it has a Xircom CE3 PCMCIA or Compaq Netflex 3 PCI Adapter, you will not be able to resume computing from hibernation or standby modes. To avoid the issue, Microsoft officials say to disable Power Management if you are using these adapters.
Do not install or upgrade to Windows 2000 on a computer that has an AVM ISDN adapter. Microsoft officials say to uninstall and remove the adapter, then install Windows 2000. After installation, you can reinstall the adapter and configure it.
According to Microsoft officials, Digi International Datafire RAS PCI onboard DSP-based modems are not supported in Windows 2000. However, they say that Digi will be updating their driver package, which will then provide support.
On a Windows 2000 computer, if you have a Digi International 8-port PCI card installed, and you have an 8-port concentrator connected to the card, you will not be able to install or support modems, according to Microsoft officials. There is no fix.
If you have a Digi International Multiport Serial card, and you go to Windows 2000 Device Manager and change its properties, the Properties window will remain silently active for about twenty seconds, say Microsoft officials. During this time, you will not be able to close the Device Manager window. The workaround have patience.
Microsoft officials say that some PC card network adapters may not be able to handle heavy network traffic on a Windows 2000 network, and may either lose their connection or hang. These cards include: 3Com Megahertz 10/100 (3C575); Xircom CreditCard Ethernet IIps (PS-CE2-10); Earlier versions of the Xircom CE2, although later versions are OK.
If you are running Windows 2000 on a Compaq Presario laptop computer that has a Lucent Technologies modem, you may have some problems. According to Microsoft officials, the modem will be detected, and Windows 2000 will install the correct drivers, yet the modem won't work. They say this will be fixed by Compaq, who will have an updated BIOS.
Windows 2000 may not be a good idea on a computer with a display adapter using the Voodoo2 chipset. According to Microsoft officials, it will only work as a secondary display adapter on a multi-monitor system. Voodoo3 Pass Thru and Scan Line Interleave are not supported. According to Microsoft officials, this will leave you with sub-par performance. You may want to check in with 3dfx to see if they have new or updated drivers at http://www-dev.3dfx.com/.
If you are running Windows 2000 on a computer with an ATI Mach 64 display adapter, with the drivers that come with Windows 2000, Microsoft officials say your computer may lock up when you start the game Return to Krondor. There is no fix yet.
If you are running Windows 2000 on a computer with an Intel i740 display chipset, you may not want to disable PCI bus-mastering. If you do, Microsoft officials say your display adapter may hang. There may also be incompatibilities between drivers for this chipset included with Windows 2000, and the VIA system chipset.
According to Microsoft officials, a bug in the streaming video decompressor may cause problems with display adapters that use the nVidia Riva 128 Chipset. The bug may cause some streaming video to play upside-down. They don't give a workaround, but standing on your head may work.
There is an incompatibility between Windows 2000 and Adaptec CD Creator 3.5b. Microsoft officials say you should upgrade to CD Creator 4.0.
In Windows 2000, if you are looking at a folder in Large Icon view, the icons for Adobe Illustrator 8.0.1 files may show up as black squares. The only workaround is to pick some other folder view.
If you upgrade from Windows 95/98 to Windows 2000, you will lose the File, Adjust Color Printing function in Adobe PhotoDeluxe. Microsoft has not yet found a workaround to bring this function back.
If you are going to do a clean install of Windows 2000, or when you upgrade on a Windows NT 4.0 computer, the installation process will not be able to automatically find any ISA-based display adapters. Once you manually install the correct driver, the adapter should work.
If you try to install Broderbund Software Calendar Creator 5.0 on Windows 2000, you are going to get an error message saying that the Setup routine can't find Windows NT 4.0 SP3, which it needs. Since you probably don't want to move back to that OS, you better wait for an upgrade to Calendar Creator.
Microsoft officials say not to use Command Software Systems Command AntiVirus 4.54 on a Windows 2000 computer. If you do, things will get so messed up that you will have to reinstall Windows 2000. Microsoft officials say an update will be coming from Command Software at http://www.commandcom.com/.
If you upgrade to Windows 2000 on a computer that has Eudora Pro 4.2 on it, Microsoft Outlook Express will elbow Eudora aside and register itself as your default e-mail program. When you start Eudora Pro, you will see the prompt asking if you want Eudora as your default. If you say yes, you will then see this error message: "Eudora was unable to update the system registry. Your default mail program has not been changed." Microsoft says you can go to the Control Panel, Internet Options, Programs tab, and select Eudora Pro as the default.
Microsoft says that Asymetrix ToolBook 1.5 and 1.53 DayBook Month View will not run on Windows 2000. They say to check with Asymetrix for any updates.
If you upgrade from Windows 95/98 to Windows 2000, and you had HotSync Network installed to synchronize with your Palm device over a network, you will have some initial problems. The network synchronization won't work until you first do a local synchronization between your Palm and the host computer, using the cradle attached to the local PC.
When you upgrade from Windows 95/98 to Windows 2000, and your computer had Hummingbird Exceed 6.1 installed, your Exceed XConfiguration file may be lost. This will cause the error message: "INETD Error: Error creating configuration file." Microsoft says to reinstall Exceed 6.1 on to Windows 2000.
Windows 2000, there are some incompatibilities between IBM ViaVoice 98 Executive 5.2 and IBM Simply Speaking Gold 3.5, and some video cards. Because of this, Microsoft officials say that sometimes the Actor will only show up as a black square when you select Begin reading. There is no workaround at this time.
According to Microsoft officials, you will not be able to install Intergraph DiskShare 3.2 on Windows 2000. If you try, you will get this error message: "This Setup process has determined that you are running on the Microsoft Windows NT 5.0 operating system. This version of DiskShare does not support this operating system. Please verify that you are installing the correct version of DiskShare." For now, there is no workaround.
According to Microsoft officials, a number of programs that use the InstallShield 3 Setup Engine will have a problem when trying to install multiple listings under the Start, Programs menu. It may cause you to see a message such as: "Variable is not large enough for string. Check string declarations. Error 401." It may also cause the shortcut to stay on the Start menu even after uninstalling. Some of the software in question: Raxco Software PerfectDisk; Panda AntiVirus; Norton Crashguard; Executive Software International Diskeeper; Iomega Windows NT tools for JAZZ drive; Berkeley Systems After Dark 3.2; Apple Computer, Inc. QuickTime 3.0 and QuickTime 3.0.2; Interbase Client & Server; Master Clips Publisher; Autodesk AutoCAD 14.
According to Microsoft officials, Symantec Norton Utilities 2.0 for Windows NT will not be able to handle FAT32 drives on Windows 2000. If you try to use Disk Doctor or Speed Disk on FAT32, you will see this error message: "Partition has an unrecognized error on it, would you like to fix the problem?" If you say Yes, you may lose data. Check with Symantec for compatibility information regarding their utilities and Windows 2000.
If you are going to install the Novell GroupWise 5.x client on a Windows 2000 computer, Microsoft officials say you first have to install WMS. This will install MAPI components that GroupWise needs. You can do this from the Windows 2000 CD, in the Valueadd\#092Legacy folder.
Special Windows 2000 Bug Report by Bugnet's Bruce Brown and Bruce Kratofil, who are co-authors, with InfoWorld's Brian Livingston, of Windows 2000 Secrets, published by IDG Books. -------------------
The only reason a car manufactorer would get sued would be because they would have injured or killed a person through their own negligence. I know Windows is bad, but it isn't that bad.
Really?   Ask the Navy about that possibility! -)
"Solaris and Linux Vulnerable To Hack -- An Amendment By Staff February 11, 2000 As many readers have pointed out, the February 11, 2000 article titled, "Solaris and Linux Vulnerable To Hack," posted on our site (www.computercurrents.com) was in error. Although we are responsible for any editorial that appears on our site (and yes, we should have scrutinized this item before we posted it), keep in mind that this was in fact a "feed" from the Newsbytes service, much like an AP or Reuters feed. And as such, we don't typically have control over the content. We naturally contacted Newsbytes about the error, and they pulled the article from their site, as did we. Computer Currents sincerely regrets the error. Based on our own research, we can note that Network Associate's MyCIO.com service (which was created in response to the recent flurry of Denial of Service attacks against Yahoo, eBay, and other major Web sites) can scan Unix-based systems for three DoS agents: TFN, Trinoo, and Stacheldraht. Since these agents do not currently run on any version of Microsoft Windows, there is no need to scan Windows servers with this service. We'd also like to address a few points raised by readers. Computer Currents is in no way associated with Microsoft. In fact, the Computer Currents Web server is run on Linux/Apache/PHP. And Computer Currents is dedicated to accurately reporting on all products, services, and events-- including those related to Linux, Sun, FreeBSD or other *nix products. But yes, we screwed up in not properly screening this feed. Thanks for bringing it to our attention, as painful as that was! Sincerely, Robert Luhn Editor-in-Chief Garth Gillespie Webmaster Computer Currents Magazine www.computercurrents.com"
Slashdot Mirror
Almost all of these devices use UHF or microwave frequencies that shouldn't be affected by ionospheric disturbances. You might see some long distance propagation on VHF frequencies (lower TV channels and FM broadcast band).
;-)
True... most of these devices hover around that 900Mhz range, which is well below the the gamma range...   But I guess my concern is an increased ionization of some of the heavier particles in the atmosphere that may inturn cause interference, as well as how this will impact our already fragile ozone layer, allowing more stuff to leak through...
"...hardware such as those old 386s can be put to use." Yeah, right. What recent version of Linux will run on a 386 with maybe 8 Meg of RAM (but probably only 4) *and* fit on that under 528M hard drive that's the biggest thing the mobo's BIOS will take? I've got some old hardware I'd like re-use.
There are a bunch of "micro" Linuxes out there that are designed to run entirely on a floppy like Trinux, although they recommend at least 12MB RAM...   There's also the Linux Router Project and FreeSCO for using Linux as a router (which is what alot of the old 386s and 486s are used for).   For a list of full blown distributions, you can go here.   This is pretty cool.
I remember back in the mid-70's when there was a particularly nasty and extended sun spot peak - right in the middle of the "CB" (Citizen Band) radio and "trucker" era... It did some major damage to CB sales then.   And with the proliferation of cell phones, sat phones, global positioning devices, wireless lans, etc., it would be interesting what the radio/x-ray interference will do to folks, especially since we've become so dependent on this technology.
The one industry that has always gotten impacted every time one of these events occurs is short-wave/ham radio...   Those who listen in or manage these media know that they always have to change their broadcast frequencies - particularly during heavy EM bursts such as what's being described as coming - which inturn impacts the listening audience.   'Tis a shame.
Wow... they're kinda doing for video what Aureal has been trying to do with 3-D sound. A shame they didn't post any prices on the page...
I always thought that the latest work with blue lasers and holograms would be the forerunners of this type of 3-D display technology, but I guess I was wrong.
I think you missed the point. There are computers in Africa, believe it or not. It's not entirely unpopulated. S. Africa for example. They feel the same pressures over there regarding this issue, I would imagine. Enough to create the need for open source, apparently.
I would agree.   South Africa is considered by the WTO and most of the world as being a fully industrized (not developing) country (eg., they have nuclear power, nuclear weapons, etc.), no different than most European countries.  I would expect that majority of the use of Linux would occur there first and spread via the OAU to major cities in places like Zimbawe, Egypt, Ghana, Nigeria, and Senegal, Ethiopia,and Kenya.   For example, TUCOWS (a major Linux distributor), has locations in South Africa, Zimbawe, Ivory Coast, Mozambique, Kenya, and Egypt.   And if you go to this link, you will note that there are *9* South African Linux Users groups listed and here you will see that there are 4 LUGs in Egypt.   There are Linux references (link and "counter") for Zimbabwe, Ethiopia, Sierra Leone, Togo, et. al.   I also expect that they are also already big users of the *BSDs right now.
Note that with many of those countries, you have 2 classes - the very wealthy, who have access to everything including the net, and the poor.   The continent is not what Hollywood or the National Geographic has portrayed it as being.   Once the colonial puppets are finally booted out and the continent stablizes a bit, you'll have a near 1 billion person potential market there, and a number of large businesses have already considered this fact and are opening up shop there.
I think compaq.com (Solaris)
;-)   As I said, I can redirect any IIS link to my Apache... ;-)   (yes I'm being juvenile)
Windows are far more compleate and complex than Linux.
????   Yeah I guess so...   Linux is just a kernel... Windoze is a nightmare...
My last customer was using Exchange Servers (2) for a total of 1000 users (email mainly). No down time in 4 months...
;-)   What kind of hardware were they using?
No flame here...   just informational question...  
Thanks!
To me, this sounds like they are dropping NT on Alpha and selling NT on Intel instead. The space left void with this move will be filled with those eight-way servers running NT, not Alphas running Linux or that other Unix. This looks more like Alpha loss than NT loss.
I followed that whole issue from start to finish, since we have nothing but Compaq and VAX boxen (except for a few Intel Xpress mistakes) and it became a who will drop who first kind of thing between Compaq and M$ - and with some pretty bad feelings between the two about it.   And why do you suppose?   Because the alpha was the only (and please someone correct me if I'm wrong here) non-Intel box that NT could run on and now M$ is truly limited (support wise) to intel platforms only.   And they expect folks with souped up non-intel legacy hardware to throw it all out so they can run win2K?   And for poor slobs like us with mission critical stuff running NT with those alpha processors, when you read the below rest of the story, you see them offering what?   Their Tru64, OpenVMS, and Linux!   Hell... I'll take one of them thar alphas!
Q: What kind of migration programs and options?
A: If a customer has an Alpha server running NT, we will offer them a free license to Tru64 Unix, OpenVMS or Linux -- where it is validated on Alpha servers. The other thing we will do is offer trade-ins with various discounts depending on how long [customers] have had those systems. There will be different scenarios. In some cases, customers will get free trade-ins.
Actually www.compaq.com is not an alias of compaq.com. According to my DNS cache www.compaq.com has it's own address record
;-)  I can point EVERY link from my static main page on my IIS site to my Apache server running on Red Hat 6.1 and you would never know it....   ;-)
;-)
My NT4 server (yes... I run IIS on NT4) has 5 different addresses (and 5 different ANAME records) - all on a single server, not multi-homed , with 1 address assigned to Oracle Web Server and the rest to IIS), so that doesn't tell you much...  
if it was an alias it would have a cononical name (cname) record. So I really do believe they run NT as their web server.
But both names resolve to the web page...   So I ask again... which is it that they are really using?  
I have a Sony Playstation.   I've heard alot of good things about the graphics on the Dreamcast...   Anyone want to share their experiences?
FIRST POST!
compaq.com may resolve to a Solaris box but www.compaq.com is NT.
;-)
Hmmm.... www.compaq.com is just an alias in DNS like compaq.com.   BOTH take you to the Compaq web site.   So now the question becomes which is it or do they maybe have a farm of servers, some requests going one way, others some place else??????  
I find it hard to believe that Compaq would not run their website on their own hardware.
Uh... hello?   Why would you think that Solaris doesn't run on Compaq hardware?   From Sun's Solaris 8 page:
System Requirements
SPARC (32-/64-bit) or Intel Architecture (32-bit) platforms
Disk space: 600 Mbytes for desktops; 1 Gbyte for servers
Memory: 64 Mbytes minimum
If you had to reboot NT more than 68 times, you're simply an incompetent moron.
Why is it that everyone who says they had to reboot, reinstall, blah blah any windoze product, they're considered incompetent?
I've been using M$ products since 1988 and NT since 3.51 and it's known (and admitted by uslop) that there is a problem with it and some apps (like Oracle, SQLnet, etc.) and what they term as "memory leaks".   Memory leaks as in when windud won't (or can't) completely REMOVE your app from memory when it is closed and thus pieces of it build up and build up and build up until you run out of RAM and the whole fschking thing gives you BSOD!   This is what happens when you so entangle your apps into your core kernel that they can't be released.   Poor things get lost in a goddamn maze.
I mean come on...   What kind of crap is that????
NTworkstation -- $150
Oh.... I wish I could find NT Workstation for $150!   Last I paid for it was something like $359 at CompUSA... hee hee hee.
Of course my Red Hat 6.1 install over FTP was free as a bird... hee hee hee
Where did you get this? Compaq dropped Aplha NT because Inter NT was much cheaper, and more people were buying it.
;-)
;-)
Here and there's a press release on Compaq's site, the link to which I can't for the life of me get ahold of at the moment (no surprise - navigating Compaq's site is about as easy as navigating M$'s)...
Bottom line... our main office is right now pulling our critical apps running NT on their Compaq alphas and are putting them on intel boxes due to the loss of support... You'll note that most of the big sites have avoided intel boxes (we have VAXes) and have chosen other hardware platforms.   In fact Compaq itself, based on this link (which is an interview with them) is pushing their own Unix - True64 plus others like Linux for their alphas - the point of my post.  
Just to serve as a devil's advocate for a moment - and no, I certainly don't advocate MS operating systems - I just have to live with them because people pay me to write software for them - but I've had my NT4.0/sp6a box online (as in connected to the Net) for over 11 days
/.ers spend their days trashing uslop because we like to...   it's because much of M$'s hype is true - they do run their OS & NOS in over 90% of corps. & gov't around the world and we poor slobs have to fix, reboot, reinstall, blah blah blah this damn crap day after fschking day after fschking day.   Believe me...   it gets old real quick.
You're lucky you didn't try SP 6 (or maybe you did?)...   How about that M$-lovers?   Remember the SP6 fiasco (or would you prefer not to?), which inturn brought about SP6a?   We had a BDC go down cold with SP6....   or was that YaF® (Yet another Feature) of windud...??
For those who think that
And to add fuel to the fire, here is what Netcraft says about what Compaq is REALLY running as their web server:
compaq.com is running Apache/1.3.1 (Unix) on Solaris
Where the HELL is M$ getting it's stats?   Oh... I know... the FUD-o-matic.   It slices, it dices, it spits out whatever you want...  Ptiouuuuuuu.....*splat*.
Quote.com is owned by Lycos, Inc., and is a part of the Lycos Network of sites.
And according to Netcraft:
"lycos.com is running Netscape-Enterprise/3.6 SP3 on DIGITAL UNIX"
'Nuff said.
Some of the biggest e-businesses and dot coms run on Windows: Dell, the largest e-business on the Internet, runs on Windows. Other major sites include Barnes & Noble, InfoSpace, Data Return, buy.com, monster.com, reel.com, bigcharts.com, Hotbot.com, Nordstrom's, realtor.com, eHome, MarthaStewart.com, cooking.com, and Compaq, to name a few.
So why did Compaq drop support for NT last Octoboer on it's biggest boxen with alpha processors in favor of the *nixes?   Answer, windud can only half work on wintel boxes but is totally unreliable on other, more powerful hardware platforms - the stuff that the *BSDs and Solaris run on.   Windoze is still not ready for primetime and it's sad that alot of those companies will lose money from the downtime...
Compaq's internal network used to be Banyan Vines before Banyan basically went belly up and they switched to M$lop.   Apparently they are having second thoughts...
Even clustering for reliability sucks. We run a pair of big Compaqs, and they both fell over a while back. It took over an hour and a half to reboot and restart, largely because of the complications caused by clustering. We could have simply kept the second box warm, and installed a backup from the failed machine on it, and lit it off in less time.
Same situation happened at one of our sites not a month ago, with 2 Compaq boxen running NT in a cluster... Having had VAX clusters running for YEARS, isn't the point of a cluster the fact that if one box goes down, it doesn't take the whole cluster down with it?   If that's the case, what's the point of the cluster, really?   I have never seen such bizarre behavior like this.   THIS is M$'s so-called enterprise NOS.
From an Infoworld article:
BugReport Special: Windows 2000
According to Microsoft, you should not have a fully qualified DNS computer name with more than 64 characters in Windows 2000. If you do, PKI (public key infrastructure) services will fail, which will cause failures in Enterprise Certificate Authority, domain controller and computer automatic enrollment, and IPSec enrollment.
In Windows 2000, if you upgrade your file system from FAT to NTFS, your CA services will fail with this error message in the Application Log: "Certificate Services did not start: Unable to initialize the database connection for (Your CA Name here). Class not registered 0x80040154." Microsoft says you can fix this by uninstalling the CA service and then re-installing it. Make sure to use the same CA name, key pair, and database that you did before.
An upgrade "feature" that you should be aware of: During an upgrade to Windows 2000, Microsoft officials say that the default security settings you would get if you did a clean install will be applied automatically. This means that if you had tighter security prior to the upgrade, those settings are gone. If you want them back, Microsoft says you need to reapply any custom security settings.
You should delay using EFS (Encrypting File System) on a computer that you have upgraded from Windows 95/98 to Windows 2000 until you are sure that the computer has actually joined the new Windows 2000 domain. If you don't, you may have problems with your EFS recovery and migrating private cryptographic keys.
Microsoft officials say that if you want to use Microsoft Office 95 on a Windows 2000 computer, you need to have the Office 95 Year 2000 update installed, which is at officeupdate.microsoft.com/downloaddetails/o95y2k. htm. Make sure that you have installed the latest patches for all the Office applications.
If you have Microsoft Outlook 2000 installed on your Windows 95/98 computer, and then you upgrade to Windows 2000, you will have to reinstall Outlook 2000 after the upgrade. Microsoft officials say you will be warned during the upgrade process. If Outlook 2000 is in your Startup folder, it will happen automatically. They also say that the Outlook reinstallation is very slow, and the progress bar will reset a number of times. Do not cancel the installation, even if it appears the computer is locked up.
If you have a Windows 95 computer with the Microsoft Proxy client, with Winsock 1.1 and you upgrade to Windows 2000, the Proxy Client will be uninstalled. You will see a message to that effect during the upgrade. Reinstall the Proxy Client after the upgrade.
Microsoft officials say that if you are running Windows 2000 on a multi-homed computer, and if you have two or more interfaces with an APIPA (Automatic Private Internet Protocol Addressing) address, you may end up with inconsistent routing behavior for your computer. Microsoft will have more information in its online Knowledge Base.
If you install Windows Media Services as part of an upgrade to Windows 2000, you may cause some problems if you are trying to use Netscape Navigator 3.04. That browser may not be able to get the URL of the web page that contains an embedded client, which causes a problem in logging the client information-the URL value of the cs(Referrer) field. Microsoft doesn't mention a fix, but they specifically cite this older version of Navigator, so an upgrade of Navigator may be in order.
If you upgrade to Windows 2000 and add the optional Windows Media Services components, you may run into an incompatibility if you also have Microsoft Site Server 3.0 with the Site Server Membership Authentication plug-in. According to Microsoft, there is a boot race problem, which means the plug-in won't load, and clients won't be able to connect to the Windows Media Services. This error won't show up in the Windows 2000 Server Event Log service. But if you use the Windows Media Administrator to connect to Media Services, you will get an error message saying you must restart the Windows Media Unicast service. Microsoft officials say to follow that advice as a workaround.
If you have installed Windows Media Services as part of a Windows 2000 upgrade, and you then enable HTTP streaming in the Windows Media Administrator, Microsoft officials say you need to restart your computer. If you don't, the Windows Media Services Event Log fills up with errors.
According to Microsoft, if you upgrade to the release version of Windows 2000 from a previous (presumably beta) version of Windows 2000, and you have a disk that is part of a fault-tolerant set, it may become orphaned during the GUI setup. However, they say you will not lose any data, and you can rebuild the disk with the Disk Administrator snap-in. If it is a mirror disk, use the Resynchronize Mirror command. If it is a RAID 5 disk, use Regenerate Parity.
Here is a situation to avoid, according to Microsoft. When upgrading from Windows NT 4.0 to Windows 2000, you may not want to create logical drives within extended partitions on basic disks. A drive geometry translation error in the Logical Disk Manager may trigger this error message: "Parameter is incorrect." There is no workaround.
Microsoft points out a problem with the Windows 2000 Backup procedure that is caused by Microsoft Office. Sometimes, applications won't restore because of long file names. The Office components use short 8.3 names when registering component locations in the Registry. After a restore, some of these may point to the wrong place, because short file name generation is based on the order in which the applications are installed. The fix is to reinstall any applications that fail.
If you do a Windows 2000 System State Restore, which is part of Windows 2000 Backup, your network identification may say that your computer is already part of the domain. This is wrong. Microsoft says you must rejoin the domain, otherwise you may see this error message: "Trust relation failure." The workaround is to: 1) Join a workgroup; 2) Restart the computer; 3) Rejoin the domain; 4) Restart the computer again.
If you are going to do a scheduled backup with Windows 2000 Backup, and the wrong kind of media is mounted in the backup drive, the backup operation will not start. There will be no outward notice of the failure, since a scheduled backup runs without a user interface. However, if you look in the backup log, there will be a notice of the failure.
According to Microsoft, it is only a display issue, but in Windows 2000 Backup the elapsed and estimated times will not be correct. For now, Microsoft says to ignore the display.
If you are going to do a Windows 2000 Backup to an Exabyte EXB-220 Changer with 8-mm tape, Microsoft says you need to upgrade your firmware for the changer to 6.4.3. Otherwise, you may see this error message: "write file mark."
The Windows 2000 Backup applet may not be for you, if you have huge data volumes (more than 100 GB) that have file counts in the millions. According to Microsoft officials, you may not be able to restore files at the end of a large backup set. They have two suggested workarounds. Either use third-party backup software without the limitations, or break up your backup procedures into smaller segments.
In Windows 2000, you may get an access error in NTBACKUP.EXE if you have a path name greater than 1000 characters in length. The workaround use shorter path names.
When you upgrade to Windows 2000 from Windows 95/98, you may be told by Windows 2000 that these network adapters will not be supported: 3Com EtherLink III EISA 10/100 (3C597-TX); IBM Etherjet ISA Adapters; Crystal LAN CS8920 ISA Adapter; Olicom Plug and Play Token-Ring ISA 16/4 (OC-3118) Adapters. After installation, you may be pleasantly surprised to find that they work anyway. Microsoft says you might have to reset any static network settings.
Microsoft says that the following adapters will not support Media Sense in Windows 2000: Hewlett Packard HP 27247A PC LAN/16 ISA Adapters; Hewlett Packard HP 27250 PC LAN/8 ISA Adapters; Hewlett Packard HP 27247B PC LAN/16 TP Plus ISA Adapters; Hewlett Packard HP DeskDirect J2973A 10baseT PCI LAN Adapters; Intel Pro/10+ PCI Adapters; SMC EtherEZ 8416; SMC EtherCard Elite 16 Ultra (8216). Because of this, you may be affected by the following errors: display of the wrong connection speed; inability to updated speed after enabling; wrong status of cable connection. There is no workaround.
When you upgrade to Windows 2000 from Windows NT 4.0, you may be told by Windows 2000 that these network adapters will not be supported: 3Com EtherLink 905x 10/100 series of Adapters; Compaq Ethernet or Fast Ethernet PCI Adapters; DEC FDDI Controller PCI (Defpa) Adapters; HP EN1207D-TX PCI 10/100 Fast Ethernet Adapters; Intel EtherExpress PRO/10 Adapters; Intel Pro/100 Intelligent Server Adapters (I960). Yet after installation, you may find that they work anyway. Microsoft officials say you might have to reset any static network settings.
If you are using multiple 3Com 3c509 TPC ISA adapters in EISA mode on a Windows 2000 computer, once you disconnect them using Network and Dialup Connections, you will not be able to reconnect them to the network without rebooting your computer. These adapters also sometimes have problems with Windows 2000 Plug and Play.
If you have a 3Com Fast EtherLink ISA 100BaseTX adapter (3C515-TX) on a Windows 2000 computer, and you disable or enable the adapter through Device Manager, your computer may lock up. There is no fix yet.
On a Windows 2000 computer with a wimpy power supply, an Adaptec ANA62044 64-bit 4-port PCI Fast Ethernet adapter may not be able to automatically negotiate network connection on two of the ports. The only "fix" is to upgrade to a computer with a greater power supply.
Windows 2000 is incompatible with multiple Madge ISA TR adapters. According to Microsoft officials, this will trigger system instability, especially with network connections.
If you have SMC 8216 Ultra, 8216 Ultra Tiger, or 8416 EtherEZ cards installed on a dual processor, ACPI-compliant Windows 2000 computer, you should not have adapter resource settings of IRQ 10, I/O address 300, and RAM address CC00. This will cause a boot failure. You will have to choose adapter resources that don't conflict with other system resources, say Microsoft officials.
Windows 2000 TAPI is incompatible with any ATI video cards that have TV tuners. This would include the ATI-TV, the ATI-TV WONDER, and the ATI All-in-Wonder cards, according to Microsoft officials. They hope to add support later.
The shipping version of Windows 2000 will not have drivers for Kodak USB cameras. However, Microsoft officials say you will be able to get drivers for these cameras from Kodak at http://www.kodak.com.
If you are going to run Windows 2000 on an IBM ThinkPad 760EL, 760XD, or 765D laptop, you probably don't want to use an IBM Ethernet Credit Card adapter. According to Microsoft officials, this adapter will not receive a DHCP address, which means it won't have network connectivity. There is no fix at this time.
If you use a Macronix MX98713 on an ACPI compliant Windows 2000 computer, the adapter may cause the computer to hang. Microsoft officials say you need to check with Macronix for an update for this adapter.
You will have problems updating to Windows 2000 if you have an NE2000 or compatible network adapter in your computer, and it has an input/output (I/O) address at 340h (0x340). According to Microsoft officials, your computer may lock up during installation when you get to text mode. As a workaround, you can remove the card or change its I/O setting. After Windows 2000 is installed, the card will work correctly, even at that address.
If you install Windows 2000 on an ACPI-compliant computer, and it has a Xircom CE3 PCMCIA or Compaq Netflex 3 PCI Adapter, you will not be able to resume computing from hibernation or standby modes. To avoid the issue, Microsoft officials say to disable Power Management if you are using these adapters.
Do not install or upgrade to Windows 2000 on a computer that has an AVM ISDN adapter. Microsoft officials say to uninstall and remove the adapter, then install Windows 2000. After installation, you can reinstall the adapter and configure it.
According to Microsoft officials, Digi International Datafire RAS PCI onboard DSP-based modems are not supported in Windows 2000. However, they say that Digi will be updating their driver package, which will then provide support.
On a Windows 2000 computer, if you have a Digi International 8-port PCI card installed, and you have an 8-port concentrator connected to the card, you will not be able to install or support modems, according to Microsoft officials. There is no fix.
If you have a Digi International Multiport Serial card, and you go to Windows 2000 Device Manager and change its properties, the Properties window will remain silently active for about twenty seconds, say Microsoft officials. During this time, you will not be able to close the Device Manager window. The workaround have patience.
Microsoft officials say that some PC card network adapters may not be able to handle heavy network traffic on a Windows 2000 network, and may either lose their connection or hang. These cards include: 3Com Megahertz 10/100 (3C575); Xircom CreditCard Ethernet IIps (PS-CE2-10); Earlier versions of the Xircom CE2, although later versions are OK.
If you are running Windows 2000 on a Compaq Presario laptop computer that has a Lucent Technologies modem, you may have some problems. According to Microsoft officials, the modem will be detected, and Windows 2000 will install the correct drivers, yet the modem won't work. They say this will be fixed by Compaq, who will have an updated BIOS.
Windows 2000 may not be a good idea on a computer with a display adapter using the Voodoo2 chipset. According to Microsoft officials, it will only work as a secondary display adapter on a multi-monitor system. Voodoo3 Pass Thru and Scan Line Interleave are not supported. According to Microsoft officials, this will leave you with sub-par performance. You may want to check in with 3dfx to see if they have new or updated drivers at http://www-dev.3dfx.com/.
If you are running Windows 2000 on a computer with an ATI Mach 64 display adapter, with the drivers that come with Windows 2000, Microsoft officials say your computer may lock up when you start the game Return to Krondor. There is no fix yet.
If you are running Windows 2000 on a computer with an Intel i740 display chipset, you may not want to disable PCI bus-mastering. If you do, Microsoft officials say your display adapter may hang. There may also be incompatibilities between drivers for this chipset included with Windows 2000, and the VIA system chipset.
According to Microsoft officials, a bug in the streaming video decompressor may cause problems with display adapters that use the nVidia Riva 128 Chipset. The bug may cause some streaming video to play upside-down. They don't give a workaround, but standing on your head may work.
There is an incompatibility between Windows 2000 and Adaptec CD Creator 3.5b. Microsoft officials say you should upgrade to CD Creator 4.0.
In Windows 2000, if you are looking at a folder in Large Icon view, the icons for Adobe Illustrator 8.0.1 files may show up as black squares. The only workaround is to pick some other folder view.
If you upgrade from Windows 95/98 to Windows 2000, you will lose the File, Adjust Color Printing function in Adobe PhotoDeluxe. Microsoft has not yet found a workaround to bring this function back.
If you are going to do a clean install of Windows 2000, or when you upgrade on a Windows NT 4.0 computer, the installation process will not be able to automatically find any ISA-based display adapters. Once you manually install the correct driver, the adapter should work.
If you try to install Broderbund Software Calendar Creator 5.0 on Windows 2000, you are going to get an error message saying that the Setup routine can't find Windows NT 4.0 SP3, which it needs. Since you probably don't want to move back to that OS, you better wait for an upgrade to Calendar Creator.
Microsoft officials say not to use Command Software Systems Command AntiVirus 4.54 on a Windows 2000 computer. If you do, things will get so messed up that you will have to reinstall Windows 2000. Microsoft officials say an update will be coming from Command Software at http://www.commandcom.com/.
If you upgrade to Windows 2000 on a computer that has Eudora Pro 4.2 on it, Microsoft Outlook Express will elbow Eudora aside and register itself as your default e-mail program. When you start Eudora Pro, you will see the prompt asking if you want Eudora as your default. If you say yes, you will then see this error message: "Eudora was unable to update the system registry. Your default mail program has not been changed." Microsoft says you can go to the Control Panel, Internet Options, Programs tab, and select Eudora Pro as the default.
Microsoft says that Asymetrix ToolBook 1.5 and 1.53 DayBook Month View will not run on Windows 2000. They say to check with Asymetrix for any updates.
If you upgrade from Windows 95/98 to Windows 2000, and you had HotSync Network installed to synchronize with your Palm device over a network, you will have some initial problems. The network synchronization won't work until you first do a local synchronization between your Palm and the host computer, using the cradle attached to the local PC.
When you upgrade from Windows 95/98 to Windows 2000, and your computer had Hummingbird Exceed 6.1 installed, your Exceed XConfiguration file may be lost. This will cause the error message: "INETD Error: Error creating configuration file." Microsoft says to reinstall Exceed 6.1 on to Windows 2000.
Windows 2000, there are some incompatibilities between IBM ViaVoice 98 Executive 5.2 and IBM Simply Speaking Gold 3.5, and some video cards. Because of this, Microsoft officials say that sometimes the Actor will only show up as a black square when you select Begin reading. There is no workaround at this time.
According to Microsoft officials, you will not be able to install Intergraph DiskShare 3.2 on Windows 2000. If you try, you will get this error message: "This Setup process has determined that you are running on the Microsoft Windows NT 5.0 operating system. This version of DiskShare does not support this operating system. Please verify that you are installing the correct version of DiskShare." For now, there is no workaround.
According to Microsoft officials, a number of programs that use the InstallShield 3 Setup Engine will have a problem when trying to install multiple listings under the Start, Programs menu. It may cause you to see a message such as: "Variable is not large enough for string. Check string declarations. Error 401." It may also cause the shortcut to stay on the Start menu even after uninstalling. Some of the software in question: Raxco Software PerfectDisk; Panda AntiVirus; Norton Crashguard; Executive Software International Diskeeper; Iomega Windows NT tools for JAZZ drive; Berkeley Systems After Dark 3.2; Apple Computer, Inc. QuickTime 3.0 and QuickTime 3.0.2; Interbase Client & Server; Master Clips Publisher; Autodesk AutoCAD 14.
According to Microsoft officials, Symantec Norton Utilities 2.0 for Windows NT will not be able to handle FAT32 drives on Windows 2000. If you try to use Disk Doctor or Speed Disk on FAT32, you will see this error message: "Partition has an unrecognized error on it, would you like to fix the problem?" If you say Yes, you may lose data. Check with Symantec for compatibility information regarding their utilities and Windows 2000.
If you are going to install the Novell GroupWise 5.x client on a Windows 2000 computer, Microsoft officials say you first have to install WMS. This will install MAPI components that GroupWise needs. You can do this from the Windows 2000 CD, in the Valueadd\#092Legacy folder.
Special Windows 2000 Bug Report by Bugnet's Bruce Brown and Bruce Kratofil, who are co-authors, with InfoWorld's Brian Livingston, of Windows 2000 Secrets, published by IDG Books.
-------------------
The only reason a car manufactorer would get sued would be because they would have injured or killed a person through their own negligence. I know Windows is bad, but it isn't that bad.
;-)
Really?   Ask the Navy about that possibility!  
Check this.   Here's the text:
"Solaris and Linux Vulnerable To Hack -- An Amendment By Staff February 11, 2000 As many readers have pointed out, the February 11, 2000 article titled, "Solaris and Linux Vulnerable To Hack," posted on our site (www.computercurrents.com) was in error. Although we are responsible for any editorial that appears on our site (and yes, we should have scrutinized this item before we posted it), keep in mind that this was in fact a "feed" from the Newsbytes service, much like an AP or Reuters feed. And as such, we don't typically have control over the content. We naturally contacted Newsbytes about the error, and they pulled the article from their site, as did we. Computer Currents sincerely regrets the error. Based on our own research, we can note that Network Associate's MyCIO.com service (which was created in response to the recent flurry of Denial of Service attacks against Yahoo, eBay, and other major Web sites) can scan Unix-based systems for three DoS agents: TFN, Trinoo, and Stacheldraht. Since these agents do not currently run on any version of Microsoft Windows, there is no need to scan Windows servers with this service. We'd also like to address a few points raised by readers. Computer Currents is in no way associated with Microsoft. In fact, the Computer Currents Web server is run on Linux/Apache/PHP. And Computer Currents is dedicated to accurately reporting on all products, services, and events-- including those related to Linux, Sun, FreeBSD or other *nix products. But yes, we screwed up in not properly screening this feed. Thanks for bringing it to our attention, as painful as that was! Sincerely, Robert Luhn Editor-in-Chief Garth Gillespie Webmaster Computer Currents Magazine www.computercurrents.com"