clutch

NetBEUI is faster than than TCP/IP and IPX/SPX in MS OSes. It always has been. It is much smaller and simpler, and takes a VERY low amount of overhead to operate on a small LAN (which was its intent). As far as whether or not NetBIOS is "secure" over TCP/IP, and if NetBEUI is secure at all, that's completely pointless. NetBEUI is not routable, so the traffic can't go anywhere other than your small network. And as for NetBIOS over TCP/IP (or IPX/SPX for that matter), it was merely for built-in name resolution/broadcasting on a network. It was never meant to be used on large networks where you would have a true name resolution service anyway. When you remove it from your bindings, the only change you will see is that you can't use "Network Neighborhood" (UNC Paths) without a WINS box. Almost anything that was developed to ride on TCP/IP used clear text initially, so I would think that is a much bigger hole than unwilling name resolution would ever be. Not to mention you can perform reverse DNS lookups on a target IP, and know what network it is a member of anyway. If NetBEUI is removed from WinXP, I could live a long life knowing that. TCP/IP is the protocol of choice now. MS figured it out a while ago, and so has Novell. That's why you don't see Novell wasting its time with that lame NIC-killer protocol anymore. One more thing, for those who do move large files (ISOs in particular; you know, for "archiving" ) you can use "ESEFILE" from the Exchange 5.5/2000 CDs. This is pretty useful for copying large files, and could shave a good amount of time off of your copying. It was only a modest improvement for me in one case: I copied a 404MB ISO of Win2k Server in 76secs using this from my Win2K AS box to my Win2K Pro box using TCP/IP, Intel Pro/100 Mgmt adapters, and a Linksys router with built-in 10/100 switch. Use Explorer, it took 81 secs. However, there was a noticable reduction in drive chatter from my server using ESEFILE. http://support.microsoft.com/support/kb/articles/Q248/4/06.ASP

The only way I know is to rename/delete the desktop.ini file in the "My Pictures" directory. Clears it up quickly for me.

I don't know if many of you know this, but BMW of North America is making short movies featuring their cars. I saw one commercial briefly about it, and I thought I would check it out. The movie pretty much kicks a$$, and is worth watching. Then again, I am a typical male who likes movies with car chases, explosions, and hot women. However, even only catering to 2 of the 3 seems to work well for the clip "Ambush". Check it: www.bmwfilms.com

What format were you using? I have used all 3 and haven't had any issues. I haven't used the "BMW Enhanced Player" though.

I believe that there are new features/settings in the service packs that simply copying over the files in that manner wont initialize. In addition, I don't think that the setup would be updated either, therefore I don't think any HAL related enhancements would be brought to light. So, the best bet would be to install NT, and then install the service pack.

Why 3DFX, and where's Matrox?

I am not entirely sure if XP will be only geared for newbies or not. I did use "classic" mode, and it was much nicer. The reason why I don't intend on going to it is that it doesn't offer anything that I can use. Stability isn't an issue for me, and neither is compatiblity. If it was much faster, then I might consider it. 2462 wasn't that great, and I am sure that it will change a lot by the time it is released. However, I don't get the feeling that it is going to be any better for my needs than Windows 2000.

The last thing that I read was MS will probably bundle AOL 6.0 with WinXP. Not that I am entirely concerned, as I don't plan on using XP anyway. I think I will just wait for Blackcomb to come out before I switch to another MS OS.

Access is very easy to work with. The best thing to do would be get a book on it or take a couple of classes. However, if you are within a tight timeframe to get this developed, then this may not be the avenue to use.

You can put in the Win2K Pro Upgrade CD, delete the partition and reformat it, then install Win2K Pro without having an OS currently installed. The only extra thing that will happen versus a full retail CD is that you will be prompted to insert a "qualifying product" CD (Win95/98/ME/NT) before it will complete the install.

As far as compatibility with hardware goes, NT "hides" a lot of its issues from you. You see, a great deal of hardware during NT's reign didn't even COME with drivers for NT. That's why you wouldn't see very many problems with NT being able to work with peripherals and add-on cards, because everybody using NT knew it wouldn't anyway. Case in point, a buddy of mine had wireless internet access through a company called "Gain" in Tucson, AZ. He had NT Server setup along with a Win98 Workstation. Now, normally you would want to put the card in the NT box and run some sort of proxy for the other workstation right? Well, he couldn't, because the company that made the card REFUSED to make drivers for NT claiming that it wasn't a consumer OS. Now, they did go on to say that they would make drivers for Win2K (due to the similar driver model base) and as far as I know, they did. As you can see, NT clearly had a compatibility issue, yet it didn't. While it didn't work with the card, it was because nobody wanted to write a driver for it. Most of the problems that you see here, are people having problems with hardware and software functionality/performance because they know that it is SUPPOSED to work with Win2K, but they are having their own problems. I think that some people are confusing compatibility problems with a lack of functionality altogether. I know that at work and home, I have digital cameras that I use. I had to use the crappy software that comes with the camera in order to get the pictures on the PC since that's the ONLY way I could get the pics using NT. Once Win2K was out, I just got a SanDisk reader and "developing" the pics is way faster and much, much easier now. Plus, at times the other software would crash the NT box. I don't have that issue anymore since using Win2K. Researching what the best OS is for you is a great idea, jut make sure that you see the difference between performance issues and a complete lack of compatability. Oh, and BTW, if you are looking for future driver support, count on it going to the XP line since it will be using the same driver model as Win2K and takes less development time.

Win2K has FAR MORE integrated support for enterprise management, especially with respect to using AD. In addition, I have found it to be faster than NT4 on systems that are PII 400 and higher. As a matter of fact, I am running Win2K Server on a Celeron 333 with 128MB RAM and it's doing fine. I am using it as a file server, IIS box, AD controller, Terminal Server, and secondary DNS server. It performs all of these functions very well, and it a good deal quicker than NT4 Server was with half of the functionality. In addition, the Win2K install "feels" faster over the duration of its uptime than NT4 does on the same machine. Another benefit of Win2K over NT4 is better driver functionality for all of our hardware. This is especially noticable in faster machines that use UDMA 33/66 interfaces, as NT never really supported them. Win2K also makes better use of RAM over 256MB than NT4 does (and even at 256MB, I have seen a Win2K install run faster than an equivalent NT install). Also, you don't have to reinstall the SP over and over again after you make any changes since Win2K will protect the files in question, and reload them if needed. Those are what I can come up with at the moment. I manage a domain that was NT4 only until last year when we started bringing in PCs with Win2K on them. I am now bringing in servers with Win2K because I like the increased remote management ability of the systems. As for laptops, the last 4 that we brought in have been Win2K because of its stronger ACPI support along with better peripheral compatibility. I have been a big fan of NT, but with more modern software and hardware coming out, Win2K has been the only choice for myself and my company to take advantage of it. We haven't had any issues using Win2K, and I don't expect to in the future either.

I use CAD (Solidworks 2000/2001 w/ Edrawings) software and I game as well. Plus, I do a bunch of other things with my systems, and Win2K works very well for all of the above.

You can't "slipstream" the NT 4 CD Image, and IIS 5.0 only works on/comes with Win2K.

I ran Exchange 5.5 SP3 on NT Server 4.0 SP6a for quite a while with no issues.

Sounds like you are using Novell 5, as this issue seems to carry down all throughout the MS line of OSes using the MS version of the Novell client. I would *imagine* that it would install, but from what I remember about the client32s, they are VERY picky about almost everything that is installed on the local PC. If you have the time for a possible repair, then try installing the client. Otherwise, I would just try to limp along without the client at all until more "official" word comes out from Novell.

I think that's his problem, his second system has the burner, not the one that he wants to image.

I have noticed significant performace increases with respect to load times of applicatations and large files (like 3D models in CAD/CAM apps) when I set the min/max to be the same (usually 1-1.5X the amount of RAM up to 256MB MAX) and moving the swap file off of the system partition. However, moving the swap file off of the system partition only to go to a slower drive may actually hurt performance in the end. Just something to think about.

www.swynk.com http://www.microsoft.com/technet/exchange/default.asp http://www.exchangefaq.org/ http://www.swinc.com/resource/exchange.htm These should start you off...

What facet are you looking to monitor? The logs? Uptime of the server? Uptime of a specific app? There are tons of things that you can monitor, but what are you looking for?

No, I don't.

Well, I am running a Maxtor 20GB ATA-100 drive on one of my servers at home (using Win2K Server) with SP2, and it works fine. The HD comes up as "Maxtor 52049H4" in the device manager, and is using the regular "disk.sys" driver. This is on an older BX-based Diamond Micronics C400 mobo.

The PXE reference is for booting off of the NIC (at least from what I remember). You may want to go into the BIOS of the NIC (you should see a prompt for it just after POST and before the OS starts-on Intel NICs it's "Ctrl+S") and see if it's set to boot off of the NIC. The mainboard itself could be set to boot off of the NIC first, then floppy/CD/HD. You can check the boot order in the main BIOS as well.

I tell the user that it should have been on his/her network folder so I could restore from backup. But they know better where I am at, so I guess the weekly public beatings have worked.

Seeing as many people have nothing better to do, more vulnerabilities have been found and this update should patch them up. http://www.microsoft.com/technet/security/bulletin/MS01-026.asp