Tripredacus

Well that is ok. At least now the links are underlined. That was the reason I used Orange because links inside of posts would stick out better.

What is the Code number in the Description in the Properties of the device?

A 64bit WinPE can deploy both 32 and 64bit images. Windows 7 setup doesn't really care what the architecture is. Not sure about Vista, because Vista still uses an installer where 7 basically uses Imagex.

Not to my knowledge there wasn't. Is there a way I can check to see if any drivers were added to the image and if so, is there a way that I may remove them. Yes you can do this. If you mount the image, you can look in mount\Windows\inf and look for oem*.inf. Some of these are built into Windows, but additional ones get appended at the end. You'd have to compare this to the source in the install.wim of the Windows 7 DVD. But let's say, for example, the DVD only goes up to OEM13.INF, then if you had INF files up to 33, those extra 20 would have been injected after the fact. I've had to remove an injected driver from an OS before. If you knew exactly which driver it was, you could search the OEM*.inf files for the HwID of the affected device. You can use DISM to remove the INF file once you find it.

It may be because it sometimes isn't actually just File association. I believe that Default Browser setting is profile specific. Have you set Firefox as the default web browser for the limited user account?

I'm not sure how successful this can be using the regular OS. There is a WinPE portable OS build that can work as a Thin Client, as seen here: As far as official support goes, you do have the ability to create a thin client using Windows 7 Embedded. The WES Trial contains documentation on how to do this.

Sometimes finding MSFN on Google is annoying, especially when you search for something and just find the topic you made here.

Ooo I can see the separator. I'll have to check things out and see how it is. Oh um... back to normal color scheme. Almost didn't see it. How can I get back to using Orange?

What do you mean? I honestly don't know what else you could ask for. I was using the wrong terminology. I was thinking about how Link Aggregation works on our managed switches, but the correct term (and such things do exist) is Dual Band wireless, which will allow for separate N and G bands that do not interfere with each other. I'm still kinda green on wireless tech, mostly because I don't trust it yet.

No the reason why you aren't seeing XP from OEMs anymore in the retail market is because Microsoft dropped XP support from the channel. However, you can still buy whitebook products (barebones) and put your own OS on it. Your specs made me think of this model: http://www.msiwhitebook.com/product_spec.asp?model=MS-1454-ID1

That's good. I wouldn't be much help on XP installs, because I don't do them that way.

Welcome to the MSFN!

The Wii should be fine. My PS3 works fine on the wireless, however I am going to research how to use N on the PS3. The fact that I am using mixed mode is causing some problems for Wireless N clients. Now if someone were to make some managed N routers that would be awesome.

Add this to your diskpart script: sel vol d assign letter=v Change the assigned letter to what you want it to be. When the system is booting up, go into the F8 menu and choose the "Disable automatic restart on system failure" so that you can see the STOP error you are getting.

FWIW, I see that AVG is installed. A best practice for any unattended install is to install your antivirus client LAST.

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.