ThePumpKinKing

The problem is NetBEUI. Remove this protocol and the hanging when opening Network Neighborhood (and when searching for PC's by name in case you haven't tried that) will go away. By default, if you have NetBEUI installed your PC will try to use it first to search by name on a network without WINS. It's a good protocol for a small Workgroup without TCPIP, but that's about it.

Black Ice already has an update. Download and install it and it will update the "blackdrv.sys" and all will be fine.....

It's because SWBell dosen't support Win2k (this they've told me). Every time I call them for anything they tell me that to support me I'll have to install Win98 and take Internet Connection Sharing off of my PC. They're a bunch of fools and don't listen to them. Just tell them you have Win98 and whack that POS from your drive. The parts will show up in the mail and you can do the rest.....

No; the profile is already there. First right click on "My Computer", then click on the "Advanced" tab. The top window will show you what the default paths are set to (ex: set temp=C:\Windows\Temp) Change this to whatever you want by clicking the "Edit" button and hitting Ok. As soon as you do that you're all set.....

Actually, all you have to do is right click on "My Computer", then click the advanced tab. Click on "enviroment Variables". You'll see the default locations for Temp etc. Click on edit and point it to the right place.......

The problem is most definitely ASPI, but not corrupt drivers. Windows 2000 does not use ASPI drivers, so if you're using them that would be what's causing this. I've spoken w/ Adaptec about this and they basically told me that if I installed a burning program that was pre-Win2k it would install ASPI drivers and hose any functioning software I had. Best thing here is to uninstall all burning software you have, then do a search for *aspi*.* and delete the hell outta them. Then reinstall your Win2K compatible software and you're good to go....

P.S. EZCD Creator 4.0 is not Win2k compatible. Get the latest update off of their site (4.02C) and install it after you install 4.0. DON'T REBOOT AFTER THE INITIAL INSTALL or you will have ASPI drivers setup in your system32 dir. Install the patch immediately after installing 4.0, then reboot....

Unfortunately I don't know the correct entry to change, but I can probably help you track it down a bit easier. The entry you are looking for is the reg entry that tells your machine that it IS NT Wkstn/Srver. The 10 connection limit is a way for Microsoft to get you to purchase Server if you want it unlocked. Wkstn and Server are the same exact OS. This reg entry does not exist in Win2K. Ok, actually it does exist, but they wised up to it. This reg entry is set to restore itself on bootup if it detects a change (other than a proper upgrade). I took a Win2K course a few months ago and asked my instructor about this, and he's tried it and failed.....

If so, what did you do? I'm fairly pissed that I spent $40 on this game and have never been able to play it........

The reason for your problems might be that Win2K does not use ASPI. If you've upgraded from NT/98 OR installed a non-Win2K compatible burning program, you have an ASPI driver installed that's causing some grief.....

Yes I realize the difference between an operating system and a file system (I didn't just spend 10 grand on an MCSE to walk out not knowing at LEAST that). The reason I mentioned Win98 is that that's how most people relate to Fat32. The MFT: The MFT ONLY retrieves info as the data is initially recorded to the hard drive and/or as it changes and is moved. BROWSING FOR the cluster isn't necessary as the MFT already knows where the cluster IS. The actual RETRIEVAL of the cluster might take longer due to the 16K size. But that's where NTFS 5.0 comes in. Yes, it is a totally different file system, and yes it is 32K clusters. Go try some lookups on keywords "NTFS" and "2000" on Microsoft's Technet website. It'll tell you all bout it. And I'm not sure that by mentioning a one and a half year old operating system that means I don't know what I'm talking about. And BTW; NTFS 5.0 CAN access FAT32 partitions, so there is no reason to do only one or the other. [This message has been edited by ThePumpKinKing (edited 03 May 2000).]

Funny you should ask. I have been playing Focomm flawlessly for about a month on Win2K. Then I reinstalled it due to a mobo upgrade, and have just been dumped back to the desktop each time I try to start it. So I emailed Lucasarts Tech support and was told this: "We are sorry for your problems with Force Commander. Unfortunately, there is nothing we can do for you. Our game was not designed to work with Windows 2000, nor is Windows 2000 a gaming operating system. I recommend going back to Windows 98, or looking to Microsoft for an answer to your problems." Pretty friggin classic, huh? I just paid $50 for a freakin game that LucasArts REFUSES to support on a particular platform. This will most definitely be the LAST LucasArts game I buy. Not to mention the fact that Lucas is an idiot for not releasing Star Wars on DVD. I've had it with him. [This message has been edited by ThePumpKinKing (edited 02 May 2000).]

Ok; what HarU says about the drive clusters is correct (as far as 16k and 32k) but as far as having to scan 2 clusters/causing a slowdown, that's incorrect. Nt uses an MFT (Master File Table) to keep track of the location/permissions on ALL directories and files on your disk, thus making scanning a cluster unnecessary. In addition, NTFS 5 uses 32 bit clusters, so that comparison is mute (since the original question was related to Win2K). And finally, the way NT handles memory management/page files and works BETTER with a fixed swap file kicks fat32's ass, since Win98 has no concept of how much of a page file it has and just keeps adding more and more crap to it. Win98 Drive performance bombs in that area..... NOW wich do we think is faster & better? [This message has been edited by ThePumpKinKing (edited 02 May 2000).] [This message has been edited by ThePumpKinKing (edited 02 May 2000).]

Bad news; I don't think there is a way to stop this IRQ Steering without reinstalling 2K. Creative is actually correct in stating that this IRQ sharing causes problems (especially if you're running a VIA KX133 and a Geforce) because I had this same problem and was told this by Epox. The reason this happens is this; your motherboard has reported that it is "ACPI Compliant", meaning Windows can pretty much do whatever it needs to with hardware/power management resources because it'll listen and comply. You need to have the motherboard shut up nad have NT stop listening. One thing you can try is to disable ACPI functions in your BIOS (under power manament), then delete the ACPI portion of your motherboard under "System Devices" in Device manager, reboot, and see if this solves it. If not, your only solution is to FDISK and reintall 2K. If you have to do this, here's what Microsoft Technet says about this: When setup starts (after files are first copied to your hard drive and you reboot) you'll see a message saying "Press F6 To Install A Third Party SCSI Or RAID Driver". When you see this, hit F7. Windows will silently (won't give you ANY messg. you did it right) stop looking for ACPI portions of the motherboard and let the BIOS do the IRQ Assignements. I hate to be the bearer of bad news, but once you get this working right, you'll be very happy: Trust me.....