cluberti

Well, honestly, you'd have to contact Ominpage about that specifically. They may have a newer driver that doesn't break IE that you can use, but if they don't, the likely answer to this question is "no".

The WinSxS folder is the side-by-side .dll cache for applications requiring access to .dll files other than what is currently on the system. The TEMP folder inside contains all of the pending operations, to be done on a reboot, like renaming, deleting, or copying in .dll files. I would suggest strongly not touching this folder - if a reboot doesn't delete the contents, you can fairly safely wipe out the pendingdeletes folder, but the pendingrenames folder hanging around is a bad thing indeed.

I beg to differ - DRIVERS for Vista SUCK, not Vista. I have none of these issues, and no one who's machine I've suggested an upgrade for do either - but that's because all of the hardware and drivers are on the HCL or are Vista logo'ed.

ophook32.dll is either from ScanSoft, as Mr Snrub stated, or it's malware. If you've got ScanSoft software on your machine, I'd recommend removing it for now. Otherwise, if you aren't running ScanSoft apps, you definitely have something that's less than savory.

what happens if you run "iexplore -extoff" from the start menu? Does it work properly then? If so, you have an add-on installed in IE that doesn't work in Vista under UAC / IE protected mode, and you should either remove it or upgrade it to something that is Vista-compatible.

Where did you get this copy of Vista? Unless you installed the Paradox crack yourself, someone is scamming you if you bought that copy. and http://www.msfn.org/board/Warning-Paradox-crack-t110904.html Tread lightly.

Technically, that's a pre-SP1 patch. You should not need this after installing SP1.

Technically, you should be able to increase it up to 8192 (8MB), but remember on 32bit versions of Windows you're borrowing from one kernel resource to increase another. By changing this, you modify how the kernel allocates all other resources, and you could also exhaust session space by increasing interactive 5MB (it's a 20MB pool by default, up to 48MB max if necessary). You should technically be OK, but definitely monitor for other wierdness after making the changes, and revert back if anything "wierd" happens afterwards. It's hard to say what would happen (kernel memory ranges are allocated dynamically, within certain limits, at boot time - so it's impossible to be 100% accurate as to what will happen with an increased session space). The real issue here is platform - if you're exhausting 4MB of desktop heap space, you need to seriously consider x64 rather than hacking away at x86. By default, x64 versions of Windows have 20MB of desktop heap.

Not entirely accurate. That those numbers are possible is entirely accurate, but those are not the usual defaults. The reason for this is that unless you use /3GB, there's 2GB of VA available to the kernel, and approximately 12.5% of that will be dedicated to npp. If on boot you have drivers or applications that memory map that use RAM, or require larger Paged Pool or PTE pool, or an increased session space, then yes, that is the "low water mark" max you will see. However, by default, the kernel will try (and almost always succeed) in mapping all of npp into RAM at 256MB (or 128MB with /3GB) - remember, kernel memory is allocated dynamically on boot unless certain registry modifications and/or boot.ini options are in place. It's been literally YEARS since I've seen a box boot with less than 256MB of npp when 1GB of RAM or more was installed. At 512MB, this is more of an issue, but at 1GB (even 768MB is usually safe) or more, 256MB is the standard. Again, hardware drivers, startup services, and kernel-mode filter drivers can affect this dynamic allocation, but in general your machine with more than 1GB of RAM will see 256MB of npp. The OP has 2GB of RAM, so I am SURE that server has 256MB of npp as well . And to MCrocker, at this point I strongly suggest using poolmon to try and track this down.

Also, if you were to run Process Monitor on the machine, you could see what process was accessing the drive, what files/folders, etc.

You need to enable the File Services role, and you will find it's a subfeature of this role.

Let's keep it civilized. Edit: Now that I've thought about it, this is NOT the first OS to be released at SP1 on release - XP and 2003 x64 versions were SP1 as they were built off of the 2003 SP1 codebase, and stated SP1 as such after install when you looked at properties or winver.

Not really - NonPaged Pool is 256MB on systems without /3GB, and 128MB on systems with. No fluctuations - it's PAGED pool that fluctuates based on RAM . If you start getting up around 170MB or more, either you have a REALLY busy file server, or you've got a problem.

lol

Bingo - this is why we always tell people that unless you're doing the cleanup as a learning exercise, it's always best to backup your data and start over once you get infected... ...and if this IS a learning exercise, be sure to do a reinstall after you fix it anyway, as you can never really truly be sure the box is clean ever again.

Have you tried disabling IPv6 on Vsta?

Pricing should be the same, retail-wise. Perhaps a few dollars different (due to hyper-v), but pretty much the same. Just because administering it the same doesn't mean it's not worth the upgrade. SMB 2.0, better clustering, a better IP stack, more secure code, a better firewall, and for x64 machines hyper-v hardware partition virtualization are all just the beginning. How about DFS for sysvol? Read-Only domain controllers?

It probably did, although I can't imagine why. Did you use Windows setup to format the volume, or did you format it prior to install with something else? Because it's the same kernel as Vista SP1, and in keeping the build trees the same it's now the Server 2008 SP1 build tree. Confusing, yes . Not that your problems aren't real, but I'm not seeing any of this on my end. Perhaps you could give us a little more about your install and the hardware in the box? Maybe this is something specific to how things are set up or how we did the install?

USB devices are attached in such a way that the OS can format and use them as any other drive. They're on a special pseudo-SCSI bus that allows them to be removable, but still accessed like hard disks.

By default the administrator account is disabled - so what you've effectively done is disable all ways of logging into the system by removing the only active account with admin access. Your options are to reinstall, or use WinRE from the Vista install DVD to recover. Both will be painful .

Zxian is right, that imaging onto a larger array is a much better option (or adding another 4x 147GB drives as a new RAID5 array if the controller and chassis will support it). Purchase larger drives, image the old array (and remove if you replace, or reformat if you are adding 4 more drives), create a new RAID5 with the 147GB drives (in this case ~430GB), drop the image of the old 200GB array down on it, and viola, more storage.

Sorry - forgot to mention, you should put the path in quotes: "C:\Program Files\Internet Explorer\iexplore.exe" -extoff

Eventually, yes, the retail channels will sell of the RTM copies and the SP1 copies will take their place. Won't happen for awhile though, I'd guess. Sorry about the post edits everyone, but I don't want this info searchable on the internet. Please keep this to yourselves.

This error has nothing to do with the pagefile. The "storage space available" it speaks of is either kernel pool or desktop heap - remember, only the memory manager knows about RAM and the page file, not a running process; they only see 2GB of VA. This isn't a memory manager error speaking of VA, it's an error of pool or heap.

If you install the "Desktop Experience" role, you can enable and start the service, yes.