Tripredacus

The IP address certainly can, never tried specifying a port before.

It's enabled for my primary monitor, but it cannot be disabled. It's greyed out. Right, you can't disable the primary monitor. In the Display Properties/Settings tab, you will see monitor 1 and 2. Click on 2 and you should have an enable option. It may be in the context menu.

I am tasked with changing the HAL on a Windows XP image. Here is what I have encountered so far, and do not know if Windows is lying to me or what. First we start with a computer that has Windows XP Pro, SP 2 that has had some software installed on it by a customer. Unfortunately, all of the software was installed in Factory Mode rather than Audit Mode. This computer has a Celeron CPU and uses the ACPIAPIC_UP HAL as according to Device Manager. We send this image up to the Ghost Server and then I did a test by putting this image down on an identical Computer except it has a Dual Core in it. Another thing to note is that Sysprep is NOT run before the image is sent up generally, so the computer is in Factory Mode after it is deployed. I rebooted the computer after the Ghost was dropped and I went into the Device Manager to check the HAL. The HAL was now set at ACPIAPIC_MP without me making any changes. Am I to believe that Windows has automatically changed the HAL for me? Shouldn't it still come up as UP after ghosting it? I had also prepared a new SYSPREP.INF that would change the HAL but it seems that I do not need it. What are your thoughts on this?

In the old days, this meant that someone wrote their website wrong. It is much better nowadays. So it is usually an issue with the browser's settings or you have a helper app (like a pop-up or script blocker) running and that can cause this message. This of course means you are using IE.

Compare the Hardware ID from Device Manager with the ones listed in the INF.

1. Try deleting the files in c:\documents and settings\%username%\local settings\temp and c:\windows\temp if that folder exists. If there is a read only file in the temporary folder, it could make the installer fail to install. 2. Make sure you have administrator rights 3. Install using Add/Remove programs.

You can set the spindown of the drives in the Power Scheme in Windows. THe state your computer goes into when it goes into standby is determined by the BIOS Setting. We use Intel and MSI boards and their default is S1 but we change them to S3. So see what your BIOS says and if it doesn't say, then only the manufacturer would know.

I first need to have access to the source image, which totally depends on what orders placed. I did not think about a boot manager... In related testing, I have a PC that I successfully create a C drive NTFS with the size posted above, and a FAT32 ID12 hidden partition with no drive letter. I then dropped a WIM onto the C Drive, but it is the WIM for that machine and not the one I use for the test. The problem I encounter now is that after the image dropped, on the reboot, it gives the "Cannot find boot media" error. I booted back into PE and checked things out with diskpart and all the partitions are set up correctly. I also checked the boot.ini and it is correct. Since it is possible that the recovery partition requires additional files, I will have to look at one of the completed builds to see what is different. Any suggestions on files to look for besides the boot.ini?

On a testing machine I was able to use the command SET ID=12 To get the desired effect. No additional software required. I will get to do a full on test next week. Then I will have to learn to script a .cmd to do it all for me!

ive intergrated the nic (broadcom) into a custom PE build and its detecting the network just failing at step 4 do you have workaround ?? We get this problem only on about 5% of the machines we set up. In those cases when we have to "work-around" the issue, we put a Kingston NIC in there which uses the ndis driver.

You can restrict the Users group from opening it, and also have it hidden from the start menu. But you will be hard pressed to stop people from using other methods to opening a command prompt of another type. Let's start this way, what other methods would someone use to get a command prompt on the computer? 1. a USB or floppy drive 2. Download from the internet For option one, is using an external drive or disk ever a necessity for the target machine? You could say, limit opening executables from drives that aren't the C drive, and do not allow people to save files to anywhere on the C drive but a certain folder. Then have it set that they cannot run executables from that folder. You could also just rename cmd.exe, and put it into some folder where the users group does not have the ability to access. You could even ResHack to change its icon. But it sounds like you are targetting a specific person, and not a possible action a group of people could do. I am sure a disciplinary action is necessary in this case!

Doh! I forgot to mention this! All of our computers do this by default.

We know the history of SysInternals, being one of the countless companies/groups all by themselves and gobbled up by Microsoft. At first glace we could say the failings of NEWSID is caused by the fact it was third party software. NEWSID changes the Security Identifier in Windows that is not in Factory Mode. Well it changes it in factory too but why would you bother? Anyways, it does not regen the SID used for the account(s) specified in the Task Scheduler so tasks always get broken. Has a newer version of NEWSID even been released that fixes this problem? Or will we be relegated to running schtasks batch files?

Hmmm... so I have to change the type before imaging... Is there any tricks for getting a USB key to be detected in the PE? We could just launch a program that way. Unfortunately, I do not have the computer with the AIK on it, so I can't recreate my boot CD... :\

OK as I am understanding things, I need to find the command that changes the disk type. Ghost shows me this information about both volumes. Ghost is our current app for imaging this build but it runs really slow. Disk 0 61177MB ID=07 15139MB ID=12 So when I originally captured the second partition, I had assigned it a drive letter after selecting it. On deployment is the problem. I can do the C drive just fine, but as for the extra partition... Create Extended Partition Create Logical Partition Then what? I know how to image now without using the drive letter. Format the partition? Drop the image then change the drive type? Before or after I drop the image onto that partition? I have read elsewhere that you can't change the partition type in diskpart, and Microsoft's site makes no mention of such a thing. It does say that Partition Magic can do it but I need to make this totally automated.

Do you have a password for your Administrator account? If you have no password, do not have a DefaultPassword key in the WinLogon section!

I wonder if any OEMs will have problems about this!

I either call it a USB Key or a USB Drive. When I got to the company I work at now, everyone called it a "Dongle" even my many failed attempts to inform them that they are not connecting them to PCMCIA Cards.

JavaScript, HTML, CSS, AutoIT, PHP, DOS Batch. I would think that ActionScript is a language?

You changed your username but the automatic logon does not recognise this. So you get this error. You can fix it by editing the registry. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon Change DefaultUserName to your new username. There might be a DefaultPassword key right under it. If there isn't, make one and type your password in it. You will also get this message if you are still in Factory mode, but I doubt that is the case.

There is one program we use to create recovery partitions on some of our builds. When we install it for the first time, it creates a new partition and copies the contents of the C drive there. One of the more amusing errors it gives says something like "The target partition has too much free disk space in order to back up your data". One other time, one of our customer's had software that gave an error. In your standard error lingo, when you come down to it, it said that the error was caused by your administrator not knowing what he was doing.

We have encountered a problem with Scheduled Tasks that I cannot find a true fix for. We start with Windows XP that is custom setup, and has 1 or more scheduled tasks in it. They are set to use COMPUTERNAME\ACCOUNT and created by that same account. The account's password is typed in, and testing shows that the tasks complete properly. The we image the machine. Then we drop the image onto another machine. In what seems to be more than half the time, the password is "lost" for these tasks and we have to re-type it in the Set Password box on the Task Properties. This became such a problem (since you cannot see if the password is in there or not) that we added it to our Quality Phase, typing in those passwords, on every system just in case. The real issue is that we did not catch this issue right away, and there are at least 1500 computers already delivered into the field that may or may not have that password in there. I have already been contacted in at least one instance of the scheduled tasks failing because of this. We are able to do a work-around fix for now which will allow us to fix those particular computers, but this is a problem that we would rather didn't occur in the first place. Is this caused by a Windows behaviour that we cannot change? We have encountered other Windows behaviours (such as permissions lost on drives after formatting) that we have had to use work arounds for. Any suggestions?

OK I have completed the task of capturing the image of the C drive and the hidden partition. While capturing the hidden partition, I assigned the drive letter P: to it. As per Iceman's doc, drive letters assigned with diskpart are only for that specific Win PE session. I deployed the image today, which had to be done in 2 parts. One was the C drive, then the second for the drive I called E with DiskPart. But after rebooting into Windows, the E drive was visible and you could traverse the files. I Deleted the drive letter but this partition will not function. It does not give me the ability to boot into the recovery partition. My thought is that typically, the recovery partition appears as FAT32 (EISA Configuration). My deploy makes it appear as NTFS but with no parentheses next to Healthy. There is also a green border around the recovery partition. I am pretty sure that the problem appears during the deployment phase, concerning how imagex is putting the partition down, or how I am setting up the partition for putting the image onto. This partition should not be traversable, or get a drive letter in Windows. Any ideas?

I would be helpful if you posted the product name or model number of this "ethernet splitter". Also, just connect your laptop to the college network, and verify that you can connect to the internet. Then see what IP address you have. Then connect it to the "splitter" reboot it and see what IP address you have again. If what you bought was a hub or a switch, you will not be able to access the internet with both the laptop and the Playstation.

When the image is deployed, it needs to make it so that partition does not have a drive letter. Is that also possible? Or a fix that can be applied after imaging is complete?