Tripredacus

Actually 195MB isn't that big at all.

Its not hard at all. Vista drivers work pretty much the same as XP drivers. I haven't had to do anything more than adding the Vista (Windows 6.0) support line and copy the DEV IDs into that section.

Are you using wireless internet? Specifically 802.11b? They use the same freq as your keyboard and mouse. That is my first idea.

I don't get it... You can already do this with the PE Command Prompt...

There are a bunch of errors when you try to validate it. I don't know how picky MS is about that. http://www.stg.brown.edu/service/xmlvalid/

Yea the WAIK and the OPK are basically the same thing. The WAIK is for when you need to install Windows in a corporate environment, and the OPK is for when you need to install Windows on a computer that you are selling. The difference is all a licensing thing really. I was using the WAIK until VMux told me I should be using the OPK. Migrating to the OPK was seamless.

http://www.msfn.org/board/Internet-Explorer-8-t113661.html

Are you trying to installing through the website or with the exe? Also do you get an error?

My original question was going to be "how big is your profile" but wasn't sure how roaming profiles work with RDP.

No. You should only compress files that are not used often. The compression only gives you more available disk space. Compressing EXEs and DLLs (especially the Windows, Program Files or Documents and Settings folders) are not recommended and may lead to an unstable system.

I noticed that on some boards, if you disable the AC97 in the BIOS it still sometimes show up in Windows but won't let you install it. I hate integrated sound!

For your desktop's private NIC (the one to connect to your notebook) put the DNS info in there that is on the other NIC. You would probably have less problems if you just bought a router to use.

My friend has a problem with his sidebar also. He runs a widescreen resolution (not sure which one but not 1280x1024 or 1600x1200) and if he loads up a game (typically running 1024x768 or 800x600) when he exits and can see the Desktop again, the Sidebar takes up half the screen! It was quite funny to see it do that.

Wow am I glad I never told Intel I was writing Vista drivers for the IME on their boards that only have XP drivers...

New Diskpart script (revised) select disk 0 clean create part pri size=62220 select part 1 active assign letter=c: format fs=ntfs quick create part ext size=14096 select part 0 create part log size=14096 select part 2 assign letter=d: format fs=fat32 quick exit Revised Cleanup script select disk 0 select part 1 attributes vol set hidden attributes vol set nodefaultdriveletter set id=12 I Was about to attempt a second time imaging but I somehow broke my WIM... looks like I am SOL for the moment. I will get to do more work on it next week when I can do a recapture again. Anyways, I found my ID changing cmd in another thread I made someplace on this forum: http://www.msfn.org/board/Imagex-question-t103807.html

Alright I am manually testing this script and there appear to be some issues with it. 1. It won't let me assign the ID byte when creating the partition. I will instead set the partition ID during the cleanup phase by using 'attributes set id=0x12' instead. 2. When you create an extended partition, the default numbering for it is 0 (zero). 3. I cannot make part 0 active because it says it is not a data volume. HELP: I need to insert the following after creating the extended partition? create partition extended [offset=n] [noerr] I will try it out, or is it recommended to create the logical partition instead of the extended one? Also, obviously my cleanup script needs to be changed from selecting part 2 to part 0.

Because we cannot use RE for XP recovery options, we use another method. This changes the drive ID to x12 instead of x07 so if we are to expect it to match previous computers we shipped out, we need to duplicate it as best as possible. We can already see the current ID with Ghost which shows the C drive to be 7 and the recovery partition to be 12.

I believe all you need to do is run the copype to your destination and just don't do any peimg steps afterwards.

Hey, isn't there a Service Pack requirement to burn CDs in XP? Also, I remember having to install the HiMAT software in order to enable it when I originally set up my computer.

When you are logging on to these other machines, you are using your own creds? Do you get different speed results on different computers at the same site?

Virtualisation Technology is in fact being able to run multiple virtual sessions on the same machine. This will, in effect, all you to run a Windows 95 program IF you happen to have a Windows 95 session running. http://en.wikipedia.org/wiki/Server_virtualization http://en.wikipedia.org/wiki/Hyper-V

Doesn't OfficeReady exhibit this behaviour after 60 days? The Office COA should still work tho.

Currently I am evaluating the use of WDS to deploy images that contain a recovery partition. ATM I am imaging a test machine from which I will be testing out capturing methods, so I wrote up this quick script (yes literally wrote it on a pad of paper) for how I can structure my diskpart scripting during the deploy phase. Please review the following and LMK if you see anything I should revise or be aware of. The Volume IDs are the real ones I need to use. Pre-image Diskpart script: select disk 0 clean create part pri size='62220' id='0x07' select part 1 active assign letter='c:' format fs='ntfs' quick create part ext size='14096' id='0x12' select part 2 active assign letter=d:' format fs='fat32' quick Post-image diskpart script: select disk 0 select part 2 active attributes set hidden attributes set nodefaultdriveletter

Which is it? 0xC000000F or 0xF?

You are kinda all over the place here... These are examples. First image: use /capture image.wim "VistaBusiness" Second image: use /capture image.wim "VistaUltimate" For SP1, deploy image.wim "VistaBusiness", install SP1, /append image.wim "VistaBusiness" LMK if I got this wrong.