Jito463

Might help if you say what error you're getting.

Or if you could get access to an OPK disc (some places sell them on pricewatch.com) you could do an unnattended network install. Mind you, the OPK is explicitly for OEM system builders, so I don't know of the legalities involved in a non-system builder using it.

I believe what he's trying to say is that after installing Windows, but before logging in, he has some automated installs going and the computer goes into hibernate during their install. Not during the install of Windows itself.

Click the Language Bar under Toolbars to disable it. I think that's the culprit.

The SIF file it's referring to is your txtsetup.sif, not winnt.sif. You can post that here if you're still having problems after trying the above suggestions.

Somehow I don't see that happening anytime soon. Not because it's impossible (though it may very well be), just because I don't think MS wants people with 32-bit PC's able to run 64-bit Windows, even if there's a performance hit from the emulation.

To be honest, I haven't used a registry cleaner in about 2 years. At one time I recommended them, but not anymore. I've seen a few issues arise from various different regcleaners with certain software programs. For example, we had a customer recently on the Alcohol forums who could not install or uninstall Alcohol, but only after running the JV16 Power Tools. He verified that was the problem by restoring a backup from before he ran JV16 and after, and each time he couldn't get Alcohol to install/uninstall properly after using it. I used to use the JV16 RegCleaner all the time back in the day, but this just goes to show how even a good program can cause problems.

Just went through all the trouble of making a screenshot so I can post it here, and here you are already working on it. Curse you and your speedy responses

Right-click in the blank space and choose "Close Toolbar" from the context menu.

When you tested loading Word up with and without the memory controller, did you flush the prefetch each time? Otherwise, after it loads into prefetch that would affect your results and cause the program to load up faster.

I would have to also agree that Windows is the more user-friendly OS. I consider myself a bit of a geek. My second computer was a 486 DX-2/66 with MS-DOS 6.22 (my first being a Commodore Amiga 2000), and it's safe to say I know my way around DOS. Having said that, using Linux is a completely different beast. I've played with a few distros, but in the end I always come back to Windows. Of course, I'd say the biggest reason being that I love playing games on my PC, and games support for Linux is far inferior to that of Windows. I've run Win3.11, Win95a/95b, Win98se, WinME (it was free from MS, so sue me), Win2k (RC2 - SP4), WinXP (RC1-SP2) and now WinXP x64 (RC1-RTM). Even played some with NT4, but never ran it for myself. There's been issues and problems with all of them, sure. But Windows has improved greatly over time and I'm happy with Windows on my PC.

I'm not really sure if you're saying you like the pope or not, but either way this really isn't the forum for such discussions. You should use PM or start a topic in someplace like the Spam forum. Mind you I'm not a mod and am not pretending to be, but I'm pretty sure that's what the mods would say. Besides, look at his sig. Get Internet Explorer? Obviously he doesn't have much of a clue to begin with.

Actually, it's the P4's that are the hot beast atm. AMD64's run very cool comparitively. Admittedly AMD processors ran hotter at one time (anyone remember the 1.4GHz Thunderbird?), but that was then and this is now.

They don't use VLK's. They use a pre-activated key that's tied to the hardware (BIOS). If you were to use that key on another PC, it would: A) Require you to activate the PC and B) Not activate because the hardware is not the same as the one that key is linked to *EDIT* I always forget the smileys...

Well, I don't know if this would work, but it's worth a shot. Just use the multi-boot guide from http://flyakite.msfnhosting.com and use the instructions for XP Professional (using the boot files you've already got) to launch UBCD just like you would any other Windows setup. Though you'll also need to copy the winbom.ini to the root of your disc. I've got my doubts it will work, but you can give it a try. I've never used UBCD so I have no way of testing it myself.

So, let me clarify something. In order to add a new program to the computer, you can't simply tell IE to allow it you have to disable IE complete. Is that not correct? This is what I'm referring to by it not replacing AV. If someone turns off IE and installs a program that turns out to contain a virus, when you turn IE back on, the virus is already there. And since it was installed while your program was disabled, it's now considered a part of the safe list and allowed to run. At least with traditional AV, even if the virus gets in you can still turn the AV back on and run a scan to remove it. Your program doesn't do that. Tell me where in your statements you said your program will remove existing viruses. This is exactly what I mean when I say it may complement traditional AV but will never replace it. The only place I can see this completely replacing AV is in locations where new programs are not regularly installed such as a business environment, but not your average home user.

You need to make sure the following files are located in the root of the CD/DVD: Win2000 Pro: CDROM_IP.5 CDROM_NT.5 CDROMSP?.TST You could have multiple versions of the CDROMSP?.TST file, depending on what service pack it came with by default. For example, CDROMSP1.TST, CDROMSP2.TST, etc. They all have to be on the root of the disc. You could also try reading the guide from the link below. It will explain what files are needed on the root of the disc. http://flyakite.msfnhosting.com/

Oops, meh bad. You're right.

Did you make sure you downloaded the x64 specific versions of the files?

It allows you to share your drives (CD/DVD-ROM/RW) over the network so another computer can use them as if they were local to that PC.

Any app that worked under XP will work under XP x64. It's only drivers or applications that rely on drivers (such as Alcohol and Daemon Tools) that will not work without a specific x64 compatible version.

Yeah, that was some time ago. In fact, Service Pack 1a (as opposed to SP1) for XP was released for the sole intention of removing MS Java due to the lawsuit slapped on them.

I feel like we're going around in circles again...

You won't be able to integrate XP x64 or 2003 Server just yet. Read the link below for more details. http://www.msfn.org/board/index.php?showtopic=47226

Winnt.sif is *ONLY* for preinstalling or unattended setups. Upgrades cannot by done by winnt.sif.