allen2

I will post the real cause and solution of this wierd problem: - the chkdsk worked only a few days then the problem was there again. - i decided to backup, format and restore the partition affected to solve this. In the restoration process, after restoring all datas and all was fine, i restored FSRM quotas and configured shadow copies (to have a few versions of files there). And you know what the problem reappeared (in its low effect: i.e. the partition total size is reported wrongly in explorer and free space isn't much affected). As i just restored quotas, i saw there was a quota set on the root folder and the quota amount was the same as the total space reported by explorer. So i removed the quota, and the problem wen away. And after some more research, i found those MS KB: http://support.microsoft.com/kb/944830 and http://support.microsoft.com/kb/977522. The first clearly show that there was a bug in the ntfs.sys driver and that with many shadow copies the reported space would decrease twice fast. And chkdsk /F would only "fix" the ntfs $bitmap as it would only update it. I though i'd let anyone encountering the same behavior know the root cause and its dumb solution.

Winpe wasn't designed to run those but you could add the files and the needed reg entries but it might take a little time. If you don't want to go this way, you could try pslist and pskill from the Microsoft pstools.

The default imap port isn't 993 it is 143. 993 is for IMAPS (IMAP + TLS) and it is enabled by default in exchange 2010. I would disable TLS if you don't have a real cert. Also be aware that some client doesn't support sending email through imap/imaps and then need an smtp/smtps.

You really don't need to write anything complex: - Do it one time - copy the shortcut "%APPDATA%\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar\Windows Explorer.lnk" somewhere safe - copy it to "C:\Users\Default\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch" if you want the setting to apply to all new users profiles.

The proper way is booting from winpe or your nlited dvd (you can boot an iso from hd using grub4dos). Also i don't think it is a good idea to include the driverpacks as usually you only really need 2/3 mass storage drivers and 5/6 others drivers.

I think Valerie is speaking about recovery console and not safe mode and the reg entry is explained there. See there for a more complete guide on how to install the recovery console on hard disk.

Launch it from a dos prompt (start/run/cmd.exe [enter]). If you want to monitor in realtime your open ports, you can try something like this: netstat -b 5 Or if you prefer something with a gui, you could try tcpview.

AntiVirus

For vmware workstation 7.1 you don't need to create one=> go to edit menu virtual network editor and assign the VMs you want to one of the custom or host-only vswitches but of course you could use other settings if you want you VM to communicate with physical machine (in this case bridged should be the best option as long as you have multiples available ips on your lan).

I wasn't able to conclude anything from the crash dump except that it seems something prevented csrss accessing to disk. As it doesn't seem to be an hardware failure, it could be a filter or a driver interfering like an AV software. You might try disabling the AV software and see if you can reproduce it. BTW, what is your AV (if you have one) ?

The answer is "Create a virtual switch" or a vswitch. You can look at the esx manual in the networking section.

When i said "upload the memory dump somewhere" that was on a free files hosting provider like megaupload or mediafire or another .... Of course you can't upload it there.

Sorry i missread your post, did you read this as you saif there was errors in bad sectors fixed by chkdsk ? Most likely, some system files are missing doing a repair install with another CD might work, but i don't like this as it overwrite all system files and might cause other problems (because it's hard to have a CD updated as the computer was). You best option is comparing a backup (i you have one) of your system32 folder with the current not working system32. If you don't have a backup, you could check from a working XP and add Microsoft files one by one (of course trying to get the same versions you had is better). Hope this helps.

Could you please do the asked test (at least 3 times in this thread) : disable automatic reboot on the F8 menu (if you still have it) and post a screenshot or a copy of the error ? Perhaps repeating it will have an effect...

The F4 bsod are usually related to hard drive problems (either bad connected or failling). You should try checking your hard drive with the tool provided by your hard drive manufacturer. You should also try to compress the full with 7zip (compression set to ultra) and then upload it somewhere so it can be properly analyzed. You should also provide a little more details about when it happens and if you can reproduce the problem and how often it happened.... In between, you might also check the ram with memtest.

If you want to use remote desktop, you can enable it easily from a remote computer using remote registry: - you need to connect to the registry of the computer (launch regedit then "connect to remote registry" and enter the ip or the computer name). - go to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server" and modify the value "fDenyTSConnections" to 0 (it should be set to 1 by default). - you can now use remote desktop. You could even script it easily if you wanted.

If you want to change some settings for another user account of a computer, you have to launch regedit select either HKEY_USERS or HKEY_LOCAL_MACHINE then from the file menu select load hive, then browse to find the hive of the user profile (located in the user profile and named ntuser.dat) and select it then enter a name (it will apear as a folder under the select key and you can choose whatever you want). Then for editing the loaded hive, instead of going to the HKEY_CURRENT_USER Key, go to the name you just entered and do your modifications there. When you're done, select the name enter before and go to the file menu and select unload hive. This step should always be properly done. The official MS tutorial is there. For the reasons why you need to do it without the targeted user being logged on: - if the user is logged on, some files are locked in its profile folder especially in "application data" - when a user isn't logged on, its hive is unloaded (when he is logged on, the hive is loaded under HKEY_USERS) so you can't edit its registry.

The folder c:\windows\installer store all msi packages you installed on your computer and are needed if you need modify or remove an application. You shouldn't remove them unless you spend the necessary time to remove also the related registry entries (and you might encounter problems with some applications that install feature on demand).

All vnc server binaries i know, will need at least some registry entries (to set at least the dafault password). But i've seen automated vnc server installations, which would install and set the default password. There is also tightvnc portable that might answer to your need. Ultravnc might also work as a portable app : see this post.

In my experience, nothing good ever come from making a raid array sleep. The problem you encounter is quite normal, if the array is getting out of sleep that's because you tried to access it and when an OS try to access to a drive not responding fast enough it freeze (i've seen often this behavior). Also as already said the psu might be having a hard time when the hard drives are waking up, but unless your hard drives have very short spin up sequence there will still be a small freeze when you try to access your raid array. But i already warned you about this behavior.

There are no side effects if you copy properly (using robocopy for example and from another account to avoid having locked files) the folders you want to move before trying to modify the path in the registry (you will have to load the hive of the user and modify it then unload it as the current reg entry will be for the current user). It will affect all applications after the next logon the target user. If you want to move all the profiles (best option IMHO), you should do it when installing (quite easy, for example nlite can help you) or right after (and then it's quite complex to do it properly). If you still want to do it after some time, you 'll have to check the key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList" and the values under. That were all things should be modified.

Sorry to be quite picky but what did you ping exactly (the ip xxx.xxx.xxx.xxx or the hostname ?) ? If you did ping the dhcp hostname then it's most likely normal. What are the ip of the servers (the hosted VM and the host) ? Also believing isn't enough, you have to be sure which computer is hosting the dhcp. Seriously, i feel like a mechanic who is called over the phone to fix a car by someone who don''t even have a driving license and let alone providing useful information.

You might try to boot to safe mode (and try things from there) but most likely, you'll need to do a repair install with an XP SP3 install CD. To avoid spending time for nothing, i'd backup all useful files and try the repair install or reinstall from scratch as an incomplete installation of a service pack can be very very hard to repair.

Google is your friend: here's one already made script that might fulfill your needs.

An even better way would be: redirect all profiles folder on D: (for example) this you'll have all users datas stored on another partition. Also, under XP there is no specific registry entry for quicklaunch, the process explorer.exe get the the "application data" folder from "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\AppData" and then add to it "Microsoft\Internet Explorer\Quick Launch" (most likely written directly in the related dll/exe). So you'll need to redirect the entire "application data" folder if you want to move the quick launch folder.