S.SubZero

I don't think there is a single disk of any size possible that can hold ALL POSSIBLE software for Windows. You're talking hundreds of thousands of applications.

CompUSA was an anchor store at the local shopping plaza where I lived in New Jersey. What I remember from going there over the years from 1998-2005: - WE OPEN AT 9AM. NOT 8:57AM. 9AM. (this was on a brutal cold Saturday morning) - Their gaming section was decrepit and neglected. I mean dirty, old torn boxes, etc. It was disgusting. - Any demo input devices (keyboards, mice, controllers) were usually broken and horribly outdated - They never got any latest title sooner than a month after it came out - Typical clueless sales staff - They sold like two Lian-Li cases. Every other case, and every other accessory, was no-name generic stuff - They had dirt cheap and reliable CompUSA branded blank CDs. I think I still have some somewhere. When Best Buy opened midway between this CompUSA and another a few miles down the road, it pretty much destroyed all of their business. For anyone who has never been to a Fry's, you want to make an effort when visiting anywhere that has one to check it out. They are CompUSA on steroids. You can buy a computer, a stereo, a refrigerator, a stove, and Transformers toys all at one place. Oh and the one by me has a cafe in the middle, so I can do all this AND get a bite to eat, without leaving the store.

Which virtualization software you use depends on which OSs you want as hosts and guests, since some work better than others. VMWare are the only ones with software that can support 64-bit guests. For testing an XP64 slipstream I made with nLite, this was very handy. XP64 ran slow in VMWare Server, but for just testing the installation it worked. Speaking of which, VMWare doesn't like Vista x64 host at all, since none of it's drivers are signed. Getting it to run on Vista x64 is clumsy and very unprofessional (F8 every boot). VPC2007 is only for Windows, and only officially supports 32-bit Windows guests and OS/2. I tried it for OS/2 and it ran but some aspects seem slow, probably due to the very low PC specs it virtualizes. Virtualbox is for Window, Linux, and Mac hosts. It support many guest OSs. It's a little flaky, my Vista x64 host seems to blue screen if I really stress the virtual machine (again, OS/2). The latest version is also practically unusable for me. However it runs fast and has an extensive community. I wanted to try Parallels, but they still make people pay for even the basic software.

FYI - This is a hardware limitation. Every OS on x86 has this issue, even Linux. They just do a better job of hiding it. http://www.spack.org/wiki/LinuxRamLimits The decision for workstation-grade Windows to not do PAE was probably a good idea. PAE is not foolproof and has its own limitations. It is better to lean everyone towards x64 rather than try to kludge fake 4GB+ support.

Very relevant, accurate, timely information. Guys I hear Vista is going to make our MP3s stop working too.

The Spike energy drink I take on workout days, which has 0 calories, 0 carbs, and 0 sugar: Per 8.4oz can: 300mg caffeine

I did another image without the hotfix and that install did not have the error. Yay!

Hmm.. I used to support a corporate Token Ring network ~12 years ago and while the hardware was kind of weird, it was very reliable and network performance was exceptional compared to ethernet of the time. I think one good thing about it was that it didn't suffer from performance problems as network traffic increased, since the "token" was always the only thing on the network, and it stopped at every workstation regardless. I can't see any real use for it today though, as Ethernet has evolved to a point where it can be used in any situation where Token Ring might have been beneficial long ago. The only companies using it probably have big infrastructures that would be prohibitive to convert to Ethernet. Madge, the company that today makes most Token Ring hardware, is still in business, so they must still have customers.

I used nLite to make the image. I don't know if nLite does anything weird. The only options I chose were to slipstream SP2 and add the one hotfix. I didn't change any options or remove anything or anything else. The only reason I used nLite was to make the bootable ISO quickly. I may make another ISO without the hotfix to see if that is the problem. It's the timezone fix, I just wanted that stock on the install but I could live without it.

I'm tinkering with VMWare Server 1.0.4, specifically for testing my XP64 SP2 slipstreamed disc I made. I also added a single hotfix to the slipstream, KB931836. The install of XP64 as the guest OS goes just fine, no errors at all. However, the Event Viewer says there were non-fatal errors during install. The setuperr.log file shows: "The digital signature file D:\AMD64\SP2.CAT could not be installed. The error code is fffffc05. The system cannot find message text for message number 0xfffffc05 in the message file for syssetup.dll." This same error is repeated a few times, but the file in question changes to NTPRINT.CAT, NT5IIS.CAT, WOW64.CAT, and WOWLANG.CAT. I don't know what these files are nor how critical they are. The virtual XP64 install seems to work fine, though I haven't done much with it. Should I take these errors seriously? Would running in a VM cause them?

If I browse with IE7, and I hit pretty much any web site with banners or whatever ads, these ad sites get individually added to my browsing history. This means if I hit the 'back' button, instead of going to the page I was just on, it tries to load up another ad. I have a hosts file that sends a bunch of ad-centric domains to 127.0.0.1, which makes the ad not show up, but instead I have to hit the 'back' button multiple times to actually go back just one page. This is a problem with some pages that load several ads, and they ALL go to the history. Is there any convenient way to make this *not* happen? Firefox does not do this at all, it's 100% reliable with knowing what the previous page actually was.

If a game doesn't directly support dual core then it won't get any benefit from it.

I can't understand the problem at all. You have XP64 on hard disk? Is it installed already? If your XP64 is not legitimate, you will not get any help here.

You have to read up on your specific brand. I know with my Netgear stuff I can technically set up multiple WAPs and they will all talk together, but I have never tried it. I know one thing they CANNOT do it link two wired networks over wireless. Like I can't have a WAP complementing a wired network, and another WAP complementing another wired network, and have the two wired networks integrate. It's odd that they can't do this (and it cost me $200 to find this out.. grr).

It was definitely a kid's movie and definitely corny. You are correct in your badass observation though. Every movie needs more evil Mustangs. Every movie.

Neither nVidia nor ATI officially support their laptop chipsets with the drivers on their website. It's typically just a hacked .inf file with the relevant hardware detection to get it working. I suggest rage3d.com for assistance.

More detailed answer: QoS is Quality of Service. It's a special priority Windows Vista (and XP) can give to specific traffic. In order for this to work, the application generating the traffic must support QoS. If it doesn't, it can't request the QoS reservation of bandwidth. Long story short - Unless an application is designed *specifically* to reserve QoS bandwidth AND needs it, there is no "20% reserve". I think the only app that comes with Windows that can do this is Windows Update, and I'm not even sure on that. You're not losing any bandwidth having this enabled.

Check the website of the company that makes the server?

The CDs are certainly not individually keyed at Microsoft. Every XP64 disk that comes off the retail line is exactly the same. Every XP64 disk that comes off the VLK line is exactly the same. If someone slipstreams a disk and adds the key themselves to the image, that's a different story.

I stole a bunch of letters out of your topic title, if that counts for anything.

So ya know, MS does not put the cd key on the disc. If you have lost your key and do not have XP64 installed with that key already, there is no way to get it back. You would need to get a new key, which will probably involve buying another copy of XP64. Do not lose your key.

What version of textpad are you using? According to their site they have had "Vista 64" compatiblity since 5.0. There also seems to be a 64-bit shell extension. Maybe it will work with XP64. If you own textpad, ask the taskpad people. 8)

You mean sorta like how you're asking this kind of question and your name is "geniusguy"? 8P Really, this is not a good idea at all. If you don't damage the BIOS utterly, you will cause all kinds of stability and compatibility issues. This is one of those things you just don't do.

Since I don't see any way to fix this association problem, the codecs don't do me any good. I mean it's nice you're informing people about the association but you may want to include a "I don't know how to fix it" or "here's how to fix it.." thing because just telling me the reason isn't providing any solution.

Unless the process has changed, then it won't, since I tried it already. In fact I posted in that thread about it.