cluberti

Well true - but NO *required* updates are protected by WGA. If the update requires a WGA check, it's likely a tool or optional update, and as such you should have an OS that's legit. However, MrJinje is correct - the WGA check on *almost all* packages is only for the download itself - there are only a select few packages that will actually do the WGA check when running (like Microsoft Security Essentials, for instance) that would fail. I would, however, strongly encourage of course the continued education of your users (I assume this is a repair-type CD you're talking about, given the language of the original post) that using a legitimate copy of Windows is good for them in the long run, for situations just like this. There's no 100% guarantee Microsoft will continue to cater to pirates, and if that stops happening people with pirated installations (intentional or just a victim of a scam) will all be in a pretty bad place.

I answered your question here, and apparently you're asking a similar, perhaps the same, question. You've not heeded my warning to start assisting others here and not be a leech, so I'm banning you under rule 4.c. [banned].

Don't you find that for the past few years, that many web pages don't render properly (or even satisfactorily) with IE6 on win-98? That's my observation. I started running FireFox on my win-98 systems a few years ago exactly for that reason. And I don't think this entire thread has satisfactorily answered the question regarding IE integration into the "guts" of any given windows version (be it 98, XP, etc) and the vulnerabilities that flow from that integration. (there are those that believe that IE6 was not properly "ported" to win-98. They point to unresoved dependencies in Dependency Walker as their main evidence) Any app backported from a newer OS to an older one will have this issue, especially when we're talking about packages built from an NT-based OS tree and backported to Win9x, like versions of IE or media player. The lack of unresolved dependencies of course means little if other binaries have code to handle the expected failure. I do remember a thread on this in the past, here, that you were involved in. I never saw any further information from your source either .

No desktop-licensed OS does, but every server OS since NT4 Terminal Server edition has had at least a "remote administration" mode that allows 2 remote admin users at a time. It requires a full Terminal Services configuration and licenses to get more than that, though.

I've also seen remote differential compression cause this exact behavior with external drives - it's a feature you can disable from the "Turn Windows features on or off" option under Programs in the Control Panel.

Considering 2008 is the same as Vista SP1 and 2008 R2 is the same as 7 (and in fact, even with the Desktop Experience feature installed for both, it's actually not a 100% feature-complete implementation of the same shell), I'd say yes.

Considering Microsoft says it works fine on Win7 32 and 64bit, probably not.

Yeah, not sure exactly what you mean. Netsh can set network configuration settings, but netsh can't do anything for a domain or computer name. Maybe you're talking about IPs and Firewall/location settings? If you could be a little more clear in what you're trying to achieve, we can try to help.

Agreed - without the BSOD info (at the very least) we won't be able to do much more than you are doing - guessing .

If they're doing the install and testing and warrantying the work, it's not ridiculous. If they're just selling sticks on the shelf at that price with no value-add or additional warranty, then yes that is highway robbery.

Or paying to shoehorn the old NT 2D subsystem into the new DWM cost too much to be considered fiscally feasible. Laziness usually isn't the answer, driving costs down and keeping revenue up for shareholders in a public company usually means decisions like this come down to cost rather than laziness.

Moving from the Win7 forum to the vLite forum as per the big red bolded text right above where you posted: "If you have questions about customizing Windows 7 that are vLite-specific, please post them in the vLite forum, not here."

Not a problem. I find it best to type up my post in notepad, and then pick out the key words and search on those - the post never gets posted, but it does give me the keywords I may need to find something if it exists here. And, on the off chance I don't find anything useful, I just paste my post into a new post window in the browser.

It likely has to do with creating the new .msp answer file with the same name as the old. Try something not named admin.msp (make it descriptive if you want, but avoid using common names like "unattend.msp" or "admin.msp", etc, and start from scratch with setup.exe /admin (don't load an existing file, create a new one). Clean the updates dir of all answer files, then save your new one there. Put SP2 and any post-SP2 updates you need in the folder, and it should work as long as you don't automate anything other than the product key. The only reason a setup should fully automate is if you told it to - none of the Microsoft service packs or update packages include automation either, they're driven solely by the Office 2007 setup. It's possible that the admin.msp file was simply corrupted in some way, or you chose a set of options that caused automation. If done properly, there should be no need for creating an SFX or anything of that nature, just use the Updates folder and a new, descriptively-named .msp file without automation and you should be quite fine.

All of those questions have been discussed, either in the Unattended Win7 section or here. Do a quick search for each, and you'll likely find your answers.

This was discussed as recently as 2 weeks ago, here. Basically, it's a bug, and there are workarounds.

HFSLIP is licensed under the Attribution-NonCommercial-ShareAlike 3.0 Unported Creative Commons license. That means you can freely re-share or adapt the work, but you are NOT allowed to use the work for any commercial purposes - that includes use in an environment supporting a commercial endeavor, even if money does not directly change hands in direct response to use of the work. For example, use it in a work environment, even behind the scenes, is disallowed. Given you're operating as an employee or officer of a commercial computer shop, using HFSLIP for repair (for profit or pro bono) of a computer as said employee of said business would fall under this licensing restriction, given that a customer has given you the machine to repair, under the auspices that you're a computer or software repair shop (or both) - this constitutes commercial use. It's spelled out very clearly in plain English here, and the full text is in the .rtf with the product, but also available online here. Also, only the copyright holder of the product that is licensed under this agreement (in this case, tommyp) can absolve you of these terms, and I think it's clear you are not absolved. Lastly, HFSLIP was never meant for this use, so attempting to use it for this even in a non-commercial setting is probably caveat emptor, and no guarantees are made for HFSLIP's fitness for this purpose. If you're doing a lot of repair installations, this probably is not the best option anyway. It would probably be better for you to create a repair installation disc using Microsoft methods, and installing apps and such afterwards manually. I know it's a pain, but using an HFSLIP source to repair a computer in this state with anything other than the default app load the OS would normally have is probably a worse cure than the disease. In short, good luck on your endeavors, but I must strongly suggest that you stop using HFSLIP for your business, and refrain from asking HFSLIP questions here regarding your business. Usage of HFSLIP in a commercial, non-personal-use setting violates the license agreement, and in following board rules (1.d specifically), thread closed and warning issued. Further violation will result in a ban. [Closed].

I don't know if you can or cannot add a key to that list, but I've not tried - the UI has always worked properly for me. Also, those keys are there for the ISearchCrawlScopeManager API, so I'm not sure modifying it directly is a good idea. There does exist a set of group policies (local or otherwise) that you can configure under Computer Configuration > Administrative Templates > Windows Components > Search that allow you to set the default indexed paths, excluded paths, etc.

Nirvana - You know you're right

I'm assuming the ISO you have works fine in other VMs (you've tested), but not Virtual Box, correct? Also, I've only really ever seen this when someone takes a VHD with a Windows OS already installed from, say, Virtual PC or Hyper-V, and tries to get it to boot in Virtual Box (it won't until you uninstall the additions in those cases).

Please search before posting. This is a constant theme with you - you have been warned.

http://lmgtfy.com/?q=add+folder+to+windows+search Please search before posting. This is your last warning.

Most of the problem with POP mail gadgets is that people forget that hotmail/live mail do NOT use the standard 110 port - it uses port 995 with SSL encryption. Also, since it requires SMTP auth, unless you find a gadget that does SMTP auth before attempting the POP3 connection, none are going to work.

If you're deploying software to a machine and don't want the user to have interaction with it, you're better off using audit mode and having the software install at that point before the user gets the machine. You can use RunOnce in Windows 7, but if the software requires the admin to do the installs and the user is at the machine at that time already, there's not a whole lot you can do (due to the way Vista/Win7 is designed, it's not quite like XP and it's not as foolproof, especially if the user has any sorts of admin privileges on the box). You could also consider preinstalling the apps into your WIM file that you're deploying as well, or using something else for deployment like SCCM which allows for zero-touch installations.

I would suggest using the WAIK 2.0 to do the export of both the Vista Ultimate and Win7 Ultimate images to a new .wim file, then use a Win7 x86 source as the host for the new install.wim. This was asked here a short while back already.