Tripredacus

This error can be caused by faulty memory, not enough memory or a network timeout while transfering the boot image to the client. You need a minimum of 512MB RAM on the client to boot WinPE 2.x 32bit, 1GB for 64bit.

You can use the DriverPaths object, among others. http://technet.microsoft.com/en-us/library/dd744282%28WS.10%29.aspx

The topic still exists but has been hidden by another mod. This type of topic you posted should be in the board issues section, which is where I will move this topic to.

Computer repair comes down to two part, fixing hardware and fixing software. Both have different skill sets. Don't worry about what exactly you want to do if you are just starting out. Play around with everything you can that holds your interest. I did not truly find what I wanted to do until maybe 8 years into my IT career. When you figure it all out (if ever) you can then correctly plan your career and certification path.

Nice collection! I have found its often easier to fix your own machines, but sometimes riskier to try to fix other people's computers.

I have a D-Link DIR-615 rev C1. It is horrible at stock. I am using the DD-WRT firmware and it is much better. If you are looking for the N speed, use DD-WRT's guide on it, but know you won't get a full speed if you are supporting G or B devices, such as the Wii. I currently have 1 PC, 2 notebooks (on and off) and a PS3 on wireless. PS3 is G speed, so my router is running at 2.4GHz even for the N clients. My PC is hard-wired. However, I can't really recommend any D-Link products. I hated mine for forever until I found the custom firmware. I can't complain tho, I got mine for $40 on clearance! You get what you pay for.

I think you'll need a wrapper to detect the hardware configuration and launch the appropriate setup. Or instead of detection you could have a choice option. So basically have the winpeshl.ini set to launch your app or script. Select which option, say like this: Option 1: setup.exe /unattend:autounattend1.xml Option 2: setup.exe /unattend:autounattend2.xml etc.

Yes well pre-staging can be helpful in certain situations. It depends on what your environment is like. For example, pre-staging doesn't work for me, but if I were doing it for an enterprise environment with appropriate inventory collection, I would definately use pre-staging.

If your dial-up connection is your primary way to connect to the internet, and an application tries to go online at boot, this can pop up. You can check these settings that work for XP. Go to Internet Options. Then go to the Connections tab. Never dial a connection should be selected. This way, if you want to go online, you must connect manually.

Ah yes, it is alt+space. Brain fart!

Included in those "plenty of others" (that is if you reference 2600) you can put in the Sega Genesis as well. You just try playing a 2600 game with a Genesis controller...

This was a good joystick for me. I wish I hadn't lost mine in a flood.

The answer is yes, but a couple things. 1. Recovery PE? like WinRE is actually just WinPE. 2. WinPE can be a custom OS, look here: Your main problem is that you would need a 32bit WinPE to build, but then you can't install 64bit OS. Another problem (uh yeah I can't tell you how to do this) is if you don't build your boot environment properly, you may find that no PC will have enough memory to boot your custom PE. You already received your warn about Hiren's...

Well you can do a FirstLogonCommands to delete the XML file, but the log files (and modified XML) will show up in the various Panther folders anyways. Or you can put your XML into a folder that is accessable by the system but not by users. That way the unattend should work but users can't get into the folder without proper permissions.

I'm not too sure about the behaviour of unattends in domain environments. I do know that you can't log into the domain and then do the join. The PC needs to join then you can login. Does this help? Maybe also you can pre-stage the system in AD to get it to join that way, not sure.

Good luck on your new venture!

Not really. In fact we had so many threads about Seagates getting bricked that we created a subforum for those types of threads: http://www.msfn.org/board/forum/169-hard-drive-and-removable-media-issues/

I disabled both of the IGD adapters detected in Device Manager in Safe Mode. This let me boot into normal mode! Annoying thing, that's for sure.

Of course jaclaz, that's why I made this thread also. I did not know if it was possible, so instead of just telling the user that, I help out by asking questions in the right place where the right people can answer.

I put "upgrade" in quotes because you could say I did a side-step or downgrade. I wanted to upgrade my video card to be able to use three monitors. The card I have now is an ATI FireMV. It was not compatible with my motherboard, Intel DB43LD. It would just reboot during post. I called Intel support and they said this was because the board did not detect a GPU. Or more specifically, since IGD disables the integrated graphics if there is any card in the PCI-E x16 slot, the ATI card had not responded fast enough during POST and the system would reset. I had updated the BIOS, but the BIOS ended up getting corrupted! I backed that down and no change. I tried another DB43LD that had the BIOS upgrade but no luck. I tried a DQ45CB and the card worked but NOT after updating the BIOS. I found 1 board that did work, a DG45FC. We'll forget about the fact that I now have a Mini-ITX board in a 7 bay/full ATX case.... and that I like to tell long stories about things... After confirming the board actually would POST after the BIOS update and the card, I put it into my case and hooked everything back up. One other change, I upgrade the PSU to a 500W. My first boot (HEY the OS is 7PRO32) went fine. It booted up, I logged in and it detected all my new stuff and then installed the drivers. It prompted for a reboot and I did. Then it would get to the Starting Windows screen, work for a bit and then just sit there. The animation would stop and the CAPS LOCK key did not work, thus PC is locked up. I reset and tried to run Startup Repair but this didn't work either. However, I am able to boot into Safe Mode, but as usually, I can't install or uninstall anything. There is no left-over devices in Device Manager and nothing (non network related) is logged in Event Viewer. I need to know what options I have for getting it to boot into Normal Mode again. Here is a summary of what I had done: 1. Changed from Intel DB43LD to Intel DG45FC motherboard 2. Changed from ATI X1800 Radeon PCIE to ATI FireMV PCIE 3. Changed from 350W PSU to 500W PSU 4. Disabled CCC with MSCONFIG in Safe Mode CCC was complaining that there was no ATI card installed because only the WDM drivers were installed. Hmm I have an idea just now. I have previously used this board with XP and a Matrox Parphellia, and just like this current system, IGD does NOT disable the onboard video like it is supposed to. What ends up happening is that it still gets detected, and on the XP I had to disable the onboard in Device Manager. I guess I will try that out, but if you have any other ideas, let me know.

Well I don't actually pay for these parts, let's call it a work benefit. Anyways, I located the missing video card, but the PC it used to be in is still MIA.

Well you could mount the install.wim with DISM (using the WAIK) and delete the fonts out of there. Or maybe one of these tools can do it:

You don't join the domain in Audit mode. The join should happen during First Logon after Windows Setup. You can just use the sysprep GUI if you want. Then name your file UNATTEND.XML and put it in one of the search locations: http://technet.microsoft.com/en-us/library/cc749415%28WS.10%29.aspx Otherwise, in order to use the commands I posted, you need to close the sysprep box that shows up. Otherwise you will get an error saying that sysprep is already open. I don't really like using the method of sysprep looking for the file. I'd rather specify it myself.

If this is a case where you delete a file or folder, and it reappears because it is "protected" then you have only one choice. You would have to delete the backup file AND the actual file. The same is true if you are trying to replace files, like hacked screensavers. Your best bet is to boot into another OS that can read NTFS, like WinPE (you'll have to change ACLs) or NTFSDOS. Linux can do this too I think. But why is this a big problem? Do you just want to hide it? You could also change the ACLs on the folder itself, then delete the contents. I've done ACL trickery on viruses to stop them from working. For example, if you remove all right for the SYSTEM account, any functions that Windows carries out using that account on that object will not work anymore.

I don't know WinPE 1.x very well, but this is a pretty neat method: