ajm786

Can you please tell me how to turn off Windows File Protection in WinXP Pro? Thanks.

Ok. I know this is not a hardware question, but the Network section of this forum seems to be a little dormant. Here is the problem I am having. Let's say there are two computers, Computer A and Computer, both loaded with Win2k. A network is set up on both of these computers, and both are included in a Windows workgroup. Let's say now I am on Computer A. I try to access Computer B from Network Places, and when I try to, a small dialog pops up that states: Enter Network Password Connect as: Password: Now I know you can do this on Win2k. How do I enable this option on my home network, which has WinXP? Everytime I access another computer on the network, the connection goes right through without asking me for a password, etc. Thanks.

Yes. I sort of get what you are saying. But that is still confusing. For example, at my work, two computers are both set up for administrator accounts, with a different password for each. The password dialogue comes up. If I set up two different computers in WinXP with different accounts/passwords, the dialogue does not come up. Thanks.

So by changing that option, will I get the dialogue that asks for a passwords when I am trying to access my computer from another terminal?

Ok guys. Got a problem, and would appreciate some help. It's not usual that I get any problems at all, but I'm stymied by this one.... I just bought a USB 2.0 PCI controller with an NEC chip on it. If I install it on Windows XP, it detects and installs fine, but there is a small entry in the device manger that says "Unknown device...". I'm not sure if the card works fine or not with USB 2.0 because I don't have any USB 2.0 devices. ;( The card works fine with USB 1.1 devices. Another issue is that after installing, Windows XP lost the ability to hibernate. Any suggestions? Thanks.

Ok guys. I have been thinking about upgrading my system. My current rig has become too slow, well, sort of. I wanna get a P4 1.6 Northwood and probably a better video card. You could take a look at my system specs below. Before we delve into anything, let me ask: Is it possible to get a P4 1.6 Northwood and overclock it to 133FSB using my current mainboard? Or what is the max overclock I can do to that processor using my current board? Otherwise, I would appreciate any suggestion of a motherboard that can overclock the 1.6 Northwood to 2.3 or higher. Also, please advise on the best type of DDR. Thanks.

Do you mean by BIOS overclocking (Jumperless) or jumper overclocking?

Quote: Just the double amount of 2nd level cache (512k on Northwood, 256k on your current CPU) will make a nice difference. Then of course the Northwood's can alo be nicely overclocked. I'm not an overclocker myself, so personally I'm waiting for the Northwood B CPU's and will initially hopefully be running it in my ASUS P4T-E (I know my Samsung RDRAM will happily run on a 133Mhz FSB). Might be worth waiting a little while, once the Northwood B's are available en mass the Northwood A's will drop nicely in price. ??!???!???!?!?!!! So are you saying that I would be able to overclock to 133FSB using my Asus P4T-E?

Of course. Thanks. I appreciate it.

But yeah. If I can overclock the 1.6A to, like, 2.xxx, of course I would see a good performance increase, not night and day though.

Yep. Been there, done that. But hey. Don't sweat it. I just think that if it is gonna cause me all this hassle, I'll forget it. Thanks Clutch and Sampson.

Whoa, hold on a sec. I didn't know that these things have BIOSs on them. It sure don't look like to me. There is only the big fat NEC chip in the center. Second, the drivers were just regular NEC drivers, because the card is a "generic", if you wanna put it that way. Where could I find drivers for USB 2.0, by the way? Thanks.

Meaning???

No sweat man, but, just to get WinXP working right, I almost re-installed every day!!!!!!!

Here is the simple solution. This worked for me. I had WinXP and was getting BSODs all over the place. Any driver/software that you have that is not updated or made for WinXP, GET RID OF IT. In my case, it was my virus scan and my firewall, both of which happened to be Norton Antivirus and Blackice Firewall. As soon as I switched over to a free virus scan made for XP and Zonelabs Zonealarm firewall, all the problems disappeared. It has nothing to with IRQs or anything like that, unless you have a defective hardware...

Question. I have two hard drives on my primary channel, a Western Digital 40GB as the master and an IBM 41GB as the slave. I have Win98SE on the WD HDD, partitioned as a FAT32. I have WinXP on the IBM HDD, partitioned as NTFS. So in effect, Win98 is on the master HDD, and WinXP is on the slave HDD. I get frequent, and I mean frequent, BSODs on WinXP. IRQL_LESS_THAN_OR_EQUAL errors and page faults, everything. Do you think this could be attributed to the fact the WinXP is on the slave HDD? And by the way, everything, EVERYTHING in my system is WinXP compatible. See for yourself. Here are my system specs: Asus P4T-E w/BIOS Rev. 1003 P4 1.5Ghz 512MB PC800 ECC Samsung RDRAM Western Digital 40GB 7200RPM ATA100 HDD IBM 40GB 7200RPM ATA100 HDD Pioneer 16X DVD-115 Mitsumi CR-48X8TE 16x8x40 CDRW PNY Geforce 3 Ti200 Realtek LAN Ethernet card Adaptec 2940AU SCSI adapter Soundblaster Audigy Platinum Hauppauge WinTV TV tuner Thanks in advance for any help.

Quote: Now things are getting clearer.If you used win2k drivers for your SCSI card or for any other hardware you might be experiencing incompatibility problems that result the BSOD.Win2k and WinXP are built on the same NT kernel but they are quite different.I've seen a lot of hardware that don't work properly on winXP with the drivers of win2k.Download all the XP drivers for your hardware, by going to the manufacturer.You wouldn't have any problem finding it, since your hardware is new and the manuf. are big names. And i do mean every driver, including your sound blaster ones.I am not saying that the SCSI fails for a 100%, it might be some other device.That's why you should try upgrading to XP drivers first to eliminate the chances of incompatibility. GL I think you misunderstood me a bit. I am NOT using Win2k drivers in WinXP. Personally, I would think that would be absurd. WinXP has default drivers for the Adaptec 2940AU SCSI drivers. I don't have to install any other drivers. The only drivers I install for my devices are the WinTV card and the Audigy sound card; everything else is picked up automatically during WinXP setup. Thanks for your help.

I don't understand how it could in fact be the SCSI card, because if it was I would get the same error in Win2k. The two OSs are alike so much. I've tried basically everything. If you look at my hardware specs, do you think you could give me any suggestion to which other hardware could be causing the problem other than the SCSI card? THNX.