Intlharvester

This is from Q123498: HKEY_CURRENT_USER\Control Panel\Keyboard InitialKeyboardIndicators: REG_SZ: NUMBER Default: 0 This specifies initial values for keys. 0 means that NUMLOCK is turned off after the user logs on; 2 means NUMLOCK is turned on after user logs on. This value is set during log off or shutdown to preserve the state of the NUMLOCK key at that time.

The Linksys is a great product functionality-wise. I highly recommend it. However, it's of rather cheap consumer construction. Personally, I would look into something designed for the commercial market for work use. (I once spent hours at work hunting down a defective $15 Linksys 10Mb hub that had brought the network to it's knees. Vowed at that point that the when money is at stake, buying the cheapest equipment possible is not a smart plan.) That having been said, the thing will serve ~254 DHCP clients on a single subnet, so it would probably work fine for a small single-site office with no DMZ or VPN requirements, etc.

You should format the disk and reinstall the OS. At least in the UNIX world, it's common for hack kits to modify the kernel or 'ps' so that you can't see the evil process running. It's possible to do this on Windows, so you should consider all system binaries untrusted and blow them away.

The Windows Explorer FTP client is broken because it shows GMT and not local time.

I think you need to tweak the telnet server somehow to recieve plaintext logins instead of NTLM. Try it with telnet.exe and see if it works.

Shutdown/Reboot -- shutdown.exe from the resource kit. process/ram/cpu -- pmon.exe from the support tools (somewhere on the W2K CD)

Why would you want to put the pagefile into RAM? This would seem to defeat the entire point of virtual memory.

SHS - Those ISA slots you have are not EISA slots. EISA was a pre-PCI 32-bit spec from Compaq and others that offered back-compatibilty with ISA. The cards kinda look like ISA cards, but the contacts are twice as long. And MSGuy - EISA can answer all of your questions. It was workable PnP from back in the 80s (as was MCA, btw). The only real problem is that you had to use a system config menu instead of an OS menu. While EISA never really caught on, there's still some very servicable 4x200Mhz PPro boxes out there with EISA slots. I don't think MS can afford to drop support yet.

This sounds like it could be caused by a duplicate IP address or NetBIOS name. Another possibility is that you are on different subnets, and that they're filtering port 139 for security reasons. Depending on what ports are being filtered, it's possible that you can see but not touch.

A WINS server is probably overkill for a single-segment home network. Better to just turn disable the ability to become a Master Browser on all machines except one. (Especially any 9x machines you might have, they have the nasty tendancy of thinking they won the MB elections.) Besides, WINS requires a Server install, and, minus defective 9x networking, that should win the browse elections anyway even without WINS. Also, check Q191611 and Q288801 and turn off the MS networking stuff on any Internet-only NICs due to an issue with multihomed machines and browsing.

ptree (in the resource kit) also can be used to view and kill remote processes.

Look for the DOS Client 3.0 software on a NT or Win2000 CD. You should be able to find a network driver on the 3Com disk (look for a NDIS directory). You will have to tweak the protocol.ini and system.ini files a bunch to get the card driver loaded. Type NET START to load the network drivers. The clients do have TCP/IP, but I'd recommend sticking with NetBEUI.

Kind of a silly question, but is there anyway to get W2K to recognize different font options for the command prompt? I have a few other FON and TTF files installed (some of which support the DOS codepage), but the only options seem to be "Raster Fonts" and "Lucida Console". Searching the registry hasn't really turned anything up.

OK. Thanks for the information!

Database tuning is a wizardly art and depends a lot on your application. I suspect the reason that you can't find a webpage is because the people who know are too busy making $200/hour to give their knowledge away for free. You could start with "Inside SQL Sever 7" from MS Press, which is a great book about MSSQL internals, and then start connecting the dots, but that's gambling with what is probably an important production system. (I assume if this wasn't MS-SQL, you probably wouldn't be on NT.) Or, you could figure that you have an expensive box, and expensive applicaiton, and you might as well open your wallet again and get some expensive tuning help.

I'd hate to disagree, but 'load balancing' NICs is fairly common in server environments, so there has to be a way. What it is, I don't know! - maybe it's automatic if both NICs have the same gateway address.

The original purpose of this site was a game compatiblity list (or that's why I had it bookmarked back in the bad 'ol NT4 days). Anyway, the advice is: Magic the Gathering (Microprose) Yes W2000 01/00 Install it under Win9x, and then make sure that you install the 1.25c update. Then use regedit to export the two following keys: HKEY_LOCAL_MACHINE\Software\MicroProse and HKEY_CURRENT_USER\Software\MicroProse.Boot into W2K and import the reg keys and then you should be able to play the game with no problems. You may need to use SETWIN95 on the executables (i.e. MAGIC.EXE, DECK.EXE, and DUEL.EXE).

For servers, Microsoft could learn a few lessons and steal some of the good bits from UNIX: For example: + GUI-less operations mode (remote admin tools and terminal server still enabled, but also commandline versions of ALL admin functions, particularly network config and printer admin). + Replace the fairly braindead Service Control Manager with a structured system like init where you can create service startup and shutdown dependancies and different 'runlevels'. + Give *everything* a admin-friendly COM interface so that you can access it via the scripting host. Oh, define a authorization sandbox interface for local COM controls while you are at it to prevent total virus devistation. Either that or make sure that the COM to NET conversion is complete as soon as possible (ha!). + Force OEMs to preload XP with the NTFS filesystem, even on consumer machines. + With the new disconnect session thing and an improved version of RunAs, there should be no reason for Administrator logins. Do whatever necessary to discourage normal user operations as Administrator. + (Radical, Unlikely) Dump the registry for any possible user-editable function, as well as application-specific settings. Instead store the information in XML files with a publically documented schema. This would allow applications to be more portable and also would give administrators great control over app config and security (the current system of Registry permissions is an undocumented mess). + (Even more radical and unlikely) Dump all Windows RPC in favor of SOAP/SSL running on a documented port that is not 80.

After wrestling with SCSI for the last 10 years, the only word of advice I have is to try replacing the cables before spending hours trying to debug other things.

"Show icon in taskbar when connected", yes I know. But no "Show icon in taskbar when DISconnnected"! -- That's apparently automatic.

What I want to know is how to turn off that stupid icon! (It probably depends on whether your hardware supports media sense or not.)

I would imagine that the batchfile is just START /HIGH %1, but if not, I'd be interested to here what's in there.

I wouldn't rely to heavily on anthing thats reported by the IE download box. If you really want to measure bandwidth, the best way to do it is with a stopwatch. Use a FTP program (not IE/NS) and find a really well connected, lightly loaded server, with a large file (ftpN.netscape.com, where N is 1-9 works really well.) Neither 2K or ME should have any problem keeping up with broadband throughput in the 128Kbps to 5Mbps range.

Older hubs sometimes had one port which was AUI or AUI/BNC (selectable by a switch). This was because earlier ethernet 'backbones' were usually thick-or-thinnet and the port was used as an uplink. If you are just using 10Base-T you should be able to ignore the switch and the AUI/BNC ports. It's also possible the switch turns one of the 10BT ports into an uplink.

Intel SMP machines support up to 255 IRQs - I see something similiar even though I only have 1 CPU installed on my 2-way BX machine. I've never heard a real good explaination of when the AT-style IRQ controller was replaced (back in the PPro days?) and why it was only in MP machines and not UP. ACPI also makes a difference somehow, esp on W2K. So, if anyone can shed light on the issue... Suffice it to say that it usually works fine. I've seen some pretty high load servers with 'high' IRQ NICs and there never has been a throughput problem.