cluberti

That depends - ntuser.dat is the user's HKEY_CURRENT_USER registry hive, so if it stores changes there, then yes. If it stores changes elsewhere in the registry or in the filesystem, then no, it will not.

I plan to. But you need to remember that it's NOT freeware, it's open source (free as in beer). There is a difference, it does have a license, and it should/must be followed (at least here on MSFN we try to follow EULAs regardless of from whom or of what type, closed source or GPL/BSD/open source). If the FF people (an actual FF dev or a spokesperson) says you can make the binaries portable in this manner, then I don't think there will be any more noise from the mods here about it. Short of that, it's still in limbo. However, we've decided not to take any further actions with regards to this project, until there's word from the Firefox team directly on how they want to address it (if at all - again, this may be perfectly OK). I'll read up when I get the chance later, as I want to see this newsgroup and perhaps ask some questions.

A quick google search on your problem description and the file name brought me to this, which appears to be your problem and the fix.

Log onto a machine matching the one you're automating (same software, etc) and get things the way you want. Then, log out (and reboot to make sure handles to the profile are indeed unloaded), and then as another user copy the %userprofile%\ntuser.dat file off the system. Now, place this in the \Documents and Settings\Default User\ folder on systems you want to use these settings for - all new profiles on that system will get their settings from the default user ntuser.dat file on first logon.

This was the reason they postponed the SP release before. Looks like you're hitting the bug anyway. Only sure-fire way is to do a repair install from the original media (choose a restore point prior to the hotfix install) and install all prerequisite patches before trying SP1 (and reboot inbetween too!).

Second for GFI - it's absolutely wonderful compared to other products I've used.

From what I am able to grep, it appears there's some difference in the IOVMM subsystem used to do the hardware partitioning/virtualization, and this can perhaps be done in BIOS on some machines with the right BIOS and an F2 chip, but it appears Microsoft recommends/requires you to use an F3 stepping AMD for Hyper-V: http://blogs.msdn.com/mikekol/archive/2007...r-2008-rc0.aspx

Been using it for the past 24 hours on and off. No real troubles. FF3 locked up just once but that could easily have been the browser. It is a beta after all. Hopefully someone is still looking into the naming issue, if there is one that is. Separate from this forum I'm in touch with some of the FF3 development guys so if i come across any definite positive info I'll flag it up in a new thread here, admin permitting of course. Course of action is very good .

Expect to see an RTW date by the end of April.

I don´t! Explain me. It's a euphemism for some of the more biblical needs of the human species. Look it up if you have to .

Just so people don't think I'm hiding something, this is expected behavior in W2K3 R2. It is able to be modified in W2K8, but not 2K3 R2. That's the gist of it.

PM sent.

Good read on how they all work (together and apart). It's not a huge upgrade.

The moderation staff are speaking about this in a general review of the board contents. We apologize this particular project was put "on hold" temporarily, but it wasn't the first and will not be the last. I am fairly confident this will be resolved today or tomorrow and then more will be known, but do not take out your anger on PuntoMX. This is something we should have done long ago but didn't have the manpower to do until recently, so we are currently reviewing all forum projects to make sure we aren't violating the legal rights of copyright, IP, and patent holders. The Mozilla foundation and Firefox project authors did not code Firefox B3 for Win9x OSes, and the EULA / License for the beta was a gray area on whether or not this is allowed (other projects, like Debian, have run into similar issues). This is being dealt with. Please PM me if you have other questions, let's take this offline for now.

There's actually a KB article on how to do this, in many ways.

Happy birthday old man. Would've wished it earlier, but it was my mother-in-law's birthday yesterday as well, so I was busy . Hope you had a great time, now.... back to work!

Hmmmm - it's decompressing the .wim image at this point. Are you sure the x64 DVD is good? I don't doubt it, but there's not much difference in the WinPE setup portion of the installer between x86 and x64 minus the x64 WinPE can access the additional 32 64bit registers that the x86 cannot. Not sure that has anything to do with it though - seems more likely the .wim image file on the x64 DVD would be the problem.

Does it actually crash and go away? If so, generate a dump of an application crashing as per the instructions here.

The 2000 driver should work in XP if it's a WDM driver, but if not you can download one from the vendor's download page. I also managed to find one with a google search.

Microsoft Office 2003 Professional Enterprise Edition was only available to Academic and Volume-License program customers. The highest retail version was Professional, so if you indeed have "Professional Enterprise", you either got it from an academic VL program, or a corporate VL. If you have this edition, you should know where you got it from. However, since it's giving you an error (and saying retail/OEM), it is likely this was garnered from an Academic VL program, which won't allow admin installation points.

Are you utilizing the bForceAppsClosed == True in your call? Also, just an FYI, but using the ExitWindowsEx function provides the logoff+shutdown/reboot functionality, and should be used instead of InitiateSystemShutdown function unless you want to do this remotely (ExitWindows is a local API only).

I used to do mainly C/C++, but I've branched a bit into learning java, scripting languages, and asp and asp.net. I've done VB in the past as well, but not anymore. I guess the short answer is "whatever the dev is comfortable with" .

Not entirely sure, but all of the searching of the SDK and DDK bring out that it's an error with either .dll or CRL hash information on the server side of things...

If you haven't already, you might want to read this thread.

Check, check and check. Still no difference in performance... Memory management bugchecks mean you've got a misbehaving driver, that makes kernel calls (thus the nt! calls...). That doesn't leave many options, just video, audio, and potentially firewall and antivirus...