ragefire

Ok here's the deal. I *had* Win2k Pro on one machine, connecting to a machine running Win2k Server RC3 and its own domain. Could log into domain server just fine from pro. Then my Pro installation got messed up, and I had to reformat the harddrive. At the same time I upped the Server to final build. Now it seems no matter what I do to connect to my domain I get the following message: The following error occurred attempting to join the domain "newworld": The network path was not found. Now, I can't for the life of me understand that message. The IP on the Pro machine is static for connection sharing, and the server is doing DHCP. They both completely see each other in network neighborhood and all that stuff. If anyone has any clues about this problem, please help me out! Thanks!

Ok, this may have been just my installation being corrupted, but here's the problem I ran into. I was running packaged BIOS for Abit BP6 and Win2k just fine - no snags, except on shutdown I'd have to hold in the power button since ACPI wasn't enabled. So, being lazy, I decided I didn't like having to press the power button and flashed up. Because I thought it'd be a good idea to freshen up, I reinstalled Win2k. During setup, it claimed to not be able to tell my system type!! So I flashed back down to NV, and installed win2k, then USB wouldn't work!! And yes, it had worked previously because I was watching TV on a WinTV USB just a few days ago (like I said, I'm lazy). Everyone else seems to have had a peachy time with QQ, am I the only one? I will be formatting my HDD within 2 days so if anyone thinks that may fix it, please let me know! Thanks! One last thing - I'm doing dual cel 500's... anyone have any luck overclocking them? I'd try it but I don't have the money to replace any fried components! :-)

My only suggestion to you guys having a problem with windows letting go of files is this - if you still have a 98 machine around, specifically a 98 boot disk, boot with that. Since you know the exact filenames you should have no problems deleting them from a dos box. hope this helps.

This is slightly off-topic but I thought I should put my info in. I was getting the same blue screen as you folks - about a bad DATE_STAMP or something. So I played around some more. My advice - be VERY careful with what you're playing around with. When all was done, I would boot to NTOSKRNL.EXE stop screen - no safe mode or anything. And no, I didn't have the hacked lw3 drivers, i'm running dual processor system. Just a quick word of advice, as I'm going to be reformatting 18 GB in a day (I'm in win98 now and HATING every minute of it ;-) )