cluberti

I'll discuss with the mods, but calling it a "standard" is a bit of a stretch. We shall see what happens.

Hmmm - hate to say it, but it is working for me on known file types (like Office .doc files). If I right-click a file I've opened in the past, I have an "Open With" option with a list of all the programs I've recently used to open files of this type. You aren't seeing this?

I don't know if xcacls can do just folders, as the /T option does folders *and* files. I believe you would be looking for a tool to go above and beyond the Windows tools, like Security Explorer, which can do this sort of thing.

Add the server to the domain, similar to how you'd add a workstation to the domain.

http://www.msfn.org/board/index.php?showtopic=136510

Do not double-post.

It appears this is an AMD box, and a 9C means the hardware reported an error, and Windows was obliged to bugcheck with said error (it's how Windows works when an unresolvable hardware error is reported by your computer's CPU). I've discussed 9C errors in depth before, so this time I'll just dump out the analyze analysis of the issue, and try to explain it: NOTE: This is a hardware error. This error was reported by the CPU via Interrupt 18. This analysis will provide more information about the specific error. Please contact the manufacturer for additional information about this error and troubleshooting assistance. This error is documented in the following publication: - Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors Bit Mask: MA Model Specific MCA O ID Other Information Error Code Error Code VV SDP ___________|____________ _______|_______ _______|______ AEUECRC| | | | LRCNVVC| | | | ^^^^^^^| | | | 6 5 4 3 2 1 3210987654321098765432109876543210987654321098765432109876543210 ---------------------------------------------------------------- 1011001000000000000000000000000000000000000001110000111100001111 Looking closely, it appears that this is what it's saying: VAL (bit 63) is set to 1, meaning a VALID ERROR was detected UC (bit 61) is set to 1, meaning the error is NOT correctable by hardware (so the machine should STOP whatever it's doing) EN (bit 60) is set to 1, meaning that error reporting is enabled for this error in the actual MCA control register, so we should report this PCC (bit 57) is set to 1, meaning the actual state of the CPU may actually be corrupted because of the error condition, and as such whatever was executing should stop to avoid potential data loss (hence why Windows actually bugchecks - this is serious) Bits 18, 17, and 16 are set to 1, meaning the extended error code came from the northbridge on the motherboard, and it reads 0111 (19 -> 16), which means the error was a BUS error, indicating an error in the HyperTransport or actual DRAM errors Bits 11, 10, and 09 are reserved, and are ignored Bit 08 is set to 1, meaning that an error was found by the DRAM scrubber (indicating potential memory problems) Bits 03 and 02 are reserved, and are ignored Bit 01 indicates there was an error associated with the CPU 01 core Bit 00 indicates there was an error associated with the CPU 00 core This means the DRAM scrubber caught a system watchdog error on the northbridge, meaning bad DRAM (or bad DRAM communications) somewhere on the motherboard. This could be CPU cache, it could be the actual RAM in the system, or it could indeed even be bad capacitors on the motherboard causing enough of a problem to throw the error (although this is rare, it's been known to happen, so I've included it in the possibilities). Honestly, at this point I'd provide this to the vendor that sold you the machine, because you do have a hardware problem.

Wow, way to jump to conclusions. Want a mat? The vulnerability is in the ATL code used when building COM components in Visual Studio (all the way back to VC6), not IE - the fix is so that IE won't load any controls that ARE vulnerable. Note that any application that loads C/C++ code built with ATL that is vulnerable, is vulnerable.

Is this the Dell OEM disc that came with the box, or another that you made (and if so, from what source, and was nLite used)?

Correct, worked here as well. What do you mean by "doesn't work" specifically?

Done.

Windows.old can also be removed safely once the installation is complete, it's no longer used. See KB 933212 for instructions.

Sounds like the application that installs the driver is manifested to interact with UAC, and you won't be able to bypass this. You should find a way to extract the driver and install it manually from device manager at this point.

Done.

I have a FreeNAS box currently, but I'm thinking when it gets a bit older of replacing it with a 2008 storage server box running one of these, for basically that reason. While the netgear kit is always made well, things like this seem a bit overboard for the price. The features are great, but at that price they're a bit too expensive for even my blood.

If Dell is shipping it, beware - it's likely the cheapest "newer" generation POS they could order in quantities and slap a "4" in the front to fool you into thinking it was good. It's better than a Radeon 9400, of course, but a 3650 or a 4650 will wipe the floor with it. If you are constrained for power and space, however, I guess your choices are already limited.

Otherwise, failing all that, you've got a laptop that's likely dead. Either the CPU is dead, or the power brick is dying, etc - if it's not old, consider warranty repair/replacement. If it is old, break out the piggy bank and get something shiny and new .

I would agree - I have no problems with the folks who want to hold onto Windows XP, or Windows 2000, or even run Win9x. However, expecting hardware sold 10+ years ago to work with a new version of Windows from this year is a bit extreme. The hardware vendor has already written drivers for 9x, 2000, and XP, and you've gotten your money's worth. Most people won't work for free, which is essentially what these folks want driver / hardware vendors to do - write a new driver for a REALLY old device just so they don't have to pay for a new one. It's actually a double-whammy - the vendor doesn't get you purchasing a new device, and they'd be wasting money on man-hours writing software that would specifically keep you from spending money on new hardware. It's bad for business, and it's bad for stockholders. Again, no problem with folks using older hardware and older versions of Windows, but you'll have to stay on those versions to keep using the drivers you have. If the printer is that important that you can't replace it with something else, you're stuck where you are if you have no new drivers. That's the choice you have to make. Not entirely true - there are drivers that work fine in XP that will NOT work in Vista or Win7 (these are mostly older video card drivers, due to the new WDDM 1.1 spec), and things like printer drivers written for the old NT4 spooler model that won't handle running in a service but without the user-mode portion of session 0 available (trust me, there are quite a few printer drivers that will fail this model, and thus won't work on Vista, 2008, or Win7/2008 R2) introduced with Vista and Server 2008.

Wouldn't it be better to use a server OS if you're using your box as a server? Technically hacking a client OS to behave as a server OS (at least a Terminal Server) is legal grey area, at least in the US.

It doesn't even go to a BIOS post screen?

Note that if you move either the users' directory location or the Program Files' directory location, you will disable all folder virtualization. For some this might not be a problem, but it does have consequences. Note there are KB articles (and documentation in the WAIK CHM) that say that doing this causes updates to fail, but this is actually incorrect - the documentation was written before Vista SP1 (and apparently wasn't changed for Win7, it seems - it still exists in the 7 CHM) and the Vista SP1+ servicing stack will indeed work properly if either of these directories are moved. However, folder and registry virtualization will indeed no longer function.

Happy birthday to gamehead - officially not a teenager anymore .

Lazy Eye - Silversun Pickups.

No, this is *the* build. It will not change, OEM, retail, or VL. Everyone will be running 16385.

No, in fact compression can only be done on capture or export. You could consider creating a new WIM file with just the version you want via exporting that section of the WIM to a new WIM via DSIM, and then using that to vLite. Not sure if you'll get it down under 700MB though, that'll be quite a feat if you can.