MrJinje

The only legal way was downloading them from XBOX 360 LIVE but that link is now saying Content not found. Here is the old link in case it comes back online. http://marketplace.xbox.com/en-US/videos/m...c-58e6e8ab89e2/ Same link from google. http://www.google.com/search?hl=en&q=s...live+uncensored The episodes were about 1GB for HD version. 200 MB for SD quality. Not sure when they went offline, but they were up 2 weeks ago. So maybe is chance to come back online.

Can't seem to find any Linspire laptops anymore, they were about $100 cheaper for the same hardware. So that is about the most you will save. Did find this link with links to plenty of company's who will sell a no-os laptop. http://mcelrath.org/laptops.html

Let's say he manages to get DELL to send him the upgrade DVD. Depending on when the original buyer bought the lappy, he may also need to update his BIOS with the August 28th release. (includes update for Windows 7). Without that BIOS the DELL Windows 7 Upgrade DVD should fail to activate. M4400 Downloads Page BIOS Info Can be checked at boot-up, just hit escape or delete or whatever button DELL uses to enter the BIOS and find out if you already have BIOS version A15. No reason to flash the BIOS if you already have the new stuff. (also if you have A15, we probably owe apology to sleazy internet sales guy)

For Group Policy Settings under the GPEDIT.msc "Administrative Templates" Follow this method 1) Install XP - Customize your gpedit.msc by hand. 2) Copy the contents of this folder into your $OEM$ directory on the DVD. C:\Windows\System32\GroupPolicy XP_ROOT\$OEM$\$$\System32\GroupPolicy 3) Make ISO and test in VM. If done correctly the machine and user policies will be applied before first login. I guess if someone wants to batch script the file copy instead of using the OEM folder that could work too. I prefer OEM folder as is less work. Remember to GPUPDATE /FORCE or REBOOT in your batch script. GPUPDATE /FORCE is not needed for OEM method, as the machine reboots automatically. For Local Security Policies See Post #6

What is *not* there: - any mention of relative or absolute paths - any mention of a difference between CD or RIS installs, setup.exe and winnt32.exe The way I read that, it means if your $OEM$ folder is at D:\$OEM$, you only need to specify "D:" (was not in your list of failed tries) without the "\$OEM$" like thisOemFilesPath=D: or maybe like spoiled said try. OemFilesPath=%source% Your verbiage is misleading. Are you having trouble with a network based RIS install, or are you trying to create a multi-boot DVD. Makes a difference.

Yes, only 5. But a better question might be, is it allowed to use your VLK image to quickly provision those machines with all the company settings. Then follow Microsoft's procedure to manually change keys and re-apply the 10 OEM XP licenses (paid for) back on these machines. Why throw away 5 perfectly good OEM licenses. Or waste time manually doing the company settings, when the key can be changed after the fact. Can anyone confirm or deny if this is a breach of license Think this could only work if the OEM machines are already XP Pro, if they are XP home, this is definitely a no go. I assume it should be allowed as each OEM license is tied to hardware and the hardware isn't being changed, so is not breach of license. Anyone got a different take on that.

He shouldn't be sending you any Product Key, it should be on the bottom of your laptop. What does the COA sticker say, my guess is this guy installed Windows 7 Trial on a Vista machine. It is damned near impossible to change enough hardware to lose OEM activation on a legit laptop. If there is no COA sticker, then it is not a OEM laptop. Can you run this script and tell us the installation date. Any install date within the past two weeks is suspicious.

de nada

Add link to mediafire. No Captcha - No Timer - No bogged down servers with lamers trying to earn pennies for uploading movies. Very fast, reliable.

Yeah missed the edit. If IIS was unchecked in your Windows Features, you are all set.To verify, avoid his "File Sharing" scan and instead run the "All Service Ports" scan (one in the middle), it checks the 1024 known ports and provides color graph, without any biased sounding commentary. Mine only has one red port (#113) and I consider that safe. All other ports appeared in Stealth mode.

Think you are confusing web-browsing with web-hosting. Disabling IIS does not affect browsing or IE or firefox in anyway.No one said disable port 80, the link posted shows how to enable/disable IIS web server via the control panel. EDIT: Unless of course you are running a personal web server and need IIS. Then maybe you shouldn't uninstall it.

Very easy to Enable or Disable IIS Web Server on Windows 7 LAWLS: In case anyone doesn't know the port is 80 although GRC.com does not specify a port on that particular scan, they prefer to ominously mention a Hidden Web Server without giving you any information. IMO just a scare tactic to re-inforce the need for their service. They could at least post a link to IIS or tell people it can be easily disabled via the control panel.

Assuming the files are at C:\I386, the syntax is to place the SourcePath to "C:\". It will then find the I386 directory. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup] "SourcePath"="C:\\"We use a Group Policy to push the I386 from our network, but if that doesn't work for you, you'll have to copy I386 to each machine. I used to have a snip that allowed me to script a INF installation via some dll hook or other convoluted process. If I find it I will post back, that script combined with PSTools or similar, would allow you to re-install all machines from a single batch file.

I would guess that some of your drivers (SMBUS, and your two Drive Controllers) are in INF format. Cannot see in the folders but that was how mine was. You will need to get the rest of your drivers which are hidden inside the EXE another way.Check out DriverMagic or one of the other applications that exports drivers from a live system. Install your EXE onto a machine, and use the export driver button to grab all your drivers at once. Very easy.

PsShutdown can do what you are looking for. Just write a simple batch script that shutdowns each of you machines.

Recently I noticed that the first post is being spawned to all pages now. Wonder why. EDIT: Don't remember changing display option but I must have. Thanks MHz - Thread Locked.

AFAIK the Install_WIM_Tweak.exe is not compatible with DISM and by association not compatible with DISM Tool™. From what I understand the image won't save properly via Commit-WIM so you should probably be using ImageX from Vista SP1 WAIK and gimagex for this.See here for more detail. http://www.msfn.org/board/s-install-wim-tweak-t139371.html

Error87 is usually related to a space in the Install.WIM path. The fix has been to move the files to a space without path or the root of the drive. Error3 is usually reported as dropping off the So in sources during the sendkeys command while using a non-english language pack. Sadly the fix is the same, move the WIM file to the Root of your partition and it should work fine. Source code for this error has been posted earlier, we have not heard any solution for why "So" is only being dropped while running non-english language packs. (however in this case unicode does not seem to be the issue) I would be curious to know if the "So" error goes away after switching locale back to english. and if it returns when going non-english again. Jaclaz, looks good, since my Sapien IDE 45 day trial is long past, it looks like I will be re-writing the whole thing using a real IDE.

Yes, there is a way and AFAIK it is quite similar to Vista. I will wait for word from Management on whether it can be posted in the forum. Delete my thread please if we are not allowed to discuss this.Info

When you try and download only the SP, does it begin to download or does it fail without starting. If it fails without starting might just be a malformed URL.Can you attach the bad file.

I would try SetupComplete.cmd from this folder %WINDIR%\Setup\Scripts\

Not sure that is the right frame either, deleted all four of those from explorer.exe and I still got the Empty frame, (just not my custom user bmp). So I think the resources in explorer.exe are used only for displaying the user bmp inside the frame.and just to be clear, powered down my lappy, pulled the 2.5" SATA and plugged into esata caddy. Took ownership and replaced the explorer.exe from my main rig. Finally replaced HDD in lappy and booted up. On the right path, but still missing something.

Looks like you already deleted the Default user image, and are left with an empty frame at login. Haven't found that empty frame yet, but have only checked a few places (WinLogon.exe, LogonUI.exe, winload.exe, shell32.dll, spwizimg.dll, themeui.dll, ntoskrnl.exe etc.). Best bet is to get PE Explorer and start poking around, there are 11,064 files in my System32 folder, so with the 14 or so that I checked, only 11,050 more to go.Assume the orb is just the standard cursor being shown early during the boot sequence, and it goes unresponsive because the boot sequence has RT or AboveNormal priority. M$ likely displays the cursor early knowing it will do this, just to give indication computer is actually busy. Let me know if you find a way to disable. Here is some other things ran across, an article for login button configuration. And found a way to modify the Text "Hibernating" and "It is now safe to turn off your computer" via the bmp resources #2 and #3 in these files.c:\Windows\System32\ntoskrnl.exe c:\Windows\System32\ntkrnlpa.exe

See here, SetupComplete does have it's disadvantages. But I think these can be fixed with the <CopyProfile> setting via AutoUnattend.xml. Not fully sure, waiting for feedback from another reader.If that don't work, the simple answer is any apps that are user profile specific need to be ran during First Login Commands. ThinApp solves most these issues, so if you can get management to spring for licensing, do it. Most apps can be re-packaged as portable applications very easy.

LOL, can't blame me, I didn't even write that post, If I had written the first post, probably would have attached something like this. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background] "OEMBackground"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System] "UseOEMBackground"=dword:00000001 Attached is a sample setup I used for All Black Background. Unpack RAR, copy folder, follow link, paste folder, and run the reg. Can also integrate into your WIM (use DISM) and add the registry settings using a First Logon Command. BlackBackgroundLogOnScreen.rar