cluberti

This usually happens when you log off an account, and log on again without restarting. Some driver or service had a handle open to the user's registry (ntuser.dat) or a file in the profile (%userprofile%\), causing the profile to fail to unload during the log off attempt. Thus, when you went to log on again, a copy of the profile was created (otherwise the logon would fail), but it gets a different name (usually <user>.00x or <user>.computername (or a combination of the two). Normally, I would state in this situation that you would do well to download and install the user profile hive cleanup utility, but only betas of 2.0 work on x64 (and good luck acquiring it). In any case, make sure you cleanup the startup items and services on your machine you don't need, as well as make sure your print drivers, antivirus software, and any antispyware / firewall software are also running the latest versions available to you - any of these things can cause this issue.

If you can boot to the Windows CD, you could try to do a repair installation.

Take a look at this before pulling your hair out. Are you running 32bit or 64bit IIS?

Is this really a server 2008 question?

Server 2008 doesn't ship with a bluetooth stack at all (remember, it's a server, not a client) - you'll need to actually install a full 3rd party stack (like Broadcom's, for example) before you can even try using Bluetooth on 2008. And it may still not work right for you, honestly.

Forum rules violation: 1. This is not a warez site! Links/Requests to warez and/or illegal material (porn, cracks, serials, etc..) will not be tolerated. Discussion of circumventing WGA/activation/timebombs/keygens or any other illegal activity will also not be tolerated. You will be banned without notice. Banned.

I would suggest first placing that external share location (especially if it's a UNC) into the "Local Intranet" zone of the machine, and reboot (yes, reboot). Then try again.

Not a problem, no question is stupid: http://www.nliteos.com/ It's made by nuhi, and the forum is here as well.

What is the actual error message (word for word) that you get when booting normally? Honestly, this sounds like a virus, but more info would be helpful.

Please use search. This is an unknown bug at the moment, with some fixes that work for some and not others in the list. What has been found to always work is a host OS reinstall of a non-nLite or vLite'ed source, but that's drastic.

No, it's an intel driver file. Your best bet is to go to a friends' house, or a cafe, or a library, or some other place with 'net access with a portable drive and bring along nlite and your install disk on the drive. Download the Intel Storage Matrix driver set, integrate it into your disc using nLite, and then you can have that to install. It's a bit complicated, but the fact that you only have one machine and no way of downloading or running anything makes it very difficult to do this otherwise .

If changing the MTU settings on the router don't affect clients, then no, you'll have to modify the clients to work with the lower MTU. The bigger problem is why do you have to bump down to 1492 or 1486 on that connection for it to work? I'd be asking your ISP. Do you have the MTU issue if you connect your machine(s) directly to your broadband, btw?

Try booting into safe mode, and then use the "To reapply default security settings using the Windows interface" from that web page to do it with the GUI. If you can't launch that, I'm afraid it would be far easier to reinstall.

Locations.msi was the installer for something, probably a sidebar gadget or one of the gadget's supporting files, so it would be better to find out what used locations.msi to install to the system in the first place, and remove that applet and reinstall as necessary. The MSI engine keeps popping up because it's in "repair" mode - something with the package is either not installed or not registered properly, and it's trying to fix it everything the thing that locations.msi installed loads.

I helped a nonprofit with AutoCad a little while ago during a Vista migration - seems the app needs to WRITE to the program files directory. A quick Process Monitor log of the application running through it's paces, or, if you want, use LUA BugLight, should show you the way. I personally prefer the LUA BugLight tool nowadays, but procmon will get you there too.

Did Hyper-V ship with this release? I thought Hyper-V wasn't going to be in the initial release, but would be released "within 180 days of RTM"? It shipped on the DVD for x64, but it's still "beta".

Ok, do explain - because Microsoft themselves say you can't slipstream the service pack to an offline image due to the fact that the service pack updates the servicing engine needed to slipstream service packs and updates... You could reverse integrate it, or install Vista, SP1, and make a different install.wim, but I doubt that's what you mean.

Those settings are read by explorer.exe on start, and iexplore.exe as well on start (or clicking tools > options). Best practices for changing security zone settings like that is to reboot after making changes, or at least log off and back on. Not sure why the vbscript worked and the reg change did not, unless you had IE open when you changed it manually and did not when you used the vbscript (just guessing).

RE: the logon script - I have some Vista machines with broadcom NICs that do just this after coming back from sleep or first boot, and I use a vbscript to ping a known server until the machine is pingable for 5 seconds (network is up), and then move on with the logon script. If it times out after 60 seconds, I log an event to the event log and skip the rest. Just a thought.

Fantastic!

Good point - it's not something we can necessarily help with, but I guess this belongs here if not anywhere else.

Maybe - if you open a command prompt, change to %windir%\system32, and type "dir /a secedit.exe", do you see secedit.exe listed?

I'd say that'd be the local server, hosting the server-portion of the game to be played. Most (if not all) support use in a simple LAN, without internet access (assuming everyone at the LAN party is using the same game - they can all use the same server, yours).

Yes, it's the "shadow" command.

I personally find the features of Vista compelling to me (instant search, a much better x64 version of the OS, x64 MCE, everything laid out far more logical and easy to find, faster and better able to use RAM with superfetch, dynamic kernel memory management, SMB 2.0, to name a few). I also wasn't silly and bought a machine able to handle the OS, dual-core and 4GB of RAM - just like I did when XP released in 2001 (512MB of RAM!!!). As always, hardware and drivers being capable to handle the increased load a new OS and codebase puts on it is most important with a new Windows OS. XP is "fast" because it's design was for "high-end" hardware in 2001 with an NT kernel, which is sprightly but lacks security (hence SP2 brings the "bloat" in memory usage and running processes). And since the next product is built on the last, fixing bugs so they don't exist in the new codebase is a bad thing? Just like every new OS, you need beefier hardware to run it. And all of the hardware vendors will provide it to us in time - in fact, this seems to be the EXACT argument you are using for NOT using Vista... Do you remember screenshots of the XP alpha builds in late 1999 and early 2000 (before 2000 even RTM'ed, no less) and how "shockingly" similar they looked until the new XP green/blue/clouds theme hit? This is normal (read above on how each version of Windows is based on the last to understand...). I know this was meant to illicit flames and be trollish, but it's just silly. You take your time and wait for Win7 and skip Vista - we'll have the exact same issues when Win7 releases that we had with Vista, that we had with XP (I remember the EXACT same comments about slow performance and driver compat issues about XP back in 2001 and 2002, before SP2 released), that we had with 2000 (hardware/driver compatibility issues, anyone? Ever try to get an old scanner, sound card, or webcam working with 2000? It was horrible at RTM and SP1, until driver vendors got it figured out or just abandoned the old products altogether).