cluberti

That is correct - I was assuming you weren't wanting to wait (due to your post about the wait time for the launch), but if you want to return to the caller, you are right .

A little more information, like what did you use to create the image, what hardware and software are we using to try and burn the disc, etc, would be helpful. My crystal ball is in the shop .

...which is also the same as the Vista SP1 kernel. It will be similar to 2000, based on NT's kernel with only minor changes, or XP based on the 2000 kernel with only minor changes. Vista's kernel was a huge change from XP, so I don't expect another huge jump just yet.

I'd love to see some numbers regarding memory usage and running processes amongst all of these apps - I'd really like (honestly) if we could start seeing people posting averages of perfmon process counter information for each running process of your antivirus (everything, including the darned tray icon) of handle count, private bytes, virtual bytes, working set, and pool nonpaged and pool paged bytes. Open perfmon, create a counter log, let it run for 24 - 48 hours, stop and save/open it, then add up the averages and start posting some real numbers. For instance:

While you can use a WaitForSingleOjbect on creation, you might want to investigate WaitForInputIdle instead, as this function will actually wait through the called function's initialization routine, until the called process is idle (waiting for input) - this is "safer" than just an object wait, because if this fails you have chances to do things like break in and dump the called process if it fails to initialize in your try/except blocks or if blocks, which is always nice when debugging.

While those are vague, I'm sure you have your reasons for feeling this way. That stuff can almost always be corrected, but I understand some people just don't have good luck running Vista on their hardware. Well, personally I liked the W2K interface myself, but aero and the new breadcrumb and explorer layout actually grew on me over the past two years. I actually like it now . Bad news for you, then - Win7, based on Vista. If you don't like Vista, Win7 isn't gonna be your cup-o-tea then either.

Maybe this post can pick up some help here.

No, the master browser settings are per machine, not per NIC.

Hopefully this will get more help here.

This is actually a construct of explorer.exe, shell32.exe, win32k.sys, and potentially other system files. You'd have to hack these into the OS, or write your own shell (explorer.exe) and use it in place of the inbox explorer.exe to make this work. This is a little more than a shell extension you're asking for, you're asking to modify the shell itself now.

It's possible, I suppose, to modify the setup routine or hack it, but I've never heard of it done and a google search turns up nothing. It's possible the answer is simply, no.

Controls - how? What specifically are you trying to accomplish?

Computer objects (any objects, actually) don't delete automatically, ever. If you remove a machine from the domain successfully, the object should become a tombstone object and go away after a set time period (see below), but if it is unsuccessful or you just rebuild or down the box permanently without removing it from the domain properly, that object will not go away, ever, on it's own. Objects that are deleted are actually stored for 60 or 180 days even after deletion (60 days 2003 pre-SP1 and older AD, 180 days 2003 SP1 and later) until garbage collection wipes them out for good.

Moving to more appropriate section, as this isn't specifically a Win2K/3 question, but an AVG question.

Sorry for the late reply, but I don't see anything out there that currently does this at all.

Moving to more appropriate forum - somewhere were this will hopefully get seen and replied to.

I'm not sure if this is a documented bug, but I've reproduced this many times in a 2003 AD environment. Once you create a mandatory profile, there doesn't seem to be any way of going back.

Well, not a GUI app per-se, but a menu system - wbat. I used this heavily before RIS and WDS .

They are that way for compatibility with plugins, codecs, etc (notice IE by default launches the 32bit version of that application too). I can see no reason to use a 64bit media player unless you need to open a file larger than a few gigabytes, in which case it would make sense.

Hopefully he documented the admin password. Otherwise, you'll have to login as the local machine administrator account after you reset the password offline. You change the username to administrator (hopefully it wasn't renamed), put the password you reset it to offline, and change the log onto to the (local machine) entry.

As jcarle stated, you are confusing RAM, or physical memory, with virtual address space (VA), or what the memory manager allows an application to "see". In practice, this VA is a "virtual" 2GB or 3GB (depending on /3GB in boot.ini or the boot config in Vista/2008), and it can be mapped as pages either into physical RAM or the pagefile (or both, if the memory is pagefile-backed). http://www.brianmadden.com/content/article...it-really-mean-

This is actually stored in the registry, but it's stored as a binary blob in (in this example) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\Generic / Text Only\PrinterDriverData\TTY DeviceConfig. If you want to push this out, you will need to push it out as a .reg change, and it would have to be as an admin (so perhaps a machine startup script). The key would have to write to a pre-existing printer, and all of the configurations would need to be the same in this key (and I'm not sure it'll even work, as I don't have a box to test this on).

Heheheh - good luck with that. Let us know how it goes

Do you have a network trace of this behavior, showing the connect and the timeout to one of the devices? The network stack in 2003 was far different than 2000, so we'd need to see the actual conversation failure to be sure. However, are you sure you aren't running out of something like ephemeral ports, or perhaps seeing kernel pool issues? How is the server configured (RAM-wise, boot.ini, etc)?

Service packs should do just that - service the OS. No feature adds, no upgrades, no potentials for a service pack to break anything compat-wise by anything other than a hotfix. Including IE7, especially, means potential app and website compatibility issues, which means people will be LESS likely to deploy SP3, not more. Not a good idea, IMHO.