Recent content by Serpent77

Routers and Switches/hubs are two entirely differnet things. A Switch or hub operate on layer 2 of a theoretical 7 layer cake that describes how a network should work. The router works on Layer 3 of that cake. To break this down a little further, a switch or hub's purpose in life is to move...

Blackice isn't better, its noisier. It gives ya more false positivesthen ZA. ZA is deffinatley the way to go. --Serp

Again, exactly what I said. It's not necessary to keep it on the %systemroot%, and most people ignore the memory.dmp file, or delete it. But if you want to send it back to MS, or go through KB's and Technet to try and resolve a problem you might need it. The system will technically work fine...

check the following KB articles: Q223188 Q249321 Hope this helps. --Serp

The only way to truly make it go away is to erase or repair/rewrite the boot sector. If your drive is less than 8G, you might be able to do a "FDISK /MBR". Generally I have to erase the boot sector to get rid of it or LILO from Linux. But if you do that, you will lose all your data...

I've never seen an instance where the NDIS VXD ever loaded, the others don't look to familiar to me tho. --Serp

Don't just delete it, it'll give you log on troubles(besides the fact that you can't just delete it without have NTFSPro or a utillity similar to such). In my experirence, there has to be a swap file there (regardless of whether or not your Swap size is set to 0), or you can't log on the next...

The "codes" in brackets are memory addresses. Win2K uses a 32 bit flat memory model, and those address are the locations in RAM, or swap drive space that the problem is believed to be coming from by the OS. I'd start by building up a clean system. Start with an HD, Mobo, Processor...

I'm sorry, I think you misunderstood my annotation, the swap MUST be in %systemroot%, and MUST be 1.5x's the size of your physical RAM as a minimum. For you 768MB would be the swap partion likely in your C: drive/partition. FYI, at that point you might as well just bump to 1024 to give...

oops, I had it backwards, min swap file is 12MB+Physical Ram, to do a dump you 1.5xPhysical Ram. Ex: if you only had 128MB, you'd need a swap on %systemroot% at least 192MB in size. --Serp

you have to have 12MB+Physical Ram on your %systemroot% partition, its all outlined in the first of the two MSKB article links I posted a little bit ago. --Serp

Tis why I said he could technically leave the swap where its at and not harm anything. I just wanted him to have a complete heads up. TTFN

Yes, you lose the abillity to do a memory dump if you have no swap file, or a swap file smaller than 12Mb+Total Physical RAM on your system partition. you have the option of doing this regardless of that fact for the same reason you have the option of completely disabling memory dumps by...

Putting the swap on a seperate partition is not going to affect performance, not noticeably anyway (though in the long term you may lose a couple seconds of your life waiting for the BIOS to do the partition table conversions on the drive) What you do hurt thou is the abillity to create a crash...

you don't have your NIC running yet lo is your loop interface, you should see two addresses listed there the second card will be named eth0 usually. I'm assuming you don't have the DHCP client installed then either, time to hit the man pages (I'm not familiar enuff with linux to rattle off...