cluberti

Yes, 2003 x86 and XP x86 are basically the same, and 2003 x64 and XP x64 are basically the same, but 2003 x86 and XP x86 are really not like 2003 x64 nor XP x64, therefore a product working on the XP x86 version isn't guaranteed to work on the x64 version of XP - although they have the same product name, they are not alike. Sorry, I'm not aware of an application or shim that hides the fact that the OS would be XP x64 from an installer. Perhaps you should be asking this in the Application Installs forum; moving there.

Obviously not. Why not try it and see what happens? You could post back with your tests and results.

If you were to run process monitor on a machine you'd see winlogon opening handles on user logon to those locations - it's built into winlogon to use wininet for network communications. The only thing that'd break if you replaced winlogon with one that didn't ingest wininet was that you would be unable to logon anywhere but locally (no domain logons). Note that the requirement for wininet isn't in a reginst section, it's actually a static link in the winlogon code loaded when winlogon.exe starts, so you'd have to rewrite winlogon and replace with your own.

What was the blue screen error you received (specifically)?

If he owns a vista license it's not warez no matter where he gets the actual installation media from. This has been argued OVER AND OVER AND OVER AGAIN! ANY source but MS or an official distributer is illegal, even if it is only a OS disk! Thats like saying "I still have my keys from that Jaguar I wrecked, maybe I'll just go use his." It's people like you and attitudes like yours that is the reason the vLite and nLite are so close to being shut down... I'm sorry but you're just an id***. Warned for violation of rule 7, both parts. Also, Microsoft *does not* permit redistribution of their code, compiled or otherwise (ask the autopatcher folks what happened to them when they redistributed PUBLIC hotfixes). So, Kels is correct, it *is* actually "illegal" in most counties to get your Windows source from anyone other than Microsoft or an authorized distributor. Regardless of how you feel about it, it doesn't change the fact that getting a Vista ISO from, say, a torrent is not a legal way to acquire media. Noting you post from the US, assuming you're a resident, it is illegal in your country of origin to do such a thing, for what it's worth.Visit the Microsoft piracy pages if you want more information on how Microsoft feels about unauthorized copies of Microsoft software. Again, I'm not saying don't use torrents, etc, as I can't police the internet (nor would I want to), but I am saying that treating it like it's legal seems like an effort to convince yourself that what you're doing isn't wrong, rather than basing your opinion on reality (Microsoft cracks down on unauthorized distributors all the time).

How would it be damaging to their sales? That's like saying people buying XP downgrades from Vista is somehow cutting into sales - you still bought a copy of Windows, Microsoft still got paid. The reason they don't like it is because you're removing binaries that contain exported APIs that other apps or even Windows components may rely on. If they're not there, things may not work. I'm sure it's because they want to reduce support costs (customers calling Microsoft because <insert product or API call here> doesn't work, when the reason it doesn't work is because something was permanently removed via xLite).

It might be easier to reverse-integrate SP1 on a runniing Vista RTM VM and then sysprep it and imagex /capture it, if vLite gives you too much trouble.

Windows 7 and Windows Vista share the same kernel and driver architecture, so working on Win7 when a product supports Vista is expected. However, XP x64 is *not* the same as XP x86, in fact it's Server 2003 (and the 64bit variant) - also, XP x64 is *not* like Vista x64 or the x86 XP. You can be fairly certain the product doesn't work on XP x64 because they didn't want to spend the development time to make it work, as it has a different kernel and architecture than the other products they do support. Even if you were somehow to get it to work, the networking and security APIs are different between XP x64 and Vista, so it's likely a lot of the features wouldn't work either. Also, Norton 360 v1.0 and v2.0 are *not* built on Norton Internet Security, they were their own product codebase with features actually ported over to the Genesis codebase (1.0 took features from NIS 2007, 2.0 took from NIS 2008). N360 v3.0 however is the same codebase as NIS 2009, but that's because NIS 2009 was built from the Genesis codebase and the old NIS code is basically dead. If you want to keep bashing your head against the brick wall that is N360 on XP x64, I wish you luck. Hopefully you're just doing this as an experiment, because otherwise I would strongly recommend considering products other than Symantec/Norton anyway, just from a product quality standpoint.

http://shop.symantecstore.com/DRHM/servlet...;ThemeID=106300 It's technically only a 32-bit product even if it installs on x64 Vista, as certain features are 32bit only. They (Symantec) didn't make a 64bit version until 3.0 - there's no conspiracy, so take off your tinfoil hat. If anything, blame the vendor for releasing a product in 2008 without any x64 OS support. From the 2.0 page linked above: System Requirements * Operating system: Windows® XP Home/XP Pro/XP Media Center Service Pack 2 or later, Windows Vista®** Home Basic/Home Premium/Ultimate/Business/Starter Edition * Phishing Protection feature requires Microsoft® Internet Explorer® version 6.0 or later or Firefox® version 2.0 or later * Email scanning supported for POP3-compatible email clients * Online backup feature requires high-speed Internet connection Hardware Requirements * 300MHz or faster processor * 256MB of RAM minimum * 300MB of available hard disk space Required for All Installations * Standard Web browser * DVD-ROM or CD-ROM drive * Internet connection **Additional Windows Vista Requirements * Must meet minimum Windows Vista operating system requirements * Phishing protection feature available only on 32 bit Explorer Also, to tack on some more bad news, if you're going to run XP x64 you're going to have to find a different antivirus product, because no version of Norton 360 supports x64 XP - Norton 360 v3.0 only runs on x86 XP or Vista or x64 Vista (not x64 XP or 2003).

Wininet creates and opens a handle to these files on logon (it hosts wininet.dll, causing the files to be created). I don't think you can avoid this without replacing winlogon.exe with a hacked version, which I wouldn't recommend.

I see this one around work quite often, especially amongst the travelers. Supposedly a very good bag.

Netstumbler is a good tool for this as well.

Why do it the hard way when you could do it the easy way?

That's ok. Again, though, there are holes in your argument - you don't get those parts for free, and Microsoft *still* creates patches for NT4 for customers who want to pay (the exhorbitant prices, now) for it. Ultimately, as a company that sells software, keeping people on staff (both at the dev level and the support level) to handle code that is 10, 15, even 20 years old just isn't practical for the amount of revenue it would bring in versus the cost to keep the software up and maintained. Business as a public company being as it is, Microsoft needs to continue to sell software and services that people want to buy to keep the shareholders happy, and although Vista (thanks to it's poor performance and driver support pre-SP1) was an abject failure in the marketplace, the code itself is not - and I think Windows 7 sales figures and corporate adoption over the next 3 years will bear that out.

The only flaw in your argument is piracy. It'd be like GM providing the regular maintenance for it's vehicles for free, but half the people who use GMs cars actually didn't pay them for it, but still expect GM to service the vehicle's systems for free (and some people, forever rather than have an end of life date where you're expected to move up to something newer after 10 years).Microsoft does it to try and get money from people who use their software - is it the best method? I don't know, sincerely. But it is a method, and if it didn't work they very likely wouldn't be spending the money to maintain and develop that codebase and the servers hosting the service. Car analogies rarely work when compared to the software industry.

Depends on how your fianceee "downgraded' your box to XP. Usually the factory restore options are stored on a partition on the hard disk, if you didn't get a physical Vista DVD (which it sounds like you didn't). If she didn't whack the restore partition, you should be good to go. However, if she did, your only recourse is to either find a way to get a copy of a Vista DVD that has Home Premium, or contact Gateway for media. Obviously getting the media from Gateway would be preferred, as it probably is OEM preactivated, but it's not a requirement if you have a valid Home Premium key to use.

Well, you really should have some development skills in the language(s) used in the apps you're debugging first (otherwise you are likely not to understand how the app works, therefore you'll have a hard time spotting 'non-working' behavior), in this case it's Windows so C and C++. Next, you'll need to actually study the debugger help (there's documentation in the actual windbg help files, installed with the debugging tools for windows package), and it also helps to read some books and do some debugging on your own. Debugging is more art than science too, so keep that in mind - experience is the best teacher.

Good. Let us know how it goes.

Does the whole UI hang, including explorer? Or just open applications?

ISP or DNS, depending on the failure.

http://www.microsoft.com/windowsserver2008...pare-specs.aspxAlso, it's worth noting that Windows Server 2008 R2 will support up to 256 logical processors on the higher-end versions, up from 64 for x64 2008 server.

Works here as well from 7100 x86 or x64, both IE8 and FF3 on these two VMs.

If you aren't afraid of a VM and making a WinPE disc, it's pretty easy to do it. First, you'll need the Vista SP1 AIK, the SP2 installation media, and a VM with a 40GB hard disk (Hyper-v, Virtual PC, VMWare, etc - doesn't matter how you do it). There's a post with pictures here by a user named "bjfrog" that shows you how to do it. Once you've got the install.wim with SP2, extract your Vista DVD to a folder on your machine, replace the \sources\install.wim with the new SP2 install.wim, and use oscdimg to make a new ISO you can then burn.

In fact, I was able to get my 64GB key working! I had to use the HP USB key format utility to format it NTFS first, then I used diskpart to set the partition active, copied the files (I have a WIM file with all the Vista, 2008, and Win7 versions I have to install as one install.wim on a Win7 install ISO I'm using on the key now), and then after running bootsect it works. To verify, I used the diskpart method entirely to create partitions and format, and it *didn't work* for whatever reason. Perhaps there's something specific with this Patriot USB key that required the hackery, or perhaps not, but it's working now. I have an ~10GB WIM on the key and it installs everything properly, so it can be done.