Tripredacus

Some systems require the proper SM Bus driver to be installed for usage of devices on the USB Bus. A lot of notebooks nowadays will reroute some of the integrated devices through the USB Bus as well. A common symptom of a corrupted or missing SM Bus driver is when you plug a mouse into a USB port, Windows detects it as an unknown device and you have to manually install its driver.

Welcome to the MSFN!

I am unfamiliar with RT 7 Lite. You should ask about it here:

My contact was unavailable at the time, but just replied to me. I will post the solution should they help. Make sure you ask permission to post a solution! A lot of info from Embedded OSes are communicated under NDA.

Firstly, Check out the "Forums Guidelines" or the Rules link in my signature. We require topic titles to be a little less generic than the one you chose. As far as running programs, you want to look into using the RunSynchronousCommand object in your Unattend XML. You can see an example of its usage here:

I agree about the boot time. I leave my PC on all the time, and I am not in a situation where I need my computer to turn on in order for me to do work. The only possibility is when I need to do a reboot mid-day because of a Windows Update. However, I have seen that using an SSD is VERY helpful when doing image testing. I have seen a 4 second deployment of a full XPe image onto an SSD. Unlike most people here I do all my image and software testing using actual hardware instead of VMs. So in that case, using an SSD is a lot better than a regular HDD.

I'm not using a trial, this is the released stuff that we purchased a month ago. I'm not using the old unattend.xml. I created completely new one using w7e toolkit, and edited those points of interest as before using the toolkit. The new toolkit verified the file and reported no errors. Finally, as I said, when I run sysprep it fails verification. Looks like a bug to me, I have no other explanation. You should be contacting your Embedded Partner. Usually your MS Rep or where you bought the Embedded kit from can tell you which Embedded Partner to contact. They have the best information on how to use the product.

You will find that we do not allow HTML in posts on MSFN. Anyways, Memtest will run constantly until you exit the program or reboot.

Official update for this, additional language options were added for WinPE. Thanks to Gosh, source here: http://blogs.technet.com/b/keithcombs/archive/2010/10/31/windows-automated-install-kit-waik-published-again-with-new-languages-inwinpe.aspx

It depends on the OS. In Windows 7 you can do this with Explorer without apps. I haven't tried to add fonts into Vista so I am not sure if that feature came out with Windows 7 or not.

I understand what you mean. I know that NICs exist out there that are PXE capable but you cannot access their boot menus OR select them as a boot device in the BIOS. However, I am not experienced in Grub (only when it goes grub grub grub grub x grub) so I did not know it *could* do a PXE boot. I wanted to make a joke about Novell in my previous post...

Microsoft doesn't make updates to things like the WAIK except possibly for documentation. But then again, all the documentation is on TechNet as it is. If there is any update to the WAIK binaries, expect to see it after Win7 SP1 releases. For now I'll close this thread.

I'm not too fond of the Windows Search either. There are many things it can miss if you don't tell it to index the folders. So I usually still use the dir /s from CMD to do my searching.

You are confusing technologies. You can't boot a system twice without a bit of programming and a bunch of testing. Or maybe I have that backwards. What do your PXE clients normally boot into? If it is a WDS you can use a WinPE CD.

Is this not documented in the help files that come with the trial? The unattend is different for W7e. Unforunately I don't think you can get official help without getting in touch with an Embedded Partner. They are not always helpful in my experience.

I have no learned how to merge WIMs only extract separate image files.

Not too bad, but I can't speak for everyone!

Well with most that use RF it may not necessarily be the system. It could be the TV or a misunderstanding of how they work together. I do not have a PSX RF adapter (I only have the composite ones) so I can't see but look to see if there is a switch on the converter box. This is for channel. Typically channel 3 is the one to use. Then you must make sure you set your TV to that channel. However, not all TVs are the same. It is possible that the TV has a special "channel" to use the port you are using. So if you set the RFA to 3, and channel 3 doesn't do anything, try going below channel 2. Some TVs will have an "input" channel to use instead. And lastly, when you turn the system on, do you get any reaction from the TV at all? Is there a flicker or the sudden appearance of snow or artifacts on the screen when you turn the PSX on?

The timings should matter. The first three values are the most important. I think I'm running my home PC with two different speeds. Just make sure they are running at the frequency (the MHz) of the slowest. Since all of yours appear to be 400MHz I don't think you need to change that.

By default you should have a 32MB Ramdrive. If you want to put files into the X:\ then you want the Ramdrive. Unfortunately, I think you can ignore the buffer overflow and Name Not Found "errors" that you see in ProcMon. They happen on every system I've ever ran it on.

Not using DISM I don't think. If it is anything similar to Vista, you can't add SP1 in offline servicing. DISM can only add CAB files. Even OCSetup can add MSI files but only on a deployed OS. With Vista there were 2 programs you had to use after installing SP1. One was a cleanup tool and I forget what the other one is. I do not know if Microsoft made these available in RC or not. Anyways, you can try deploying Win7 to a system. Then install SP1. then do a sysprep /generalize /oobe /shutdown. You can then capture that install to a WIM file and build a new Install DVD and use the captured WIM file as INSTALL.WIM in the sources folder. Of course then this DVD you would make could only install 1 type of Windows 7.

Welcome to the MSFN!

Fixing a hal.dll error on XP can be complicated. I ran into this once with my old system (because I replaced the motherboard) and got down to just doing a repair install to fix it. Fortunately, a repair install of XP should keep all of your previous settings.