Tripredacus

Check your event viewer for any errors. Have you installed the .Net Framework 3.5? This is known to break RDC, there is a hotfix or something available for it also if this is the case.

You can create a different Power profile. The use POWERCFG to change your Profile before and after playing your game. That's my idea at least. Or you could change it manually.

Hmmm, don't think so: http://aumha.org/win5/a/wpa.htm I underlined the part that both you and Tripredacus seem to have "missed". jaclaz No man, I know it allows that, but I did whole-sale changes. Such as I'd be changing video card and capture card, plus disable the 5 or so devices in the BIOS. That would be enough I'd think. Actually, we use OA2 for our licensing, I was really trying to get Vista to blow up its activation that way to see if I could reactivate it using our stuff. It was coming down to me making my decision to purchase Vista using OA2 VLK or using a retail disk, in order to ease upgrade issues. My idea was that if I could reinstall the OA2 license and unlock Vista again after it lost its activation, that would be the way to go for me. Except I couldn't get it to blow up so I'm still left wondering which Vista release I'd rather use...

I've been experiencing some network related problems using the WinPE (via PXE) on two (four) Intel motherboards using their onboard controllers. They are the DG33BU/DG33FB and the DG45ID/FC. They have different controllers, but use a newer driver package than other Intel boards that I work with. The DG33 uses the Intel 82566DC-2 (VEN_294C) controller and the DG45 uses the Intel 82567LF (don't have one of these on hand right now) and they both exhibit the same issue. Here is a run down of the symptoms. Boot via PXE. The WinPE loads the startnet.cmd, which does the init, start networking, maps a network drive, registers a DLL and launches an HTA file. But it gets hung up at mapping the network drive, it returns an 1321 error code. I had written a program to remap the drive, which I have to launch manually on EVERY machine that contains these two boards. After I run this program, it maps the drive and refreshes the HTA and everything is workable. Then I choose to image the hard drive with Imagex. After the image is deployed, it loses the network drives. If I attempt to run my program again, it always fails, and manually deleting and remapping the drives fail with error 1231. I have an additional program that I run after the drive is imaged which copies files off the server, but I can't use it on these boards. I am at a loss as to why this is. All other boards I work with (MSI, Intel, AOpen, etc) do not have this problem. There appears to be an initial network initialization delay after loading the driver for the NIC at the beginning of the process, but it shouldn't fail on the drive mappings RIGHT AFTER it is active at copying files from the server. The G33 boards are at the end of their run and will go EOL in a couple months, but the DG45ID/FC is new and I know for a fact it will be a replacement for the ending DQ35JO line, so this is going to be a major slowdown for us around Q2. I have already PEIMG the newest Vista 32 drivers from Intel for these boards and it has not changed anything. Anyone have any ideas about this? I am using WinPE 2.0 using Vista SP1 Servicing update. Latest version of OPK (we cannot use WAIK for licensing reasons) Tools. Server (IMAGEX) details in my sig. EDIT: Microsoft SR opened for this issue. I will keep you posted.

Heh I guess I missed that. I'm using WinPE 2.0.

There is a default place and a last used place. It will try to open the last used place first, if it can't find it, it will use the default place. Its good to have it in My Documents because that will always be there. I would hate to think what would happen if you changed the default place, and then moved the folder or something. Would Windows crash at that point? I was just thinking, perhaps this is located in a PATH variable?

Make sure your app is a 32bit one. oh can you open the app just by clicking on it? Does it only give this error when you try to launch it from that cpl?

This is quite the derail i've made huh... lol Its a tricky situation, I don't think I can answer this right now.

I have the answer you are looking for. Having formerly worked in the cable internet business helps me here! Almost all cable modems (that do not have built-in routers) learn the MAC address of the device (your computer) that is connected to it. So your modem registered the MAC Address of your first computer, and will only do business with a computer with that address. In order for it to recognize a different device/interface/comptuer, you need to unpower the modem and power it back on. If you have access to the internal page of the modem (as long as your ISP hasn't blocked it out) you will find where this information is kept. I'm not entirely sure why modems do this but they all do it. It must be something buried in a standard someplace.

I'm not sure about IE or Chrome, but Firefox has a built in config file you can edit. just type about:config in the address bar to get the settings.

Yes you can run scripts or batch files after imaging. Unlike using Ghost, which uses sessions, you have full access to the file system after imaging. I have an example here: http://www.msfn.org/board/index.php?showtopic=126828 As far as deployment time... I must be doing something different. Average deployment time with Imagex to multiple clients is 3 minutes. Average deployment time using Ghost to multiple clients ranges between 10 minutes to 40 minutes. I am using Server 2008 so that WDS supports full multi-cast. Server 2003 does not support multi-cast, and as such, deploying from it (my test/backup server is a WDS 2003) can only support 4 clients and deployment time is a little slower if deploying to 4 and even attempting to PXE any additional machines.

I hear all about this 24 hour limit everywhere but fail to see it in action. I've successfully had a machine booted into the WinPE for well over 3 days and still be fully functional! Is this a limitation to the PE that is built by the WAIK? I don't use the WAIK, maybe that's it. A product I know of is Ardence. It has problems with certain Intel boards however. Something about a pre-disposition to suspend to Hard Drive over RAM, whereas it does not work properly if no HDD is present on those boards. Says that Shared mode does not work this way but Private mode does. XP Embedded uses a hardware specific config file. It is possible but each Embedded boot image would have to have a different file based upon the client config.

I like it very much also. I have made 2 different backgrounds for it also, if anyone wants to use them, feel free.

Yes I have this problem every time also. I believe if you slip-stream the driver into the Vista install before you run Setup the first time, this will not happen. Something with sysprep can only install plug-and-play drivers, meaning they came with the OS. Same thing happened in XP with NIC drivers. Then again, it is beyond me to know why it doesn't remove the sound driver in the same fashion. Of course generalize is also supposed to remove all drivers, but it obviously doesn't. Can't help you with the domain thing.

This is meant to be run from a WinPE environment, not your OS. This can be very dangerous to run from your OS! Unless you got Task Manager to appear in the WinPE.

I am going to guess that you didn't modify the boot.ini after redeploying your image to the new C drive. The boot.ini boots an OS based upon the physical connection (drive 0, drive 1, etc). So if you didn't change that, when Windows tried to start, it read the boot.ini and said (ok, Windows is located on disk 0) and went to look there, but obviously you formatted that drive. Here's a summary: Prior to imaging, boot.ini had OS located on disk 0 disk 0 = c: (has OS) disk 1 = d: (empty) you did your stuff. boot.ini still said OS is on disk 0 disk 0 = d: (empty) disk 1 = c: (has OS) I had this issue once when trying to swap an OS volume and a recovery volume until I figured it out. Now, in order to edit the boot.ini in the WinPE, you are going to have to use attrib to be able to modify it. Try the following script: attrib -R +A -S -H notepad boot.ini (edit and save)* attrib +R -A +S +H R = read only A = archive S = system (protected) H = hidden * you can also keep a "reversed" boot.ini somewhere in x:\ and do a file copy instead of manually editing the file itself. Notepad is included in the WinPE already. You may have to use the full path to the boot.ini, as the OS' PATH variables won't be loaded.

DriverForge is intended to be run from the OS, not the PE. I do not think I know of a way to do what you need. Other than copy DriverForge and the drivers to the HDD after imaging, then script it so that on the reboot it installs everything for you, or use the sysprep to do it for you instead?

F6 and browsing for the drivers is the same thing really. It is just presented differently in Vista than XP. Verify that you are using the Vista 32bit driver and have the latest BIOS update. http://downloadcenter.intel.com/Detail_Des...amp;PrdMap=2800

http://unattended.msfn.org/unattended.xp/view/web/33/

You need to boot your computer with an OS that can read the NTFS partition. You can do this with WinPE or NTFSDOS. But its likely that file already exists. The "missing or corrupted" message Windows gives is pretty misleading as it usually means that one of the files THAT particular file imports (a dependent file) is the wrong version, missing or corrupted. But if you do not have access to an NTFS OS then you can put it in another computer as a slave as you noted. You may have to re-attrib the file in order to replace it, if Windows has it flagged as a protected system file. I do not recommend using this hard drive to boot in another computer.

if your ISS files are from InstallShield, use the following commands. to record the file setup.exe /r /f1 "c:\setup.iss" Edit the ISS file as necessary. to redeploy setup /s /f1 "c:\setup.iss" the F1 switch is a silent switch. When using the /r you need to specify the path and filename of the ISS file you want it to create. Using /r for InstallShield setups depends on how old the installer is. Older versions use /r for remove, but newer ones use it to record. I am not certain how you can determine which version of InstallShield created an installer. You may also be able to get the ISS file by unpacking the installer using WinRaR. If you do not find it this way, you will probably find an INX file instead, which can be read by the InstallShield dev app. Lastly, ISS files are also created by InnoSetup as well, and they are different than InstallShield.

When you do a save picture as (in either IE or Firefox), and change where to save the file, it should save that location for the next time you try to do a save as. The only reasons why it doesn't is if the last used location doesn't exist anymore. Like you are saving to a removeable drive, or you renamed the folder, etc. I imagine this is kept in the registry someplace, but it will always default back to My Documents (or My Pictures) if it can't find the last used place. Also it may be reset if you change settings in your browser, like resetting to defaults.

TechNet has this issue, but they also say there are errors. Also only on Ultimate x32. Appears to be a malware service or rogue/corrupted (or likely poorly written) BHO you came across in your travels. Some say disabling a certain ActiveX control or service can help get rid of this error. http://social.technet.microsoft.com/Forums...6-34b0330bfc5a/

Well since you threw vLite in there, I'm out. You might have configured something wrong. I have no experience with Windows after vLite.

I would never attempt to change the motherboard without sysprepping the drive image first. I did try changing video cards around. I think I had 3 of those and 2 capture cards (a Leadtek and a Pinnacle) during the early testing. I have also seen a BIOS update do that but... err I probably use a different version of Vista than you so a BIOS update for me (in some cases) would definately cause that to happen, but it would be fixable for me.